Hi team,
My customer wants to use the TMDS181 cascade, do we have some test datas for this usage? Will they meet some problems if use the chip like this? Thank you.
BR
Frank
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.
Hi team,
My customer wants to use the TMDS181 cascade, do we have some test datas for this usage? Will they meet some problems if use the chip like this? Thank you.
BR
Frank
Hi Frank,
The problem os placing several TMDS181 in cascade may come from DDC and HDCP, not really from TMDS181 redriving/retiming capabilities.
We recommend using snoop mode to avoid interoperability issues, if the cable is too long you may need other I2C buffers.
HDCP2.2 checks if the sink is not far away from the source if there are several TMDS181 in cascade there will be some delay especially in retimer mode.
Could you elaborate about the application?
Regards
Hi Frank,
40 or 100 stages are a lot, and 2m is kind of short.
TMDS181 can work in redriver or retimer mode, by default, it is redriver with data rates below 1Gbps and retimer with data rates above 1Gbps.
In redriver mode jitter and skew will be adding up, while in retimer mode jitter and skew is cleaned in each stage.
TMDS181 can be configured by I2C to retimer mode across full data rate range.
I recommend opening a HelpMe ticket to further review of this amount of devices in cascade.
Regards