Booting from USB failed

[Cavusa]

Hi there,

I've been having issues with booting the CM4 from USB, including an SD card via USB adapter, with the RPi OS written by using the RPi Imager.

The only error it gives be is the following:

• 'config failed hub doesn't have any ports: err -19'

After a little while, it then stops sending a signal to the monitor. The CM4 boots fine from the eMMC, recognising the USB ports in the Pi startup screen, and has successfully booted from the eMMC with a keyboard and either of the USB's used now configured for booting connected.

My boot order is f0x145

Cheers,

Karl

[PhilE]

When discussing Compute Modules (all variants) it's important to state which carrier is being used.

[Cavusa]

Sorry about that! The carrier board is a Luxonis DEPTHai Oak-D-CM4 DM1097.

Is there anything else I can add that would help?

[PhilE]

You could say a bit about what does work - can you access USB without trying to boot from it?

Which USB port are you trying to use?

What have you done to enable USB booting?

[Cavusa]

Yes, both the USB and SD card (via adapter) are accessible when plugged into the carrier board and it's booted from the eMMC. I can see the /boot and /rootfs folders in both.

The Oak-D board has 2 USB ports, I have tried using both.

Steps performed to enable booting from USB:

• Install RPiOS on USB/SD card using RPi Imager

• Power on the board, booting from eMMC

• Cloned, built and installed the usbboot repo - https://github.com/raspberrypi/usbboot

• Navigated to the recovery usbboot/recovery and updated the boot.conf BOOT_ORDER to 145

• Run the ./update-pieeprom.sh script

• Transferred over the recovery folder from the Oak-D-CM4 to a Windows 7 machine

• Turned off the Oak-D-CM4, removed peripherals and power, then set the on-board jumper that is equivalent to the J2 jumper before reconnected the power and connecting the Windows host to the Oak-D board via microUSB

• Installed rpiboot on the Windows machine

• Tested the connection by running the rpiboot.exe (successfully connected), before terminating the process and reconnecting

• Run '"<RPIBOOT_PATH>/rpiboot.exe" -d <PATH>/recovery' - seems to succeed

• Unplug the microUSB, reset the jumper and removed the power from the Oak-D, insert OS USB and power on

At this point, it seems to attempt to boot from USB, but fails with the err-19 message from before, and I have to power cycle to try booting again. With the USB removed, then it successfully boots from the eMMC after a power cycle.

[PhilE]

If you wait a few minutes do any more kernel messages appear?

[Cavusa]

When I wait, the screen loses signal. No further messages, as far as I can see

[timg236]

It might be worth checking the partition UUIDs are correct on the USB device.

[Cavusa]

A quick update: with the USB inserted, just before the signal to the monitor cuts out, the RPi screen flashes up for a few frames before the signal is lost.

I also tried a new USB, and it showed a slight variation of the previous observed states: this also showed a 'resizing space' on a blue screen after err -19, with a 5 second countdown, then displays the err -19 again. And then No Signal.

The UUIDs for the USB are as follows:

• /dev/sda1: LABEL_FATBOOT="boot" LABEL="boot" UUID="E183-6233" TYPE="vfat" PARTUUID="8c6ef2c7-01"

• /dev/sda2: LABEL="rootfs" UUID="1232a209-2596-48f0-a078-731d10b918ad" TYPE="ext4" PARTUUID="8c6ef2c7-02"

[PhilE]

It's possible there are a few issues contributing to your symptoms. If your config.txt include "dtoverlay=vc4-kms-v3d", try changing it to say "dtoverlay=vc4-fkms-v3d" (note the additional "f"). We are aware of a problem in this area and are trying to find a solution - this is a temporary workaround.

[Cavusa]

My config.txt only has a single line:

uart_2ndstage=1

Should I add this additional line, or is that only if that example line already exists?

[timg236]

My config.txt only has a single line:

uart_2ndstage=1

Should I add this additional line, or is that only if that example line already exists?

To get Linux dmesg on the UART please add the following to config.txt

Code: Select all

enable_uart=1

https://www.raspberrypi.com/documentati ... ml#part4.6

Also, remove the word `quiet` from cmdline.txt if present.

[Cavusa]

Hi Tim,

I've added 'enable_uart=1' to the config.txt and reflashed using rpiboot, and removed 'quiet' from the 'cmdline.txt' found in the boot folder of the boot USB.

I see a lot of messages when attempting the boot, culminating in:
'Starting Plymouth show boot screen'

It then reverts to the monitor displaying No Signal.

Cheers,

Cav

[timg236]

Hi Tim,

I've added 'enable_uart=1' to the config.txt and reflashed using rpiboot, and removed 'quiet' from the 'cmdline.txt' found in the boot folder of the boot USB.

I see a lot of messages when attempting the boot, culminating in:
'Starting Plymouth show boot screen'

It then reverts to the monitor displaying No Signal.

Cheers,

Cav

What sort of monitor / resolution is it?
Does connecting to HDMI1 instead of HDMI0 make any difference?
Are you able to login via the UART ?

If you can login try adding hdmi_safe=1 to config.txt which will amongst other things will force the resolution to be 640x480

[Cavusa]

It's an LG, it's a little old and have never been able to pin down the res of it, but the one I use is 1768x992 (1920x1080 is slightly too big for it).
The Luxonis carrier board for the CM4 only has the one HDMI, unfortunately.

I don't have a UART to USB connector, either. If the CM4 can boot from eMMC, would this not suggest the monitor is not the issue? Unless there's a problem with the OS being used? I honestly don't know. I don't think I'm reaching login, as I never get to the login screen (aside from when I boot from eMMC).

I added 'hdmi_safe=1' to the config.txt, rerun the update-pieeprom.sh before rerunning 'rpiboot.exe -d recovery' then attempted to boot with the USB inserted. I again saw the extra messages (with the line of Pi logos across the top), which then went to Signal Lost again.

[Cavusa]

Should my config.txt have more than just the one line in it? Such as the 'dtoverlay=vc4-fkms-v3d' that Phil mentioned?