Other Parts Discussed in Thread: P82B96
For TIDA-060013, may I ask if the slave can be CAN based? Or we must transform it to I2C at slave side?
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.
The intention of this design is to extend I2C by putting the signal to a differential CAN bus that can propagate over longer ranges. You don't have to transform it back to I2C, but then I'm not sure I understand what your intention is with using this design. Why not just use CAN?
Customer need this because the master doesn't support CAN.
Per my understanding. this reference design could only change I2C signal to differential signal through P82B96 and CAN transceiver, but the protocol is still I2C? SDA and SCL are separated into 2 CAN signals, if it support CAN in the slave side, then how can we make sure these 2 signals are received/transmitted at the same time?
Will the responder (formerly slave) side be feeding directly into the MCU from the CAN transceiver? Or what will be receiving after the CAN transceiver? If the communication is only going in one direction, your configuration would work, you would just just connect the CAN transceivers' RXD pins to the SDA and SCL of the receiving device. If communication needs to happen in both directions, then that won't work, you'll need something to drive the I2C communication in the other direct as well.