PROCESSOR-SDK-J721S2: [IFV700]: PC-Emulation configuration

Hi Dinesh; Could you provide the link of the instruction that you were following? We will check if it is current. And try to repeat what you have done.

Thanks and regards

Wen 

Hello Wen,

Please refer the attached document containing all the details.

pc_emulation_error.docx

Hi Dinesh;

Thanks for the detail report. We will look into it.

Best regards

Wen

Hi Dinesh,

Do you have the DCC bin files for the sensor you are using? that is being generated from the DCC tuning tool?

Dinesh Badkas said:

we could able to re-compile dcc-bins with some changes in config file

If you are referring to the .cfg file screenshot you have shared, this is used by the application and not DCC tool.

Dinesh Badkas said:

1. if we modify something in this header, will it get reflected during PC-emulation execution.

If no, is there any other way to make it possible?

I see this being compiled for PC emulation. May I know which SDK version are you using and if you are using the tuned DCC bin file for your sensor?

Regards,

Nikhil

we are using SDK: ti-processor-sdk-rtos-j721s2-evm-09_00_00_02

1. may i know what do you mean by tuned DCC bins?

2. How can we tune DCC bins for out current problem?

3. If we change related HWA parameters from - 'vx_vpac_viss_target_defaults.c', will it reflect in DDC bins and further pc-emulator output?

Hello,

Our expert is currently out of office for the week. Please expect a delay in response.

Thank you,
Sarabesh S.

Hi Dinesh,

Dinesh Badkas said:

we are looking for how control the ISP parameters like, AWB gains etc. in PC emulation mode. (x86 platform)

This is the same in PC emulation mode as on EVM.

Dinesh Badkas said:

we see config defaults are applied in header - "vx_vpac_viss_target_defaults.c".

Our queries are:

1. if we modify something in this header, will it get reflected during PC-emulation execution.

Yes, this should change the default values used by tiovx VISS kernel.

Dinesh Badkas said:

2. we could able to re-compile dcc-bins with some changes in config file. but looks like changes are not getting reflected during pc-emulation execution.

Using DCC binary files for initializing VISS and AEWB is supported by tiovx kernels.
You would need to pass the DCC binary data to those kernels as kernel creation time.

Dinesh Badkas said:

2. we could able to re-compile dcc-bins with some changes in config file. but looks like changes are not getting reflected during pc-emulation execution.

we are coping the updated dcc-bins as follows:

This is subject to some limitations in tiovx VISS kernel in PC emulation mode for some VISS modules (the binary files are not used at kernel creation time in single cam app).

In TDA4 SDK, you may find that some c header files are generated together with the DCC binary files as in the link below.

https://git.ti.com/cgit/processor-sdk/imaging/tree/sensor_drv/src/imx390/dcc_xmls/wdr/generate_dcc.sh?h=main#n18

Those header files are used by the single camera app at kernel creation time.

https://git.ti.com/cgit/processor-sdk/imaging/tree/utils/iss/src/app_iss_common.c?h=main#n76

You may follow the same convention if you use single-cam app.

Hello Gang Hua

Gang Hua said:

Using DCC binary files for initializing VISS and AEWB is supported by tiovx kernels.
You would need to pass the DCC binary data to those kernels as kernel creation time.

Request you to elaborate more please on how DCC bins will get passed/used to initialize VISS kernels? (maybe procedure in details).

Gang Hua said:

This is subject to some limitations in tiovx VISS kernel in PC emulation mode for some VISS modules (the binary files are not used at kernel creation time in single cam app).

This statement looks contradicting to above statement. Request you to please which limitations are there?

Gang Hua said:

Those header files are used by the single camera app at kernel creation time.

Does it mean, If we modify some HWA configuration parameters (if available) in the generated headers, it shall get reflected to VISS kernel and its executions?

Gang Hua said:

Yes, this should change the default values used by tiovx VISS kernel.

Our understanding is /'vx_vpac_viss_target_defaults.c" shall supply the default parameter values which shall be taken during initialization only. But during run time VISS kernel / DCC shall update the HWA configuration parameters, which shall overwrite the default parameter values. (during run time).

Hence, is there any other place (source file) where we shall provide the updated HWA configuration parameter values?

Request your guidance please.

Gang Hua said:

In TDA4 SDK, you may find that some c header files are generated together with the DCC binary files as in the link below.

Hello Gang Hua,

During DCC generation, we don`t see headers generating.

from the headers mentioned in the script from provided link, e.g. : 

dcc_2a_imx390_wdr.h;

dcc_viss_imx390_wdr.h

above headers looks to be the static files in the sdk (i.e. not generated).
Path: 

Request your suggestions.

Hi Dinesh,

Dinesh Badkas said:

During DCC generation, we don`t see headers generating.

Do you see line 18 executed while running "./generate_dcc.sh"?

https://git.ti.com/cgit/processor-sdk/imaging/tree/sensor_drv/src/imx390/dcc_xmls/wdr/generate_dcc.sh?h=main#n18

It should create "$OUT_PATH/dcc_viss_imx390_wdr.h" as the output.
You may delete the original file first and see if a new file is created after running the script.

Dinesh Badkas said:

above headers looks to be the static files in the sdk (i.e. not generated).

The file should change if you make some changes in the xml files.

Dinesh Badkas said:

Request you to elaborate more please on how DCC bins will get passed/used to initialize VISS kernels? (maybe procedure in details).

This can be done at VISS kernel initialization time.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j721s2/latest/exports/docs/tiovx/docs/user_guide/group__group__vision__function__vpac__viss.html#gaaa4e6e4ce0061cb6522c2bbb474c5a8a

The 4th input "dcc_buf" is for the DCC binary input.

The 3rd input "ae_awb_result" shall be provide as well with a valid initialization condition in "tivx_ae_awb_params_t".

If you do the initialization this way, it should be fine.

Dinesh Badkas said:

This statement looks contradicting to above statement. Request you to please which limitations are there?

If you don't initialize in the above way, but read the DCC binary after VISS initialization (via TIVX_VPAC_VISS_CMD_SET_DCC_PARAMS), you are subject to run time limitation of VISS/Openvx to change VISS parameters.

Dinesh Badkas said:

Does it mean, If we modify some HWA configuration parameters (if available) in the generated headers, it shall get reflected to VISS kernel and its executions?

In single-cam camera app, the header files are used for VISS initialization at the kernel creation time.

Dinesh Badkas said:

Our understanding is /'vx_vpac_viss_target_defaults.c" shall supply the default parameter values which shall be taken during initialization only. But during run time VISS kernel / DCC shall update the HWA configuration parameters, which shall overwrite the default parameter values. (during run time).

Hence, is there any other place (source file) where we shall provide the updated HWA configuration parameter values?

'vx_vpac_viss_target_defaults.c" is used for any parameters that are not provided at VISS kernel initialization time.