TDA4VM: Display has a blue shade on top of image

Display is connected via HDMI

Dump output from EVM on YUV player(output looks fine), is it something with output format to display or Display size issue(My monitor supports 1680x1050)

Hi Mukilan,

Strange, which usecase are you using? 

Does this display support standard 1080p resolution on HDMI? 

Regards,

Brijesh

Hi Brijesh,

Its our own Vision app application which is similar to AVP3 demo.

Monitor supports 1680x1050 not 1080p.

I have even tried connecting with my TV which supports 1080p, Showing signal however output is blank(strange not sure why)

Will try with some other monitor which supports 1080p.

I have tried steps suggested by you,

Display is controlled by Main R5F in vision apps. Changing resolution in display requires changes in two places, one in display controller and one in the display pipeline

• Display controller is initialized as part of the vision apps initialization ie when Main R5F firmware is loaded and appInit API is called. appInit API is implemented in the file psdk_rtos_auto_j7_07_00_00_11\vision_apps\apps\basic_demos\app_tirtos\common\app_init.c. This API fixes the output resolution and the timing parameters for the output resolution to 1080p as shown below. For new output resolution, frame size, timing parameters and pixel clock requires to be updated as per output resolution requirement. Once changed, display controller framework will take care of configuring it in the DSS.

prm.timings.width = 1920U;
prm.timings.height = 1080U;
prm.timings.hFrontPorch = 88U;
prm.timings.hBackPorch = 148U;
prm.timings.hSyncLen = 44U;
prm.timings.vFrontPorch = 4U;
prm.timings.vBackPorch = 36U;
prm.timings.vSyncLen = 5U;
prm.timings.pixelClock = 148500000ULL;

• Display pipeline is getting configured in each vision apps demo. By default, all demos use 1920x1080 as input resolution for display pipeline. For new resolution, the demo needs to be changed. For example, multi-camera example configures display pipeline resolution in API app_init_display in the file psdk_rtos_auto_j7_07_00_00_11\vision_apps\apps\basic_demos\app_multi_cam\app_display_module.c. It sets up the output resolution as 1920x1080 and position as 0x0. This API needs to be updated as per the new resolution.

Not works actually, getting error at some other location, I will capture the issue and share with you.

Hi Brijesh,

Tried with 1080p Monitor as well. similar issue.

Is the issue related input/output of the network?

Our Network input is RGB, I am using preprocess reference from AVP3 demo.

Dump output of Mosaic image from EVM on YUV player looks fine.

Please let me know any hint

Mukilan,

I have faced this issue before and the root cause was that the infotainment card is not firmly attached to the back to J7ES EVM. Just disconnect power supply and ensure that the infotainment card is connected evenly and firmly to the EVM. 

To rule out any software issues, you can try connecting a eDP monitor and drive the display to eDP port. (As you may be aware, this required a recompile of vision_apps after you have correctly defined the macros in /ti/j7/workarea/vision_apps/apps/basic_demos/app_tirtos/common/app_cfg_mcu2_0.h

Regards,
Shyam

Hi Shyam, 

Yes looks like connection issue, with edp output is proper.

However I tired reconnecting the infotainment card still same issue, we will use edp for the display. Thanks.

Hi Mukilan,

Any further questions on this thread?

Let us know if we can close it.

Regards,

Brijesh

Hi Brijesh,

Just one question, even edp only with one Monitor it was working, I have tried with 3 to 4 monitors.

Even if the Monitor resolution is 1080p it was not working.

May be along with resolution other Monitor params also match then only it will work?

Hi Mukilan,

Yes, other parameters should also match in order to get it displayed. 

Do you have a way to get display parameters? May be by connecting laptop to display and reading EDID information? Then we can change display parameters in the vision apps and can get it working with the monitor.

Regards,

Brijesh

Hi Brijesh,

Yes we can close this thread.