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.

How to let vout2 channel output signal

Other Parts Discussed in Thread: DRA71

Our processor is DRA71X and DRA74X, with 3.02.00.03 SDK version.

We want to test video interface like below scenario

Using vout2 to output RGB888 signal and use vin3a to receive signal. Since only test interface, so static picture signal will be enough.

How could i let vout2 output RGB888 signal? Should i provide a picture file or there exist some vout2 related registers could let i fill in vout2_data value?

Regards,

Shawn

  • Hi Shawn,

    I have forwarded your question to an expert for comment.

    Regards,
    Yordan
  • Shawn,

    I am not able to see any image attached to the post. Can you repost them?

    Do you plan to test this with the kernel? Are you testing on DRA74x or DRA71x ?

    The system outputs RGB24 by default. You only need to make sure that

    1. SOC Pinmux is setup correctly for VOUT2 lines in u-boot. Please refer to board/ti/dra7xx/mux_data.h for pinmux configuration. Thsi file has arrays specifying pinmux for each DRA7 variant. Please review the array corresponding to the SOC you are using.

    2. Please ensure any muxes on the VOUT2 lines are setup correctly.

    Once this is done, you can update the device tree to include a display on VOUT2. You can refer to the below link on how to define a virtual lcd for each VOUT.

    http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Automotive_Display_FAQ#Testing_multiple_LCD_displays_on_the_EVM

    To get static image, you can run modetest or kmstest which display color bars on screen.

    regards,
    Venkat

  • Hi Venkat,

    I didn't post any image on it, maybe is the word "scenario" to let you misunderstanding. I only descript out test method through wording.

    Yes, we'll test this under kernel, and we need to test on both DRA74X and DRA71X.

    I have some questions need to understand

    Venkat Mandela said:
    Please ensure any muxes on the VOUT2 lines are setup correctly.

    The muxes you mean is the internal mux inside the CPU video path, or is our custom board video path?

    Venkat Mandela said:
    Once this is done, you can update the device tree to include a display on VOUT2. You can refer to the below link on how to define a virtual lcd for each VOUT.

    The web page you gave to me also include the way to Setup a fake panel(s) in the device tree, but the link seems already fail to open, can you check for me?

     The web page you gave to me also mention about use HDMI PLL clk as clock source. Which mean i also need to adjust clock source for VOUT2/VOUT3 to enable them, right?

    Regards,

    Shawn

  • Shawn,

    The muxes you mean is the internal mux inside the CPU video path, or is our custom board video path?

    I meant both inside the SOC and on the custom board if you have any.

    The web page you gave to me also include the way to Setup a fake panel(s) in the device tree, but the link seems already fail to open, can you check for me?

    Here is the correct link. In my last email, I pointed to incorrect section in the FAQ.

    http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Automotive_Display_FAQ#Testing_multiple_LCD_displays_on_the_EVM

    The page hosting the patches https://review.omapzoom.org seems to be down at the moment. Please try again after sometime.

    The web page you gave to me also mention about use HDMI PLL clk as clock source. Which mean i also need to adjust clock source for VOUT2/VOUT3 to enable them, right?

    This is required only if you are using more video outputs compared to available video PLL’s i.e. more than 2 LCD’s ON DRA74 and more than 1 LCD on DRA71.

    regards,
    Venkat

  • Hi Shawn,

    We haven't heard back from you, I'm assuming you were able to resolve your issue.
    If not, just post a reply below (or create a new thread if the thread has locked due to time-out).

    Regards,
    Yordan