Hello
I'm trying to use usbboot in an automated jig.
Unfortunately, it seems to be very flaky. What type of cable I use seems to play quite a big role.
Even good quality cables https://www.brack.ch/onit-usb-2-0-kabel ... -m-1405754 seem to have problems.
Example flow with problems. The rpiboot binary is running on a Raspberry Pi 4. The Raspberry Pi 4 runs with the OS (Raspberry Pi OS) installed on a no-name USB-Stick.
The OS USB-Stick is plugged into a USB3 Port, the CM4 is plugged into a USB2 Port.
In this example (reproduced multiple times) it somehow fails to fully load mass-storage-gadget64 and never appears as MSD.
My custom hardware seems to be a bit more finicky than the CM5IO Board. Any idea how to improve this?
I'm trying to use usbboot in an automated jig.
Unfortunately, it seems to be very flaky. What type of cable I use seems to play quite a big role.
Even good quality cables https://www.brack.ch/onit-usb-2-0-kabel ... -m-1405754 seem to have problems.
Example flow with problems. The rpiboot binary is running on a Raspberry Pi 4. The Raspberry Pi 4 runs with the OS (Raspberry Pi OS) installed on a no-name USB-Stick.
The OS USB-Stick is plugged into a USB3 Port, the CM4 is plugged into a USB2 Port.
In this example (reproduced multiple times) it somehow fails to fully load mass-storage-gadget64 and never appears as MSD.
Code:
$ sudo ./usbboot/rpiboot -d usbboot/mass-storage-gadget64RPIBOOT: build-date 2025/11/13 pkg-version local fe4a6288Please fit the EMMC_DISABLE / nRPIBOOT jumper before connecting the power and USB cables to the target device.If the device fails to connect then please see https://rpltd.co/rpiboot for debugging tips.Loading: usbboot/mass-storage-gadget64/bootfiles.binUsing usbboot/mass-storage-gadget64/bootfiles.binWaiting for BCM2835/6/7/2711/2712...Sending bootcode.binSuccessful read 4 bytes Waiting for BCM2835/6/7/2711/2712...Second stage boot serverFile read: mcb.binFile read: memsys00.binFile read: memsys01.binFile read: memsys02.binFile read: memsys03.binFile read: memsys04.binFile read: memsys05.binFile read: memsys06.binFile read: memsys07.binFile read: memsys08.binFile read: bootmainFailed to write complete file to USB deviceCode:
[ 6926.477997] usb 1-1.4: new high-speed USB device number 17 using xhci_hcd[ 6926.566279] usb 1-1.4: config index 0 descriptor too short (expected 55, got 32)[ 6926.566621] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=2711, bcdDevice= 0.00[ 6926.566640] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3[ 6926.566654] usb 1-1.4: Product: BCM2711 Boot[ 6926.566665] usb 1-1.4: Manufacturer: Broadcom[ 6926.566676] usb 1-1.4: SerialNumber: c7b78f60[ 6931.144265] usb 1-1.4: USB disconnect, device number 17[ 6932.238058] usb 1-1.4: new high-speed USB device number 18 using xhci_hcd[ 6932.326530] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=2711, bcdDevice= 0.00[ 6932.326556] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=4[ 6932.326568] usb 1-1.4: Product: BCM2711 Boot[ 6932.326579] usb 1-1.4: Manufacturer: Broadcom[ 6932.326588] usb 1-1.4: SerialNumber: c7b78f60[ 6934.471296] usb 1-1.4: USB disconnect, device number 18Statistics: Posted by batwing — Mon Nov 17, 2025 5:42 pm