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.

DS90UB926Q-Q1: Does the MCU sends "user data" to 926Q through I2C, then sends it to 925Q through fpd-link, and temporarily stores it in 925Q reg?

Part Number: DS90UB926Q-Q1
Other Parts Discussed in Thread: TDA2EG-17

Hi Team

The customer has a usage situation,
TI TDA2EX / LINUX BASED / vision sdk
The MCU sends "user data" to 926Q through I2C, sends it to 925Q through fpd-link, and temporarily stores it in 925Q reg

Based on the following feasibility, :
1. 925Q reg, where will the user data be stored?
2. Will the values in reg be kept to ensure the reliability of the data?
3. Because of reverse design, INTB cannot be used
4. Does Linux based have relevant driver support/and sample code?
5. If the fourth point cannot be supported, what is the feasibility of I2cget && i2cdetect?

User data may be brightness value or motor height

MCU will send HUD DATA to TDA2EG-17 of ARC via I2C and pass it through FPD LINK!

  • Hi Kygo, 

    1. 925Q reg, where will the user data be stored?
    2. Will the values in reg be kept to ensure the reliability of the data?

    This understanding is a bit incorrect. Our devices never store the "user data"/I2C data in registers. In normal SER to DES I2C direction, the deserializer only acts as a proxy master, but from the host controller perspective on SER side, the I2C is end to end and communicates directly with the MCU with normal I2C protocol. Likewise, the MCU on DES side can also be the master and write directly to the SoC registers, with no intermediate register storage at SER.

    4. Does Linux based have relevant driver support/and sample code?

    We do not have linux sample code/drivers.

    Regards, 

    Logan