Issues using `nxpuuu` to boot an image on i.MX93

[oliben]

Hello,

I'm trying to deploy an AHAB image onto my custom board embedding an i.MX93.
I am following this user guide and have reached the  step Image Download step.

Unfortunately, `UUU` appears to be failing:

```

$ nxpuuu -vv -us F06FBE4B3F6142C2 write -f mimx9352 -b emmc ahab_image.bin

spsdk.exceptions.SPSDKError: SPSDK: run_script: returned with exit code -1 and status 0.

```

The same thing happens if I try to run `nxpuuu` with the following script:

```

uuu_version 1.2.39

SDPS: boot -f "ahab_image.bin"

```

If I now try with `uuu` instead, I get a LIBUSB error:

```

3:534-F06FBE 1/ 1 [HID(W): LIBUSB_ERROR_IO (-1) ] SDPS: boot -f "ahab_image.bin"

```

However, the same commands with a different, non-AHAB image, succeed:

```

uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.201-0-g727fc2b

Success 0 Failure 0


3:534-F06FBE 1/ 1 [=================100%=================] SDPS: boot -f "imx-boot-imx93.bin-flash_singleboot"

```

[nxf46245]

Hi, thanks for the report and the logs.

A couple of quick clarifiers and checks usually resolve this kind of early SDPS failure on i.MX93:

1) What are you trying to do exactly?

Are you:

• (A) building a new imx bootloader image (SPL + ELE/DDR binaries + ATF/U‑Boot, etc.), or
• (B) taking an existing bootable image (e.g., imx-boot-...bin-flash_singleboot) and just signing it to enable the secure boot?

If it’s (B), the simplest path is to sign the already bootable image with SPSDK’s nxpimage ahab sign (i.e., sign-in-place) rather than rebuilding containers from scratch. (see the example: https://spsdk.readthedocs.io/en/latest/examples/ahab/imx95/imx95_ahab_sign.html)

Verify first

nxpimage bootable-image verify -f mimx9352 -b imx-boot-imx93.bin-flash_singleboot -m serial_downloader

Then sign-in-place

nxpimage ahab sign -f mimx9352 -b imx-boot-imx93.bin-flash_singleboot -o signed_flash.bin -c sign_config.yaml

This approach keeps the image layout that we already know SDPS can load on your board.

2) Why does SDPS abort (LIBUSB_ERROR_IO / exit -1) with your ahab_image.bin?

The symptoms you see usually mean the SoC resets very early during download/hand‑off, which breaks the USB link and shows up as LIBUSB_ERROR_IO in uuu. Common causes:

• ELE firmware / silicon revision mismatch
  Ensure the ELE firmware packaged in your primary container matches your i.MX93 silicon revision (A0 vs A1).
• DDR training / board‑specific DDR config
  On custom boards, if DDR init isn’t stable (timing/drive strength/ODT) the SPL/ELE won’t be able to initialize memory and the device resets early. Try a lower data rate/more conservative config from the DDR Tool to see if behavior changes, and validate layout/voltages.
• USB/host layer sanity
  Still, do make sure you’re on a direct USB port (no hub), good cable, and a recent libuuu

1. Capture UART ROM/ELE output during the SDPS: boot attempt — this is the fastest way to see whether you’re hitting ELE authentication vs DDR bring‑up. Keep UART mapping/baud as on EVK unless you’ve already re‑routed consoles.
2. Verify the binary locally before download (please note that verifier just checks the structure of the image, not if the images (like DDR, SPL or ELE FW are valid):

nxpimage bootable-image verify -f mimx9352 -b ahab_image.bin -m serial_downloader

Regards,

Marek Vitula