Imx8x enters boot mode but recovery-linux.sh does not detect the port

Technical Support
, ,
1

the module entered recovery mode (this is the linux dmesg):

[mié 29 abr 12:40:07 2026] usb 3-12: new high-speed USB device number 87 using xhci_hcd
[mié 29 abr 12:40:07 2026] usb 3-12: New USB device found, idVendor=1b67, idProduct=4026, bcdDevice= 0.01
[mié 29 abr 12:40:07 2026] usb 3-12: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[mié 29 abr 12:40:07 2026] usb 3-12: Product: 0038 Colibri iMX8QXP 2GB WB IT
[mié 29 abr 12:40:07 2026] usb 3-12: Manufacturer: Toradex
[mié 29 abr 12:40:07 2026] usb 3-12: SerialNumber: 08811153
[mié 29 abr 12:40:07 2026] cdc_ncm 3-12:1.0: MAC-Address: be:6f:a5:32:05:55
[mié 29 abr 12:40:07 2026] cdc_ncm 3-12:1.0 usb0: register ‘cdc_ncm’ at usb-0000:00:14.0-12, CDC NCM (NO ZLP), be:6f:a5:32:05:55
[mié 29 abr 12:40:07 2026] cdc_ncm 3-12:1.0 enxbe6fa5320555: renamed from usb0

but recovery-linux.sh waits for ever:

Downloading Toradex Easy Installer…
uuu (Universal Update Utility) for nxp imx chips – libuuu_1.5.233-0-g79ce7d2

Success 0 Failure 0 Wait for Known USB Device Appear…

can we upload tezi by net?

Colibri imx6x not booting after reflash... how to repair uboot and easy installer
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I see you’re experiencing an issue with your Colibri iMX8X module where it enters recovery mode correctly but the recovery script doesn’t detect it. The dmesg output shows the module is recognized as a CDC NCM network device rather than the expected USB device for recovery mode.

Troubleshooting Steps

1. Check Recovery Mode Entry

Your module appears to be entering recovery mode, but it’s being detected as a network device instead of the expected USB device for TEZI loading(1). To properly enter recovery mode on the Colibri iMX8X, you need to pull SODIMM pin 91 to GND with a 10 kΩ resistor while powering up the module(2).

2. USB Connection Issues

The recovery script expects a specific USB device ID for the recovery process(1). Try these steps:

  • Use a different USB port: Avoid USB3 ports and use USB2 ports instead
  • Try a different USB cable: Ensure you’re using a reliable USB cable
  • Avoid USB hubs: Connect directly to your host computer(1)
  • Avoid virtual machines: Use a native Linux installation(1)

3. Alternative Loading Method

Regarding your question about uploading TEZI by network - the standard recovery process uses USB OTG interface(1). However, there is an alternative method using external media (SD Card/USB Stick), though this is not officially supported by Toradex(1).

External Media Method

This method relies on Distro Boot and boots in the following order(1):

  1. SD Card
  2. internal eMMC
  3. USB Stick

To use this method:

  1. Unzip Easy Installer into the root directory of a FAT-formatted USB stick or SD Card(1)
  2. Insert the media and power on the carrier board(1)
  3. For USB stick booting, you’ll need serial console access to run run bootcmd_usb0 in U-Boot(1)

4. Recovery Mode Verification

Make sure there’s no bootable SD card in the slot when attempting recovery mode, as this can interfere with the USB serial loader(2).

The network interface you’re seeing suggests the module isn’t in the proper recovery mode state for TEZI loading. Double-check the recovery mode entry procedure for your specific carrier board configuration.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Hi @zausan!

I tested the procedure, and TEZI was loaded successfully.

The steps I took were:

  • Connected my computer to the USB OTG X4 connector
  • Ran the recovery-linux.sh script
  • Short-circuited the Colibri pads
  • Powered on the board

After the TEZI was loaded, I accessed its interface using a VNC viewer, as described here.

Have you followed the same steps? If not, could you please try again?

Best regards.

4

Tezi installed correctly… the problem was tihis:

after short cirtuit and power on the board, my linux system detects this and the script was waiting for ever

[mié 29 abr 13:02:12 2026] usb 3-12: new high-speed USB device number 89 using xhci_hcd
[mié 29 abr 13:02:12 2026] usb 3-12: New USB device found, idVendor=1b67, idProduct=4026, bcdDevice= 0.01
[mié 29 abr 13:02:12 2026] usb 3-12: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[mié 29 abr 13:02:12 2026] usb 3-12: Product: 0038 Colibri iMX8QXP 2GB WB IT
[mié 29 abr 13:02:12 2026] usb 3-12: Manufacturer: Toradex
[mié 29 abr 13:02:12 2026] usb 3-12: SerialNumber: 08811153
[mié 29 abr 13:02:12 2026] cdc_ncm 3-12:1.0: MAC-Address: be:6f:a5:32:05:55
[mié 29 abr 13:02:12 2026] cdc_ncm 3-12:1.0 usb0: register ‘cdc_ncm’ at usb-0000:00:14.0-12, CDC NCM (NO ZLP), be:6f:a5:32:05:55
[mié 29 abr 13:02:12 2026] cdc_ncm 3-12:1.0 enxbe6fa5320555: renamed from usb0

Success 0 Failure 0 Wait for Known USB Device Appear…

After some probes, the kernel detects the OTG usb differently

[mié 29 abr 13:24:47 2026] usb 3-3: new high-speed USB device number 98 using xhci_hcd
[mié 29 abr 13:24:47 2026] usb 3-3: New USB device found, idVendor=1fc9, idProduct=012f, bcdDevice= 0.04
[mié 29 abr 13:24:47 2026] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[mié 29 abr 13:24:47 2026] usb 3-3: Product: SE Blank 8QXP
[mié 29 abr 13:24:47 2026] usb 3-3: Manufacturer: NXP SemiConductor Inc

and then recovery_linux.sh found it and flashed succesfully…

i don’t known why this different detection but now is working

thanks!!!

1 Like
5

Hi @zausan!

I’m glad to know that it worked.

Best regards.