• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 331 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DS90UH941AS-Q1: I2C pass through and back channel for Independent 2:2 Mode

Jared Becker
Genius 11845 points
Part Number: DS90UH941AS-Q1

Hi Team,

When using the 941AS to drive two displays in independent 2:2 mode, are there separate I2C pass throughs and I2C back-channels to each display? If yes, how are those configured so you know you are talking to the correct display?

Thank you,

Jared

  • 0
    TI__Guru** 103215 points

    Hello Jared,

    Please see register 0x1E for controls related to the secondary I2C port on FPD-Link TX port 1 for splitter/replicate modes. Enable bit 2 to allow independent I2C on both ports for 2:2 mode. 

    The deserializer ID/alias and the slave ID/alias registers are all port-specific. Select either PORT0_SEL or PORT1_SEL in register 0x1E to access port 0 or port 1 specific registers respectively where you can program the desired slave ID/aliasing for each link. (Or you can use the secondary I2C address DeviceID+1)

    After those registers are set up for each port (and assuming there are no overlapping aliases programmed between any of the devices across both ports), then transactions will get routed to the end point devices on either link appropriately. 

    Best Regards,

    Casey 

  • 0 in reply to Casey McCrea
    TI__Genius 11845 points

    Hi Casey,

    Thank you for the quick response. When you say, "...where you can program the desired slave ID/aliasing for each link." are you talking about programming the DES slave ID so you know which information is coming from which display on the back channel?

    -Jared

  • 0 in reply to Jared Becker
    TI__Guru** 103215 points

    Hey Jared,

    There are two DES ID/DES Alias registers in 941AS: one set for port 0 and one set for port 1. For each port you can independently program the DES ID to match the physical I2C address of the remote deserializer, and then you can program two independent DES alias addresses so that you can assign different I2C virtual addresses to the two deserializers as needed. When you send a command to the programmed alias address, it will get routed to the appropriate deserializer based on the ID/alias/port you have configured. Same goes with slave devices attached to the remote deserializer I2C buses on either link.

    Best Regards,

    Casey