$ 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?
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.
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.
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.
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:
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.
