• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 33 subscribers
  • Views 1319 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.

Redriver for FPD LINK-III (We are using DS90UB948 & DS90UB947)

YUTI TRIVEDI
Prodigy 50 points
Other Parts Discussed in Thread: DS30BA101, DS30EA101

Dear TI Team,

We are using the Serializer (DS90UB947) & De-serializer (DS90UB948) chips for the video interface.

Both these chips are mounted on two different PCB's. A cable connects these two PCB's via the FPD-Link III.

However due to the length constraints we are getting signal integrity issues.

Request your assistance for the following two points:

1) Are there any re-drivers available for the FPD LINK-III so that the signal integrity issues can be solved.

2) What would be the maximum length/breaks possible for the FPD Link-III

Thanks.

  • 0
    TI__Mastermind 29655 points
    Hi Yuti,

    I am part of a group that supports redrivers separate from FPD-Link III, but we may be able to support your need here for Question 1. We can offer redriver/cable driver/cable equalizer solutions, but it is important to note that our redrivers do not support back-channel communication .

    What is your operating pixel clock, and are you using single or dual link?

    If the serial bit stream is 3.125 Gbps or less, the DS30BA101 cable driver and DS30EA101 cable equalizer may be a good fit to improve signal integrity.

    Thanks,

    Michael
  • 0 in reply to Michael Lu (Santa Clara)
    Prodigy 50 points

    Hi Michael,

    We are currently using only one channel however in future would like to explore using both the links for higher resolution bigger screens.

    Operating pixel clock would be 96MHz.

    Since the serializer also tracks errors indicated by the CRC fields in each back channel we would require the CRC & I2C information.

    Hence would require the back channel information as the back channel contains the I2C, CRC and 4 bits of standard GPIO information.

    Since the serializer and deserializer can be placed apart from each other, there would be a lot of breaks in the path, such issues might have been identified earlier for which a workaround might have been developed.

    Request your assistance for suggesting a re-driver for the FPD-Link III which has back channel capability.

    Regards,

    Yuti

  • 0 in reply to YUTI TRIVEDI
    TI__Mastermind 29655 points
    Hi Yuti,

    Unfortunately, we do not have redrivers in our current portfolio that can support back-channel communication. Our existing redriver portfolio only supports data traveling in one direction per channel.

    I will reach out to our automotive team to see if they can help with your other FPD-Link related questions.

    Regards,

    Michael
  • 0 in reply to Michael Lu (Santa Clara)
    Prodigy 50 points

    Thanks Michael,

    Sure looking forward to interaction with you automotive team for our FPD-Link III related questions.

    Regards,

    Yuti