TDA4VM: mini-DP to DP is not working with ViewSonic monitor which resolution is 2k

Hi,

Could you please tell which sdk you are using to validate eDP output? The above patch is only applicable on PSDKRA. If you are using PSDKLA, then we would have to update firmware at different place. 

Regards,

Brijesh

Hi  Brijesh

I use the vision apps demo on the RTOS side to validate the DP output. But this patch doesn't seem to work.

Does tda4vm only support monitors in this list？

For my monitor, ViewSonic VX2478-SMHD-2CN, what can I do to work properly？

Thanks and Best Regards.

Hi,

Well, these are monitors that has been validated.

Can we do one experiment? On RTOS, we support only fixed resolution with fixed timing parameters, if the monitor does not support these timing parameters/resolution, then it will not work. 

If you have support for EDID read on your board, can you please try using PSDKLA ? PSDKLA has support for EDID read and can try setting supported resolution. If this can display, we can then get the resolution information from the registers and try to set it in PSDKRA to run vision apps demos. 

Regards,

Brijesh

Hi Brijesh

I have some questions to confirm.

1. How to display out on Linux side?

My Dell U2417H monitor will only output images after running the vision apps demo. So for  ViewSonic VX2478-SMHD-2CN only modify the EDID configuration on the Linux side. How to verify whether it can be displayed normally？

2. How to confirm which resolutions are supported by RTOS?

I'm not very familiar with RTOS code now so I don't know if there is such a list in the code.

Above, or can you describe this experiment step in more detail to prevent me from doing wrong operations?

Thanks and Best Regards.

Hi Gao,

Can you follow the steps mentioned at https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/out_of_box_j721e.html?  After the step 2.2.1.1.4, please use this SD card to boot on EVM, so without installing vision apps demos. Please check if you are getting something on the ViewSonic Display..

PSDKRA supports only 1080p@60fps resolution..

Regards,

Brijesh

Hi Brijesh

I have a question. On the SK board, the ViewSonic screen using the PSDKRA can work normally.

That is, ViewSonic can work properly with fixed resolution with fixed timing parameters in PSDKRA, How do you explain this?

Thanks and Best Regards.

Hi Gao,

On SDK development board, which core controls the DSS? Is it A72 or R5F? could you please check? If it is Linux, it explains, because Linux supports EDID framework. 

Regards,

Brijesh

In addition, Dell U2417H monitor with the prebuilt files mentioned at https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/out_of_box_j721e.html?  can't display directly. Our verification result is that it also needs to run the visionapp.

Thanks and Best Regards.

Whether on the SK development board or our customized board, we use the same set of code compiled images. If the DSS is controlled by Linux on the SK development board, it should also be controlled by Linux on our customized board.Isn't it?

Can you tell me Where can I confirm whether DSS is controlled by A72 or r5f?

Thanks and Best Regards.

Hi Brijesh

I tried to set BUILD_MCU_BOARD_DEPENDENCIES to no in vision_apps_build_flags.mak to control ENABLE_DSS_SINGLE and ENABLE_DSS_EDP undefined, but it didn't work.

I tried to commented out the line "name_overlays=k3-j721e-vision-apps.dtbo" in uEnv.txt file from the BOOT partition and save the file and exit. Then boot the board, it didn't work.

The DP0_3V3_EN pin is changed from gpio0_111 to gpio0_16 on our customized board. 

I modified DP power in the K3-j721e-eaik.dts file accordingly, as follow:

If I control the dss by R5F, should I make corresponding changes in RTOS and where to modify it?

Thanks and Best Regards.

Hi Gao,

I am bit confused. If you are planning to run vision apps demos, then DSS must be controlled by R5F, as the display node supported in vision apps runs on R5F. In this case, can you please make sure to install vision apps binaries in sd card, using "make linux_fs_install_sd"? 

If you are not planning to use vision apps, please remove vision apps dtbo file and also remove the line from uEnv.txt file as well. In fact, i would suggest to start a fresh, create a SD card, copy filesystem, and without installing vision_apps demo, boot with this SD card. You should see output on eDP on EVM. 

If you are trying it out on your board, please make board specific changes in the dtb files and then rebuild dtb files from PSDKLA, copy them into SD card and try it out.

You are making above changes eaik.dts file, are you using this, ie EdgeAI demos? Otherwise, it will not be used and will not be setup..

Regards,

Brijesh 

Hi Brijesh 

I am bit confused. If you are planning to run vision apps demos, then DSS must be controlled by R5F, as the display node supported in vision apps runs on R5F. In this case, can you please make sure to install vision apps binaries in sd card, using "make linux_fs_install_sd"? 

——Yes, I am planning to run vision apps demo. I have used "make linux_fs_install_sd" to install vision apps binaries in sd card.

If you are not planning to use vision apps, please remove vision apps dtbo file and also remove the line from uEnv.txt file as well.

——I removed vision apps dtbo file and  removed the line from uEnv.txt as well because you suggest that I do an experiment to verify whether the monitor can display normally by setting a fixed resolution in PSDKLA. The result is a kernel panic occurred and the system was restarted.

In fact, i would suggest to start a fresh, create a SD card, copy filesystem, and without installing vision_apps demo, boot with this SD card. You should see output on eDP on EVM. 

——How to do it？I can't "follow the steps mentioned at https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/out_of_box_j721e.html?  After the step 2.2.1.1.4, please use this SD card to boot on EVM, so without installing vision apps demos.", because I need to verify it on my customized board.

If you are trying it out on your board, please make board specific changes in the dtb files and then rebuild dtb files from PSDKLA, copy them into SD card and try it out.

You are making above changes eaik.dts file, are you using this, ie EdgeAI demos? Otherwise, it will not be used and will not be setup..

——We set board_is_j721e_eaik() to true in linux-sdk\board-support\u-boot-2021.01+gitAUTOINC+53e79d0e89-g53e79d0e89\board\ti\j721e\evm.c and change DP0_3V3_EN in eaik.dts and rebuild linux to make SD card. Then run vision apps demo, will this pin(DP 3V3 EN) be set?

How is the hardware designed to support EDID reading? There is only DP port on our customized board, and the related designs of HDMI have been deleted. I saw the following instructions in a tda4vm user guide，but I don't see DP port connected to I2C in the schematic diagram. So I am bit confused.

~/j7/ti-processor-sdk-linux-automotive-j7-evm-07_00_01/board-support/linux-5.4.40+gitAUTOINC+66cf445b76-g66cf445b76$ git

show

commit e6701fe722d1a5880a408a670f10152e94502525 (HEAD -> oringinal)

Date: Fri Sep 4 17:22:46 2020 +0800

dp port:

default sdk can not display, the reason is the i2c that need to communicate with other module.

But the dtb disable the I2C, so need to enable the I2C for DP converter.

diff --git a/arch/arm64/boot/dts/ti/k3-j721e-vision-apps.dtso b/arch/arm64/boot/dts/ti/k3-j721e-vision-apps.dtso

index 14913ccc7..be0e6ec23 100644

--- a/arch/arm64/boot/dts/ti/k3-j721e-vision-apps.dtso

+++ b/arch/arm64/boot/dts/ti/k3-j721e-vision-apps.dtso

@@ -59,6 +59,3 @@

status = "disabled";

};

-&main_i2c1 {

- status = "disabled";

-};

(END)

I made the following changes in the K3-j721e-vision-apps.dts and rebuilt linux/, there is exception log output，

[ 10.093935] cdns-mhdp8546 a000000.dp-bridge: Failed to initialize PHY: -22

[ 10.448038] cdns-mhdp8546: probe of a000000.dp-bridge failed with error -22

//&serdes_wiz4 {
// status = "disabled";
//};

//&mhdp {
// status = "disabled";
//};

//&dss {
// status = "disabled";
//};

//&main_i2c1 {
// status = "disabled";
//};

Thanks and Best Regards.

Hi Brijesh 

The DP monitor is working properly.

My hardware colleague modified a crystal oscillator to solve this problem.

Thanks for your full support！

Best Regards.

Hi Guifeng Gao,

Could you please provide more information on the fix? What was the crystal you were using earlier and what changed fixed the issue? 

Regards,

Brijesh

Hi Brijesh 

On our hardware, this X1301 is 20MHz，but reference design is 19.2MHz.

I change the dss control from R5F to A72 and there is exception log output as follow:

So hardware colleagues tried to modify the X1301 crystal oscillator to 19.2MHz and it took effect. There is no exception log, and the display can display normally.

Thanks and Best Regards.