Hello!
I have a Rpi 4B which has the latest 64-bit OS installed (Bookworm). CM4 is connected to the Rpi 4B via USB cable. I was wondering why the rpiboot-msg fails and then I saw this in dmesg:
Not sure if that error is related or not but then when I run the rpiboot with the mass-storage-gadget I get this:
(and this is stuck in a loop trying over and over again)
And when running the legacy rpiboot:
Failed to claim interface probably means Linux trying to autorun the drives. They mount just fine in the end.
Running as root both times. rpi-eeprom-update says up to date.
Note that the CM4 works fine when I connect it to Windows and run the MSG gadget. I can also program the eMMC without issues. On the Rpi 4B I have it connected to USB 2.0 port, although it doesn't matter if I plug it into a USB 3 port.
Could this be because there's a mass-storage-gadget64 on github? That one doesn't work because rpiboot expects a bootcode* files and that dir has bootfiles.bin in it... Work in progress?
I have a Rpi 4B which has the latest 64-bit OS installed (Bookworm). CM4 is connected to the Rpi 4B via USB cable. I was wondering why the rpiboot-msg fails and then I saw this in dmesg:
Code:
[ 8883.540781] usb 1-1.3: new high-speed USB device number 32 using xhci_hcd[ 8888.753377] usb 1-1.3: device descriptor read/64, error -110[ 8906.398717] usb 1-1.3: new high-speed USB device number 33 using xhci_hcd[ 8906.498993] usb 1-1.3: config index 0 descriptor too short (expected 55, got 32)[ 8906.499351] usb 1-1.3: New USB device found, idVendor=0a5c, idProduct=2711, bcdDevice= 0.00[ 8906.499370] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3[ 8906.499383] usb 1-1.3: Product: BCM2711 Boot[ 8906.499395] usb 1-1.3: Manufacturer: Broadcom[ 8906.499408] usb 1-1.3: SerialNumber: xxxxxxCode:
RPIBOOT: build-date Dec 15 2022 version 20221215~105525 Loading: ./bootcode4.binWaiting for BCM2835/6/7/2711...Loading: ./bootcode4.binSending bootcode.binFailed : 0x0Waiting for BCM2835/6/7/2711...Loading: ./bootcode4.binSending bootcode.binFailed control transfer (-7,24)Failed to write correct length, returned -7Waiting for BCM2835/6/7/2711...Loading: ./bootcode4.binSending bootcode.binAnd when running the legacy rpiboot:
Code:
Waiting for BCM2835/6/7/2711...Loading embedded: bootcode4.binFailed to claim interfaceLoading embedded: bootcode4.binFailed to claim interfaceLoading embedded: bootcode4.binLoading embedded: bootcode4.binSecond stage boot serverCannot open file config.txtCannot open file pieeprom.sigLoading embedded: start4.elfFile read: start4.elfCannot open file fixup4.datSecond stage boot server doneRunning as root both times. rpi-eeprom-update says up to date.
Note that the CM4 works fine when I connect it to Windows and run the MSG gadget. I can also program the eMMC without issues. On the Rpi 4B I have it connected to USB 2.0 port, although it doesn't matter if I plug it into a USB 3 port.
Could this be because there's a mass-storage-gadget64 on github? That one doesn't work because rpiboot expects a bootcode* files and that dir has bootfiles.bin in it... Work in progress?
Statistics: Posted by pematnl — Fri Feb 09, 2024 10:19 am
