Manual

Info assembled from inclusions from other pages so that its always updated. Mostly Hw and Sw categories. For example assembly/disassembly from repairs. Screenshots of every installed app.

Pyra images

https://packages.pyra-handheld.com/images/

• buster is the "current" OS, though it is outdated. bookworm is newer and is being actively worked on, but there are things that are broken still (from a pure usability standpoint, it works fine).
• Images with "install" in the name will automatically flash the system to emmc, erasing anything that was on it previously in the process.
• Images that do not have "install" in the file name can run directly from the SD card that you write them to, leaving emmc untouched.

Reflashing a Pyra

Sometimes you've played with your pyra so much that you need to start again. With a spare SD card, we have you covered.

1. Grab the latest image with install in its name from https://packages.pyra-handheld.com/images/buster/
2. Extract that 7z file to get an .img file
3. Write that image file to an SD card with something like etcher. This will erase everything on the SD card
4. Insert SD card into Pyra left SD card slot
5. Power on, and it should start flashing. This will erase everything on the internal drive of the Pyra

From there, power off when it tells you, eject the SD card, power back on, and you should get to the first-run setup stuff.

On extending the F2FS root partition of the Pyra-bootable SD card

Creating a bootable SD card with a img without "install" in the filename for the Pyra does not make use of the entire SD card if you have something larger than 4.3ish GB. Extending the F2FS partition using gparted/parted breaks the bootloader somewhere, but extending using fdisk works. All of this can be done on the Pyra if you boot from eMMC. There is a report of a Pyra freezing at or after the fsck.f2fs step, so that person had to do it on another machine.

1. Grab the latest image without install in the name, e.g. pyra-40.img.7z. Insert your sdcard.
2. Write the image to the sdcard, something like (as superuser or with added sudo in the pipe for dd device access) 7z x -so pyra-40.img.7z pyra-40.img | dd of=/dev/mmcblk3 bs=1M. Make sure you are writing to the correct device, at least take a glance with sudo fdisk -l
3. Once image writing is done, sudo fdisk /dev/mmcblk3 to begin the fdisk process. we're going to tell fdisk to delete a partition and make a new one with the larger size, but keeping the signature so we're really just resizing.
4. In this fdisk prompt:
   • d to delete a partition
   • 2 to hit the f2fs partition
   • n to create a "new" partition
   • p for primary
   • 2 to match the number of the deleted partition
   • Enter to take the default first sector
   • Enter to take the default last sector (largest possible partition).
   • n for "no" and hit enter to retain the original signature of your partition from before.
   • w to write all the changes.
5. sudo fsck.f2fs /dev/mmcblk3p2 just to be sure?
6. sudo resize.f2fs /dev/mmcblk3p2 to resize filesystem to partition size
7. reboot your pyra and it should get to the firstboot wizard, booting off of your left sdcard.

Note: This manual resizing won't be required once the image has resizing put into the firstboot process somewhere. There is a test image that has automatic resizing of the f2fs partition (though with mixed results on a small sample size of usage)

Testing keyboard/buttons/nubs

The input tester accesses the hardware directly and therefore conflicts with funkey monkey. To use it, you must stop funkey monkey temporarily (systemctl stop pyra-input afair)