New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UUU libusb: error ubuntu 20.04 #183
Comments
Fixed with using "-pp 1" |
Actually I could not flash either with my Ubuntu 20.04 with the -pp 1 option either. Various option didn't change a thing. Will be posting the verbose results here today. (worked on 18.04 before upgrade on the same machine, same target hardware). |
It work well in my ubuntu 20.04. Not clue yet |
Some more details
libusb version
Linux kernel info |
I tried to edit the udev rules as suggested in using uuu -udev
I see that log and it hangs here, nothing is being flashed to the device and it never exits. |
|
look like SPL-aeler-imx7ulpea-ucom is not boot. USB still in ROM PID\VID. SPL should use difference PID\VID |
The Same SPL are used under Ubuntu18.04 successfully though with the same uuu calls. |
Result with latest uuu release:
|
We observed that in fact the uuu tool works as epxected on 20.04 as long as the device is not in a closed state (burned fused) After that, subsequent attempts at uuu calls to flash M4 or A7 program fails with a HW libust tiemout issue. |
Did your closed part stop here? 1:12>Start Cmd:SDP: boot -f SPL-aeler-imx7ulpea-ucom look like autherization failure. Are you use signed image to download? |
Apologies, the capture above was from a flashing of the M4 program before the device was closed. After the device was closed though, here is what I got:
Note that reverting to Ubuntu 18.04 with the exact same files (uboot.itb, signed SPLs, signed Linux image and M4 program), everything goes as expected. So we are sticking to 18.04 for that reason at the moment. |
I don't know what happen now. it is very strange |
Trying on a different 20.04 machine the tool worked well. Hence, diving deeper, it seems it is an Ubuntu issue not an issue directly linked to uuu. Thanks for your support ! |
I'm having problems with UUU also. Similar but different. Instead of the "LIBUSB_ERROR_TIMEOUT", I'm getting a "LIBUSB_ERROR_NO_DEVICE". UPDATE: Sorry for the noise. |
Hello @nxpfrankli We have been using older hardware (old Thinkpad and Alienware M17x from 2012) to flash closed devices ever since the problem was experienced but it is not a viable solution long term. We have tried again with more recent versions of the uuu tool and the issue persists. We are running on closed i.Mx7-ULP boards. Under windows our manufacturers have been facing the same issues for our first series production but it seems the use of a USB hub helped (it degrades the USB driver that is used to USB 2.0 if I am correct). could we re-open this ticket ? We depend on this tool proper operation for series production. This might depend on a LIUBUSB issue but I would not know where to repost the issue if this is coming from lower in the stack. |
Example the script works on:
|
It is quite difficult to debug the problem. It may related USB host controller driver. Can you try run see what happen at your failure machine. |
Can you sperate boot cmd to 3 commands? SDP: dcd -f uboot Check which command cause failure. |
Might be missing something here but it tells me "no valid IVT header found" |
using spl_mfgtool.signed instead of u-boot-mfgtool.itb |
Test with spl_mfgtool.signed
|
With -pp 1 option
So the write command seems to be the problematic one |
I know i am not able to use this tool with usb hub. |
So far only you report hub problem, our internal test have not problem with hub. |
@nxpfrankli The issue persists with and without a hub on my side for most ubuntu computers. |
The current clue can't help me identify the problem. |
Hello, please add support for new ubuntu LTS. After upgrading to ubuntu 20.04 LTS uuu stopped working (on both machine- both were upgraded). Throwing libusb: error. With verbose -V cmd argument it works sometimes (50/50).
The text was updated successfully, but these errors were encountered: