TDA4VM: Display Problem when bringing up a 5M YUV camera in TDA4

Hi Hua Jianxiong,

Couple of questions,

- Please confirm if you are using YUV422 or YUV420 as output format.

- Are you seeing any underflow or sync lost errors from the DSS?

- Can you please save DSS Video pipelines registers value and share them?

Regards,

Brijesh

Hi Brijesh, 

Brijesh Jadav said:

- Please confirm if you are using YUV422 or YUV420 as output format.

- The camera output format is YUV422, but I'm not sure the VPAC output format, I kept the default setting. 

Brijesh Jadav said:

- Are you seeing any underflow or sync lost errors from the DSS?

- I'm not familiar with Display Subsystem, and I'm not clear how to check the errors. 

Brijesh Jadav said:

- Can you please save DSS Video pipelines registers value and share them?

- I'm not sure what registors' value should I save?

All the DSS settings are kept default in sdk 7.03 except for the "dss_soc_fw.c", I changed this .c file to solve DP signal promblem on some types of screen according to [FAQ] PROCESSOR-SDK-J721E: eDP firmware responds wrongly to some messages and thus causes display incompatibility. - Processors forum - Processors - TI E2E support forums and TDA4VM: Problem of DP output on screens - Processors forum - Processors - TI E2E support forums. 

The "dss_soc_fw.c" is attached. dss_soc_fw.c

Best reagrds, 

Jianxiong Hua

Hi Hua Jianxiong,

Yes, this patch is required for DP, but really doubt the issue is due to DP.

Which example application are you using to verify this resolution? If you slightly lower the resolution, to lets say 2048 line width, does it work fine? 

Even with Scalar and other modules enabled, DSS should be able to support this resolution, so want to check DSS pipeline registers.

I think by default we are using VID1 and VID2 pipelines in all vision apps usecases. so can you please same 180 registers 0x04A50000 and 0x04A60000 offsets and share them?

Regards,

Brijesh

Hi Brijesh,

Brijesh Jadav said:

Which example application are you using to verify this resolution?

I'm using "run_app_single_app.sh" to start the stream. 

Brijesh Jadav said:

If you slightly lower the resolution, to lets say 2048 line width, does it work fine?

Do you mean use another camera with lower resolution? (It works fine with resolution of 1920*1080 camera with RAW input). Or do you mean to change the resolution setting in "iss_sensor_ovX5B_uyvy.c"?

Brijesh Jadav said:

I think by default we are using VID1 and VID2 pipelines in all vision apps usecases. so can you please same 180 registers 0x04A50000 and 0x04A60000 offsets and share them?

OK, I'll check and share them. 

best regards, 

Jianxiong Hua

Brijesh Jadav said:

I think by default we are using VID1 and VID2 pipelines in all vision apps usecases. so can you please same 180 registers 0x04A50000 and 0x04A60000 offsets and share them?

To read the registers, I did the following operations: 1) Connect TDA4 board with PC through eth2, and open MobaXterm to start SSH; 2) run_app_single_cam.sh to start the camera; 3) I opened another session, and use command "devmem2 0x04A50000" to read the register value. 

However, all the registers value from 0x04A50000 to 0x04A60000 are 0x00000000. Is there any mistakes during my steps?

Hi Hua Jianxiong,

No, the method looks correct. Do you have way to connect to the board using CCS? Because once you start running single camera application and display is enabled, these values should not be 0. Can you please try reading these registers from CCS? 

Regards,

Brijesh

Hi, I used SSH and adb tools to read these registers, but the results were the same. Some of the results are attached here:

Hi,

I see you are able to read DSS register, see last register read has some valid values. So can you please now try reading all registers that i suggested earlier in the post?

Btw, what is your DP resolution? ie are you using default 1920x1080 resolution for the DP output? Is 5MP resolution only for Camera? Also typically VISS outputs in YUV420 format, have you changed it to output YUV422 format? Essentially other than resolution, are there any other changes in the single camera application? 

Regards,

Brijesh 

Hi Brijesh,

Here are the register results of 0x04A50000-0x04A6FFFF. 

My DP resolution is 1920x1080, 5M resolution is only for camera. 

I didn't change output format (which is still the default value I think). And I didn't do any changes on single camera application. 

registers_0x04A50000-0x04A5FFFF.txtregisters_0x04A60000-0x04A6FFFF.txt

best regards,

Jianxiong Hua

Hi Jianxiong Hua,

From the register, i see that

- you are using YUV422 as input format

- the input resolution is 2592x1808

- Scaling is enabled in the DSS video pipeline to downscale input resolution 2592x1808 to 1920x1080.

Can you please confirm above settings?

Also what is the sensor output format that you are using? Is it in RAW12 or in YUV422 format? Can you please save output from sensor and check if it looks correct? 

Also are you using LDC in your data path? Because the default LDC LUT in the SDK is for 1920x1080 resolution.  

Regards,

Brijesh

Brijesh Jadav said:

Can you please confirm above settings?

Yes, I use these settings. 

Brijesh Jadav said:

Also what is the sensor output format that you are using?

Sensor output is YUV422 format with resolution of 2592x1808.

Brijesh Jadav said:

Also are you using LDC in your data path?

When I run single app, I select LDC=0 to bypass the LDC. 

Best regards,

Jianxiong Hua

Hi Jianxiong Hua,

Can you please try one experiment? Instead of using 5-tap filter for vertical resizing, can you please change it to 3-tap filter and see if it works? 

This is currently not configurable from the openVX node, so you would have to update it when display is running. 

Can you use k3dump or devmem2 utility to write value 0x80BFF to register at the offset (0x04A60020)?

Regards,

Brijesh

Hi Brijesh, 

I wrote the value to 0x04A60020 register, but nothing take effect. The DP output is still incorrect. 

When I wrote 0x80bfd value to register 0x04A60020, the DP output is below:

compared with figure1 above, does it mean the Y channel is not correctly displayed?

Hi Jianxiong Hua,

The value 0x80bfd just means change of YUV422 format, so Instead of UYVY format, it would expect the format in YUYV format. 

I am still suspecting something related to the horizontal width of the image.  Instead of 2592 line width, can you please reduce line width to 2048 in the sensor and try it again?  As such, specs mentions that 4K line width can be supported for YUV422 dataformat with scalar enabled, so it should work, but might require additional changes.. 

Also can you please try one more change? In the file pdk\packages\ti\csl\src\ip\dss\V4\priv\csl_dssVideoPipe.c, driver decides to use either 5-tap filter or 3-tap filter, based on the line size and format, can you please hard code here the filter to be use to 3-tap filter, like below and try it out with 2592 line width? You would require to rebuild pdk, sdk with this change? 

/* Select scaler filter */
isDataFmtRgb = Fvid2_isDataFmtRgb(pipeCfg->inFmt.dataFormat);
if((TRUE == isDataFmtRgb) && (pipeCfg->inFmt.width > 2048U))
{
verticalTaps = CSL_DSS_VID1_ATTRIBUTES_VERTICALTAPS_VAL_TAPS3;
}
else
{
verticalTaps = CSL_DSS_VID1_ATTRIBUTES_VERTICALTAPS_VAL_TAPS5;
}

verticalTaps = CSL_DSS_VID1_ATTRIBUTES_VERTICALTAPS_VAL_TAPS3;

Regards,

Brijesh

Btw, which SDK release are you using? I wanted to check if there is any change in the latest release in calculating the scaling parameters.

Regards,

Brijesh

Can you please check if you have attached patch applied in your codebase? If not, can you please apply it on pdk/packages/ti/csl folder, rebuild pdk and sdk and check it again with 2592 line width?

/cfs-file/__key/communityserver-discussions-components-files/791/6013.0001_2D00_DSS_2D00_CSL_2D00_FL_2D00_Bug_2D00_Fix_2D00_PDK_2D00_9681_2D00_DSS_2D00_displays_2D00_corrupted_2D00_d.patch

Regards,

Brijesh

Brijesh Jadav said:

which SDK release are you using?

I use sdk 0703. 

ok, please apply patch i shared in earlier post and check the output. This issue was fixed in later release. 

Regards,

Brijesh

Hi Brijesh, 

After I apply the patch and rebuild sdk, I can get correct image through DP output. 

Thanks! 

Best regards, 

Jianxiong Hua