• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 277 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.

DS90UH948-Q1: Questions for DS90UH948 & 949 application

Jacky Wang(QD)
Genius 11590 points
Part Number: DS90UH948-Q1

Hi Team,

Our customer is evaluating DS90UH948 and DS90UH949 in their application as attached, and having following questions, can you help to check them? Thanks a lot!

Questions for DS90UH948&949 Applications.pdf

Q1: Can we connect this signal to DS90UH948 GPIO pins for insert detection? Will 948 automatically report GPIO status to 949?

Q2: Do we need an additional MCU on deserializer side to configure 948? Can we achieve Serializer side I2C transparent transmission to deserializer side to configure other I2C devices like touch screen controller on LCD?

Q3: Do we need an additional MCU on serializer side to configure 949?

Q4: Can we achieve Serializer side I2C transparent transmission to deserializer side to configure other I2C devices like touch screen controller on LCD?

 

 

 

  • 0
    TI__Guru** 108530 points

    Hello Jacky,

    1) why do you need to use GPIO for that purpose? why not to monitor LOCK pin which will get high once the Serializer is connected!?

    2) MCU is not required on the DES side. You can configure your DES and Display using the I2C local bus of the SER.

    3) MCU to configure the 949 only is not required. You can configure the 949 by hardware pin settings. But the MCU on the SER side is may be necessary to monitor/configure the remote side.

    4)Yes this is possible.