Verdin i.MX95 can not start any more

Technical Support
,
1

Verdin i.MX95 can no longer start.

Verdin i.MX95 SoM can not start. No output appears to Debug port.

I tried to recover by writing a new TEZI image in recovery mode. But it failed, even on Windows or Ubuntu. I paste a log below,

```

$ lsusb
Bus 001 Device 006: ID 1fc9:015d NXP Semiconductors OO Blank 95

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

Success 0 Failure 1

1:5-09806E0B 1/ 1 [HID(W): LIBUSB_ERROR_NO_DEVICE (-4) ] SDPS: boot -f ../imx-boot-recoverytezi

Downloading Toradex Easy Installer failed…

```

Does anyone have any another suggestion for recovering it? Or is the SoM possibly damaged?

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.

The error message LIBUSB_ERROR_NO_DEVICE (-4) you’re encountering indicates a USB communication issue during the recovery process. Since your Verdin iMX95 is detected as “NXP Semiconductors OO Blank 95” in recovery mode, the hardware is likely functional.

Troubleshooting Steps

1. Verify Recovery Mode Setup

For the Verdin iMX95, ensure you’re entering recovery mode correctly. The recovery pin (SODIMM pin 246) needs to be pulled down with <1kΩ during initial power-on (cold boot) (1). Make sure there’s no bootable SD card inserted, as this can prevent the module from entering USB serial loader mode (2)(1).

2. USB Connection Issues

The LIBUSB_ERROR_NO_DEVICE error often occurs due to:

  • USB cable quality: Try a different high-quality USB cable
  • USB port: Switch to a different USB port on your host machine
  • USB hub interference: Connect directly to your computer, avoiding USB hubs
  • Power supply stability: Ensure stable power during the recovery process

3. Alternative Recovery Tools

The Universal Update Utility (uuu) is the standard tool for i.MX-based modules recovery (3). Since you’re experiencing issues with the standard recovery script, you can try:

  • Using the official uuu tool directly from NXP’s repository (3)
  • Trying different versions of the uuu tool
  • Running with elevated privileges (sudo on Linux)

4. Host System Considerations

Based on community experience, recovery success can vary between operating systems (4). If Windows recovery continues to fail, Ubuntu often provides better compatibility for the recovery process.

5. Hardware Verification

If all software approaches fail, the issue might be hardware-related. However, since your module is detected in recovery mode, this suggests the primary boot circuits are functional.

The fact that your Verdin iMX95 is recognized in recovery mode is a positive sign that the SoM is likely not permanently damaged. The issue appears to be related to the USB communication during the recovery process rather than fundamental hardware failure.

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 @takahiro_ii , if you are correctly entering recovery mode but still the board is not downloading TEZI, something could be damaged, specially if you already have experience loading TEZI. However, having the device showing in lsusb is a good sign. Make sure to reconnect all the cables and the SOM so that everything is correctly connected.

Do you have another SOM or another carrier board to try to load the recovery mode with different HW?

Alvaro.

4

Please verify your silicon revision of the imx95. If you have the A1 revision, the modern versions (7.5.0) of the easy installer and the Toradex operating systems won’t work. For A1 you need version 7.4.0 or below.

(Apparently, Toradex kept selling the A1 revisions for some time while the software colleagues already removed the support from the software.)

5

I have the A1 revision, and I flashed TEZI 7.5.0 onto it. I understand why the SoM is not working.
Is there any way to recover it?

6

If you are using a Verdin iMX95 V1.0A it has indeed an A1 silicon. V1.0B uses B0 silicon: Verdin iMX95 | Toradex Developer Center

For V1.0A just recover again using a TEZI up to 7.4.0.

More details on the A1 to B0 transition, including details on the SW version: i.MX95 A1 to B0 silicon revision Update Guide | Toradex Developer Center

You can find the TEZI image here:

7.3.0: https://artifacts.toradex.com:443/artifactory/tdxref-oe-prod-frankfurt/scarthgap-7.x.y/release/8/verdin-imx95/tdx-xwayland/tdx-reference-multimedia-image/oedeploy/Verdin-iMX95_Reference-Multimedia-Image-Tezi_7.3.0%2Bbuild.8.tar

7.4.0: https://artifacts.toradex.com:443/artifactory/tdxref-oe-prod-frankfurt/scarthgap-7.x.y/release/10/verdin-imx95/tdx-xwayland/tdx-reference-multimedia-image/oedeploy/Verdin-iMX95_Reference-Multimedia-Image-Tezi_7.4.0%2Bbuild.10.tar

Kind regards,
Alvaro.

1 Like