• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 33 subscribers
  • Views 904 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.

DS90UH949A-Q1: Interfacing of TI serializer using a microcontroller

Vivek Karna
Prodigy 10 points
Part Number: DS90UH949A-Q1

Hello,

  • 0
    TI__Guru 66810 points

    Hi Vivek,

    The serializer device is written to by standard I2C interface, reading and writing registers through standard I2C protocol. From I2C interface and protocol perspective, there shouldn't be any additional considerations needed to successfully communicate to the SER. The device address is defined by SER IDX pin strap modes, and address offsets are described in the datasheet of device. 

    Regards, 

    Logan

  • 0 in reply to Logan Cummins
    Prodigy 10 points

    Hello Logan, 

    Thank you for the information. 

    Can you please tell me how any microcontroller can control the application of the TI serializer using I2C? The thing is, I haven't found any register mapping list in the TI serializer documentation. Can you please provide me with that, it would be a great help for me. If you have any links to interface any TI-based serializer using a microcontroller then that would also be a great help. 

    Thanks.

  • 0 in reply to Vivek Karna
    TI__Guru 66810 points

    Hi Vivek, 

    You will need to consult with I2C vendor on how to implement I2C transactions. You can reference the EVM as well, since as you mentioned there is an MCU on-board that is communicating I2C transactions that will demonstrate the schematic level implementation (pull-up resistor to VDD, I2C lines tied together, etc)

    Section 7.6 in the datasheet details the register map of the serializer device. It is unclear what exactly you are needing help configuring, so if you have something in particular that is needed; please let me know.

    At a high-level, these devices do not need any software configuration to operate and can be configured by the ModeSel straps. If you are needing to communicate to remote MCU on deserializer side, then you must enable I2C pass-through and set up slave alias in serializer. Please refer to section 7.5 of the datasheet, which has all the information required to accomplish this.

    Regards, 

    Logan 

  • 0 in reply to Logan Cummins
    Prodigy 10 points

    Hello Logan,

    Actually, I want the extract the information of a touch screen that is connected to the DeSel side and when the data come to the Sel side of touch screen, using I2C communication, I want to fetch those information. Can I know that how can I use the interrupt fucntion of Sel device using the microcontroller.

    Is there any software tool which can ease my work of configuration of Sel device?

    Thanks.

  • 0 in reply to Vivek Karna
    TI__Guru 66810 points

    Hi Vivek, 

    Thanks for the additional details. 

    In order for the SER to communicate to the remote touch controller the following is required to be set in SER registers via I2C:

    • Set-up I2C device alias of touch-controller in SER registers according to section 7.5 of the datasheet
    • Enable I2C pass-through in SER

    Once above to items are complete, then SER-side MCU can talk through the SerDes link to the remote touch-controller. 

    Regards, 

    Logan

  • 0 in reply to Logan Cummins
    Prodigy 10 points

    Hello Logan,

    Can I not directly get the information of touch display from SER device using I2C communication, as all the data is coming to SER device also using DESER device, as touch screen is connected to DESER device? And what is the use of the ISR register of SER?

  • 0 in reply to Vivek Karna
    TI__Guru 66810 points

    Hi Vivek, 

    Vivek Karna said:
    Can I not directly get the information of touch display from SER device using I2C communication, as all the data is coming to SER device also using DESER device, as touch screen is connected to DESER device?

    Not quite sure I follow this question. After setting up the touch screen device address/alias, you can communicate directly to the Touch controller device from MCU (host controller on SER side). In other words, the Ser to Des is an extension of the local I2C bus and will allow direct read/writes from host controller on SER side to touch controller on Des side. 

    Vivek Karna said:
    And what is the use of the ISR register of SER?

    The INTB_IN (DES) and INTB (SER) can be used if interrupts from touch controllers need to be used to create interrupts out of SER into the MCU. 

    Touch controller interrupt signal is a common use of the INTB pins on SerDes link. 

    Regards,

    Logan