Failed to open USB device on windows 10 device.
PREMjITHT opened this issue · 16 comments
Hi @nxpfrankli,
The programming failed due to the Failure in opening the USB device on Windows 10 device.
Opened Windows PowerShell with admin rights,
The device is detected(imx6s), but it showing the below-mentioned error while programming.
FYI: The same UUU tool is working on the Linux machine.
Please find the attached screenshots,
Can you check devices manage if winusb driver correct install automatcally?
I am not sure if your uboot is updated
I am using U-boot 2019.
I am testing the UUU Tool on Windows 10. As per the documentation only in Windows 7, I need to use winusb to install the driver.
FYI: The same UUU Tool is working on Linux host machines.
uboot need provide USB WCID information to let win10 can auto load winusb driver, It is needed only for windows.
you can use https://zadig.akeo.ie/ check if WCID work at your machine.
Please check your uboot include below commits.
https://github.com/search?q=repo%3Anxp-imx%2Fuboot-imx++WCID&type=commits
I checked the WCID driver using Zadig.
Below are the results,
After installing the WCID driver, the Zadig application is showing that the driver is not installed.
The above scenario is when I connected the serial USB cable to a powered USB Hub(USB 3.0).
I tried connecting using a normal adapter(Type A - Type C),
That time I am getting an error that "The USB device is not recognized".
I think you choose wrong USB devices, USB ID 0x0E0F and 0001 is not our devices.
Sorry, I read you first screen shot carefully, Your devices still be in ROM HID phase.
Can you use uuu -v to get more detail information.
Below is the result of uuu.exe -v
Can you show full log included uuu cmd line
Please find the requested image attached below,
when appear Fail open usb devices, can you check if there are "usb download devices" at zadig?
Hi @nxpfrankli ,
The same UUU Tool is working on another Windows machine.
It has a USB Type-A port. Previously I was using a laptop with a Type C port.
Now the tool is able to detect the OTG and flashing.
But while programming the rootfs it got stuck, The progress bar was not moving. But this is not happening on Linux machines.
Did you use bz2 as rootfs?
yes.
Please check the below error snapshot for more information.
Sometimes it works, but sometimes the flashing gets stuck and later throws the above error.
It should not related your windows environment. The decompress was done at boards. Maybe boards was out memory and kill tar by linux.
can you try drain some file system cache before tar?
https://www.tecmint.com/clear-ram-memory-cache-buffer-and-swap-space-on-linux/
Okay, I will try this.
But I wonder why this is not happening in the Linux Host. There it works always without any lag/hangs/USB Bulk error.
In the Windows host, I observed that the rootfs programming speed got reduced and stuck at one point, later I got the error mentioned in the previous comment.
Yes, suppose all transferred's data should be the same between linux and windows. Maybe wireshark trace some usb packages to help diagnosis. Try clean cache firstly.
sure, Let me try that and get back to you. Thank you.