Ok. Have removed that jumper. I then applied power to the IO board USB C. The red light came on briefly and then the D2 green light started flashing 3 times slowly, once fast and then off for 3 secs before repeating the cycle. This just carries on with no signal to the HDMI monitor and no other apparent activity on the IO board / CM5. The latter is starting to get slightly warm.
I must be missing something really silly here, but it’s driving me mad. What to do?
Can you not update the eeprom from the diagnostics mode with RPI boot? I seem to be stuck with no obvious route forward
take the sd out and flash it on another computer. if that doesn’t work use rpi-imager to flash a sd card with the bootloader stuff and boot that. then try the os again.
Does the uConsole image boot properly in an RPi IO board?
I would use a standard RPi image downloaded with Imager to flash for the IO board.
Make sure the CM module is turned the correct way and that both connectors are seated properly. Since your CM4 works I’d guess you are doing this properly, but worth checking.
I have flashed directly multiple times using RPI imager to MicroSD reader on PC. The image used (your one) to run the CM4 worked fine that way, so imaging to MicroSD works that way. I’m struggling to understand why multiple apparently good images (either done directly on PC, or via RPIboot to IO card) just do nothing - as I say, on power up the IO board F2 simply flashes 3 slow greens and one 4 fast green with a 3 second pause before repeating.
What do I do to flash an SD card with the bootloader stuff? Is that a specific RPI image just to test the boot loader?
I have not managed to have either of the CM5s with any image on boot, either in the ClockworkPI or the IO board.
If the RPIboot works and can write an image to the MicroSD on the IO board and it allows access to the USB gadget diagnostics console - does that mean the CM5 is booting or not? Apologies, but I’m getting very confused.
The CM is definitely seated fine and the correct way around (the only way where the 4 PCB corner holes are aligned).
with rpi-boot the CM5 is only partly running. what io board do you have? in rpi-imager in the choose os menu towards the bottom there’s an option (Misc utility images) then select (Bootloader (pi 5 family)) then (sd card boot) flash that to a sd and boot it in the io board with the cm5. it should update it and fix it if anything is wrong. then use a normal os and if it boots edit the eeprom as described in the first post. then try it in the uconsole.
I’ve just swapped the original CM5 for the new CM5 (delivered today) and the behaviour is identical. This can’t be a failure of both. I must be missing something
Ok, programmed the boot loader SD card boot image. When plugged into USB power, after a few seconds I get an all green display over HDMI. The D2 light is flashing a steady fast green. Is that normal?
Huge thanks. After doing the bootloader programme on both CM5s, they were both able to boot each of the SD cards into Clockwork PI. The 64GB Sandisk and Lexar could have the Clockwork image applied on the IO board. For some reason, the 512GB super fast Samsung would never boot on the IO board. It was however programmable with RPI Imager and the PCs own MicroSD adaptor. With the image applied to the 512GB card, it was bootable in the ClockworkPI with both the CM5s and the CM4. I was also able to boot the CM4 and both CM5s with the 64GB Lexar and Sandisk card - so all working now
It is hard to believe that the only way of getting the CM5s to work with the IO board or the Clockwork was to do the Bootloader SD card Boot image applied to them before loading any image with the Imager. Not great for RaspberryPI as a business as these cards were purchased 3 months apart.
Anyway, now looking forward to applying your SDR installer to get the HackerGadgets card working.
One hopefully little thing. I’ve successfully run your RTL-SDR install (the whole package). The next step was the sudo hwclock -w. This returns "hwclock: Cannot access the Hardware Clock via any known method. hwclock: Use the --verbose option to see the details of our search for an access method'. When I do that latter it shows hwclock from util-linux 2.38.1 System Time: 1753981081.107942 Trying to open: /dev/rtc0 Trying to open: /dev/rtc Trying to open: /dev/misc/rtc No usable clock interfaces found. hwclock: Cannot access the Hardware Clock via any known method'
