Unable to reach stage 2. Brand new CM4
c157fl opened this issue · 10 comments
Model: CM4102008
Objective::
- Flash EMMC
Issue::
- Running usbboot does not lead to the storage appearing.
Available carrier boards:
- dfrobot router board
- pitray mini
- pibox
- mcuzone tiny cs*2
Available systems:
- W11
- Pi4B(64OS)
Available cables: USB-A to USB-C, USB-C to USB-C
Usbboot behaviour on both Pi4B and W11:
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode4.bin
Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7/2711...
Different combinations of cables and carrier boards were tried to no avail.
When at this stage the ACT green LED blinks 8 times in short pulses.
According to the documentation this would imply faulty SDRAM.
Is there anything I can do to recover it or is my only option to send it back to the seller?
Thank you in advance
The logs suggest this is an old version of usbboot. It might be worth updating that first.
Also, update the EEPROM to latest stable release
cd recovery
../rpiboot -d .
Thank you.
On my Pi4B I had done the:
sudo apt install git libusb-1.0-0-dev pkg-config
git clone --depth=1 https://github.com/raspberrypi/usbboot
cd usbboot
make
sudo ./rpiboot
If I do that in the Pi4B with the verbose flag I have:
sudo ../rpiboot -d . -v
RPIBOOT: build-date Aug 13 2022 version 20220804~165403 3e7df2a1
Boot directory '.'
Loading: ./bootcode4.bin
Waiting for BCM2835/6/7/2711...
Loading: ./bootcode4.bin
Device located successfully
Initialised device correctly
Found serial number 3
Sending bootcode.bin
libusb_bulk_transfer sent 24 bytes; returned 0
Writing 87944 bytes
libusb_bulk_transfer sent 87944 bytes; returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7/2711...
It might be worth trying the recovery and then mass-storage-gadget instead of msd/
Thank you @timg236.
Since doing the sudo rpiboot -d recovery hangs (I'm assuming this is flashing the EEPROM) hangs when doing Waiting for BCM2835/6/7/2711 for the second stage, I Interrupted and attempted at doing sudo rpibood -d mass-storage-gadget.
Unfortunately I did not have success. It does not get detected.
If I then reset the device, it gets detected and does stage 1 but then hangs again:
RPIBOOT: build-date Aug 13 2022 version 20220804~165403 3e7df2a1
Boot directory 'mass-storage-gadget'
Loading: mass-storage-gadget/bootcode4.bin
Waiting for BCM2835/6/7/2711...
Loading: mass-storage-gadget/bootcode4.bin
Device located successfully
Initialised device correctly
Found serial number 3
Sending bootcode.bin
libusb_bulk_transfer sent 24 bytes; returned 0
Writing 106008 bytes
libusb_bulk_transfer sent 106008 bytes; returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7/2711...
This sounds like a hardware issue. You could try older versions of usbboot
Did:
git checkout XXXX
make
cd recovery
../rpiboot -d . -v
to versions:
| cc72bc0 | May 4 | Hangs |
| 42fe88d | April 26 | Hangs |
| 3ef29d3 | Feb 8 | Hangs |
| d49a1a2 | Jan 27 | Hangs |
| 0eb1b63 | Jan 27 | Hangs |
| 97f618f | Jan 11 | Failed to write correct length, returned -7 |
| 515b972 | Dec 14 | Failed to write correct length, returned -7 |
Unfortunately with no success.
Keep being stuck at stage 2 with the blinking 8 times LED.
Oh dear, that sounds bad, possibly needs an RMA. Do you have another CM4 to cross check it against the carrier boards? Although, given that the DDR voltages comes from the on-module PMIC it's unlikely to be an issue with the carrier board.
The carrier boards are good. This CM4 was going to replace a beefier one currently deployed DFRobot's router carrier board.
I talked to the seller but wanted to exhaust all the options. This one took almost a week to arrive (Germany->Portugal) and now sending it back and getting an answer will probably take double of that.
Thank you for help @timg236. I'll be continuing the RMA process then.
The carrier boards are good. This CM4 was going to replace a beefier one currently deployed DFRobot's router carrier board. I talked to the seller but wanted to exhaust all the options. This one took almost a week to arrive (Germany->Portugal) and now sending it back and getting an answer will probably take double of that. Thank you for help @timg236. I'll be continuing the RMA process then.
What was the outcome of this? I also have two brand new CM4, one of them is working as it should, the other one like you described.
Also tried several combinations of cables, 4 Operating Systems, Carrier Boards.
I'll need to send it back as well I guess, but there are no new ones in stock so I thought I'll ask here at first. Thanks!
The carrier boards are good. This CM4 was going to replace a beefier one currently deployed DFRobot's router carrier board. I talked to the seller but wanted to exhaust all the options. This one took almost a week to arrive (Germany->Portugal) and now sending it back and getting an answer will probably take double of that. Thank you for help @timg236. I'll be continuing the RMA process then.
What was the outcome of this? I also have two brand new CM4, one of them is working as it should, the other one like you described. Also tried several combinations of cables, 4 Operating Systems, Carrier Boards. I'll need to send it back as well I guess, but there are no new ones in stock so I thought I'll ask here at first. Thanks!
Got my refund, even though they did not refund the return costs as previously stated.
The replacement unit I got while handling the RMA worked directly. No issues like with the former.
Took more than a month of the unit being forgotten somewhere "inspected" and me being annoyed at them for a decision to come through.