• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 340 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3517 USB problem with linux2.6.37 kernel

weng lucheng
Prodigy 25 points
Other Parts Discussed in Thread: AM3517, DM3730

Hi,  

   We have designed a board with AM3517,we use USB3320 chip as host phy on USB port1 connected with ULPI interface.   The linux kernel version is "linux-2.6.37-psp04.02.00.07.sdk".   When I connected a usb massage storage device to the USB phy,some error message appear to the console as following.    

 root@am3517-evm:/dev# [  156.749877] usb 1-1: new high speed USB device using ehci-omap and address 2
[  157.304412] usb 1-1: device not accepting address 2, error -71
[  157.429412] usb 1-1: new high speed USB device using ehci-omap and address 3
[  157.569976] usb 1-1: device descriptor read/64, error -71
[  158.226226] usb 1-1: device not accepting address 3, error -71
[  158.351226] usb 1-1: new high speed USB device using ehci-omap and address 4
[  158.780975] usb 1-1: device not accepting address 4, error -71
[  158.906005] usb 1-1: new high speed USB device using ehci-omap and address 5
[  159.335479] usb 1-1: device not accepting address 5, error -71
[  159.341735] ehci-omap ehci-omap.0: port 1 cannot be enabled
[  159.349212] ehci-omap ehci-omap.0: Maybe your device is not a high speed device?
[  159.357910] ehci-omap ehci-omap.0: USB host (EHCI) controller does not support full speed or low speed device on it's root port.
[  159.371307] ehci-omap ehci-omap.0: Please connect full/low speed device via a high speed hub.
[  159.381256] hub 1-0:1.0: unable to enumerate USB device on port 1

But a board with DM3730 with the kernel of linux2.6.32 was OK! The hardware circuit is same.Do you think it is the difference of the kernel which leads to the problem?

  • 0
    TI__Guru**** 167181 points

    Without details it is hard to say it is hw or sw issue. But AM3517 and DM3730 use the same kernel source - omap3.git on Arago.So if you think the hw design is the same and it could be sw issue, I think you can run the .32 kernel on AM3517 and .37 kernel on DM3730 to see if that gives a clue.