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.

J784S4XEVM: Unable to get DisplayPort to work

Part Number: J784S4XEVM
Other Parts Discussed in Thread: TDA4VM

Hello,

I'm using the J784S4XEVM evaluation board and I'm trying to output an image to a monitor through the DisplayPort interface but have so far been unable to get it to work.
I'm using processor-linux-sdk-09_00_00_07 and building the tisdk-default-image. I'm trying to figure out what packages I need.

For example when using command glxinfo all i get is "Unable to open display".

I tried building using processor-sdk-analytics-09_00_00_01 and building the edgeai kit but I was unable to even get the serial communication working with that image. Is there a difference in regards to serial communication using this image or did something go wrong with the build?

Any pointers for what I'm doing wrong would be greatly appreciated!

Regards,
Mattias

  • Hi Mattias,

    TI India has a holiday today. Please expect a response early next week once the assigned engineer is back in office.

    regards

    Suman

  • Hi Mattias,

    Is display enabled in your dts file? Do you see any /dev/fbdev entry? It seems display itself is not enabled in the dtb file. Can you please share Linux boot log to check it?

    Rgds,

    Brijesh

  • Hello,

    I am unable to share the boot log because the board is on a separate secure network.

    I checked and don't see any /dev/fbdev entry, however I do see /dev/dri/card0 and /dev/dri/card1.

    I also tried using TDA4VM and with that board I was able to get a picture on my monitor, I'm not sure what the difference is. That board also had no /dev/fbdev but had the same /dev/dri/card0 and card1.

    I am using k3-j784s4-evm.dts

  • Hi Mattias,

    Are you using the same display device? If the display is enabled, it should work fine even on j784s4 EVM. Can you please confirm that you are not using vision apps firmwares? Because if you are, then dss is controlled from R5F and so we might not see any images after it boots. 

    Regards,

    Brijesh