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

TUSB7340 issues support need

WELLES WANG
Prodigy 60 points
Other Parts Discussed in Thread: TUSB7340

TUSB7340 in Linux 3.0.3.5 system.we use USB3.0 HDD copy test. occur below as error xhci_hcd 0000:01:00.0: WARN: transfer error on endpoint usb 4-3: reset SuperSpeed USB device number 2 using xhci_hcd xhci_hcd 0000:01:00.0: WARN: short transfer on control ep xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep d6ab7120 xhci_hcd 0000:01:00.0: xHCI xhci_drop_endpoint called with disabled ep d6ab714c what next step.

by the way, we check out  pin A45, B41 of TUSB7340 connect  PCIE port REFCLK+ and REFCLK- it's opposite with TI's  TUSB7340EVM layout, may be it important  cause of the foult. 

 

 thanks  

  • 0
    TI__Expert 4055 points

    Hello Welles,

    I see that you are using an old version of the Linux Kernel (probably around 2 years old). By that time the xHCI driver development was in early stages (xHCI driver development is maintained by the Linux community), so the operation/behavior between the driver and the TUSB7340 could be unpredictable and unstable (this has been verified by internal testing when using kernel versions older than 3.2)

    Anyhow, I highly recommend to update the version of your kernel to the latest stable version available (3.11.4 as of now) which will contain the latest changes/fixes for the xHCI driver, thus, the behavior of not only the TUSB7340 but also any other USB3.0 device will be highly improved.

    Regarding the inversion of the REFCLK, I don't see any issue on that.

    Best Regards,

    Alexis Cortes. 

  • 0 in reply to Alexis Cortes9585
    Prodigy 60 points

    dear alexis 

    appreciating  your response.

    in order your advice, concern  about  Linux Kernel,we run  the same version at  TUSB7340EVM,it's ok.

     USB2.0 device  no problem, only  several USB3.0 devices occur fault.

    we change REFCLK  connect  line , the status maintain previous.

    another problem , TUSB7340  surface temperature reach to 80℃  more than  TUSB7340EVM  obvious.

    may be TUSB7340  layout need  improve , does USB3.0 device reqiure higher quality  PCB design?

    we'll find out new version  kernel try again.

    any proposal  let us know.

    thank you 

    Best Regards

    welles wang

     

  • 0 in reply to WELLES WANG
    TI__Expert 4055 points

    Hi Welles,

    For a proper PCB design please make sure to follow the documents and application notes on the TUSB7340 website:

    - TUSB73x0 Board Design and Layout Guidelines (Rev. B)

    - QFN/SON PCB Attachment Application Report (Rev. A)

    - Design Summary Multi-row Quad Flat No-lead (MRQFN)

    Best Regards,

    Alexis Cortes.

  • 0 in reply to Alexis Cortes9585
    Prodigy 60 points

    Alexis

    thanking your reply.

    we used linux3.4  inspect TUSB7340EVM with 4 kinds of USB3.0 devices again,  accidentally,it's occurs can't identify the device,it's duty 20% lose efficacy.

    could you have any advice?

    thanks 

  • 0 in reply to WELLES WANG
    TI__Expert 4055 points

    Hi Welles,

    I saw that you opened another e2e post that could be related to this. Please make sure that the kernel you are using has the xHCI driver stack enabled. Also, what do you mean when you say that the USB3.0 device is not identified (it doesn't get recognized at all? not even as a high speed device?  Could you send the dmseg log after you plug to the host one of the USB3.0 devices?

    What happens if you use a different xHCI host (in case you have another xHCI host available at your end)?

    Aditionally, are you powering externally the TUSB7340 EVM? Or only via the PCIe bus. You have to power the TUSB7340 EVM externally in order to make its ports to work.

    Best Regards,

    Alexis Cortes.

  • 0 in reply to Alexis Cortes9585
    Prodigy 60 points

    Dear Alexis

    we were using linux3.4 for contrastive test on TUSB7340EVM and new version improved PCB  The EVM inspection result more better than the new one. we uesed  external laboratory power supply in this  inspection

    EVM  desn't recognize USB3.0  device at 20% condition , but it's can be run with USB2.0 totally.

    the new PCB is similar too, but more failure rate.  

    there is an appearance, change some one of  host port  when we didn't recognize USB3.0  on EVM at power on status,it's can be normal operated. 

    we test various of power start sequence with external power , there hasn't edffect any more.

    I'll send you the error code recoder later.

    one question:

     what's the dmseg log,

    could provide orginal code special for TUSB7340 drive on  linux version.

    thanks

     

     

     

     

  • 0 in reply to WELLES WANG
    TI__Expert 4055 points

    Hi Welles,

    Could you elaborate more on the 20% condition with the TUSB7340 EVM? Could you explain the exact reproduction steps along with the system characteristics? Which USB3.0 devices are you using? Could you provide the exact kernel version (on a console type: uname -r)?

    The xHCI driver is developed and managed entirely by the Linux community under the GNU General Public License (open source) so you can get the kernel source files directly from the linux community (you can find the source files at  www.kernel.org).

    My first suggestion will be to update the kernel on your system to the latest stable version available from kernel.org (version 3.12), this way you will make sure that you are getting the latest changes/fixes of the xHCI driver stack. The kernel you are using is a bit old so it is highly possible that upgrading the kernel will solve issues you are experiencing (bare in mind that the kernel is continuously change and fixes are being applying regularly).

    About 'dmesg': it is a linux command that prints kernel messages. Some info about this command: http://www.linfo.org/dmesg.html.

    Please do the following:

    1. After powering on the system open a linux console terminal.

    2. On the terminal, type: 'dmesg -c' (without quotes). Send the log you get from this.

    3. Afterwards, connect a USB3.0 devie to the host.

    4. Get the dmesg log again and send it too.

    Please let me know if you have any questions or comments.

    Best Regards,

    Alexis Cortes.