• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 78 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

SN65DSI83-Q1: Clarification on Reinitialization Sequence for SN65DSI83-Q1

Adarsh Verma
Prodigy 80 points
Part Number: SN65DSI83-Q1

Tool/software:

Dear Expert,
We are using the SN65DSI83-Q1 bridge IC to convert DSI data to LVDS for our display and are intermittently facing display blanking issues.
To recover and bring back the display to a working state, we are re-writing all the CSR registers as per the recommended sequence starting from Step 5 in the initialization flow. Despite this, we continue to observe error flags in register E5 in some cases.
Could you please confirm whether, during such reinitialization, it is necessary to follow the complete initialization sequence starting from Step 2, including driving the DSI CLK lane to HS mode and the DSI data lanes to LP11?
We are trying to understand if omitting those early steps could lead to unreliable reinitialization and potentially cause the blanking behavior.
Looking forward to your insights.

  • 0
    TI__Mastermind 20870 points

    HI Adarsh,

    According to the datasheet sequence, is 0xE5 is not 0x00, indicating errors, then the recommendation would be to go back to Step 2, which is then followed by setting EN pin low, then set HIGH.

    Could you also share what blanking issue you are facing? Could you tell us what the observation is (black screen, flickering, etc), and how often it occurs? And is the issue always showing the same error flags in 0xE5? What does the register read? Have you tested with internal test pattern? Does the test pattern show a similar issue?

    If it's a recurring issue, it could be something related to initialization, power sequence or display configuration which needs to be corrected to prevent the error.

    Best regards,
    Ikram