Trying to upload image to i.MX95 and i.MX943 and getting LIBUSB error -9

[LudekZaloudek]

Hello.

I am trying to upload an image to EVK from Windows command line and I keep getting this issue. Yes, I have the DIP switch set to USB serial download mode.

uuu -b sd_all imx-image-full-imx943evk.wic
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.201-0-g727fc2b

Success 0    Failure 1


2:3-586B3F86 1/ 1 [HID(W): LIBUSB_ERROR_PIPE (-9)        ] SDPS: boot -scanterm -f imx-image-full-imx943evk.wic -scanlimited 0x800000

The thing is, it probably depends on the alignment of planets or something like that. Some days, this works, some other days (and that is roughly 80% of the time) it does not and gives me this error. I can try different cables, different PCs but this is the result. And then some other day, I come to work and it suddenly works. And then again it does not.

[nxpfrankli]

Doe you have serial port log?

[LudekZaloudek]

Doe you have serial port log?

Sorry, no log is produced. Do I turn it o somehow?

[nxpfrankli]

you can use -v to show how much download to guest what's current rom state. Normal ROM reset chip because received unexpected data.

[LudekZaloudek]

Sorry, for delay, I had to deal with other tasks. However, this is my result using -V:

Wait for Known USB Device Appear...
New USB Device Attached at 2:3-
2:3->Start Cmd:SDPS: boot -scanterm -f imx-image-full-imx943evk.wic -scanlimited 0x800000
55%2:3->Fail HID(W): LIBUSB_ERROR_PIPE (-9)(0.303s)



libusb: warning [libusb_exit] device 2.0 still referenced
libusb: warning [libusb_exit] device 1.4 still referenced
libusb: warning [libusb_exit] device 1.1 still referenced
libusb: warning [libusb_exit] device 2.9 still referenced
libusb: warning [libusb_exit] device 2.12 still referenced
libusb: warning [libusb_exit] device 1.3 still referenced
libusb: warning [libusb_exit] device 2.4 still referenced
libusb: warning [libusb_exit] device 2.7 still referenced
libusb: warning [libusb_exit] device 2.11 still referenced
libusb: warning [libusb_exit] device 1.0 still referenced

[LudekZaloudek]

I also get different behaviour with different image:

Wait for Known USB Device Appear...
New USB Device Attached at 2:3-586B3F8619A74982
2:3-586B3F8619A74982>Start Cmd:SDPS: boot -scanterm -f imx-image-full-imx943-19x19-lpddr4-evk.rootfs.wic -scanlimited 0x800000
100%2:3-586B3F8619A74982>Okay (3.672s)
libusb: error [hid_open] could not gain access to HID top collection (HidD_GetAttributes)
libusb: error [auto_claim] could not auto-claim any interface
libusb: error [hid_open] could not gain access to HID top collection (HidD_GetAttributes)
libusb: error [auto_claim] could not auto-claim any interface
New USB Device Attached at 2:3-
2:3->Start Cmd:SDPS: boot -scanterm -f imx-image-full-imx943-19x19-lpddr4-evk.rootfs.wic -scanlimited 0x800000
100%2:3->Okay (3.65s)

[nxpfrankli]

There is bootloader in wic image, which need match your board, lpddr4 board need use lpddr4's image, ddr5 board need ddr5s image. otherwise, ddr init will be failure, when ROM try to write DDR, check sum will be wrong, then reset chip.

[LudekZaloudek]

There is bootloader in wic image, which need match your board, lpddr4 board need use lpddr4's image, ddr5 board need ddr5s image. otherwise, ddr init will be failure, when ROM try to write DDR, check sum will be wrong, then reset chip.

Thanks. I will check if my bootloader is correct.