• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 33 subscribers
  • Views 7201 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.

TUSB2077A: USB Hub device descriptor error in Linux

Michael Liesenberg85
Mastermind 7560 points
Part Number: TUSB2077A
Other Parts Discussed in Thread: TUSB2036

Hi,

i am having an issue with TUSB2077.

On the boot time i am getting this error messages:

"usb 1-1.1: device descriptor read/64, error -71

usb 1-1.1: new full-speed USB device number 4 using ci_hdrc

usb 1-1.1: device descriptor read/64, error -71

usb 1-1.1: device descriptor read/64, error -71

usb 1-1.1: new full-speed USB device number 5 using ci_hdrc

usb 1-1.1: device not accepting address 5, error -71

usb 1-1.1: new full-speed USB device number 6 using ci_hdrc

usb 1-1.1: device not accepting address 6, error -71

hub 1-1:1.0: unable to enumerate USB device on port 1"

When i log in on linux and check the usbs i get this:

"root~# lsusb

Bus 001 Device 002: ID 0451:2077 Texas Instruments, Inc. TUSB2077 Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub"

Once i plug an USB Stick on the hub i get this messages:

 

usb 1-1.1: new full-speed USB device number 7 using ci_hdrc

usb 1-1.1: device descriptor read/64, error -71

usb 1-1.1: device descriptor read/64, error -71

usb 1-1.1: new full-speed USB device number 8 using ci_hdrc

usb 1-1.1: device descriptor read/64, error -71

usb 1-1.1: device descriptor read/64, error -71

usb 1-1.1: new full-speed USB device number 9 using ci_hdrc

usb 1-1.1: device not accepting address 9, error -71

usb 1-1.1: new full-speed USB device number 10 using ci_hdrc

usb 1-1.1: device not accepting address 10, error -71

hub 1-1:1.0: unable to enumerate USB device on port 1

usb 1-1.6: new full-speed USB device number 11 using ci_hdrc

usb 1-1.6: not running at top speed; connect to a high speed hub

usb-storage 1-1.6:1.0: USB Mass Storage device detected

scsi0 : usb-storage 1-1.6:1.0

scsi 0:0:0:0: Direct-Access     Corsair  Flash Voyager    1100 PQ: 0 ANSI: 0 CCS

sd 0:0:0:0: [sda] 15728640 512-byte logical blocks: (8.05 GB/7.50 GiB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] No Caching mode page found

sd 0:0:0:0: [sda] Assuming drive cache: write through

sd 0:0:0:0: [sda] No Caching mode page found

sd 0:0:0:0: [sda] Assuming drive cache: write through

 sda: sda1

sd 0:0:0:0: [sda] No Caching mode page found

sd 0:0:0:0: [sda] Assuming drive cache: write through

sd 0:0:0:0: [sda] Attached SCSI removable disk

Any idea why the device descriptor on linux not able to read on the TUSB2077 ports?

The USB2514B USB Hub from Microchip works well in the same system.

  • 0
    TI__Guru* 76130 points
    Hello,
    Can you provide your schematic, it may be a hardware issue, have you tried with another kernel version?
    Regards
  • 0 in reply to Elias Villegas M.
    Mastermind 7560 points

    Hi Elias,

    yes could be, please have a look at it.

    8154.schematics.pdf

    I manage to get it to work on Linux Kernel somehow. It recognizes the HUB and doenst give me any descriptor error anymore once bootet.

    So all channels are working but it still dont work with uBoot. I am getting descriptor error if i want to read like a usb file while in uBoot.

    Any idea?

  • 0 in reply to Michael Liesenberg85
    TI__Guru* 76130 points
    Hello,
    The schematic looks correct.
    The only possible hardware issue could be the power-up sequence, terminal RESET# must remain asserted from 3ms to 10ms after VDD is stable and after the clock on XI is also valid and stable.
    Other possibility is an issue with the uBoot, you may want to go to the linux community.
    Regards
  • 0 in reply to Elias Villegas M.
    Mastermind 7560 points

    Hi Elias,

    i change the uBoot enviromental variable to wait for the USB HUB longer or something:("increases delay after enabling port")

    setenv usb_pgood_delay 10000

    But that dindt work.

    I tested my system yesterday with  the USB2517 evaluation board USB HUB with 7 Ports from Microchip and it works fine.

    I dont have enought time to serach the reason for it  and i decided to design the USB2517 instead of TUSB2077A on our system for now.

    But thank you for your answer.

    Kind Regards,

    Michael

  • 0 in reply to Michael Liesenberg85
    Prodigy 30 points
    Hi, guys

    this is probably too late, however I wanted to share this anyway (if someone searches for the same problem).

    I had exactly the same problem with TUSB2036, spent weeks trying to find the hardware issue...
    It turned out that it is not hardware fault at all!

    There is a bug in uBoot source code that makes it very unstable while working with Full Speed devices. High Speed devices at the same time work just fine. If you want to know that you have the same issue, just check the USB communication signals at D+ D-. What I have found is that some bits are stretched from 83nS to 107nS due to this software bug.

    Once our software guys downloaded different version of uBoot it magically started to work!

    I hope this will save some time for others.

    Cheers


    Zman