How to flash the iMX95 Verdin Development Board V1.1F

Hi , I had recently bought the Verdin Development Board V1.1F with the Verdin IMX95 SOM from Toradex. I am trying to flash the kit using the easy installer and I am facing the following issue.

rithika@ECON002576L:~/Downloads/nightly_95/Verdin-iMX95_ToradexEasyInstaller_7.5.0-devel-20260107+build.415$ sudo ./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

3:3-2158A523 1/ 1 [HID(W): LIBUSB_ERROR_NO_DEVICE (-4) ] SDPS: boot -f ../imx-boot-recoverytezi

Downloading Toradex Easy Installer failed…
rithika@ECON002576L:~/Downloads/nightly_95/Verdin-iMX95_ToradexEasyInstaller_7.5.0-devel-20260107+build.415$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0c45:6d1d Microdia Integrated_Webcam_HD
Bus 003 Device 002: ID 27c6:639c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 003 Device 038: ID 1fc9:015d NXP Semiconductors OO Blank 95
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
rithika@ECON002576L:~/Downloads/nightly_95/Verdin-iMX95_ToradexEasyInstaller_7.5.0-devel-20260107+build.415$ sudo ./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

3:1-2158A523 1/ 1 [HID(W): LIBUSB_ERROR_NO_DEVICE (-4) ] SDPS: boot -f ../imx-boot-recoverytezi

Downloading Toradex Easy Installer failed…

How to resolve it . Thanks

1 Like

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 you’re encountering is a LIBUSB_ERROR_NO_DEVICE (-4) during the recovery process for your Verdin iMX95. This typically indicates a USB communication issue during the Easy Installer download process.

Troubleshooting Steps

1. Verify Recovery Mode Setup

Ensure your Verdin iMX95 is properly in recovery mode(1):

  • Power off the module completely
  • Set the recovery mode jumpers/switches correctly on your Development Board
  • Power on while maintaining recovery mode

2. USB Connection Issues

From your lsusb output, I can see the device is detected as ID 1fc9:015d NXP Semiconductors OO Blank 95, which indicates the module is in recovery mode. However, the USB communication is failing.

Try these steps:

  • Use a different USB cable (preferably a high-quality, shorter cable)
  • Try a different USB port on your computer
  • Ensure you’re using a USB 2.0 port rather than USB 3.0 if possible

3. Permission and System Issues

The error might be related to USB permissions or system configuration:

# Check if your user is in the dialout group
groups $USER

# If not in dialout group, add yourself:
sudo usermod -a -G dialout $USER
# Then log out and log back in

4. Alternative Recovery Methods

If the standard recovery continues to fail, you can try the Universal Update Utility (uuu) approach as mentioned in the documentation(2). The uuu tool is designed specifically for i.MX-based modules recovery purposes(2).

5. Hardware Verification

Since you mentioned this is a recently purchased board:

  • Verify all connections are secure
  • Check that the Development Board power supply is adequate
  • Ensure no other processes are accessing the USB device

6. Recovery Mode Instructions

You might need to enter recovery mode following the specific instructions for your hardware(1). Check the Recovery Mode Instructions(1).

If these steps don’t resolve the issue, the problem might be related to the specific Easy Installer version or a hardware compatibility issue with your development setup.

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.

I had the same issue and for me it was because of the silicon revision. The 7.5.0-devel installer lacks support for the A1 silicon. V7.4.0+build.8 works on A1. Can you check which silicon you have?

Silicon Revision Compatibility Issue

Excellent point! This is indeed a known compatibility issue with the i.MX95 silicon revisions. The error you’re experiencing is likely related to silicon revision compatibility between your hardware and the Easy Installer version.

Check Your Silicon Revision

To determine which silicon revision you have, you can check your Verdin iMX95 module revision(1):

  • V1.0A modules use A1 silicon revision(1)
  • V1.0B modules use B0 silicon revision(1)

Compatibility Matrix

According to the official documentation, here’s the compatibility for Torizon OS(1):

Module/Silicon Revision Scarthgap (BSP 7) Further major releases
V1.0A - A1 :white_check_mark: Supported Up to 7.4.0(1) :cross_mark: Not supported(1)
V1.0B - B0 :white_check_mark: Supported Starting from 7.5.0(1) :white_check_mark: Supported(1)

Resolution

Based on the compatibility matrix(1):

If you have A1 silicon (V1.0A):

  • Use Easy Installer version 7.4.0 or earlier(1)
  • Version 7.5.0-devel that you’re trying to use is not supported for A1 silicon(1)

If you have B0 silicon (V1.0B):

  • Version 7.5.0-devel should work
  • If it doesn’t, there might be another issue

Next Steps

  1. Identify your module revision by checking the physical label on your Verdin iMX95
  2. Download the appropriate Easy Installer version based on your silicon revision
  3. Use version 7.4.0+build.8 if you have A1 silicon as suggested

This silicon transition approach provides a practical transition window between hardware and software versions, minimizing disruption as customers migrate to newer releases(1).

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.

Thank you for your input, it really helped me.
I was able to install the easy installer. The Display is not up, this is my minicom log.
Starting kernel …

[ 0.122542] cpu cpu0: EM: invalid power: 0
[ 0.245661] rtc-ds1307 0-0032: hctosys: unable to read the hardware clock
[ 0.255327] debugfs: Directory ‘wakeup’ with parent ‘pm_genpd’ already present!
[ 0.262672] debugfs: Directory ‘vpu’ with parent ‘pm_genpd’ already present!
[ 0.269719] debugfs: Directory ‘npu’ with parent ‘pm_genpd’ already present!
[ 0.269724] debugfs: Directory ‘noc’ with parent ‘pm_genpd’ already present!
[ 0.283834] debugfs: Directory ‘m7’ with parent ‘pm_genpd’ already present!
[ 0.290821] debugfs: Directory ‘gpu’ with parent ‘pm_genpd’ already present!
Running /etc/rc.local…
Toradex Easy Installer 7.4.0-devel-202508+build.11 ()
Starting udev
[ 3.076304] debugfs: File ‘:soc:display-controller@4b400000’ in directory ‘domains’ already present!
[ 3.085543] debugfs: File ‘:soc:display-controller@4b400000’ in directory ‘domains’ already present!
[ 3.101640] debugfs: File ‘:soc:display-controller@4b400000’ in directory ‘domains’ already present!
[ 3.111156] debugfs: File ‘:soc:display-controller@4b400000’ in directory ‘domains’ already present!
[ 3.134091] mali 4d900000.gpu: recalculation of power model mali-simple-power-model returned error -517
[ 3.143790] mali 4d900000.gpu: IPA initialization failed
[ 3.149140] mali 4d900000.gpu: Continuing without devfreq
[ 3.152089] pcieport 0002:01:01.0: of_irq_parse_pci: failed with rc=-22
[ 3.169839] imx95-pixel-interleaver 4b0d0000.bridge: Failed to create device link (0x180) with 4b400000.display-controller
[ 3.199334] usbmisc_imx 4c200200.usbmisc: vbus is error
[ 3.204827] usbmisc_imx 4c200200.usbmisc: Error occurs during detection: -22
[ 3.285923] tpm tpm0: A TPM error (256) occurred attempting the self test
[ 3.753983] fsl_enetc4 0001:00:10.0: Failed to get PHY mode
System time was Thu Jan 1 00:00:04 UTC 1970.
Setting the System Clock using the Hardware Clock as reference…
hwclock: RTC_RD_TIME: Invalid argument
System Clock set. System local time is now Thu Jan 1 00:00:04 UTC 1970.
Fri Mar 9 12:34:56 UTC 2018
Saving the System Clock time to the Hardware Clock…
Hardware Clock updated to Fri Mar 9 12:34:56 UTC 2018.

Welcome to the Toradex Easy Installer

This is a Linux based installer for Toradex modules. Currently, the installer
does not have a serial console interface. You can use the Toradex Easy Installer
via any of the available display interfaces using USB mouse/keyboard or via a
network connection using VNC. Use:

ip addr show

to display the Ethernet IP address(es) or use USB NCM at IP 192.168.11.1.

Check our documentation at:

I have connected the HDMI to the Display. What do we configure next and flash the kit.

I can’t help with the Verdin Development Board. I’m running the Verdin IMX95 SOM on a Dahlia board. There, the video output is not on the HDMI connector, but on the (secondary) HDMI provided by the “DSI to HDMI” plugin board. It might be possible that the display needs to be connected before booting. Since we are using the same SOM it is possible that the video out is on the DSI for you as well.

Hi @Harish-23 , I saw in another thread that you were able solve this problem. Would you mind marking the relevant tips as being the solution so others can reference to it? You can do so by clicking the check mark icon under each post. Thank you.

Hi @doespaddel , Sure will do. Thank you for your input. I was able to use HDMI only with the DSI to HDMI Adapter. I flashed the BSP after this but currently facing the following issue. The log is recursive and continuous until I power off.
U-Boot SPL 2024.04-7.4.0+git.cf50ed467107 (Aug 05 2025 - 15:22:26 +0000)
SOC: 0xa1009500
LC: 0x40010
Trying to boot from USB SDP
Failed to configure default pinctrl
“Synchronous Abort” handler, esr 0x96000010
elr: 000000002049816c lr : 00000000204974b4
x 0: 000000004c200000 x 1: 00000000932002d8
x 2: 0000000000000001 x 3: 00000000fffffffd
x 4: 0000000000000000 x 5: 0000000000000002
x 6: 0000000000000001 x 7: 0000000000000003
x 8: 000000002049ff28 x 9: 000000000000036c
x10: 0000000000000000 x11: 000000002049ff28
x12: 0000000000000018 x13: 0000000000000000
x14: 0000000000000000 x15: 0000000000000000
x16: 0000000020493684 x17: 0000000000000000
x18: 00000000204c5df0 x19: 00000000932002d8
x20: 0000000093200050 x21: 00000000932001d0
x22: 00000000204c7348 x23: 000000004c200000
x24: 0000000093200268 x25: 0000000000000000
x26: 00000000204999f7 x27: 0000000020499000
x28: 00000000204999df x29: 00000000204c5b60

Code: a9be7bfd 910003fd a90153f3 aa0103f3 (b9418401)
Resetting CPU …

resetting …

Did you face any issue like this .
Downloaded and using this for Easy installer since mine is Version 1.0A - Verdin-iMX95_ToradexEasyInstaller_7.4.0+build.8

The BSP I am flashing is – Verdin-iMX95_Reference-Multimedia-Image-Tezi_7.4.0+build.10.tar

No, sorry, I never faced this specific issue.
Currently, I have the same image installed, and it works for me (same SoM, also silicon revision A1, but on a Dahlia carrier board). So, the issue might be carrier board related.

I’m not sure what USB SDP refers to. I know that abbreviation as “standard downstream port” in the context of usb power delivery, but I don’t understand why the U-Boot loader should want to boot from it. Do you have anything connected to USB or an sdcard inserted?

For reference, this is what a normal boot process looks for me:

U-Boot SPL 2024.04-7.4.0+git.cf50ed467107 (Aug 05 2025 - 15:22:26 +0000)
SOC: 0xa1009500
LC: 0x40010
Trying to boot from MMC1
Primary set selected
Load image from MMC/SD 0xbe800
NOTICE:  BL31: v2.10.0  (release):lf-6.6.52-2.2.1-dirty
NOTICE:  BL31: Built : 06:40:36, Jul  7 2025


U-Boot 2024.04-7.4.0+git.cf50ed467107 (Aug 05 2025 - 15:22:26 +0000)

CPU:   i.MX95 rev1.1 at 1800MHz
CPU:   Automotive temperature grade (-40C to 125C) at 58C
LM Boot reason: unused, origin: -1, errid: -1
LM shutdown reason: unused, origin: -1, errid: -1
DRAM:  Delete node /pcie@4ca00000/ethernet@10,0
7.8 GiB
Core:  323 devices, 32 uclasses, devicetree: separate
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Model: Toradex 0089 Verdin iMX95 Hexa 8GB WB IT V1.0A
Serial#: [redacted]

BuildInfo:
  - SM firmware Build 509, Commit f73086cf, Sep 22 2025 16:22:58
  - ELE firmware version 2.0.2-4e395675

Setting variant to wifi
flash target is MMC:0
Net:   WARNING: no MAC address assigned for MAC0
imx_get_mac_from_fuse: fuse read err: 0
eth0: enetc-0 [PRIME]Could not get PHY for emdio-0: addr 7

Fastboot: Normal
Normal Boot
Hit any key to stop autoboot:  0

Thank you for your input. Will check on this.

Also are you building the kernel-source in local and replacing the Image.gz ,dtb and modules? Can you please let me know.

No, I’ve not touched the kernel itself.