UUU does not return after writing images

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

UUU does not return after writing images

Jump to solution
1,025 Views
tanoue
Contributor III

I wrote images to i.MX 8M Plus EVK with UUU.

However, UUU does not return after writing images.

 

My procedures is here.

1. Build image with "Linux 5.15.32_2.0.0" according to i.MX Yocto Project User's Guide(Rev. LF5.15.32_2.0.0 — 12 July 2022)

repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-kirkstone -m imx-5.15.32-2.0.0.xml

2. After build, write images(.bin-flash_evk and .wic.bz2) to EVK using the following command.

sudo ./uuu -b emmc_all imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk imx-image-full-imx8mp-lpddr4-evk.wic.bz2

3. The following message shown and stop writting images. UUU did not return after writing .bin-flash_evk and .wic.bz2 was not written to EVK.

uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.165-0-ge10b026

Success 0 Failure 0


1:8 1/ 1 [=================100%=================] SDPS: boot -scanterm -f /<path>/imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk

 

What should I do.

 

Best regards.

tanoue.

0 Kudos
1 Solution
942 Views
tanoue
Contributor III

My problem was solved with using next stable uuu(1.4.193).

However, I didn't understand which changes solved my problem.

 

Please, let me know.

 

Best regards.

tanoue.

View solution in original post

0 Kudos
7 Replies
1,011 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

Please run the tool in verbose mode by using the following command:
sudo ./uuu -V -b emmc_all imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk imx-image-full-imx8mp-lpddr4-evk.wic.bz2

After this, please share the tool output so I can see more information on what is going on.
Also, please share the serial terminal (Uboot) log.

Best regards,
Aldo.

0 Kudos
1,004 Views
tanoue
Contributor III

Hi, @AldoG 

Thank you for your reply.

I did it and attached log that has UUU and Uboot output.

Please, see it.

 

Best regards.

tanoue.

0 Kudos
984 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

This seems to be a problem when using Ubuntu 20.04/libusb, unfortunately haven't found what is actually going wrong, more details here:
https://github.com/NXPmicro/mfgtools/issues/183

Some workarounds that have worked for other customers that you could try on your side are:
> Using Ubuntu 18.04 host PC
> Do not use USB Hub, connect directly to host PC
> Even connecting to a different USB port has helped in some cases

Please try any of the above if it can help you, if not please do let me know.

Best regards,
Aldo.

0 Kudos
955 Views
tanoue
Contributor III

Hi, @AldoG 

 

I tried it again on Ubuntu 18.04 host PC without USB Hub.

However, its result was same.

I attached log.

 

Best regards.

tanoue.

0 Kudos
943 Views
tanoue
Contributor III

My problem was solved with using next stable uuu(1.4.193).

However, I didn't understand which changes solved my problem.

 

Please, let me know.

 

Best regards.

tanoue.

0 Kudos
923 Views
AldoG
NXP TechSupport
NXP TechSupport

Hi,

Glad to hear that it is now working, unfortunately is hard for me to say what actually fixed your issue since device got stuck at Run fastboot…. So, it could be some random USB issue.

Finally, from the release notes the bug fixes between those 2 versions are the following:
https://github.com/NXPmicro/mfgtools/wiki/Release-Notes#bug-fixes-1

Bug fixes
Fixed 314 Corrupt image with larger transfer sizes at sdp(s)
Fixed missed true at else branch at built-in fat_write script and nand_burn_loader
Fixed invalid progress percentage in verbose mode
Fixed QSPI flashing script
Fix #297 print error when run quit cmd in shell mode
Fix #180 support check getval return value

Best regards,
Aldo.

0 Kudos
903 Views
tanoue
Contributor III

Hi, @AldoG 

Thank your for your replying.

I understood your opinion.

Anyway, I hope this topic helps someone with the same problem.

0 Kudos