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 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? Are any initial provisioning steps or PMIC configuration requirements needed for newly assembled components that would already have been completed on a factory EVK? What is the recommended way to distinguish a USB transfer failure from a reset or boot-image execution failure at this SDPS: boot stage? 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? Which power rails, reset signals, clocks, and boot configuration signals should be checked first during hardware bring-up? 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. Re: Newly assembled i.MX8ULP 15 × 15 EVK-based SOM fails at SDPS boot with LIBUSB_ERROR_NO_DEVICE (- Hello,
1. Your command is correct for your design, and trusty-dual is a valid Android bootloader variant.
I suggest you use the -i option to test because it only loads U-Boot and enters Fastboot:
sudo ./uuu_imx_android_flash.sh -f imx8ulp -i
2. No, uses the same power-up sequence as POR/cold reset.
3. In both cases will show the LIBUSB_ERROR_NO_DEVICE error, even if the board is not able to inter in fastboot mode.
4. No, this should not be an issue at this stage, use the Cortex-A UART debug port. Here you can see if the board is not able to enter in fastboot mode.
5. Basically all, check the power-up sequence aligned with the documentation and all MISC signals in your design, including the correct clock signals in crystals/oscillators.
6. You could try flashing just the bootloader and enter to U-boot.
sudo ./uuu_imx_android_flash.sh -f imx8ulp -i
Best regards. Re: Newly assembled i.MX8ULP 15 × 15 EVK-based SOM fails at SDPS boot with LIBUSB_ERROR_NO_DEVICE (- Hello Jorge, Thank you for your response and troubleshooting recommendations. I tried the U-Boot-only command you suggested: sudo ./uuu_imx_android_flash.sh -f imx8ulp -i However, the operation still fails, and I have not been able to reach U-Boot/Fastboot. I would like to clarify the following differences between my assembled SOM and the i.MX8ULP 15 × 15 EVK reference design: Reference EVK PMIC: PCA9460AUK PMIC installed on my SOM: PCA9460BUKZ DDR installed on my SOM: Micron MT53D512M32D1ZW My understanding is that the MT53D512M32D1ZW supports LPDDR4 and LPDDR4X operation. I enabled both configuration paths while using the PCA9460BUKZ, but I am unsure whether this is the correct configuration. I suspect that the PMIC variant or its configuration may be contributing to the failure, although I have not confirmed this. Could you please clarify the following? Can this SOM boot using the PCA9460BUKZ instead of the PCA9460AUK? Could the difference between these PMIC variants explain the failure when running the command above? For the MT53D512M32D1ZW, should I enable only the LPDDR4 or LPDDR4X configuration path? Is enabling both paths appropriate? What voltage levels should I expect at the oscillator pins associated with the 24 MHz and 32.768 kHz crystals? I would like to verify these measurements during hardware bring-up. Which exact bootloader image should I use for this PMIC and DDR combination? Can I use the prebuilt image from android-14.0.0_2.2.0_image_8ulpevk, or do I need a customized image? Please confirm the appropriate image filename and whether the trusty-dual variant remains suitable. Thank you for your assistance. Re: Newly assembled i.MX8ULP 15 × 15 EVK-based SOM fails at SDPS boot with LIBUSB_ERROR_NO_DEVICE (- Hi everyone, I am experiencing a persistent boot loop/failure when trying to run Android on my NXP i.MX board. Interestingly, when I flash a standard Yocto image to the exact same board, it boots perfectly fine without any issues. However, switching over to Android causes it to crash during the early boot sequence. I have attached my complete boot log below. Could anyone help me analyze this log to point out what is failing? I suspect it might be related to partition tables, U-Boot environment variables, or AVB configuration differences between the two operating systems, but I would really appreciate an expert eye. Thank you.
View full article