beaglebone A3 - problem with the on board usb hub

Hello Beagleboard Community,

I want to check with people on here on my suspicion that I may have killed my beaglebone’s usb hub.

It had been working perfectly fine over the past weekend. I put it in it’s altoid’s tin and was keeping it with me for study breaks. On my last one I noticed that I was no longer able to access ttyUSB0, in fact no serial console was being displayed. At first I thought that a recent kernel upgrade (on my laptop) had caused this, so I rolled back to the previous kernel with no change. My dmesg outputs are below:

`

[ 1236.313314] usb 8-1: device descriptor read/64, error -71
[ 1236.533285] usb 8-1: device descriptor read/64, error -71
[ 1236.743339] usb 8-1: new full-speed USB device number 11 using uhci_hcd
[ 1236.859976] usb 8-1: device descriptor read/64, error -71
[ 1237.079984] usb 8-1: device descriptor read/64, error -71
[ 1237.290009] usb 8-1: new full-speed USB device number 12 using uhci_hcd
[ 1237.703338] usb 8-1: device not accepting address 12, error -71
[ 1237.809974] usb 8-1: new full-speed USB device number 13 using uhci_hcd
[ 1238.223309] usb 8-1: device not accepting address 13, error -71
[ 1238.223337] hub 8-0:1.0: unable to enumerate USB device on port 1

`

When googling around with this I found a few posts saying that the problem was with uhci_hcd and the I could remove that module and use the usb port as usb1.1. I’m afraid I haven’t been able to reproduce those dmesg logs, as it was a couple hours ago that I did that, but it didn’t work. Now what makes me think that I some how damaged the beaglebone’s usb is the following dmesg output when plugged into a different usb port on my system:

`

[ 1485.256623] usb 6-1: device descriptor read/64, error -71
[ 1485.476618] usb 6-1: device descriptor read/64, error -71
[ 1485.686629] usb 6-1: new full-speed USB device number 5 using uhci_hcd
[ 1485.713649] usb 6-1: not running at top speed; connect to a high speed hub
[ 1485.723756] hub 6-1:1.0: USB hub found
[ 1485.725654] hub 6-1:1.0: 2 ports detected
[ 1485.828671] hub 6-1:1.0: hub_port_status failed (err = -71)
[ 1485.829650] hub 6-1:1.0: hub_port_status failed (err = -71)
[ 1488.357662] hub 6-1:1.0: hub_port_status failed (err = -71)
[ 1488.358645] hub 6-1:1.0: hub_port_status failed (err = -71)

`

It’s the device descriptor read/64, error -71 and hub_port_status failed (err = -71) that really concern me. The first output suggests I can keep poking around with uhci_hcd to fix it, but the second suggests to me that the hub is not communicating.

I have been able to reproduce this on three seperate linux machines (all the same distro, but I can load up another distro if that is worth testing). A windows 7 x64 machine with the 64bit drivers from the beaglebone getting started page installed reports an Unknown Devices when the beaglebone is plugged in.

When connected via the ethernet conection I was able to ssh into the beaglebone (while connected via usb). Once I tried to enable the ethernet over usb the beaglebone stopped responding, and would not accept another ssh season.

I’m hoping someone can suggest another software thing I can try, or if this seems like a hardware problem?

Thank you all for your time.

Have a good one,

magyarm

Keeping a board in a metal box for storage, is well, a very bad idea. ESD just loves metal boxes, especially those that may be carried around in pockets. So, there is a good chance something got poped.

Gerald

Hi Gerald,

Thank you for your response. Unfortunately, I wasn’t thinking about ESD at the time. I was only worried about it getting physically damaged by the other stuff in my bag.

Since yesterday I have found that for a brief time the usb serial port and the usb jtag do get recognized by my system, but I never get a chance to access it. With in a couple seconds I get the dmesg output I did earlier.

At least learned (the hard way) don’t store boards in metal containers. Since it looks like the hub is dead, is there anyway to replace that part, or is it not worth it?

You can request an RMA and get it all checked out. They will replace whatever parts are found to be bad.

http://beagleboard.org/support/rma

Gerald