Other Parts Discussed in Thread: TUSB211,
In the HD3SS3220 DFP Eval module, there is a redriver for the USB2 signals (TUSB211), but there is not a redriver for the USB3 signals? Why is there no redriver for the USB3 signals?
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.
it just depeds on your PCB layout If needed, you can add USB3 redriver as well.
Regards
brian
thanks for the reply, but please provide a more direct answer - why was the USB3 redriver not needed in that eval board?
... what about its PCB layout caused it to not be needed? Also, please direct me to any literature like app notes that may clarify how to determine if it is needed.
muxes and redrivers have different applications. Redriver is needed when the PCB on the board is too long and caused lots of loss more than CPU or SOC can handle.
You can look at white paper SLYY121 from ti.com
HD3SS3220DFP module is designed to test type-C USB3, actually TUSB211 is not needed here.
Regards
Brian
Thanks for the whitepaper reference and clarifications! What do you mean by "designed to test type-c USB3" and why does that mean TUSB211 is not actually needed in the DFP eval board?
HS3SS3220 is a mux only for USB3 signal. We put USB2 redriver here is just to promote TUSB211 device, customer can either use it or not for their system design. By the way, input and output of TUSB211 are routed together on PCB , so customer can just remove it if don't needed.
Regards
Brian