Can not enter storage device on CM3+

[PovilasID]

Describe the bug

Could not get CM3+ module with emmc to boot as mass storage device or run recovery on it.
First I tried Balena etcher but it would show "Initializing the compute module" and then stop would not be on the list.
So I tried using this to boot it as storage devices and it also failed to do that.
I am on Windows.
After I plug the daughterboard I see 'BCM2710 Boot' under 'Universal Serial Bus devices'

Steps to reproduce the behaviour

Then I tried .\rpiboot.exe -d .\mass-storage-gadget64\
Got No 'bootcode' files found in '.\mass-storage-gadget64\'
So I tried running recovery:

.\rpiboot.exe -d .\recovery\
Until Cannot open file recovery.elf

Device(s)

Raspberry Pi CM3+

Compute Module IO board.

Nebra daughter board

RPIBOOT logs

.\rpiboot.exe  -d .\mass-storage-gadget64\
RPIBOOT: build-date Oct 26 2022 version 20220815~145439 9e57f462
No 'bootcode' files found in '.\mass-storage-gadget64\'
Usage: rpiboot
   or: rpiboot -d [directory]
Boot a Raspberry Pi in device mode either directly into a mass storage device
or provide a set of boot files in a directory from which to boot.  This can
then contain a initramfs to boot through to linux kernel

To flash the default bootloader EEPROM image on Compute Module 4 run
rpiboot -d recovery

For more information about the bootloader EEPROM please see:
https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md


rpiboot                  : Boot the device into mass storage device
rpiboot -d [directory]   : Boot the device using the boot files in 'directory'
Further options:
        -l               : Loop forever
        -o               : Use files from overlay subdirectory if they exist (when using a custom directory)
                           USB Path (1-1.3.2 for example) is shown in verbose mode.
                           (bootcode.bin is always preloaded from the base directory)
        -m delay         : Microseconds delay between checking for new devices (default 500)
        -v               : Verbose
        -s               : Signed using bootsig.bin
        -0/1/2/3/4/5/6   : Only look for CMs attached to USB port number 0-6
        -p [pathname]    : Only look for CM with USB pathname
        -h               : This help
 .\rpiboot.exe  -d .\recovery\ -v
RPIBOOT: build-date Oct 26 2022 version 20220815~145439 9e57f462
Boot directory '.\recovery\'
Loading: .\recovery\/bootcode4.bin
Waiting for BCM2835/6/7/2711...
libusb: error [init_device] device '\\.\USB#VID_046D&PID_C326&MI_01#6&35ABC081&0&0001' is no longer connected!
Loading embedded: bootcode.bin
Device located successfully
Initialised device correctly
Found serial number 0
Sending bootcode.bin
libusb_bulk_transfer sent 24 bytes; returned 0
Writing 52456 bytes
libusb_bulk_transfer sent 52456 bytes; returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7/2711...
libusb: error [init_device] device '\\.\USB#VID_046D&PID_C326&MI_01#6&35ABC081&0&0001' is no longer connected!
Loading embedded: bootcode.bin
Device located successfully
Failed to open the requested device
libusb: error [init_device] device '\\.\USB#VID_046D&PID_C326&MI_01#6&35ABC081&0&0001' is no longer connected!
Loading embedded: bootcode.bin
Device located successfully
Initialised device correctly
Found serial number 1
Second stage boot server
Received message GetFileSize: autoboot.txt
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file autoboot.txt
Received message GetFileSize: config.txt
Loading: .\recovery\/config.txt
File size = 16 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer sent 16 bytes; returned 0
Received message GetFileSize: recovery.elf
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file recovery.elf
Received message GetFileSize: start.elf
Loading embedded: start.elf
File size = 523192 bytes
Received message ReadFile: start.elf
File read: start.elf
libusb_bulk_transfer sent 523192 bytes; returned 0
Received message GetFileSize: fixup.dat
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file fixup.dat
libusb: warning [winusbx_submit_control_transfer] ControlTransfer failed: [22] The device does not recognize the command.
Second stage boot server done

Kernel logs

No response

Device UART logs

No response

[timg236]

You are running a very old version of the software. Please update to latest release and run rpiboot without arguments.

Recovery etc are for CM4 and newer

[PovilasID]

@timg236 I replaced the latest release version one in master branch.
Still was not able to mount the the storage:

USB mass storage gadget for Raspberry Pi 5
RPIBOOT: build-date 2025/05/19 pkg-version local 402baf02

Please 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: mass-storage-gadget64/bootfiles.bin
Using mass-storage-gadget64/bootfiles.bin
Waiting for BCM2835/6/7/2711/2712...

Loading embedded: bootcode.bin
Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7/2711/2712...

Loading embedded: bootcode.bin
Loading embedded: bootcode.bin
Second stage boot server
Cannot open file autoboot.txt
Loading: mass-storage-gadget64/config.txt
File read: config.txt
Cannot open file recovery.elf
Loading embedded: start.elf
File read: start.elf
Cannot open file fixup.dat
Second stage boot server done

Raspberry Pi Mass Storage Gadget started
EMMC/NVMe devices should be visible in the Raspberry Pi Imager in a few seconds.
For debug, you can login to the device using the USB serial gadget - see COM ports in Device Manager.

Are all these files not being able to load expected behavior?
Still do not see the drive loaded.

[timg236]

The mass storage gadget does not support CM3.
Run rpiboot without any arguments

[PovilasID]

I did not not mass storage gadget dropped CM3+ support (in previous versions mass storage gadget had CM3 mentioned in it's shortcut)
Running rpiboot without any arguments did not make the EMMC memory appear as storage device in disk manager or device manager or show up in Balena etcher's or Raspberry Pi Imager's storage target list.
Here is the log:

C:\Program Files (x86)\Raspberry Pi  .\rpiboot.exe
RPIBOOT: build-date 2025/05/19 pkg-version local 402baf02

Please 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.

Waiting for BCM2835/6/7/2711/2712...

Loading embedded: bootcode.bin
Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7/2711/2712...

Loading embedded: bootcode.bin
Loading embedded: bootcode.bin
Second stage boot server
Cannot open file autoboot.txt
Cannot open file config.txt
Cannot open file recovery.elf
Loading embedded: start.elf
File read: start.elf
Cannot open file fixup.dat
Second stage boot server done

[timg236]

It looks like it’s working.

[PovilasID]

@timg236
After I reboot the pi (replug usb cable I see)

But after I run rpiboot it disappears. At no point before or after running rpiboot or after replug the device it shows up as storage device or a flashing target.

I re ran the command with verbose flag:

.\rpiboot.exe -v
RPIBOOT: build-date 2025/05/19 pkg-version local 402baf02

Please 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.

Waiting for BCM2835/6/7/2711/2712...

Device located successfully
Loading embedded: bootcode.bin
Initialised device correctly
Found serial number 0
last_serial -1 serial 0
Sending bootcode.bin
libusb_bulk_transfer sent 24 bytes; returned 0
Writing 52456 bytes
libusb_bulk_transfer sent 52456 bytes; returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7/2711/2712...

Device located successfully
Loading embedded: bootcode.bin
Failed to open the requested device
Device located successfully
Loading embedded: bootcode.bin
Initialised device correctly
Found serial number 1
last_serial -1 serial 1
Second stage boot server
Received message GetFileSize: autoboot.txt
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file autoboot.txt
Received message GetFileSize: config.txt
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file config.txt
Received message GetFileSize: recovery.elf
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file recovery.elf
Received message GetFileSize: start.elf
Loading embedded: start.elf
File size = 536536 bytes
Received message ReadFile: start.elf
File read: start.elf
libusb_bulk_transfer sent 536536 bytes; returned 0
Received message GetFileSize: fixup.dat
libusb_bulk_transfer sent 0 bytes; returned 0
Cannot open file fixup.dat
Second stage boot server done

[timg236]

It looks like it's running as expected. Since the drives aren't appearing in the very old or very new versions it's possibly a Windows issue. Can you try on Linux?

[PovilasID]

I did run it on debian based machine:

git clone --recurse-submodules --shallow-submodules --depth=1 https://github.com/raspberrypi/usbboot
....
cd usbboot
make
xxd -i msd/bootcode.bin > msd/bootcode.h
xxd -i msd/start.elf > msd/start.h
xxd -i msd/bootcode4.bin > msd/bootcode4.h
cc -Wall -Wextra -g   -o rpiboot main.c bootfiles.c decode_duid.c `pkg-config --cflags --libs libusb-1.0` -DGIT_VER="\"fe4a6288\"" -DPKG_VER="\"local\"" -DBUILD_DATE="\"2025/11/07\"" -DINSTALL_PREFIX=\"/usr\"
sudo ./rpiboot 
RPIBOOT: build-date 2025/11/07 pkg-version local fe4a6288

Please 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.

Waiting for BCM2835/6/7/2711/2712...

Loading embedded: bootcode.bin
Sending bootcode.bin
Successful read 4 bytes 
Waiting for BCM2835/6/7/2711/2712...

Loading embedded: bootcode.bin
Loading embedded: bootcode.bin
Second stage boot server
Cannot open file autoboot.txt
Cannot open file config.txt
Cannot open file recovery.elf
Loading embedded: start.elf
File read: start.elf
Cannot open file fixup.dat
Second stage boot server done

I did not find any new disks under lsblk command

[timg236]

It could be an issue with the CM3+ module. Please could you post pictures of both sides of the module.

btw: The github release of the mass-storage-gadget64 will probably boot on this board. If it does it will create a UART console and CDC uart. From there you could see if the EMMC is visible (e.g. lsblk)

[PovilasID]

Hardware seams ok and I have a couple of them and behavior is consistent with both Pis and since boards seam to be communicating (reading '4 bites') the daughterboard looks to be operating correctly.

I actually got one of them a year ago and did some quick testing and manage to flash it but was very late and did not write down the process. I think I tinkered with using different firmware files to flash or edited the config.txt to make it work. I do not remember any more. Hoped that latest version may have solved the issues but either I forgot something or nobody raised an issue so then I have some time for debugging I will try to figure it out. Any suggestions are welcome.

[timg236]

This commit adds mass-storage-gadget support for CM3, CM3+ and CM3E.

4926dba

If you are able to capture the UART data whilst running the mass-storage-gadget and also run lsblk from the UART console it would indicate if there is a problem with the EMMC e.g. if there is a problem with the EMMC re-enable signal.