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

TUSB1310A: Cannot communicate USB3.0

cafain
Mastermind 6755 points
Part Number: TUSB1310A

Hi,Staff

This is a consultation about the TUSB1310A (USB3.0 transceiver) failure.

There is a problem that USB3.0 communication is not possible.
(It is possible to communicate with USB2.0)

TUSB1310A (USB3.0 transceiver)
It has been confirmed that communication is possible by cooling with a cooling spray.

When there is a problem with the USB analyzer
Power States (See TUSB1310A Datasheet 5.3.4.1 USB Power Management)

It seems that it has stopped because it cannot change from P2 to P0.

When it cools down, it works normally.

There are some boards that can make several boards and communicate with USB3.0.
I think that the operation is unstable.
※It is not a new design.

Please tell me the points to investigate the cause.


best regards
cafain

  • 0
    TI__Guru 60870 points

    Hi Cafain,

    Can you check on the failing device that the VSS pins in the center of the device have a good connection?  Can you send a trace of when the transceiver fails to transition back to P0?  Or is it just a link training issue where it drops to recovery?  Is it a consistent failure?

    Thanks,

    JMMN

  • 0 in reply to JMMN
    Mastermind 6755 points

    HI, JMMN-san

    Thank you for your speediness port.

    Comment on the current situation.

    ・The reason for cooling.
    → I was able to communicate immediately after turning on the power of the set,
    but after a lapse of time (about 1 or 2 minutes)
    Since communication is no longer possible, it is presumed to be the effect of device heat.
    (The device's normal heat generation is such that even if you touch it with your finger, you will not notice it)

    ・Cooling time
    → Lightly spraying the quenching material for a few seconds

    ・Isn't communication possible immediately after turning on the power to the board?
    → Communication is possible immediately after turning on the power of the set.
    　　After that, communication will not be possible, but communication is possible if it is cooled.

    　In particular
    -Turn on the power of the set and connect it to the PC with a USB 3.0 cable
    ・Recognized by device manager (Windows 10) (*A)
    (Up to this point, it will succeed even if the device is not cooled)
    ・After this, the device shifts to the U2 state
    ・When connecting with the set communication application
    　Communication fails if the device is not cooled
    　Successful communication when the device is cooled　

    　If communication fails, reconnect the USB 3.0 cable again
    　Recognized by device manager (returns to *A state)

    ・What is the clock source used for?
    → Using a crystal oscillator (DSO321SRDB 40MHz (1.8V) )
    <www.kds.info/.../>

    -Check at a later date if the LFPS handshake is successful.

    -The soldering condition (X-ray inspection) will be performed at a later date.
    　(It is difficult to see with BGA parts)

    best regrads
    cafain

  • 0 in reply to cafain
    TI__Guru 60870 points

    Hi Cafain,

    If the device isn't getting physically hot, but cooling it helps that seems to indicate a clocking issue.  Can you try feeding a clock to the device from a function generator?  Can you confirm the frequency of the clock source?  Do you have a scope available that analyze the compliance patterns from the phy and check for PLL or SSC issues?  If so,  download the XHSETT tool from the link here to generate the compliance mode command. Each test equipment manufacturer has their own USB3.0 test procedure, here is the generic one.

    Regards,

    JMMN