After donwloading EasyInstaller_.2.0 build 9, it finds the USB and downloads the code , but the second stage doesn’t work. “Failure open usb device.”
The problem is that while I may be able to use earlier ones, the board no longer displays any files and easyloader says it is downloading the list continuously.
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 reaching out regarding your issue with the Toradex Easy Installer. Based on your description, it seems you are encountering the “Failure open usb device” error during the second stage, and also experiencing continuous downloading in the Easy Installer UI.
Here are some troubleshooting steps you can follow:
-
USB Connection Troubleshooting
- Try using a different USB port on your PC, preferably a non-USB3 port (reference).
- Avoid using USB hubs between your PC and the Toradex board’s USB OTG port (reference).
- If you are using a virtual machine, try running the Easy Installer from a native (non-VM) environment.
- Swap your USB cable for a different one to rule out potential cable issues (reference).
-
Continuous Downloading Issue
- Disconnect and reconnect the Ethernet cable to force a fresh DHCP request (reference).
- Make sure your DHCP server is providing full network configuration, including internet access, so the Easy Installer can download the list of available images (reference).
-
Check for Debug Logs
- Connect to the serial console on UART1 (also known as UART_A) and check the log file at
/var/volatile/tezi.logfor detailed error messages (reference).
- Connect to the serial console on UART1 (also known as UART_A) and check the log file at
Following these steps should help address both the USB device detection failure and the continuous downloading issue. If you can provide details about your host operating system, Toradex module, and carrier board, I can tailor further suggestions to your setup.
Let me know if these steps resolve your issue or if you need more specific guidance.
Best regards,
Toradex AI Assistant.
Please clarify the Easy Installer version. May be you meant 7.2.0 ?
Please provide a full output from the dev computer where you run recovery-xxx script together with log from the serial debug output of Ivy board.
Which exactly earlier version of the Toradex Easy Installer your were able to download?
@alex.tx
Yes, 7.2.0.
I have builds 5.7.2, 5.7.3, 5.7.5, 6.6.0, 6.8.1 and 7.2.0. they all work except 7.2.0. Here is the output:
C:\Code\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:12332 1/ 0 [Failure open usb device ]
ECHO is off.
Downloading Toradex Easy Installer failed…
Press any key to continue . . .
Could you please fully specify version of the SOM you are using (for example : 0058 Verdin iMX8M Plus Quad 4GB WB IT V1.0B )
Some changes was done to U_Boot so manual Windows driver association is required . Please check this reply - https://community.toradex.com/t/malllow-carrier-with-verdin-not-booting/28378/14
Although this applies to the Verdin AM62, the same driver configuration steps in Windows are also required for the Verdin iMX8M
Hi @alex.tx , For some reason, your link sends me to a list of issues, none of which match what you are referring to that I can see.
Steve
What “list of issues” are you referring to?
I was able to reproduce the problem you reported on one of my PCs. The “second stage” of the 7.2.0 process fails because recent changes in U-Boot prevent it from being automatically associated with the WinUSB driver.
As a result, after the “first stage,” you’ll see an unrecognized USB device in Device Manager. You need to manually associate this device with the WinUSB driver, as explained in the link I previously shared.
@alex.tx
This is what I get when I go to your link. Is this what you intended? I am not disputing your fix and why, I just don’t see anything discussing that issue here.
Steve
