TDA4VH-Q1: LDC Firmware Driver Issue

Hi Kaan,

Kaan Berke Ulusoy said:

if I understood correctly. (imaging > sensor_drv > include > dcc_ldc_imx390_wdr.h)

Yes, this is correct.

This header file has the same DCC binary file information.
"imaging/utils/iss/src/app_iss_common.c" refers to the header and pass it to applications via "appIssGetDCCBuffLDC(...)".

i.e., "dcc_db" inpput for the LDC node below

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/latest/exports/docs/tiovx/docs/user_guide/group__group__vision__function__vpac__ldc.html#gade2239f717b1460e12be52499c6d3b4c

Kaan Berke Ulusoy said:

The thing is when we generate the header and use it directly the hwa does not perform ldc. 

What do you mean here by "use it directly"?

Do you use it with the single-cam app or some other openvx app you have?

Kaan Berke Ulusoy said:

Please see the attached original header in the sdk, the one that we generated (not working directly) and modified one (works).

If am not if I understand you correctly.
It seems you copied some data from the original binary to get your new binary to work.

One thing I can think of for the binary to work is the DCC ID (or sensor ID, camera ID) in the top of your xml file.

e.g., 390 for IMX390 in SDK as below

git.ti.com/.../IMX390_ldc.xml

It must match "tivx_vpac_ldc_params_t::dcc_camera_id" for LDC node input.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/latest/exports/docs/tiovx/docs/user_guide/structtivx__vpac__ldc__params__t.html

Another possibility is about which version of the LDC H/W (e.g., VPAC1 or VPAC3) and xml file (VPAC1 or VPAC3) you use.

Kaan Berke Ulusoy said:

We were wondering why the new generated header is not working directly? Why do we need such kind of change? Is there an initial stream to start hwa maybe? Also how come does the size have such an effect?

I don't expect any of those are necessary if you have the LDC kernel programmed correctly.

If you share your new LDC xml file, I can check if anything might be wrong.