Open howientc opened 8 years ago
jwrdegoede
commented
8 years ago Hi,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759611#10
Certainly looks related, have you tried building your android tools with this patch ? If the device does show up in lsusb when connected to a usb-3 port in fastboot mode, I would try that first.
If the device does not show up in lsusb the problem lies elsewhere.
Regards,
Hans
howientc
commented
8 years ago Thanks, Hans,
The problem is with the device not showing up. I'm actually not using android tools, so I think the problem is either on the device site (u-boot), or the OS is glitching in not recognizing it. Happens with USB 3 on Mac and Windows. Not sure about linux as my machine is USB2.
Best, Howie
howientc
commented
8 years ago On OSX, this shows up in the kernel logs: IOUSBHostDevice@fa130000: IOUSBHostDevice::getDescriptorGated: compliance violation: USB 2.0 9.3.5: device returned more than wLength data AppleUSB20HubPort@fa130000: AppleUSBHostPort::disconnect: persistent enumeration failures
I'm unable to use fastboot to access a device when it's plugged into a USB3 port in my host computer. If I plug my device (a C.H.I.P. computer, fastboot ids=1f3a:1010), into a USB2 hub that goes into the USB3 port, all works fine.
Basically, my host (OSX, though I've seen it with Windows too), doesn't see the device when it's in fastboot mode on a USB3 port. It does, however, see it when in FEL mode. I've tried on many host computers, and narrowed it down to a USB3 port issue.
Perhaps this is related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759611#10
Any ideas?