Describe the bug
With commit 87d6e03272b0ae155d85a125bfdec03e3d4a1095 on some RPi5/CM5 devices I sometimes see the following behavior:
16:22:05 [INFO ] : Waiting for BCM2835/6/7/2711/2712...
16:22:06 [INFO ] : Sending bootcode.bin
16:22:07 [INFO ] : Successful read 4 bytes
16:22:08 [INFO ] : Waiting for BCM2835/6/7/2711/2712...
16:22:10 [INFO ] : Second stage boot server
16:22:10 [INFO ] : File read: mcb.bin
16:22:10 [INFO ] : File read: memsys00.bin
16:22:10 [INFO ] : File read: memsys01.bin
16:22:10 [INFO ] : File read: rp1c0fw1.bin
16:22:10 [INFO ] : File read: memsys02.bin
16:22:11 [INFO ] : File read: rp1c0fw2.bin
16:22:12 [INFO ] : File read: memsys03.bin
16:22:12 [INFO ] : Second stage boot server done
No errors observed
Steps to reproduce the behaviour
Changing cables, not using USB hubs doesn't seem to have any influence on reproducibility.
Device(s)
Other
Compute Module IO board.
Raspberry Pi 5, Waveshare dual Ethernet carried board with CM5 (different carriers were under test)
RPIBOOT logs
No response
Kernel logs
No response
Device UART logs
No response
Describe the bug
With commit
87d6e03272b0ae155d85a125bfdec03e3d4a1095on some RPi5/CM5 devices I sometimes see the following behavior:No errors observed
Steps to reproduce the behaviour
Changing cables, not using USB hubs doesn't seem to have any influence on reproducibility.
Device(s)
Other
Compute Module IO board.
Raspberry Pi 5, Waveshare dual Ethernet carried board with CM5 (different carriers were under test)
RPIBOOT logs
No response
Kernel logs
No response
Device UART logs
No response