i.MX 8QuadMax MEK iMX8QM MEK fastboot USB device not visible

[BernardLadenthin]

Hi,

I'm trying to setup the provided example for the "i.MX 8QuadMax Multisensory Enablement Kit (MEK)": "13.0.0_2.3.0_AUTO_DEMO".

The uuu_imx_android_flash.bat is getting stuck and I'm sure I've already figured out why.

The uuu.exe uses the generated uuu.lst and loads the SDPS: boot -f u-boot-imx8qm-mek-uuu.imx

With a manual test, I was able to boot U-Boot.

I got the output and manually interrupted:

U-Boot 2023.04 (Nov 22 2023 - 22:34:50 +0100)

CPU:   NXP i.MX8QM RevB A53 at 1200 MHz at 41C

Model: NXP i.MX8QM MEK
Board: iMX8QM MEK
Boot:  USB
DRAM:  6 GiB
TCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C0 0x51]
Core:  188 devices, 32 uclasses, devicetree: separate
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... MMC: no card present
*** Warning - No block device, using default environment

[*]-Video Link 0it6263_i2c_reg_read, read err 3
faill to read from it6263 revision, ret 3
 (1280 x 720)
<9>[0] dpu@56180000, video
<9>[1] lvds-channel@0, display
<9>[2] lvds-to-hdmi-bridge@4c, video_bridge
In:    serial
Out:   serial
Err:   serial

 BuildInfo: 
  - SCFW 6638c032, SECO-FW c9de51c0, IMX-MKIMAGE 5a0faefc, ATF b68fe4e
  - U-Boot 2023.04 

Detect USB boot. Will enter fastboot mode!
Net:   eth0: ethernet@5b040000 [PRIME]Could not get PHY for FEC1: addr 1

MMC: no card present
Block device mmc 1 not supported
bcb_rw_block, get_block_size return 0
read_bootctl, bcb_rw_block read failed
read command failed
Fastboot: Normal
Boot from USB for uuu
Hit any key to stop autoboot:  3 <\b><\b><\b> 2 <\b><\b><\b> 1 <\b><\b><\b> 0 

When I interrupt, the connection is still alive, which is okay, and I'm able to run some commands like:

=> printenv
baudrate=115200
board_name=MEK
board_rev=iMX8QM
bootcmd=fastboot 0
bootdelay=3
commit_atf=b68fe4e
commit_mkimage=5a0faefc
commit_scfw=6638c032
commit_secofw=c9de51c0
emmc_dev=0
ethact=ethernet@5b040000
ethaddr=00:04:9f:07:c1:f5
ethprime=eth0
fdt_high=0xffffffffffffffff
fdtcontroladdr=fd201290
initrd_high=0xffffffffffffffff
loadaddr=0x80200000
sd_dev=1
sec_boot=no
serial#=090519aac65428b4
soc_rev=revb
soc_type=imx8qm
splashimage=0x9e000000
splashpos=m,m

Environment size: 458/8188 bytes

I've also tried to erase the eMMC (part 1 and part 2) with the mmc erase command.

I assume the generated script will initiate a command like "fastboot 0".

In automatic mode (with uuu running the lst) and with manual command prompt of "fastboot 0", no device appears. I've tested this with different USB cables on both Windows and Linux. Linux also doesn't show a device, even when using lsusb in verbose mode.

Do you have any idea what I can check to get the device (USB fastboot) visible after the "fastboot 0" command? I'm pretty sure that's the reason why the full uuu lst gets stuck. Powering off/on results in the same situation, as does using the reset button. Is a specific USB connection necessary?"

New USB Device Attached at 1:91
libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'
1:91>Start Cmd:SDPS: boot -f u-boot-imx8qm-mek-uuu.imx
13%libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'
31%libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'
51%libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'
75%libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'
100%libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'
libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'
libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'
libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'
1:91>Okay (1.781s)
libusb: warning [enumerate_hcd_root_hub] could not get child devinst for 'ROOT\SYSTEM\0002'

Thank you in advance for any assistance you can provide.

[BernardLadenthin · Accepted solution]

Hello,

I've found out that the USB-C port on the NXP board is defective. A new board is working. Thank you for any help. This topic can be closed.

[JosephAtNXP]

Hi,

Thank you for your interest in NXP Semiconductor products,

Could you confirm your silicon revision?

Are you flashing the SD or eMMC?

What is the command you are flashing your board with?

Could you perform the test of waiting, maybe it's slower and not stucked.

Regards

[BernardLadenthin]

The connection of the USB-C from the NXP board to the PC via USB-A or USB-C cable results in an error: "Unknown USB Device (Device Descriptor Request Failed)". Tested on different Windows 10/11 Laptops.

[BernardLadenthin]

Hi,

I'm attempting to use uuu_imx_android_flash.bat with the command "uuu_imx_android_flash.bat -f imx8qm" from automotive-13.0.0_2.3.0_image_8qmek_car2.

The procedure gets stuck.

I've investigated why and determined that it occurs during the uuu command.

I've used the temporarily created lst file, modified it to resolve symbolic links, and tried it manually.

This is the modified uuu.lst file:

uuu_version 1.4.182 
SDPS: boot -f u-boot-imx8qm-mek-uuu.imx
FB: ucmd setenv fastboot_dev mmc 
FB: ucmd setenv mmcdev 0 
FB: ucmd mmc dev 0 
FB: ucmd mmc dev 0 0 
FB: ucmd mmc erase 0x3800 0x10 
FB: ucmd mmc partconf 0 1 1 1 
FB[-t 600000]: flash bootloader0 u-boot-imx8qm.imx
FB[-t 600000]: flash gpt partition-table.img
FB[-t 600000]: flash dtbo_a dtbo-imx8qm.img
FB[-t 600000]: flash vendor_boot_a vendor_boot.img
FB[-t 600000]: flash init_boot_a init_boot.img
FB[-t 600000]: flash boot_a boot.img
FB[-t 600000]: flash vbmeta_a vbmeta-imx8qm.img
FB[-t 600000]: flash dtbo_b dtbo-imx8qm.img
FB[-t 600000]: flash vendor_boot_b vendor_boot.img
FB[-t 600000]: flash init_boot_b init_boot.img
FB[-t 600000]: flash boot_b boot.img
FB[-t 600000]: flash vbmeta_b vbmeta-imx8qm.img
FB[-t 600000]: flash super super.img
FB[-t 600000]: erase misc
FB[-t 600000]: erase presistdata
FB[-t 600000]: erase fbmisc
FB[-t 600000]: erase metadata
FB: done 

When I call "uuu.exe uuu.lst", it starts and gets stuck. I've figured out that it gets stuck right after the boot command.

I was able to interrupt the switch to fastboot in the bootloader via serial console.

In the serial console (with the u-boot bootloader), I'm now able to enter some commands. I've erased the eMMC and tried the first commands manually:

setenv fastboot_dev mmc 
setenv mmcdev 0 
mmc dev 0 
mmc dev 0 0 
mmc erase 0x3800 0x10 
mmc partconf 0 1 1 1 

I'll try to switch via "fastboot 0" to get the board running as a fastboot device. The USB connection was lost and no USB device appeared again.

My question and problem are: What is going wrong, that I cannot see the fastboot USB device? That's also my assumption as to why the uuu tool gets stuck.