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.

USB Hub Not working

Other Parts Discussed in Thread: TUSB7320, TUSB7340

Dear TI,

I am using TUSB7320 (EVAL board) with dart MX6 freescale based chip from variscite and these are the errors I am getting (See below).

It works with renesas chipset usb 3.0 hub but not with TI TUSB7320 chip, Could it be a driver issue? is there a specific driver that works with these chip or should it work just with the default installed driver? (TUSB7320/TUSB7340)

Please Help,

Regards

---------------------------------------------------

usb-storage 3-2:1.0: USB Mass Storage device detected
scsi3 : usb-storage 3-2:1.0
scsi 3:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6
sd 3:0:0:0: [sdb] 60751872 512-byte logical blocks: (31.1 GB/28.9 GiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 3:0:0:0: [sdb] Attached SCSI removable disk
usb 3-2: reset SuperSpeed USB device number 10 using xhci_hcd
usb 3-2: Parent hub missing LPM exit latency info. Power management will be impacted.
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a800
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a82c
usb 3-2: reset SuperSpeed USB device number 10 using xhci_hcd
usb 3-2: Parent hub missing LPM exit latency info. Power management will be impacted.
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a800
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a82c
usb 3-2: reset SuperSpeed USB device number 10 using xhci_hcd
usb 3-2: Parent hub missing LPM exit latency info. Power management will be impacted.
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a800
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a82c
usb 3-2: reset SuperSpeed USB device number 10 using xhci_hcd
usb 3-2: Parent hub missing LPM exit latency info. Power management will be impacted.
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a800
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a82c
usb 3-2: reset SuperSpeed USB device number 10 using xhci_hcd
usb 3-2: Parent hub missing LPM exit latency info. Power management will be impacted.
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a800
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a82c
usb 3-2: reset SuperSpeed USB device number 10 using xhci_hcd
usb 3-2: Parent hub missing LPM exit latency info. Power management will be impacted.
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a800
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a82c
sd 3:0:0:0: [sdb] Unhandled error code
sd 3:0:0:0: [sdb]
Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 3:0:0:0: [sdb] CDB:
Read(10): 28 00 00 00 00 80 00 00 f0 00
end_request: I/O error, dev sdb, sector 128
Buffer I/O error on device sdb, logical block 16
Buffer I/O error on device sdb, logical block 17
Buffer I/O error on device sdb, logical block 18
Buffer I/O error on device sdb, logical block 19
Buffer I/O error on device sdb, logical block 20
Buffer I/O error on device sdb, logical block 21
Buffer I/O error on device sdb, logical block 22
Buffer I/O error on device sdb, logical block 23
Buffer I/O error on device sdb, logical block 24
Buffer I/O error on device sdb, logical block 25
usb 3-2: reset SuperSpeed USB device number 10 using xhci_hcd
usb 3-2: Parent hub missing LPM exit latency info. Power management will be impacted.
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a800
xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8a0a82c

------------------------------------------------------------

  • Hello,
    Which kernel version are you using? Have you tried with the latest kernel?
    Regards
  • We have used Linux Kernel 3.14.38 and we tried 4.1.15

    we have these running on a SOM Variscite DART-i.Mx6 Board based on a Freescale arm chip.

    root@var-som-mx6:~# uname -a
    Linux var-som-mx6 3.14.38-6QP+g5b28091 #1 SMP PREEMPT Wed Mar 16 12:35:15 EDT 2016 armv7l GNU/Linux

    - So here I can see the hub from TI:
    root@var-som-mx6:~# lspci
    00:00.0 PCI bridge: Synopsys, Inc. Device abcd (rev 01)
    01:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02)

    - I just connected a USB 2 stick and this is what happened:

    root@var-som-mx6:~# usb 2-3: new high-speed USB device number 6 using xhci_hcd
    usb-storage 2-3:1.0: USB Mass Storage device detected
    scsi0 : usb-storage 2-3:1.0
    usb 2-4: new high-speed USB device number 7 using xhci_hcd
    hub 2-4:1.0: USB hub found
    hub 2-4:1.0: 7 ports detected
    hub 2-4:1.0: config failed, can't get hub status (err -71)
    scsi 0:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4
    sd 0:0:0:0: [sda] 15663104 512-byte logical blocks: (8.01 GB/7.46 GiB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI removable disk

    root@var-som-mx6:~# lsusb
    Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 007: ID 0424:2137 Standard Microsystems Corp.
    Bus 002 Device 006: ID 058f:6387 Alcor Micro Corp. Flash Drive
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


    - Here is what happened when I connect an usb stick 3:

    var-som-mx6 login: root
    root@var-som-mx6:~# lsusb
    Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 002: ID 0424:2137 Standard Microsystems Corp.
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    root@var-som-mx6:~# usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd
    usb 3-3: Parent hub missing LPM exit latency info. Power management will be impacted.
    usb-storage 3-3:1.0: USB Mass Storage device detected
    scsi0 : usb-storage 3-3:1.0
    scsi 0:0:0:0: Direct-Access Kingston DT microDuo 3.0 PMAP PQ: 0 ANSI: 6
    sd 0:0:0:0: [sda] 61457664 512-byte logical blocks: (31.4 GB/29.3 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
    usb 3-3: reset SuperSpeed USB device number 2 using xhci_hcd
    usb 3-3: Parent hub missing LPM exit latency info. Power management will be impacted.
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f00
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f2c
    usb 3-3: reset SuperSpeed USB device number 2 using xhci_hcd
    usb 3-3: Parent hub missing LPM exit latency info. Power management will be impacted.
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f00
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f2c
    usb 3-3: reset SuperSpeed USB device number 2 using xhci_hcd
    usb 3-3: Parent hub missing LPM exit latency info. Power management will be impacted.
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f00
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f2c
    usb 3-3: reset SuperSpeed USB device number 2 using xhci_hcd
    usb 3-3: Parent hub missing LPM exit latency info. Power management will be impacted.
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f00
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f2c
    usb 3-3: reset SuperSpeed USB device number 2 using xhci_hcd
    usb 3-3: Parent hub missing LPM exit latency info. Power management will be impacted.
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f00
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f2c
    usb 3-3: reset SuperSpeed USB device number 2 using xhci_hcd
    usb 3-3: Parent hub missing LPM exit latency info. Power management will be impacted.
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f00
    xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep a8782f2c
    sd 0:0:0:0: [sda] Unhandled error code
    sd 0:0:0:0: [sda]
    Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
    sd 0:0:0:0: [sda] CDB:
    Read(10): 28 00 03 a9 c4 80 00 00 08 00
    end_request: I/O error, dev sda, sector 61457536
    Buffer I/O error on device sda, logical block 7682192

    Notice it reset the superspeed USB device trying to mount it? well it keeps resetting over and over again for like a minute then it will show something like this:
    Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
    sd 0:0:0:0: [sda] CDB:
    Read(10): 28 00 00 00 04 2f 00 00 08 00
    end_request: I/O error, dev sda, sector 1071
    Buffer I/O error on device sda1, logical block 504
    Buffer I/O error on device sda1, logical block 505

    - Now when it stop resetting if I do LSUSB this is what I see: (Keep in mind that the USB stick that I put was from Kingston...)

    root@var-som-mx6:~# lsusb
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 002: ID 0951:16a3 Kingston Technology
    Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 002 Device 002: ID 0424:2137 Standard Microsystems Corp.
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    If you compare that to the first time I've done LSUSB you will not see the Kingston Device...

    So that tells me that It sees something it can read from it at low speed and retrieve the manufacturer information...But the super speed stuff get resets all the time while it's trying to mount it...until it aboard this process...

    I get the same problem on your Evaluation board (See my initial message for more detail about the eval board...) And my circuit that I designed using your part...

    Could you please provide any help about this issue? Could it be firmware related? I doubt that it is hardware since it's the same on your eval board. Which Kernel does TI recommend to use this part on?

    Please respond ASAP as we are in need to solve this problem and start using TI parts on our product or we'll be force to redesign our board with an HUB from a different manufacturer...

    Regards,
  • Hello,
    Sorry for the delay.
    We've been investigating this and we suspect that some of the USB thumb drives(recently) are not compliant with the USB spec, we need to perform more testing to be sure.
    Have you tried with different thumb drives?
    Is this detection issue random?
    Can you send a picture of the top marking of the TUSB7340 you are having issues with?
    Regards
  • On the black board it's the TUSB7340 that I am using on my design,

    I've also took a picture of the Eval board that I got to test the TUSB7320 where we were able to replicate this issue while using the iMx6 Processor. 

    Also to answer the question yes we have tried with different usb drives. same issue...

    The detection issue happens every time we put a USB 3 stick...it reset and tries to mount until it give up trying...

    Regards,

  • Hello,
    Can you change the MRRS size? Try 256 bytes.
    Look at the Table 4-55 in the datasheet.
    Regards
  • Tried that already not working...As well as other sizes too nothing works...

    How is the investigation going ?

    Regards,
  • Hello,
    We haven't been able to reproduce the issue.
    The kernel you are using looks to have a stable xHCI driver, we have tested in x64 though, so I'm thinking it could be related to the embedded processor, I will forward this request to the software/driver people.
    Regards