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.

DS90UB933-Q1: Does TI have sone info to introduce DS90UB933-Q1?

Part Number: DS90UB933-Q1

Hi team,

My customer uses the DS90UB933-Q1 to design first time.

Do you have an easy way to understand how to control DS90UB933-Q1  to get sensor info? 

Should be need a external MCU through I2C to get sensor info? 

  • Hi Jimmy,

    To clarify, you would like the ECU to communicate with the imagers correct? 

    You can have the ECU module access the imager by sending I2C transactions to the address of the imager into the 934 I2C bus. The 934 will send the transaction to the 933, and then the 933 will recreate the transaction on its own I2C bus to send to the imager. The imager will send I2C transactions back to the SER where it will travel across the FPD-Link back to the ECU. You will just need to configure the sensor addresses and aliases in the 934 targetID[x] and targetAlias[x] registers. You can also program the SCL high and low time in the serializer.

    You can refer to this app note for more information about I2C communication in FPD-Link III devices.

    Regards,

    Cindy

  • yes, I sent to customer. thank you

  • No problem, let me know if you have further questions. 

    Regards,

    Cindy

  • Hi Cindy,

    As shown in Figure 7-13 below, the communication between SER A (DS90UB933-Q1) and Camera is through I2C. In the actual I2C communication, is SER A (DS90UB933-Q1) Master? or Slave?
    Or as shown in Figure 7-15 below, uC (0xA2) is added to the I2C bus between SER A (DS90UB933-Q1) and Camera. In the actual I2C communication, is SER A (DS90UB933-Q1) Master? or Slave?

  • Hi Jimmy,

    Once the transaction passes across the FPD-Link to the 933, the 933 then acts as a proxy master since it will regenerate the I2C clock to send the I2C transactions to the imager slave device. Figure 7-15 is showing an example of there being multiple slave devices connected to multiple serializers. The SER is still the proxy master. 

    Regards,

    Cindy