HID(W):LIBUSB_ERROR_TIMEOUT error while flashing IMX8MPLUS using uuu in custom board

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HID(W):LIBUSB_ERROR_TIMEOUT error while flashing IMX8MPLUS using uuu in custom board

5,104 Views
Cyriactoms
Contributor II

HID(W):LIBUSB_ERROR_TIMEOUT error while flashing IMX8MPLUS using uuu in custom board

I build an yocto image for IMX8mp and flashed it on custom board then encountered an error HID(W):LIBUSB_ERROR_TIMEOUT

0 Kudos
Reply
21 Replies

4,895 Views
Harvey021
NXP TechSupport
NXP TechSupport

Have you tried to flash prebuild image for a test?

L6.6.52_2.2.0_MX8MP 

 

Regards

Harvey

0 Kudos
Reply

4,886 Views
Cyriactoms
Contributor II

yes i have tried L5.51.71 and the latest version also but i am getting the same error.

HID(W):LIBUSB_ERROR_TIMEOUT.

0 Kudos
Reply

4,876 Views
Cyriactoms
Contributor II
uuu - lsusb

uuu (Universal Update Utility) for nxp imx chips -- lib1.4.193

Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion
==================================================
1:5 MX865 SDPS: 0x1FC9 0x0146 0x0002

0 Kudos
Reply

4,870 Views
Harvey021
NXP TechSupport
NXP TechSupport

- Try to use the new UUU tool, uuu 

- if still not work. try to add para (-v) to show more information and share your full command line

- Is the issue with one board only?

 

Regards

Harvey

0 Kudos
Reply

4,863 Views
Cyriactoms
Contributor II

sudo uuu -v -b emmc_all imx-boot-imx8mpevk-sd.bin-flash_evk imx-image-full-imx8mpevk.wic

uuu (Universal Update Utility) for nxp imx chips -- lib1.4.193

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
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

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-imx8mpevk-sd.bin-flash_evk -scanlimited 0x800000

# This command will be run when ROM support stream mode
# i.MX8QXP, i.MX8QM
SDPS: boot -scanterm -f imx-boot-imx8mpevk-sd.bin-flash_evk -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-imx8mpevk-sd.bin-flash_evk -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-imx8mpevk-sd.bin-flash_evk -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-imx8mpevk.wic
FB: flash -scanterm -scanlimited 0x800000 bootloader imx-boot-imx8mpevk-sd.bin-flash_evk
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 1:5
1:5>Start Cmd:SDPS: boot -scanterm -f imx-boot-imx8mpevk-sd.bin-flash_evk -scanlimited 0x800000
1:5>Fail HID(W):LIBUSB_ERROR_TIMEOUT(1s)

 

I am having issue with all my custom boards.Is this a hardware issue regarding USB2.0

0 Kudos
Reply

4,852 Views
Harvey021
NXP TechSupport
NXP TechSupport

LIBUSB doesn't seem to work, as mentioned , please have a try new uuu_1.5.201 

 

Regards

Harvey

0 Kudos
Reply

4,842 Views
Cyriactoms
Contributor II
i have tried using the latest version but the same error is getting for me. Please help me to get a solution for this
0 Kudos
Reply

4,820 Views
matato
Contributor I

i.MX 8M Plus Applications Processor Reference Manual, Rev. 1, 06/2021
6.1.7 USB boot

dd.png

0 Kudos
Reply

4,837 Views
Harvey021
NXP TechSupport
NXP TechSupport

Try with dd to flash to sd card for a test if possible for your board.

 

Regards

Harvey

 

0 Kudos
Reply

4,781 Views
Cyriactoms
Contributor II

I have done dd flash to sd card and it worked when i try to boot up i got like this

 

U-Boot SPL 2023.04-lf_v2023.04+g49b102d988 (Nov 21 2023 - 07:28:53 +0000)

DDRINFO: start DRAM init

DDRINFO: DRAM rate 4000MTS

Training FAILED

Should i need to do a ddr test before flashing.

0 Kudos
Reply

4,766 Views
gidame
Contributor III

"Training FAILED"

This result shows that what matato said is right.
matato: "Harvey, For a new custom board, should I first check whether the DDR tool can run? Am I right?"

There is something wrong with the hardware design of the DDR on this custom board.
You should run config tool to check the DDR first when you have a brand new custom board as matato said.

There should be something wrong with the layout.
Of course, it may also be that the DDR type is wrong, the difference between DDR4 and LPDDR4.
This kind of high-speed DDR4/LPDDR4 generally needs to finish SI,PI.

 

https://www.nxp.com/design/design-center/development-boards-and-designs/i-mx-evaluation-and-developm...

das4.png

0 Kudos
Reply

4,557 Views
Cyriactoms
Contributor II

Can we do the ddr test using the config tool?
0 Kudos
Reply

4,430 Views
Harvey021
NXP TechSupport
NXP TechSupport

Hi @Cyriactoms 

About DDR test, we'll have other engineer who will get back to you and assist on that.

 

Regards

Harvey

0 Kudos
Reply

4,415 Views
Cyriactoms
Contributor II
Please assist me on this
0 Kudos
Reply

4,649 Views
Cyriactoms
Contributor II

Download is complete
Waiting for the target board boot...
H�������������������B���݅ɕ}�����====================


********Found PMIC PCA9450**********
hardware_init exit

*************************************************************************

*************************************************************************

*************************************************************************
MX8 DDR Stress Test V3.30
Built on Nov 24 2021 13:52:12
********************"************"***************************************

Waiting for board configuration from PC-end...

--Set up the MMU and enable I and D cache--

- Check if I cache is enabled
- Enabling I cache since it was disabled
- Push base address of TTB to TTB
- Config MAIR_EL3
- Enable MMU
- Data Cache has been enabled
- Check system memory register, only for debug

- VMCR Check:
- ttbr0_el3: 0x97d000
- tcr_el3: 0x2051c
- mair_el3: 0x774400
- sctlr_el3: 0xc01815
- id_aa64mmfr0_el1: 0x1122

- MMU and cache setup complete

*************************************************************************
ARM clock(CA53) rate: 1800MHz
DDR Clock: 0MHz

============================================
DDR configuration
DDR type is LPDDR4
Data width: 32, bank num: 8
Row size: 17, col size: 10
Two chip selects are used
Number of DDR controllers used on the SoC: 1
Density per chip select: 4096MB
Density per controller is: 8192MB
Total density detected on the board is: 8192MB
============================================


Please re-download with the correct value

 

When i run the ddrc test  its showing like this and not able to calibrate

0 Kudos
Reply

4,391 Views
Cyriactoms
Contributor II

DDR configuration DDR type is LPDDR4 Data width: 32, bank num: 8 Row size: 17, col size: 10 One chip select is used Number of DDR controllers used on the SoC: 1 Density per chip select: 4096MB Density per controller is: 4096MB Total density detected on the board is: 4096MB ============================================ MX8M-plus: Cortex-A53 is found ************************************************************************* ============ Step 1: DDRPHY Training... ============ ---DDR 1D-Training @1600Mhz...

 

 

during calibration it is not progressing 

0 Kudos
Reply

4,381 Views
Harvey021
NXP TechSupport
NXP TechSupport

Engineer for DDR replied back to you via other ticket, please communicate at there.

He will help you and check your configuration.

 

Regards

Harvey

0 Kudos
Reply

4,573 Views
Harvey021
NXP TechSupport
NXP TechSupport

I think that your board is i.MX8MP. Please refer to the i-MX-8M-Family-DDR-Tool-Release 

 

Regards

Harvey

0 Kudos
Reply

4,024 Views
Cyriactoms
Contributor II
i have downloaded the exact version for imx8mp
then getting this output
0 Kudos
Reply

4,270 Views
matato
Contributor I

Harvey,

 

For a new custom board, should I first check whether the DDR tool can run? Am I right?

0 Kudos
Reply