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 Clemens,
1. Use SPI [MCU & mouse sensor]
2. Is the TXS0104E capable of bidirectional transmission?
The TXS is auto-bidirectional, i.e., the same signal line could be used in either direction.
SPI does not have bidirectional signals. While there are signals going in both directions, each individual signal has a fixed direction. I recommend the TXU0304 instead.
Hi Clemens/Jack,
TXU0304 supports up to 200Mbps, while the current project only requires 8Mbps.
The TXS0104E push-pull mode at 24Mbps is closer to the current requirements.
For the TXS0104E, how can it be switched to push-pull mode, and what aspects of the circuit design should be considered?
The TXS itself does not have a push/pull mode.
When the TXS is driven with push/pull signals, it is faster than when it is driven with open-drain signals.
The TXS has internal pull-up resistors, so it does not work with pull-down resistors. And due to the edge accelerators, it is sensitive to noise or ringing on the data lines.
Hi Clemens,
1.TXS itself does not have a push/pull mode, so what does the datasheet mean?
2.Do you mean that TXS cannot be applied to this project?
1. When the TXS is driven with push/pull signals, it is faster than when it is driven with open-drain signals.
2. It will work. But in my design, I would use the TXU0304.
Hi Hemry,
Even though the bandwidth of the TXU device is higher and then speed of your application is not very fast (8MHz/ 16Mbps), the TXU will still be a better choice due to its buffering capability and improved robustness (i.e schmitt trigger inputs) over the TXS0104E. Ideally, the TXS0104E is to be used if the signals truly auto-direction per channel. Since there is no buffering circuitry internal to the TXS device, its open-drain outputs provide compatibility to both push-pull and open drain drivers.
Regards,
Jack