• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 151 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TSER953: I2C Slaves connected to TSER953

David Rodriguez
Prodigy 26 points
Part Number: TSER953
Other Parts Discussed in Thread: TDES954

Hello Everyone,

I am designing a board that has both a Camera Module (MIPI) and an IMU (I2C). In a previous post it was confirmed that both can be connected to a TSER953 which is then connected over Coax to a TSER954 and then onto the ISP. I am a little confused regarding the I2C remote host/slave configuration. Here a few a questions that I have.

  • Is it possible to simply have both the Camera Module and IMU as Slaves and the TSER953 acting as a Remote Host?
  • If so, can the SCL and SDA pins on the Camera Module and IMU connect together on a single path to the SCL & SDA pins on the TSER953? (Pullup resistors between TSER953 and junction of SCL/SDA.)
  • Or, would I need to add a Serial Control Bus (i.e. I2C Switch or I/O Expander) on the board that connects to the TSER953 SCL/SDA pins and then communicates to the Camera Module and IMU?
  • How do I confirm that the Camera Module and the IMU have distinct addresses both on the pin connection and on the software register? Is this where the IDX pin comes into play?

Thank you for your time!

All the best,

David

  • 0
    TI__Genius 11330 points

    Hi David,

    Thanks for your inquiry. The below points should help to respond to the corresponding points above:

    1. The TSER953 often acts as a remote host controlling image sensors and other devices in the camera module
    2. This configuration should function as long as the I2C is configured properly properly with pull up resistors and the connected devices each having unique I2C addresses
    3. The configuration listed in point 2 should be effective
    4. The IDx pin is used to set the I2C address of the serializer, however alternative methods will need to be used to set unique I2C addresses on both the IMU and camera sensor. These datasheets should contain the necessary details to do so.

    For details on how to properly configure remote slave operation, section 7.5.3 of the TDES954 should be helpful. Here you will find the applicable TDES954 register settings which can be used to set up the configuration which you described.

    Let me know if you have any other questions I can help with on this!

    Best,

    Thomas

  • 0 in reply to Thomas Bejin
    Prodigy 26 points

    Hello Thomas,

    Thank you so much for your reply. I really appreciate your time helping me with my questions. The V3 Link is pretty amazing and there is a lot of parts to understand!

    With some additional feedback from Lysny Woodahl on another Forum post, I believe I am finally beginning to understand the I2C config we need for our application. By using a remote host and alias address set-up we should be able to set the unique addresses necessary to distinguish the SER, Camera Module, and IMU.

    The IDX pin was really confusing me because I wasn't sure if it was setting the I2C address just for the SER or for any slaves pinned to it. The Section in the DESER data sheet is definitely helping to explain it all.

    Thank you again for your time. If any other questions come up I will definitely reach out.

    All the best,

    David