• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 134 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.

TUSB2E11: Impedance Limit

Allan Fan
Expert 7690 points

Part Number: TUSB2E11
Other Parts Discussed in Thread: TUSB2E221

Hi experts,

May I learn from you if we place TUSB2E111 on both the Host and Slave sides, are there any impedance limits for the cable or pcb between the USB2? Also what's the impednace limit for the eUSB side? 

 

BR,

Allan

  • 0
    TI__Guru 52405 points

    Hi Allan,

    The eUSB2 spec defines the typical differential impedance and amount of variation allowed in the eUSB2 trace:

    Section 7.1.1 of the USB2 spec defines the cable requirements for USB2 cabling:

    The TUSB2E11 should comply to both these specs.

    Thanks,

    Ryan

  • 0 in reply to Ryan Kitto
    TI__Guru 52405 points

    Hello,

    Closing thread due to inactivity. If you have any follow-up questions or concerns, feel free to reply.

    Thanks,

    Ryan

  • 0 in reply to Ryan Kitto
    TI__Expert 7690 points

    Hi Ryan,

    In addition to impedance limits, customer also inquire about the maximum allowable DCR loss. Their concern is that the low voltage levels of eUSB2 may lead to logic level recognition errors at the receiver side if the voltage drop is significant. Would you please clarify that? 

    Thanks,

    Allan

  • 0 in reply to Allan Fan
    TI__Guru 52405 points

    Hi Allan,

    Is the customer worried about the max allowed DCR on the eUSB2 side or the USB2 side?

    For the USB2 side, we have a table that outlines the max DCR on the USB2 side based on the USB2 PHY configurations:

    For the eUSB2 side, these tables from the TUSB2E221 should also apply to the TUSB2E11:

    Thanks,

    Ryan