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.

Which switch can support USB 2.0, HDMI 1.4, UART, I2C, Ethernet, 1000Base-T, SATA, etc.....

Other Parts Discussed in Thread: PCA9306, TCA9617B, TCA9517

E2E community,

It is common question to ask will (this device) support ( this signal type/standard).  When selecting an appropriate signal switch for your signal type/standard you need to consider 3 things : Configuration, Bandwidth, and voltage range.

Below is a chart to help the switches and multiplexers e2e community decide which switches and muxes can support which signal standards based on configuration, bandwidth and voltage range.  E2e community experts please help fill out the table or verify I have a line item correct. Please place your comments below.   I will then go back and add the common switches that could support that standard. 

Thank you,

Adam

  • This is great! Can this be added to the parametric table on ti.com?
  • Adam,

    I see a few things that need to be corrected in regards to I2C.

    I2C can be broken up like so:
    Interface - Data rate - Recommended Bandwidth
    Standard Mode - 100 kHz - 300 kHz
    Fast mode - 400 kHz - 1.2 MHz
    Fast Mode Plus - 1 MHz - 3 Mhz
    High Speed - 3.4 MHz - 10.2 MHz


    For common TI Level Snifters used, please also add: PCA9306, TCA9517, and TCA9617B
  • Johnathan,

    Thank you for the clarification on the I2C spec and the new part recommendations.

    Does anyone else have any updates or can verify the information? 
     
    Thank you,
    Adam

  • Regarding SPI, it is very customizable and varies quite a bit based on implementation and application so the frequency and protocol can be very different from part to part.
    1) I've seen SPI parts as slow as 100 kHz and as fast as 26MHz.
    2) I've seen "SS" or slave select referred to as "CS" or chip select in many datasheets and implementations.
    3) SPI is very loosely defined so its protocol will be different based on the part you are using.