USB Error device descriptor read/64, error -71

[rb_ontario]

I have a iMX53 quick start board and I have my own hardware 
with a iMX53 processor. I'm running Linux 2.6.35 

When I boot the quick start board using my linux image with 
the USB stick plugged in, it seems to initialize correctly. 

When I use the same linux image with my own hardware, the 
boot debug message reports a bunch of problems. The errors 
start right after the hotplug events dispatecher udevd is 
started. 
The error is: 

Synthesizing initial hotplug events 
usb 2-1: device descriptor read/64, error -71 
usb 2-1: device descriptor read/64, error -71 
usb 2-1: new low speed USB device using fsl-ehci and 
address 4 
usb 2-1: device not accepting address 4, error -71 
usb 2-1: new low speed USB device using fsl-ehci and 
address 5 
usb 2-1: device not accepting address 5, error -71 
hub 2-0:1.0: unable to enumerate USB device on port 1 

I use the same USB stick for tests on both systems. I also 
use the same microSD card on both systems. 

What can cause this error? Do any IIM fuses need to be set 
in the iMX53 for USB to work? Does the MC34708 PMIC have 
any effect on it? I have checked my schematic several times 
and can't find any errors on it.

[ShaneKaiser]

Hi Make and Rick,

Thanks for the replies.

I have tried (3) BT dongles with the i.MX53 QSB. (2) of the dongles give me the device descriptor read/64, error -71 when plugged in. The third BT dongle does not give me a USB error. However, the third BT dongle still gives me nothing when I try hcitool dev to see if any local BT devices are connected. So something is still wrong.

I have installed the BlueZ bluetooth protocol included with LTIB. In addition, I have compiled the BT HCI USB Driver into the kernel. I am not 100% sure if this driver will actually work with any of the dongles.

All (3) of the dongles seem to be recognized by the USB interface. Here is a sample lsusb:

Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 001 Device 004: ID 0a12:0001

I am trying to figure out if this is a USB problem, BT problem, or both.

[rb_ontario]

Hi Shane,

My problem occurred because one of the power rails was not connected properly on our own hardware.  Once that was fixed, devices enumerated  correctly.  In our case, no devices worked at all.  As Make suggested, it seems that your problem is not the same as ours.

[makeshi]

Any USB transfer error will report error -71,timeout, bad CRC, wrong PID, etc.And the question maybe caused by host or device. But I think your issue is not same with Rick Bosma 's. There is no problems with USB memory stick,it is possible that a Bluetooth dongle have some issue.Can your try it in other host system?

[rohith1z]

I'm facing the same problem.(with imx253 linux 2.6.28 kernel on a modified board)

the last irq recieved says:

ehci_irq: port_status[0] = 0x1000180b // portsc

Its a usb memory stick which works fine with windows.

Any debugging tips?

Note:attachment is the USB packet capture.Can be viewed with this software.

EDIT:Issue was traced to hardware.Fixed now.

Message was edited by: Rohith Ramesh

[samanthachang]

Rohith,

Was your problem also with a power rail?

Thank you.

[rohith1z]

In my case, it was a non-required resistors on the data lines, which were attenuating signal and causing USB to work/fail intermittently.

Once they were removed, all was well.

--Rohith

[ShaneKaiser]

I have the same problem when I plug in a Bluetooth dongle:

otg host ID wakeup
usb 1-1: new full speed USB device using fsl-ehci and address 2
usb 1-1: device descriptor read/64, error -71

Did you ever get this problem fixed?

What does this error -71 mean?

I have no problems with a USB memory stick. I can mount the USB memory stick and see what is on it.