-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CM4] BCM-USB-MSD seems broken #557
Comments
New insight: |
It's probably worth comparing results on a CM4IO board (or other boards). Booting from a USB drive with the BCM XHCI controller is pretty common so it sounds like there is another variable here For interop questions, it's worth asking on the Compute Module forums |
Merging this as duplicate of #588 There's some test firmware which might resolve the problem for you here |
Closing due to inactivity - BCM USB MSD was tested on CM4 IO following some interop enhancements for USB/SD adapters. Assumed fixed in the latest firmware release. |
Describe the bug
In order to be able to easily do updates to an embedded device in the field, I would like to use BCM-USB-MSD (0x5) before eMMC.
Unfortunately I'm failing at that with two problems. I tried it with pieeprom-2023-01-11.bin and pieeprom-2024-01-22.bin.
My boot.conf:
If I plug in a keyboard everything looks good:
But 11 of 12 different USB sticks are not recognized:
The error messages are identical and repeat continuously until the timeout. All sticks are recognized without any problems under Linux.
second problem
If I activate BCM-USB-MSD and have xhci (regardless of otg_mode=1 in config.txt or overlay) active in Linux at the same time, the eMMC boot process hangs until I insert a USB stick.
I would be grateful for any help.
Greetings
Dirk
Steps to reproduce the behaviour
see above
Device (s)
Raspberry Pi CM4
Bootloader configuration.
[all]
BOOT_UART=1
WAKE_ON_GPIO=1
POWER_OFF_ON_HALT=0
BOOT_ORDER=0xf15
ENABLE_SELF_UPDATE=1
System
USB is connected directly to a USB-A socket without another HUB-IC etc!
Bootloader logs
No response
USB boot
No response
NVMe boot
No response
Network (TFTP boot)
No response
The text was updated successfully, but these errors were encountered: