If you are able to run the CM4/CM5 mass-storage-gadget64 then you connect to it via HDMI console, UART console or USB gadget serial to examine the block devices directly.
The latest release on Github includes various tools like mmc / pci-utils for diagnostics.
If the mass-storage-gadget64 is not working then there's a troubleshooting guide here
https://github.com/raspberrypi/usbboot? ... leshooting
Common issues are the micro-USB cable or on CM5 the host-PC might not be able to provide enough current from the USB port if you have peripherals.
I would recommend using a Pi4 as the host. It's able to power and run RPIBOOT for CM5 on CM4IO/CM5IO board with NVNe. A short, decent quality USB-A to USB-C cable is recommended.
The latest release on Github includes various tools like mmc / pci-utils for diagnostics.
If the mass-storage-gadget64 is not working then there's a troubleshooting guide here
https://github.com/raspberrypi/usbboot? ... leshooting
Common issues are the micro-USB cable or on CM5 the host-PC might not be able to provide enough current from the USB port if you have peripherals.
I would recommend using a Pi4 as the host. It's able to power and run RPIBOOT for CM5 on CM4IO/CM5IO board with NVNe. A short, decent quality USB-A to USB-C cable is recommended.
Statistics: Posted by timg236 — Fri Dec 06, 2024 9:47 am