Just a word of warning, concerning the latest Oram update.
I updated about a half hour ago, and my fully functional Pi-5 with Oram and HDMI touchscreen stopped working completely.
This is the sequence of the rather worrying events:
After updating, Z showed at reboot the midi-audio input/output red error.
Hard reboot and Z started up.
I attempted a further reboot from admin, in order to possibly clean the registries: Z remained stuck with the admin screen visible and no active controls.
I connected with the Z through webconf, and noticed that overclock had been disabled. Everything else looked nominal.
I therefore restated maximum overclocking and triggered a reboot from webconf, only to have the Z remain idle and switched off.
Now my Pi5 seems pretty dead, and refuses even to start, with the power LED neither green nor red. Totally unresponsive and silent, even if I disconnect it from anything except the USB power supply.
I wonder what may have gone wrong with the update. I really would hate to redo the whole run of the nvme installation from scratch…
Now at least the Pi5 board starts, once I have also removed the Midi OTG Y cable, but it is set to start from Oram on nvme, and remains stuck in an endless startup loop.
How do I possibly force a reboot, using some keyboard shortcut on a connected USB qwerty, from the Raspberry OS on SD instead?
And, once there, what [sudo apt] command should I invoke, in order to recover the Pi5 firmware? Maybe [sudo raspi-config]?
Edit: [shift key at startup does not lead me to anywhere useful, for temporarily changing the boot order as SD - nvme, which I will set anyway in the end, once I will have hacked my Neo 5 case with an SD extender]
sorry to bother you with this specific request, but I am really stuck with my Pi5 Oram (latest as of yesterday morning).
I would need to be directed at a procedure for recovering the firmware of my Pi5, without completely dismantling my Argon Neo 5 kit, to extract the nvme drive containing the Zynthian OS.
I can instead access the SD card with a manageable amount of tinkering.
I guess the problem is finding an external process at startup, with arguably some kind of qwerty shortcut, in order to force the Z to boot from Raspberry OS on SD.
I would really appreciate some kind of solution. Thank you!
I remember indeed your thoughtful recommendation, for setting up a recovery option with an SD-nvme boot order, which I missed to configure, trusting maybe the testing branch a bit too much.
Providing that I decide to embark in the dismembering of my Pi5 setup, to get hold of the nvme and disconnect it, what would be the required EEPROM recovery procedure?
I was finally able to run again Oram on Pi5 with nvme.
I adhered more or less to the process explained by @riban, in the thread on Oram Pi5+nvme, except for the part about downloading through SSH, unzipping and transferring to SSD the Zynthian OS, directly from CLI in root@zynthian (which happened not to be performable on my external computers, due to apparent local net issues).
I flashed instead Oram to nvme using Pi Imager, and the rest of the procedure turned out to be pretty functional.
Reconfiguring the graphic UI with my custom color scheme, uploading a few saved snapshots, transferring some added soundfont libraries and registering Pianoteq required a bit of further work, but in the end gave me a working Pi 5 Zynthian with approximately the same configuration and setup as before.
It was crucial to identify once and for all the right cmdline.txt to check, for correct mass storage pointing, as the one located in root/dev/media.
I will write on a separate thread a simplified procedure for Oram installation on Pi5 with nvme, both as a personal reminder and as a documentation resource for the forum and the Zynthian community.
,