Hello NXP team,
Our custom board using the i.MX8DXL processor, one of our customers reported a flashing issue when flashing the device using a Windows system. The error appears to be USB-related; however, we have been unable to reproduce the issue on our end. Do you have any suggestions or potential causes that could be related to the customer's laptop?
Below is the logs
UUU Tool\iW-PRGOT-R3.0-REL1.0-TelematicsGateway_Linux6.1.22_UUU> .\uuu.exe .\iW-PRGOT-R3.0-REL1.0-B0-iMX8DXL_Linux_6.1.22_UUU.uuu
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.243-0-ged48c51
Success 0 Failure 1
2:7 1/ 0 [Failure open usb device ]
U-Boot 2023.04-iwg27_6.1.22_2.0.0_1.1+gb6bf789da2 (Mar 20 2024 - 05:40:28 +0000)
CPU: NXP i.MX8DXL RevB A35 at 1200 MHz at 34C
Model: iW-RainboW-G46M-i.MX8DXL-OSM
Board: iWave iMX8DXL IWG46M OSM
Boot: USB
DRAM: 2 GiB
Core: 169 devices, 25 uclasses, devicetree: separate
MMC: FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Board Info:
BSP Version : iW-PRGOT-SC-R3.0-REL1.0-Linux6.1.22
SOM Version : iW-PRGWZ-AP-01-R3.80000000
CPU Unique ID : 0x301E880E8293EE1C
Carrier Board Version : iW-PRGJJ-AP-01-RX.X(Custom)
BuildInfo:
- SCFW 6638c032, SECO-FW 80649c52, IMX-MKIMAGE 5cfd2180, ATF 8103e82
- U-Boot 2023.04-iwg27_6.1.22_2.0.0_1.1+gb6bf789da2
- V2X-FW 75e63de2 version 1.2.1
switch to partitions #0, OK
mmc0(part 0) is current device
Detect USB boot. Will enter fastboot mode!
Net: Could not get PHY for FEC0: addr 4
Could not get PHY for FEC0: addr 4
Get shared mii bus on ethernet@5b050000
eth1: ethernet@5b050000
Fastboot: Normal
Setting bus to 3
Valid chip addresses: 17 51 6A 6B 74 77
Boot from USB for mfgtools
*** Warning - Use default environment for mfgtool s
, using default environment
Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot auto; fi ;
Hit any key to stop autoboot: 0
## Checking Image at 83100000 ...
Unknown image format!
Run fastboot ...
auto usb 1
Hi @Tanushree
Sorry, I talked with our internal team, For now, there is no solution about uuu can not work on win10 but can work fine on win11 and Ubuntu OS.
The best way is using Ubuntu or Win11 OS run the uuu tool.
B.R
Hi @Tanushree
Please try use below uuu version try the test on windows10 OS:
https://github.com/nxp-imx/mfgtools/releases/download/uuu_1.5.201/uuu.exe
B.R
The observations with UUU are the same as what you shared in the last reply.
Please try uninstall the USB driver and re install it. It is very strange, i have never meet this problem before.
Hello @pengyong_zhang
In Device Manager, the device is listed under "Other devices" as "USB Download Gadget." Please let us know the specific driver that needs to be installed so we can proceed with testing.
Hello,
Please see below — it has detected
Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion
==================================================
1:1 MX8DXL SDPS: 0x1FC9 0x0147 0x0003
please try use the uuu -b command flash the image to your board.
hi @Tanushree
the windows 10 should not the root cause, please share the fail log on your windows10 OS.
B.R
hi @Tanushree
Please share your UUU fail log on Windows10 OS. And what is your uuu version? please use the latest uuu version.
B.R
I reviewed the release notes for the Linux 6.1.22 kernel version and noticed that it recommends using UUU version 1.5.21. Currently, I am using the following specific UUU version as shown below:
While flashing works correctly on Windows 11 and Ubuntu 20.04 or later, it fails on Windows 10. However, I did not find any mention of supported or unsupported Windows versions in the release notes—only Ubuntu 20.04 is mentioned.
We are encountering an issue where Kernel 6.1.22 is not flashing on Windows 10, whereas it flashes successfully on Windows 11. Could this be due to a lack of support for Windows 10? Additionally, we recently migrated from Kernel version 5.15.52 to 6.1.22. The UUU tool was functioning correctly with version 5.15.52 on Windows 10.
Hi @Tanushree
What is your result if you run the uuu -b emmc_all <bootloader> <.wic> command?
Do not choose the uuu script file flash.
B.R
Hello @pengyong_zhang
Thank you for the reply.
There doesn't appear to be any issue with the UUU script, as the same procedure works on some laptops. We're using our own custom build. Are there any specific Windows settings that could affect UUU tool flashing or UMS detection?
Regards,
Tanushree