Error while flashing iMX95 Verdin Evaluation kit

Technical Support
,
1

Hi , I am trying to flash my iMX95 Verdin Evaluation kit and I am facing this error. The SW2 switch is in 1010 as per the getting started and the board goes into recovery mode properly. I have downloaded the files to flash from the NXP website provided in the document. The following is the error I get, can you please guide me in resolving this

$ sudo ./uuu -v -b emmc_all ./imx-boot-imx95-19x19-verdin-sd.bin-flash_all ./imx-image-full-imx95evk.wic
[sudo] password for harish:
uuu (Universal Update Utility) for nxp imx chips – libuuu_1.5.163-0-g534bf1f

Build in config:
Pctl Chip Vid Pid BcdVersion

SDPS: MX8QXP 0x1fc9 0x012f [0x0002..0xffff]
SDPS: MX8QM 0x1fc9 0x0129 [0x0002..0xffff]
SDPS: MX8DXL 0x1fc9 0x0147
SDPS: MX28 0x15a2 0x004f
SDPS: MX815 0x1fc9 0x013e
SDPS: MX865 0x1fc9 0x0146
SDPS: MX8ULP 0x1fc9 0x014a
SDPS: MX8ULP 0x1fc9 0x014b
SDPS: MX93 0x1fc9 0x014e
SDPS: MX95 0x1fc9 0x015d
SDP: MX7D 0x15a2 0x0076
SDP: MX6Q 0x15a2 0x0054
SDP: MX6D 0x15a2 0x0061
SDP: MX6SL 0x15a2 0x0063
SDP: MX6SX 0x15a2 0x0071
SDP: MX6UL 0x15a2 0x007d
SDP: MX6ULL 0x15a2 0x0080
SDP: MX6SLL 0x1fc9 0x0128
SDP: MX7ULP 0x1fc9 0x0126
SDP: MXRT106X 0x1fc9 0x0135
SDP: MX8MM 0x1fc9 0x0134
SDP: MX8MQ 0x1fc9 0x012b
SDPU: SPL 0x0525 0xb4a4 [0x0000..0x04ff]
SDPV: SPL1 0x0525 0xb4a4 [0x0500..0x9998]
SDPV: SPL1 0x1fc9 0x0151 [0x0500..0x9998]
SDPU: SPL 0x0525 0xb4a4 [0x9999..0x9999]
SDPU: SPL 0x3016 0x1001 [0x0000..0x04ff]
SDPV: SPL1 0x3016 0x1001 [0x0500..0x9998]
FBK: 0x066f 0x9afe
FBK: 0x066f 0x9bff
FBK: 0x1fc9 0x0153
FB: 0x0525 0xa4a5
FB: 0x18d1 0x0d02
FB: 0x3016 0x0001
FB: 0x1fc9 0x0152
FB: 0x0483 0x0afb

Run built-in script:

uuu_version 1.4.149

@_flash.bin | bootloader, which can extract from wic image

@_image [_flash.bin] | wic image burn to emmc.

This command will be run when i.MX6/7 i.MX8MM, i.MX8MQ

SDP: boot -f ./imx-boot-imx95-19x19-verdin-sd.bin-flash_all -scanlimited 0x800000

This command will be run when ROM support stream mode

i.MX8QXP, i.MX8QM

SDPS: boot -scanterm -f ./imx-boot-imx95-19x19-verdin-sd.bin-flash_all -scanlimited 0x800000

These commands will be run when use SPL and will be skipped if no spl

SDPU will be deprecated. please use SDPV instead of SDPU

{

SDPU: delay 1000
SDPU: write -f ./imx-boot-imx95-19x19-verdin-sd.bin-flash_all -offset 0x57c00
SDPU: jump -scanlimited 0x800000

}

These commands will be run when use SPL and will be skipped if no spl

if (SPL support SDPV)

{

SDPV: delay 1000
SDPV: write -f ./imx-boot-imx95-19x19-verdin-sd.bin-flash_all -skipspl -scanterm -scanlimited 0x800000
SDPV: jump -scanlimited 0x800000

}

FB: ucmd setenv fastboot_dev mmc
FB: ucmd setenv mmcdev ${emmc_dev}
FB: ucmd mmc dev ${emmc_dev}
FB: flash -raw2sparse all ./imx-image-full-imx95evk.wic
FB: flash -scanterm -scanlimited 0x800000 bootloader ./imx-boot-imx95-19x19-verdin-sd.bin-flash_all
FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi;
FB: ucmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0
FB: done

Wait for Known USB Device Appear…
New USB Device Attached at 3:1
3:1>Start Cmd:SDPS: boot -scanterm -f ./imx-boot-imx95-19x19-verdin-sd.bin-flash_all -scanlimited 0x800000
3:1>Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.01s)

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

I cannot find specific information about flashing the i.MX95 Verdin Evaluation Kit or troubleshooting the LIBUSB_ERROR_NO_DEVICE error you’re encountering in the available Toradex documentation sources.

The error you’re seeing suggests a USB communication issue between the host computer and the i.MX95 Verdin EVK during the flashing process. While I can see from the sources that the i.MX95 Verdin Evaluation Kit is available and features the NXP i.MX95 processor with various connectivity options(1)(2), the specific flashing procedures and troubleshooting steps for this particular module are not covered in the provided documentation.

Potentially Helpful Resources

Since I cannot provide the specific solution based on the available sources, I recommend checking these potentially useful resources:

Would you like me to provide a general answer based on my knowledge about common USB flashing issues with embedded development boards?

Best regards,
Toradex AI Assistant.

3

Hi @Harish-23 ,

Can you paste the error logs in a text file and attach it?

4

Hi thank you for your reply, the below error_log.txt file contains the log.

error_log.txt (3.0 KB)

I am following the iMX95 Verdin Evaluation document and following the steps

  1. I am powering On the kit in recovery mode,

  2. The board is getting detected in recovery mode
    sudo uuu -lsusb
    uuu (Universal Update Utility) for nxp imx chips – libuuu_1.5.233-0-g79ce7d2

Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion Serial_no

3:1 MX95 SDPS: 0x1FC9 0x015D 0x0001 BC2398A298DB4C86

  1. I am running the script mentioned in the document for the beta release.
    sudo ./uuu -v -b emmc_all ./imx-boot-imx95-19x19-verdin-sd.bin-flash_all \ ./imx-image-full-imx95evk.wic

  2. I am having the files in the same directory along with the cloned uuu from git.
    ls -l uuu imx-boot-imx95-19x19-verdin-sd.bin-flash_all imx-image-full-imx95evk.wic
    -rw-r–r-- 1 harish harish 2839552 Jun 6 15:20 imx-boot-imx95-19x19-verdin-sd.bin-flash_all
    -rw-r–r-- 1 harish harish 10804921344 Jun 6 15:19 imx-image-full-imx95evk.wic
    -rwxrwxr-x 1 harish harish 6020936 Sep 16 17:33 uuu

  3. I am getting the error log while trying to run the command.

Kindly look into this issue and guide me with the solution ASAP. Thank you

1 Like
5

Hello @sahil.tx ,

having same problem as OP, can you please look into this?
Writing this so the thread gets more trafic.

Thank you,
David

6

We ran into a similar issue once. The thing that solved it for us was switching the board to CM33 Serial download mode as described here.

Only had to do this once to flash an image. All subsequent reflashing was done using the usual procedure with the recovery mode.

7

Hello guys, we tried all of these ideas without any obvious success or even step forward.

When trying the SD, i still get the same error “LIBUSB_ERROR_NO_DEVICE”.

Do you know what it represents? Because I can see the device in lsusb, is it possible the Linux is giving it bad driver? (we had simmilar issue on different HW in past) What driver should it use when loading the USB? What do you have shown in your system when you run “lsusb -t” ?

Thanks for any advice,

D.

8

Hi I followed the same and I am able to build in yocto and flash, the command line is working fine but the display is not working. I tried changing the dtb as in document for enabling display support but did not work. Have you faced any issue like this ? Kindly suggest any solution for this. Thanks.

FYI I am able to flash the Alpha release and it works fine , I changed the dtb and was able to see the disply. I am using HDMI connector