• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 577 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.

TUSB2036 not accepting wireless USB adapter

gismy sunish
Prodigy 70 points
Other Parts Discussed in Thread: TUSB2036

Hi

I am using TUSB2036 hub in my design. On the upstream side, the hub is connected to a Beagle bone Black. 

 

  • TUSB2036 is configured as a three port hub (NP3 pin LOW).
  • Self-powered hub (BUSPWR pin HIGH)
  • All ports are available through external USB connectors(NPINT1−0 pins LOW)
  • 6 MHz crystal(MODE pin LOW)
  • The serial EEPROM interface of the device is disabled (EXTMEM# pin HIGH)
  • Per port power over current detection circuitry using LM3526L is included (EEDATA/GANGED# pin HIGH)
  • Power Switching for self-powered hub is enabled (OCPROT#/PWRSW# pin LOW).

 

I have connected a wireless USB adapter, TL-WN721N to one of the downstream ports and got the following error message

Bus 001 Device 000: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub

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

ubuntu@ubuntu-armhf:~$ [  197.146917] usb 1-1: device descriptor read/64, error -110

[  212.361874] usb 1-1: device descriptor read/64, error -110

[  227.682199] usb 1-1: device descriptor read/64, error -110

[  242.897044] usb 1-1: device descriptor read/64, error -110

[  253.518102] usb 1-1: device not accepting address 2, error -110

[  264.035697] usb 1-1: device not accepting address 2, error -110

[  279.272027] usb 1-1: device descriptor read/64, error -110

[  294.486880] usb 1-1: device descriptor read/64, error -110

[  309.807180] usb 1-1: device descriptor read/64, error -110

[  325.022033] usb 1-1: device descriptor read/64, error -110

[  335.643106] usb 1-1: device not accepting address 5, error -110

[  346.160684] usb 1-1: device not accepting address 6, error -110

              [  346.167887] hub 1-0:1.0: unable to enumerate USB device on port 1

 

The OVRCURn# & PWRONn# pins are probed to an oscilloscope. When the wireless USB adapter is inserted PWRONn# made a LOW to HIGH transition, while OVRCURn# remains at HIGH.

When the same wireless USB adapter is connected to Beagle Bone Black directly, the device was detected and got wireless connectivity.

 

My circuit design is attached with this. Looking forward for your responses

5618.USB_ADDON_SCH.pdf

  • 0
    TI__Mastermind 18655 points 
    Hello gismy,
    Sorry for the delay, I've reviewed the schematic and everything seems OK.  It sounds like the USB connection is being suspended. 

      You can check this pretty easily. Disconnect SUSPND to ground.  Once the wireless USB adapter drops off or loses connection, check to see if the SUSPEND output of the TUSB2036 is high.

      USB automatically suspends after 3 ms of inactivity.  Let me know if the bus is getting suspended and I can send additional information to determine why the system isn't resuming properly.

     
     Regards,
     
     Joel
  • 0 in reply to Joel Jimenez0
    Prodigy 70 points

    Thanks for your response

    I have disconnected SUSPND pin from ground and checked both hot plugging and cold plugging conditions. Both  cases SUSPND output is LOW . Fortunately , when the wireless dongle is cold plugged, it got wireless connection.  So what could be the problem with hot plugging?

  • 0 in reply to gismy sunish
    TI__Mastermind 18655 points

    Hello gismy,

    Could you attach some scope captures?

       1. /RESET, VCC and XTAL lines in power up.

       2. /PWRONn and /OVRCURn when the wireless dongle is plugged.

    Regards,

    Joel