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.

TUSB8041: Unable to enumerate USB device on Linux ARM

Part Number: TUSB8041

Dear TI support,

we designed a board with the TUSB8041 chip as a USB HUB, we are running ubuntu 18.04 on a Linux ARM device 64 bit. It seems that there are some problems in detecting the hub, when I set the GRSTz pin to 1 I have this output from the kernel:

[   53.748162] usb 1-1: new low-speed USB device number 2 using xhci-hcd

[   53.868423] usb 1-1: device descriptor read/64, error -71

[   54.092343] usb 1-1: device descriptor read/64, error -71

[   54.316535] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd

[   54.333466] usb 2-1: New USB device found, idVendor=0451, idProduct=8140, bcdDevice= 2.00

[   54.333481] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

[   54.452210] usb 1-1: new low-speed USB device number 3 using xhci-hcd

[   54.572309] usb 1-1: device descriptor read/64, error -71

[   54.670114] hub 2-1:1.0: USB hub found

[   54.694422] hub 2-1:1.0: 4 ports detected

[   54.796304] usb 1-1: device descriptor read/64, error -71

[   54.900693] usb usb1-port1: attempt power cycle

[   55.532133] usb 1-1: new low-speed USB device number 4 using xhci-hcd

[   55.532585] usb 1-1: Device not responding to setup address.

[   55.736663] usb 1-1: Device not responding to setup address.

[   55.940230] usb 1-1: device not accepting address 4, error -71

[   56.060301] usb 1-1: new low-speed USB device number 5 using xhci-hcd

[   56.060731] usb 1-1: Device not responding to setup address.

[   56.264663] usb 1-1: Device not responding to setup address.

[   56.468170] usb 1-1: device not accepting address 5, error -71

[   56.468370] usb usb1-port1: unable to enumerate USB device

I attach the schematics for this part of the PCB. I am aware there is an issue with the ground missing from R17 and C66 for taking USB_VBUS to 0.5V, we fixed it wiring to ground. Input voltage to USB_VBUS is exactly 0.5.

VDD and VDD33 are clean. 
Any hints?

TC100600.PDF.pdf

  • 5V_USB is supplied by an external board and is ok, if I try to plug any device to the USB 3.0 and 2.0 nothing gets detected and no messages from Linux kernel at all.

    Here the result of "lsusb -v":

    Bus 002 Device 002: ID 0451:8140 Texas Instruments, Inc. 
    Device Descriptor:
      bLength                18
      bDescriptorType         1
      bcdUSB               3.10
      bDeviceClass            9 Hub
      bDeviceSubClass         0 Unused
      bDeviceProtocol         3 
      bMaxPacketSize0         9
      idVendor           0x0451 Texas Instruments, Inc.
      idProduct          0x8140 
      bcdDevice            2.00
      iManufacturer           0 
      iProduct                0 
      iSerial                 0 
      bNumConfigurations      1
      Configuration Descriptor:
        bLength                 9
        bDescriptorType         2
        wTotalLength           31
        bNumInterfaces          1
        bConfigurationValue     1
        iConfiguration          0 
        bmAttributes         0xe0
          Self Powered
          Remote Wakeup
        MaxPower                0mA
        Interface Descriptor:
          bLength                 9
          bDescriptorType         4
          bInterfaceNumber        0
          bAlternateSetting       0
          bNumEndpoints           1
          bInterfaceClass         9 Hub
          bInterfaceSubClass      0 Unused
          bInterfaceProtocol      0 Full speed (or root) hub
          iInterface              0 
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x81  EP 1 IN
            bmAttributes           19
              Transfer Type            Interrupt
              Synch Type               None
              Usage Type               Feedback
            wMaxPacketSize     0x0002  1x 2 bytes
            bInterval               8
            bMaxBurst               0
    Hub Descriptor:
      bLength               1
      bDescriptorType       4
      nNbrPorts            16
      wHubCharacteristic 0x0140
        Ganged power switching
        Ganged overcurrent protection
      bPwrOn2PwrGood        4 * 2 milli seconds
      bHubContrCurrent     64 milli Ampere
      bHubDecLat          0.64 micro seconds
      wHubDelay            96 nano seconds
      DeviceRemovable    0x00 0x00 0x00
     Hub Port Status:
       Port 1: 0000.06a0 highspeed lowspeed
       Port 2: 0000.06a0 highspeed lowspeed
       Port 3: 0000.06a0 highspeed lowspeed
       Port 4: 0000.06a0 highspeed lowspeed
       Port 5: 0000.06a0 highspeed lowspeed
       Port 6: 0000.06a0 highspeed lowspeed
       Port 7: 0000.06a0 highspeed lowspeed
       Port 8: 0000.06a0 highspeed lowspeed
       Port 9: 0000.06a0 highspeed lowspeed
       Port 10: 0000.06a0 highspeed lowspeed
       Port 11: 0000.06a0 highspeed lowspeed
       Port 12: 0000.06a0 highspeed lowspeed
       Port 13: 0000.06a0 highspeed lowspeed
       Port 14: 0000.06a0 highspeed lowspeed
       Port 15: 0000.06a0 highspeed lowspeed
       Port 16: 0000.06a0 highspeed lowspeed
    Binary Object Store Descriptor:
      bLength                 5
      bDescriptorType        15
      wTotalLength           42
      bNumDeviceCaps          3
      USB 2.0 Extension Device Capability:
        bLength                 7
        bDescriptorType        16
        bDevCapabilityType      2
        bmAttributes   0x00000006
          Link Power Management (LPM) Supported
      SuperSpeed USB Device Capability:
        bLength                10
        bDescriptorType        16
        bDevCapabilityType      3
        bmAttributes         0x00
        wSpeedsSupported   0x000e
          Device can operate at Full Speed (12Mbps)
          Device can operate at High Speed (480Mbps)
          Device can operate at SuperSpeed (5Gbps)
        bFunctionalitySupport   1
          Lowest fully-functional device speed is Full Speed (12Mbps)
        bU1DevExitLat          10 micro seconds
        bU2DevExitLat        2047 micro seconds
      Container ID Device Capability:
        bLength                20
        bDescriptorType        16
        bDevCapabilityType      4
        bReserved               0
        ContainerID             {008014d5-854c-b9c1-0319-8fc2b6c9d000}
    Device Status:     0x000d
      Self Powered
      U1 Enabled
      U2 Enabled
    
    

  • Hi Brian, did you had the chance to take a look at the schematic? Regarding the power sequence, is it important to power VDD33 before Vdd even if we toggle the GRSTz pin after 10 seconds?

    Regards

  • Hi Riccardo:

           It's ok to power VDD33 before Vdd even if we toggle the GRSTz pin after 10 seconds, but GRSTz pulse should be >3ms.

          I checked schematic , upstream should be detected.

      for down stream , did you connect DP/DM correct? normally pin 2 is D- 

     From your test log, [   54.333466] usb 2-1: New USB device found, idVendor=0451, idProduct=8140, bcdDevice= 2.00 

      it looks USB3 hub is detected, what device you connected on downstream port?

    Regards

    brian

  • Hi Brian,

    about the DP/DM yes we are aware it is not a standard pinout, we made the connection accordingly. We tested plugging USB flash drive, USB wifi dongle and a USB modem, no signals at all from downstream port.

    The device is detected but "unable to enumerate USB device" is the last log and no device attached is been detected from linux.

    I checked the link you sent and it seems the crystal is not oscillating, we checked the component and it is mounted well. 

    Actually the VDD is stable before the VDD33 but at that time the GRSTz is low. we set GRSTz to high after about 10 seconds from powering on the board.

  • After  1.1v and 3.3v are stable , hold GRSTz low >3ms should be good enough.

    Something looks wrong if crystal is not oscillating, how is the soldering of ground pad?

    Regards

    Brian

  • Hi Riccardo::

       Any update?

    Regards

    Brian

  • Hi Brian,

    there were an error in the schematics but connector side. TX and RX were swapped.

    Thank you for your support. Best regards