Toradex Easy Installer 7.2.0 fails to detect iMX8MP device

borco · June 21, 2025, 8:20am

Hi,

I am trying to use Toradex Easy Installer to flash my device from Windows 11.

The latest TEZI 7.2.0 for my device, fails to detect the device (from Verdin-iMX8MP_ToradexEasyInstaller_7.2.0+build.5):

$ ./recovery-windows.bat
Downloading Toradex Easy Installer...
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.165-0-g7347a80

Success 0    Failure 1


2:2      1/ 0 [Failure open usb device               ]


ECHO is off.
Downloading Toradex Easy Installer failed...
Press any key to continue . . .

However, TEZI 6.8.2 works fine (from Verdin-iMX8MP_ToradexEasyInstaller_6.8.2+build.10.zip):

$ ./recovery-windows.bat
Downloading Toradex Easy Installer...
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.165-0-g7347a80

Success 1    Failure 0


2:2      8/ 8 [Done                                  ] FB: done


ECHO is off.
Successfully downloaded Toradex Easy Installer.
Press any key to continue . . .

This is my tdx-info:

$ sudo tdx-info

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           6.6.84-7.2.0-g87bfb710b6f1 #1-Torizon SMP PREEMPT Mon Mar 31 08:47:48 UTC 2025
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/157a467dd3b97eaebfbf6e17d0c8859fdd0abc1d397c637c6ecd808f79dc0260/0
Distro name:              NAME="Torizon OS"
Distro version:           VERSION_ID=7.2.0-build.13
Distro variant:           VARIANT="Docker"
Hostname:                 verdin-imx8mp-15229926
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Plus WB on Verdin Development Board
Toradex version:          0058 V1.1B
Serial number:            15229926
Processor arch:           aarch64
------------------------------------------------------------

The device was originally running Torizon 6, but I have upgraded it to Torizon 7 by updating the bootloader and then the OS itself. The device runs ok and I can flash it with the old TEZI 6.x. However, the latest TEZI 7.x is not detecting the device.

Can this problem be solved? Is my device stuck to TEZI 6.x? Is this a problem with TEZI 7.x?

Thank you.

ToradexAI · June 21, 2025, 8:20am

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer?

Hello! Thank you for providing detailed information about your situation.

Based on your description, you are using a Verdin iMX8M Plus module that was originally running Torizon OS 6.x and is now updated to Torizon OS 7.2.0, including the bootloader update. You are having issues with the recovery-windows.bat script from TEZI 7.2.0, but TEZI 6.8.2 works fine in recovery mode.

Key Points

TEZI 6.x works in recovery mode (uuu/U-Boot USB download).
TEZI 7.x fails with “Failure open usb device”.
You’ve updated both the bootloader and OS, and regular operation is fine.

Possible Causes

There are a few known changes from TEZI 6.x to 7.x:

TEZI 7.x uses a new configuration format and has additional requirements regarding the boot ROM and bootloader versions.
Some devices may require further steps to work with TEZI 7.x, especially if they were initially set up with older bootloaders or older SoC revisions.

The fact that TEZI 6.8.2 works while 7.2.0 does not suggests there may be a compatibility issue either with:

The SoC boot ROM version/hardware revision (less likely on a Verdin iMX8MP V1.1B module)
The current bootloader (however, you said you already upgraded it)
The universal update utility (uuu.exe) used in TEZI 7.x

Troubleshooting Steps

Check USB Connection & Driver
- Make sure no other application (or earlier uuu.exe) is holding the USB device.
- Try a different USB port/cable.
Ensure UUU/Driver is Updated
- TEZI 7.x ships with an updated uuu.exe. It’s possible your Windows system prefers an older WinUSB driver or that another uuu.exe is on your %PATH%.
- Try running the recovery-windows.bat from an administrative Command Prompt directly in the TEZI 7.2.0 extracted directory.
Device in Serial Download Mode
- Ensure the module is truly in USB serial download (recovery) mode during the process (following this guide).
Try uuu.exe Manually for Debugging
- Open a command prompt in the TEZI 7.2.0 directory.
- Run:
```
.\uuu.exe -v scripts\imx-bootloader-recovery-all.cmd
```
- This will show detailed output and may indicate at which step the failure occurs.

Is Your Device Stuck to TEZI 6.x?

No, your device is not permanently stuck! The fact that it boots Torizon OS 7.2.0 shows that it is capable of running with the new kernel and userland. The issue is likely a minor compatibility quirk with the recovery image or update tool in TEZI 7.x, not a permanent hardware or bootloader limitation.

Additional Steps If The Above Don’t Work

Consider updating to the very latest bootloader (U-Boot) if you performed a manual/partial upgrade before.
Test recovery mode from another Windows PC, or if possible, from a Linux host to see if it’s a USB driver quirk on your machine.
Double-check that you are using the correct TEZI image for the Verdin iMX8MP and that the download was not corrupted.

For more details, refer to:

Summary:
Your device is not permanently limited to TEZI 6.x. The issue is a minor compatibility quirk with either the recovery USB tool or hardware detection in TEZI 7.x on your system. Try the troubleshooting steps above to resolve the issue.

If you encounter a specific error while running uuu.exe -v, please share it and I can help analyze further.

Best regards,
Toradex AI Assistant.

References:

borco · June 21, 2025, 8:46am

Even though the AI Assistant is as always outdated, I have managed to grasp enough info to run the uue.exe in verbose mode.

This is the output of TEZI 7.2.0:

Downloading Toradex Easy Installer...
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.165-0-g7347a80

Build in config:
        Pctl     Chip            Vid     Pid     BcdVersion
        ==================================================
        SDPS:    MX8QXP          0x1fc9  0x012f  [0x0002..0xffff]
        SDPS:    MX8QM           0x1fc9  0x0129  [0x0002..0xffff]
        SDPS:    MX8DXL          0x1fc9  0x0147
        SDPS:    MX28            0x15a2  0x004f
        SDPS:    MX815           0x1fc9  0x013e
        SDPS:    MX865           0x1fc9  0x0146
        SDPS:    MX8ULP          0x1fc9  0x014a
        SDPS:    MX8ULP          0x1fc9  0x014b
        SDPS:    MX93            0x1fc9  0x014e
        SDPS:    MX95            0x1fc9  0x015d
        SDP:     MX7D            0x15a2  0x0076
        SDP:     MX6Q            0x15a2  0x0054
        SDP:     MX6D            0x15a2  0x0061
        SDP:     MX6SL           0x15a2  0x0063
        SDP:     MX6SX           0x15a2  0x0071
        SDP:     MX6UL           0x15a2  0x007d
        SDP:     MX6ULL          0x15a2  0x0080
        SDP:     MX6SLL          0x1fc9  0x0128
        SDP:     MX7ULP          0x1fc9  0x0126
        SDP:     MXRT106X        0x1fc9  0x0135
        SDP:     MX8MM           0x1fc9  0x0134
        SDP:     MX8MQ           0x1fc9  0x012b
        SDPU:    SPL             0x0525  0xb4a4  [0x0000..0x04ff]
        SDPV:    SPL1            0x0525  0xb4a4  [0x0500..0x9998]
        SDPV:    SPL1            0x1fc9  0x0151  [0x0500..0x9998]
        SDPU:    SPL             0x0525  0xb4a4  [0x9999..0x9999]
        SDPU:    SPL             0x3016  0x1001  [0x0000..0x04ff]
        SDPV:    SPL1            0x3016  0x1001  [0x0500..0x9998]
        FBK:                     0x066f  0x9afe
        FBK:                     0x066f  0x9bff
        FBK:                     0x1fc9  0x0153
        FB:                      0x0525  0xa4a5
        FB:                      0x18d1  0x0d02
        FB:                      0x3016  0x0001
        FB:                      0x1fc9  0x0152
        FB:                      0x0483  0x0afb
Wait for Known USB Device Appear...
>Start Cmd:CFG: FB: -vid 0x1b67 -pid 0x4000
>Okay (0.001s)
New USB Device Attached at 2:2
2:2>Start Cmd:SDPS: boot -f ../imx-boot-recoverytezi
100%2:2>Okay (1.391s)
New USB Device Attached at 2:2
2:2>Fail Failure open usb device(1.845e+16s)



ECHO is off.
Downloading Toradex Easy Installer failed...
Press any key to continue . . .

I have run the command both as a normal user and as admin. They show the same output. The commands were run from the extraction directory, so the uue.exe should be the one from the TEZI zip.

This is the verbose output from running recovery with TEZI 6.8.2:

Downloading Toradex Easy Installer...
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.165-0-g7347a80

Build in config:
        Pctl     Chip            Vid     Pid     BcdVersion
        ==================================================
        SDPS:    MX8QXP          0x1fc9  0x012f  [0x0002..0xffff]
        SDPS:    MX8QM           0x1fc9  0x0129  [0x0002..0xffff]
        SDPS:    MX8DXL          0x1fc9  0x0147
        SDPS:    MX28            0x15a2  0x004f
        SDPS:    MX815           0x1fc9  0x013e
        SDPS:    MX865           0x1fc9  0x0146
        SDPS:    MX8ULP          0x1fc9  0x014a
        SDPS:    MX8ULP          0x1fc9  0x014b
        SDPS:    MX93            0x1fc9  0x014e
        SDPS:    MX95            0x1fc9  0x015d
        SDP:     MX7D            0x15a2  0x0076
        SDP:     MX6Q            0x15a2  0x0054
        SDP:     MX6D            0x15a2  0x0061
        SDP:     MX6SL           0x15a2  0x0063
        SDP:     MX6SX           0x15a2  0x0071
        SDP:     MX6UL           0x15a2  0x007d
        SDP:     MX6ULL          0x15a2  0x0080
        SDP:     MX6SLL          0x1fc9  0x0128
        SDP:     MX7ULP          0x1fc9  0x0126
        SDP:     MXRT106X        0x1fc9  0x0135
        SDP:     MX8MM           0x1fc9  0x0134
        SDP:     MX8MQ           0x1fc9  0x012b
        SDPU:    SPL             0x0525  0xb4a4  [0x0000..0x04ff]
        SDPV:    SPL1            0x0525  0xb4a4  [0x0500..0x9998]
        SDPV:    SPL1            0x1fc9  0x0151  [0x0500..0x9998]
        SDPU:    SPL             0x0525  0xb4a4  [0x9999..0x9999]
        SDPU:    SPL             0x3016  0x1001  [0x0000..0x04ff]
        SDPV:    SPL1            0x3016  0x1001  [0x0500..0x9998]
        FBK:                     0x066f  0x9afe
        FBK:                     0x066f  0x9bff
        FBK:                     0x1fc9  0x0153
        FB:                      0x0525  0xa4a5
        FB:                      0x18d1  0x0d02
        FB:                      0x3016  0x0001
        FB:                      0x1fc9  0x0152
        FB:                      0x0483  0x0afb
Wait for Known USB Device Appear...
>Start Cmd:CFG: FB: -vid 0x1b67 -pid 0x4000
>Okay (0s)
New USB Device Attached at 2:2
2:2>Start Cmd:SDPS: boot -f ../imx-boot-recoverytezi
100%2:2>Okay (1.77s)
New USB Device Attached at 2:2
2:2>Start Cmd:FB: ucmd setenv fastboot_buffer 0x42e00000
2:2>Okay (0.011s)
2:2>Start Cmd:FB: download -f ../boot.scr
2:2>Okay (0.019s)
2:2>Start Cmd:FB: ucmd setenv fastboot_buffer 0x42e10000
2:2>Okay (0.011s)
2:2>Start Cmd:FB: download -f ../overlays.txt
2:2>Okay (0.019s)
2:2>Start Cmd:FB: ucmd setenv fastboot_buffer 0x44200000
2:2>Okay (0.01s)
2:2>Start Cmd:FB: download -f ../tezi.itb
2:2>Okay (1.184s)
2:2>Start Cmd:FB: acmd source 0x42e00000
2:2>Okay (0.007s)
2:2>Start Cmd:FB: done
2:2>Okay (0s)



ECHO is off.
Successfully downloaded Toradex Easy Installer.
Press any key to continue . . .

alex.tx · June 23, 2025, 9:11pm

You can update your device to Torizon 7.x using TEZI version 6.x or even 5.x. If you want to have TEZI 7.x installed on your module, you can first load TEZI 6.x and then use it to flash TEZI 7.x. I’m unable to reproduce the issue locally, but the behavior you’re observing may be related to USB signal integrity. I recommend trying a different USB cable, using another USB port on your development machine, and avoiding USB hubs, if applicable.

borco · July 11, 2025, 10:36am

I can install TEZI 7 on my device once TEZI 6 is up and running, but this is not what I need.

What I need is that, after

pressing the RECOVERY button,
connecting the power cord to the board,
releasing the RECOVERY button after more than 4 secs, then
running the recovery-windows.bat from the TEZI 7 archive on my Windows machine,

the recovery-windows.bat detects the device and the device starts with TEZI 7 loaded.

What I am forced to do now is to use recovery-windows.bat from the TEZI 6 archive to reset the device. This can be a potential maintenance issue if some devices have to be recovered with TEZI 6 and some with TEZI 7.

Changing the cables didn’t solve the problem. I am not using any hubs - the cable connects the dev board directly to the PC. And the recovery-windows.bat from TEZI 6 works just fine with the same hardware. So the problem is with your TEZI 7, in my opinion.

borco · July 11, 2025, 10:42am

I’ve just checked the newer Verdin-iMX8MP_ToradexEasyInstaller_7.3.0+build.7 and it behaves the same - it fails to detect the device.

BTW, I have checked this behavior with 2 distinct devices upgraded from toradex 6 to 7 mounted on 2 distinct dev board and the 2 device-board pairs exhibit the same behavior - TEZI 7 doesn’t detect the devices, while TEZI 6 detects them.

alex.tx · July 11, 2025, 5:36pm

It looks like you need to re-associate the Windows WinUSB driver with the U-Boot download gadget. Please refer to the recovery-windows.README file included in the Toradex Easy Installer (TEZI) package for detailed instructions.

Please note that all new Verdin iMX8M Plus modules are shipped pre-flashed with Toradex Easy Installer version 5.6.0. We recommend using this version for production programming of your custom image.
If consistency across devices is a concern, we suggest using Toradex Easy Installer 5.6.0 for the recovery procedures you described above to ensure a uniform setup.

borco · July 12, 2025, 7:13am

Manually associating the USB driver allowed TEZI 7 to work. Thank you.

borco · July 12, 2025, 7:53am

Just a side-note:

I had to manually associate the USB driver to each device that was upgraded individually.

Updating the driver for one device didn’t automatically make the other ones be recognized by TEZI 7.x (that is, every device that had not the driver manually updated appeared as a new USB download gadget under Other devices until its driver was manually set to ADB Device).

Is this the expected behavior? Can this be fixed so that manually setting the driver is not required at all?