My communication link:
BBB USB <-> USB2514B based USB hub <-> FTDI FT232
Abruptly fails for no evident reason (possibly EMI or other induced 
noise... there is a vast evidence ( better say a lot of rumors ) of the BBB 
USB being very sensitive all over the web).
uname -r output:
4.1.10-ti-r21 
dmesg output:  
[ 4951.213705] usb 1-1.1: USB disconnect, device number 3
[ 4951.215742] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now 
disconnected from ttyUSB0
[ 4951.216492] ftdi_sio 1-1.1:1.0: device disconnected
[ 4951.458827] usb 1-1.1: new full-speed USB device number 5 using musb-hdrc
[ 4951.538810] usb 1-1.1: device descriptor read/64, error -32
[ 4951.728815] usb 1-1.1: device descriptor read/64, error -32
[ 4951.918801] usb 1-1.1: new full-speed USB device number 6 using musb-hdrc
[ 4951.998947] usb 1-1.1: device descriptor read/64, error -32
[ 4952.188807] usb 1-1.1: device descriptor read/64, error -32
[ 4952.378887] usb 1-1.1: new full-speed USB device number 7 using musb-hdrc
[ 4952.798847] usb 1-1.1: device not accepting address 7, error -32
[ 4952.898825] usb 1-1.1: new full-speed USB device number 8 using musb-hdrc
[ 4953.318766] usb 1-1.1: device not accepting address 8, error -32
[ 4953.325078] usb 1-1-port1: unable to enumerate USB device 
the link doesn't recover unless the hub goes through a hardware reset or a 
power OFF\ON cycle; 
The hub appears to go in "Suspended Mode" when the problem arises.
I am wondering:
there is a Sitara Linux MUSB Issue with the USB_RESUME in AMSDK 
08.00.00.00: is the kernel 4.1.10-ti-r21 incorporating the workaround?
Any way I can software reset the hub from Linux?
Any hint on what is happening?
Thanks in advance for any help on this.

Guido
 



-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to