-
Notifications
You must be signed in to change notification settings - Fork 279
Description
Describe the bug
I'm trying to flash a CM4 on Win11, but it always hangs at "File read: start4.elf."
Running with -v and -l shows it's hanging on "Cannot open file fixup4.dat"
I've read that fixup4.dat is unnecessary and the process should continue after this point, but it doesn't.
Steps to reproduce the behaviour
Simply run rpiboot and then connect the CM4.
Device(s)
Raspberry Pi CM4
Compute Module IO board.
CM4IO
RPIBOOT logs
Waiting for BCM2835/6/7/2711...
libusb: warning [init_device] could not get node connection information for device '\.\USB#VID_046D&PID_C088&LAMPARRAY#6&689911D&0&806D681057942292_SLOT00': [87] The parameter is incorrect.
libusb: warning [set_composite_interface] failure to read interface number for \.\HID#HID_DEVICE_SYSTEM_VHF#A&1290A874&0&0000. Using default value 0
Loading embedded: bootcode4.bin
Device located successfully
Initialised device correctly
Found serial number 4
Second stage boot server
Received message GetFileSize: config.txt
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file config.txt
Received message GetFileSize: pieeprom.sig
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file pieeprom.sig
Received message GetFileSize: recover4.elf
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file recover4.elf
Received message GetFileSize: recovery.elf
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file recovery.elf
Received message GetFileSize: start4.elf
Loading embedded: start4.elf
File size = 293564 bytes
Received message ReadFile: start4.elf
File read: start4.elf
libusb_bulk_transfer sent 293564 bytes; returned 0
Received message GetFileSize: fixup4.dat
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file fixup4.dat
Kernel logs
No response
Device UART logs
No response