• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 382 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.

DLPDLCR2000EVM: DLPDLCR2000EVM debug issue

Dong Ba
Intellectual 1055 points
Part Number: DLPDLCR2000EVM

Hi Team,
The customer has a debug issue about DLPDLCR2000EVM.
For details, please refer to the document attached.
The customer has no access to E2E post, if it is convenient for you contact the customer directly, the customer’s email is listed in attached. Or feel free to post it here.

Thanks,

CSC Team
Eric

question.docx

  • 0
    TI__Mastermind 28005 points

    Eric,

    Based on the customer's summary above, it sounds like there are a couple potential issues which may be occurring:

    > You should first verify that I2C functionality is working in the first place. It is possible to change from splash screen to internal TPG mode? Does the EVM respond to basic commands such as resolution and TPG mode? If you aren't seeing any result of I2C input you can probe I2C lines to check to see if your Raspberry Pi is actually sending out a signal. Make sure you are setting the EVM to RGB666 mode when confirming this via I2C command.

    > Assuming I2C is working, you should next verify if the video stream from the Raspberry Pi is actually being transmitted. You can do this by checking critical lines such as VSYNC to see if a signal is being sent. You can also verify Raspberry Pi video output settings in terminal.

    > Finally, you should verify the implementation of the video connection between EVM and Raspberry Pi. I see in the image provided that jumpers are being used for certain connections. I've found from personal experience that using bundle of jumpers to connect video DPI interface can be very cumbersome to get working due to poor signal quality and losses. If possible, use a ribbon cable or PCB adapter board to ensure good signal integrity.

    I hope this helps. Let me know if the customer comes back with more questions and information on the above.

    Regards,

    Philippe Dollo

  • 0 in reply to Philippe Dollo
    Prodigy 10 points

    Hello, I agree with the question you raised, but since it is my first contact with Raspberry Pi, I don't know how to judge whether there is video output. I can see the interface of Raspberry Pi through remote control. Then how do I verify that VSYNC is working properly on the terminal? Can you have an example for me to follow along, thank you

  • 0 in reply to 6573458
    TI__Mastermind 28005 points

    User,

    Do you have a scope available to probe signals such as VSYNC? Since there is a concern about signal integrity it may be difficult to debug with terminal commands alone (since issue may be in connection and not the Pi's output).

    - Philippe

  • 0 in reply to Philippe Dollo
    TI__Mastermind 28005 points

    User,

    Do you have any updates on this issue? If you are still struggling, I recommend following the signal from Raspberry Pi to the EVM to verify signal integrity, and verify all hardware connections. 

    Best Regards,

    Philippe Dollo