iMX95 Torizon Easy Installer stuck

Technical Support
1

Hi all,

I am trying to get the Verdin iMX95 Hexa 8GB WB IT V1.0A up and running with my own image. But the Torizon Easy Installer (Verdin-iMX95_ToradexEasyInstaller_7.4.0+build.8) is getting stuck on download with the following output.

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

Success 0    Failure 0


1:3-DED5508E 3/ 3 [=================100%=================] SDPV: jump

I’m looking forward to read any ideas and suggestions to solve this issue.

Kind regards

KDehren

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 issue you’re experiencing with Toradex Easy Installer getting stuck at the “SDPV: jump” stage on your Verdin iMX95 suggests the download process completed successfully, but the module may not be transitioning properly to the next boot stage.

Here are some troubleshooting steps to help resolve this:

Check Your Setup

  1. Verify USB Connection: Ensure you’re using a reliable USB cable and that it’s connected to the correct USB port on your carrier board that supports recovery mode.

  2. Power Cycle: Try a complete power cycle of the module:

    • Disconnect power completely
    • Wait a few seconds
    • Reconnect power and retry the Easy Installer download

  3. Check Recovery Mode: Confirm the module is properly entering recovery mode before attempting to load Easy Installer.

Try Alternative Approaches

If the issue persists, you might want to consider:

  • Using a different USB port or cable
  • Checking if there are any BIOS/firmware updates needed for your host PC’s USB controller
  • Verifying that the uuu tool version is compatible with the iMX95 platform

Additional Information Needed

To provide more specific guidance, could you clarify:

  • What operating system are you running on your host PC?
  • Are you using the official Toradex recovery scripts, or a custom approach?
  • Have you successfully loaded Easy Installer on this module before, or is this the first attempt?

You can also gather detailed information about your module using the tdx-info command once you get the system running. More details are available at: Getting Device Information with Tdx-Info | Toradex Developer Center

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
  • The Host PC uses Windows 11
  • I’ve tested several USB cables
  • I am using the official recovery script
  • Sometimes I am able to load the Easy Installer successfully
4

Thank you for the additional details. Since you’re on Windows 11 and experiencing intermittent success with loading Easy Installer, this points to a USB driver issue that’s common on Windows systems.

Windows 11 USB Driver Configuration

Based on your symptoms and platform, the most likely cause is that Windows 11 isn’t correctly recognizing the USB device after the initial download completes(1). This is a known issue documented in the Toradex Easy Installer troubleshooting section(1).

Solution Steps

  1. Install the Correct USB Driver:

    • When the recovery script gets stuck at “SDPV: jump”, check your Windows Device Manager
    • Look for an unknown USB device or a device labeled “USB Download Gadget”(1)
    • You need to manually install the WinUSB Device driver with ADB device configuration(1)

  2. Driver Installation Process(1):

    • Open Device Manager
    • Right-click on the USB device and select “Update Driver”
    • Choose “Browse my computer for drivers” → “Let me pick from a list of available drivers on my computer”
    • Uncheck “Show compatible hardware” if present
    • Select “Universal Serial Bus Devices”
    • Choose “WinUSB Device” → “ADB device”
    • Click “Next” and accept the warning

  3. Alternative Driver Option:

    • Some users have reported success using the Android Bootloader Interface driver instead of the Android ADB Interface(2)
    • If the ADB device approach doesn’t work, try this alternative

Additional Troubleshooting

  • Avoid USB Hubs: Connect directly to your PC’s USB port(1)
  • Avoid Virtual Machines: Run the recovery script directly on Windows, not in a VM(1)
  • USB 2.0 vs 3.0: Try different USB ports, preferably USB 2.0 ports if available

Since you mentioned the Easy Installer loads successfully sometimes, this confirms it’s likely a driver enumeration timing issue on Windows 11 rather than a hardware problem.

You can find detailed troubleshooting steps with screenshots in the official documentation here: Loading Toradex Easy Installer - Troubleshoot on Windows(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.

5

After a couple of test runs I’ve managed to load Easy Installer and install my image. While trying to run this image I’ve noticed the exact same behavior. The device gets stuck during boot with the following (complete) log

U-Boot SPL 2024.04-7.4.0-devel+git.cf50ed467107 (Jan 01 1970 - 00:00:00 +0000)
SOC: 0xa1009500
LC: 0x40010
Trying to boot from MMC1
Primary set selected
Load image from MMC/SD 0xc9000
NOTICE:  BL31: v2.10.0  (release):android-15.0.0_1.0.0-rc3-0-g1b27ee3ed-dirty
NOTICE:  BL31: Built : 00:00:00, Jan  1 1970

while sometimes the device boots as expected all the way up to this final lines of output


Torizon OS with PREEMPT_RT 7.4.0-devel-202509+build.13 verdin-imx95-12594250 ttyLP2

verdin-imx95-12594250 login:
6

Dear @KDehren,

Thank you for bringing this up.
Glad you managed to get Easy Installer loaded and your image installed.

Regarding the intermittent boot hang at BL31, there are a couple of things to be aware of with your setup:

  • Your Verdin iMX95 V1.0A is based on the A1 silicon stepping, which has known limitations. NXP has since released the B0 revision with improvements. You can find details on the transition and what it means for your module here: i.MX95 A1 to B0 silicon revision Update Guide | Toradex Developer Center
    This early revision may contribute to the intermittent behavior you’re seeing.
  • The iMX95 can be sensitive to thermals, especially without proper heat dissipation. If you’re running the module without a heatsink, I’d strongly recommend adding one. Thermal throttling or instability during early boot stages could explain why the device sometimes hangs and sometimes boots fine.
  • The PREEMPT_RT build you’re using (7.4.0-devel-202509+build.13) has more limited test coverage on the iMX95 at this stage. If you’re able to test with the standard (non-RT) image, that would help isolate whether the issue is RT-kernel specific or more general.

Best regards,
Collin