-
Notifications
You must be signed in to change notification settings - Fork 263
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
"usb bulk write failed" errors flashing Tang Nano 9k #415
Comments
If left alone for several minutes, it finally does actually stop and print this:
I've tried with multiple different known-good cables, so it's unlikely to be that. Not really sure how to debug this. |
I'm seeing this exact same issue on an M2 Macbook Air and openFPGALoader v0.11.0 |
Could you paste dmesg output when you plug the device? |
This seems to be related to using a usb hub, plugging into the computer directly with a known good cable solves the issue. |
Weird: I have bought an 9k to do some tests. I have a long USB extender and and usb switch + usb cable and not seen anything like that. |
I'm having the same issue on the Raspberry Pi 4 with 64-bit Raspberry Pi OS. I tried different USB cables and flashing fails in a similar manner on all of them. I will try with a laptop instead, and post an update. |
Could you share |
Sometimes it works:
Sometimes it errors out:
I used a different USB port here, but it doesn't seem to be linked to a specific USB port. |
I'm hitting the same issue on a Framework laptop: dmesg on plug
Error on flash:
Before seeing the first
|
The two lines mentioned are perfectly normal. To be able to take control to the FTDI (or clone) from userspace, it's required first to detach the driver. [127777.428335] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[127777.428352] ftdi_sio 3-1.4:1.0: device disconnected The real problem here are errors ( |
Other log lines I've gotten:
another run got a bit farther:
The first 3 also logged in dmesg:
another try got up to 39% while logging the I've tried two cables that have worked with other devices, but after replacing it again with an USB-C charging cable (thicker, rated to 60W), it succeeded repeatedly. |
Yes: cables are not always good or enough. I don't know the exact reason (maybe to electrical noise, or lost of current). It's usual to have to switch between cables... |
This definitely worked a few months ago, but I've changed laptops since then and now it doesn't:
The text was updated successfully, but these errors were encountered: