• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 401 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.

TUSB1002A: Minimum trace length to add TUSB1002A

Antony Lin
Genius 13480 points
Part Number: TUSB1002A

Hi,

Do we define a minimum trace length (from CPU to USB connector) to add TUSB1002A on this data path?  Or, this minimum trace length requirement depends on the CPU itself and may not be a fixed number across all the CPU platforms?

Thanks!

Antony

  • 0
    TI__Guru 64326 points

    Hi Anthoy,

    We do not define a minimum trace length to add TUSB1002A because there are multiple factor beyond the CPU or SOC selection that effect whether a device like TUSB1002A is needed. For example even with short traces if the layout includes many vias, stubs or other impedance discontinuities that can add ISI to the system, a redriver may needed to equalize the signal. Even PCB board material can greatly effect performance. That being said the CPU or SOC selection is very important and taking into account the recommended design guidelines for your particular SOC or CPU is also important. Does this answer your question?

  • 0 in reply to Malik Barton57
    TI__Genius 13480 points

    Hi Malik,

    Thanks for your reply.  I think the description is reasonable and I can communicate this with my customer accordingly.

    In parallel, do we defined the minimum trace length between redriver and USB connector (on a host system)?  Is there a general guideline for this for different protocol of redriver (e.g. DP, USB2, USB3-5G...etc)?

    Thanks!

    Antony

  • 0 in reply to Antony Lin
    TI__Guru 64326 points
    Hi Antony,

    We do not define a minimum trace in this case as and a maximum is hard to define for the reasons mentioned before. Could you describe the customer application and distances they would like to achieve? I may be able to give more insight with more details. Is this a Type-C application? Is the customer wanting to use TUSB1002A specifically? What is the customer looking for from us? Each protocol is slightly different and requires different flavors of redrvier in certain situations. For example USB2 interface can go a lot further than USB3 due to the larger swing defined by the interface.