2418495_en-US

[#1]

Newly assembled i.MX8ULP 15 × 15 EVK-based SOM fails at SDPS boot with LIBUSB_ERROR_NO_DEVICE (-4)

Hello NXP Community,

I am bringing up a newly assembled SOM based on the i.MX8ULP EVK 15 × 15 design. I used the reference SOM and had the components assembled onto the board.

When attempting to flash the Android prebuilt images using UUU, the processor is detected in serial download mode, but the operation fails during the initial SDPS: boot command.

Software environment

• Host: Linux
• Android image package: android-14.0.0_2.2.0_image_8ulpevk
• UUU version displayed: libuuu_1.5.179-0-g02da3bf
• Intended storage target: eMMC

USB detection

Running:

uuu -lsusb

shows:

Connected Known USB Devices
Path   Chip     Pro     Vid      Pid      BcdVersion
3:1    MX8ULP   SDPS:   0x1FC9   0x014A   0x0001

Main flashing attempt

From the Android image directory, I ran:

sudo ./uuu_imx_android_flash.sh -f imx8ulp -a -e -t emmc -u trusty-dual

The script identifies the supported Android partition features, generates the UUU script, and invokes UUU. It then fails with:

Success 0    Failure 1

HID(W): LIBUSB_ERROR_NO_DEVICE (-4)
SDPS: boot -f u-boot-imx8ulp-evk-uuu.imx24274

The filename above is shown as it appears in the attached screenshot.

Other attempts

I also tried:

sudo uuu -b emmc u-boot-imx8ulp.imx

What is currently known

• UUU detects the processor as MX8ULP using the SDPS protocol.
• The failure occurs during the initial boot-image download.
• The captured output does not show progression to Fastboot or eMMC partition flashing.
• I have not yet established whether the failure is caused by the image/configuration, USB communication, a board reset, power sequencing, or an assembly issue.
• I still need to verify the exact assembled processor, DDR, and PMIC part numbers against the reference BOM.

Questions

1. Is the command above and the trusty-dual image variant appropriate for initial flashing of a newly assembled SOM based on the i.MX8ULP 15 × 15 EVK design?
2. Are any initial provisioning steps or PMIC configuration requirements needed for newly assembled components that would already have been completed on a factory EVK?
3. What is the recommended way to distinguish a USB transfer failure from a reset or boot-image execution failure at this SDPS: boot stage?
4. Could a DDR configuration mismatch cause this particular failure at this stage? What UART output or other evidence would help determine whether DDR initialization has been reached?
5. Which power rails, reset signals, clocks, and boot configuration signals should be checked first during hardware bring-up?
6. Is there a recommended minimal boot image or diagnostic procedure for checking initial boot and DDR operation before attempting a complete Android flash?

Thank you.