TDA4VM: H3A output differneces in PC and Target Emulation

Hi Sithara,

Sithara Tresa Chacko said:

I've noticed that the H3A outputs don't match between the PC and Target Emulation environments in this case.

Do you mean mismatch between PC-emulation mode output and EVM H/W output?

Sithara Tresa Chacko said:

What could be causing these differences in the H3A outputs between the two environments?

I am not aware of any similar issue in the past 2~3 years.
H3A outputs should match and I don't recall seeing any mismatch in our testing.

Could you please the outputs and the difference?

Sithara Tresa Chacko said:

I'm working with the app_viss application on the TI SDK version 7.01.00.11.

SDK 7.01 is too old and the change history at https://git.ti.com/cgit/?q=imaging only goes back to SDK 8.

I don't find any similar H3A issue fixed in the git log since SDK 8.

Sithara Tresa Chacko said:

I have attached the parameters I have used for reference.

The settings look the same to me.

                prms->h3a_params.aew_cfg_AEFMT = 2;
vissCfgRef->h3aCfg->aewbCfg.outMode =2;

                prms->h3a_params.aewinblk_WINH = 2;
                prms->h3a_params.aewinblk_WINSV = 944;//958
vissCfgRef->h3aCfg->aewbCfg.blackLineHeight =2;
vissCfgRef->h3aCfg->aewbCfg.blackLineVertStart =944;//958


                prms->h3a_params.pcr_AVE2LMT = 1023;
vissCfgRef->h3aCfg->aewbCfg.satLimit =1023;

                prms->h3a_params.aew_cfg_SUMSFT = 0;
vissCfgRef->h3aCfg->aewbCfg.sumShift =0;

                prms->h3a_params.aewwin1_WINH = 58;
                prms->h3a_params.aewwin1_WINW = 40;
vissCfgRef->h3aCfg->aewbCfg.winCfg.height =58; ///issuee
vissCfgRef->h3aCfg->aewbCfg.winCfg.width =40;

                prms->h3a_params.aewwin1_WINHC = 32;
                prms->h3a_params.aewwin1_WINVC = 16;
vissCfgRef->h3aCfg->aewbCfg.winCfg.horzCount =32;
vissCfgRef->h3aCfg->aewbCfg.winCfg.vertCount =16;

                prms->h3a_params.aewsubwin_AEWINCH = 6;
                prms->h3a_params.aewsubwin_AEWINCV = 6;
vissCfgRef->h3aCfg->aewbCfg.winCfg.horzIncr =6;
vissCfgRef->h3aCfg->aewbCfg.winCfg.vertIncr =6;

                prms->h3a_params.aewinstart_WINSH = 0; 
                prms->h3a_params.aewinstart_WINSV = 0;
vissCfgRef->h3aCfg->aewbCfg.winCfg.pos.startX =0;
vissCfgRef->h3aCfg->aewbCfg.winCfg.pos.startY =0;

Please also share the raw input image for reference.

Hi Gang Hua

ThankYou for the reply.

Do you mean mismatch between PC-emulation mode output and EVM H/W output?

Yes, that is correct.

I have attached the input image, h3a, and the final VISS output for both the PC and Target Emulation. The output is appearing in black and white. How can this issue be resolved?

The input image resolution is 1280x946.

/cfs-file/__key/communityserver-discussions-components-files/791/query.zip

Regards

Sithara Tresa Chacko

Hi Sithara,

Thanks for sharing!

Your YUV output images do not match either.
Do you have the DCC xml files for your VISS settings?

As SDK 7 is too old, I would recommend moving to the latest SDK in general in general for better support.

Hi Gang Hua

Please find the attached XML files for your reference

./cfs-file/__key/communityserver-discussions-components-files/791/6165.dcc_5F00_xmls.zip

Our project is currently based on SDK version 7.1, and we are unable to migrate to the new SDK at this time.

Hi Sithara,

Sithara Tresa Chacko said:

Please find the attached XML files for your reference

Thanks for sharing!

I went through the files and they look good for SDK 7.1.

Sithara Tresa Chacko said:

The input image resolution is 1280x946.

BTW, tt looks like your image is actually 1280x944.

Sithara Tresa Chacko said:

However, I've noticed that the H3A outputs don't match between the PC and Target Emulation environments in this case.

In SDK 7.1, with your input raw image and DCC binary created from your xml files for VISS settings, VISS shall be able to work well in both target mode and emulation mode.
You would need to program the tiovx VISS kernel with the DCC binary as input.

Sithara Tresa Chacko said:

Our project is currently based on SDK version 7.1, and we are unable to migrate to the new SDK at this time.

There has been quite some new development and bug fixes of tiovx kernels and pdk drivers for VPAC since 7.1.
TI has no plan of updating past releases for those changes.