TDA2: Lens displacement in Linux but normal in RTOS

Hi User5227399,

Can you please check the configuration parameters provided to VPE and Alg_DmaSwMs links?

Regards,
Sujith

Hi Sujith,

Which file should I check?

Regards,
Daniel

Hi Daniel,

In case of RTOS
file \apps\src\rtos\usecases\srv_calibration\chains_srvCalibration_Display.c
and function chains_srvCalibration_vip_SetAppPrms /setVpeLinkParams () is used
to configure VPE params

In case of HLOS
file \apps\src\hlos\adas\src\usecases\srv_calibration\chains_srvCalibration_Display.c
and function chains_srvCalibration_vip_SetAppPrms /setVpeLinkParams () is used
to configure VPE params

please check the chPrms->outParams[outId].width, height, chPrms->scCropCfg.cropWidth and Height.

Regards,
Sujith

Hi Daniel,

Hope the issue was resolved or you have the steps to resolve.

Regards,
Sujith

Hi Sujith,

Sorry for the late reply. I couldn't verify that your answer will solve my issue because I have to go on a business trip a few days ago. Now I will follow your suggestions and give you feedback as soon as possible. Thank you.

Regards,
Daniel

Thanks for the update Daniel.

Regards,
Sujith

Hi Daniel,

Is this issue resolved?

Regards,
Sujith

Hi Sujith,

Sorry to keep you waiting.
I checked params you mentioned. Params chPrms->outParams[outId].width and height were assigned by OutWith and OutHeight. Then OutWidth and OutHeight were assigned by swMsWinWidth and swMsWinHeight. There is no difference between HLOS and RTOS for everything above. Finally swMsWinWidth and swMsWinHeight were assigned by pObj->displayHeight/2 and pObj->displayWidth/2. It's hard to find the exact value of pObj->displayHeight and pObj->displayWidth, so I'm not sure if that's the problem.

Params chPrms->scCropCfg.cropWidth and Height were assigned by inCropWidth and inCropHeight. Then inCropWidth and inCropHeight were assigned by pObj->calibrationPrm.captureOutWidth and pObj->calibrationPrm.captureOutHeight. Params pObj->calibrationPrm.captureOutWidth and pObj->calibrationPrm.captureOutHeight were assigned by SRV_CAPT_SENSOR_OV10640_WIDTH(HEIGHT) and pUcObj->IssCapturePrm.outParams[0U].width(height). There is no difference between HLOS and RTOS for SRV_CAPT_SENSOR_OV10640_WIDTH(HEIGHT). It's also hard to find the exact value of pUcObj->IssCapturePrm.outParams[0U].width(height).
Can you give me more directions? Thank you.

Regards,
Daniel

Hi Daniel,

Can you add prints and figure out the size?

Regards,
Sujith

Hi Sujith,

I will try it. It may take some time to modify codes and re-compile. I will give you feedback as soon as possible.

Regards,
Daniel

Okay

Regards,
Sujith

Hi Sujith,

I added Vps_printf("OutWidth, OutHeight", OutWidth, OutHeight) and Vps_printf("inCropWidth, inCropHeight", inCropWidth, inCropHeight) in function setVpeLinkParams. I only got "OutWidth, OutHeight" and " inCropWidth, inCropHeight" four times after executed srv calibration, no any other values. Then I changed to Vps_printf("swMsWinWidth, swMsWinHeight", swMsWinWidth, swMsWinHeight) and Vps_printf("pObj->calibrationPrm.captureOutWidth, pObj->calibrationPrm.captureOutHeight", pObj->calibrationPrm.captureOutWidth, pObj->calibrationPrm.captureOutHeight). I still only got "swMsWinWidth, swMsWinHeight" and "pObj->calibrationPrm.captureOutWidth, pObj->calibrationPrm.captureOutHeight" after executed srv calibration, no any other values.
Can you give me more directions? Thank you.

Regards,
Daniel

Hi Daniel,

I am not sure i understand. Did the values match in both the usecases?

Regards,
Sujith

Hi Sujith,

I only added code in RTOS usecase for test. The values of OutWidth, OutHeight, etc. are not shown in terminal. Only these characters ( "OutWidth, OutHeight" etc. )are displayed. I don't know the reason.

Regards,
Daniel

Hi Daniel,

These variables might be optimized out, can you print the values from the VPE structure directly?

Regards,
Sujith

Hi Sujith,

You mean not in function setVpeLinkParams but in function chains_srvCalibration_vip_SetAppPrms?

Regards,
Daniel

You could do that or in startCalibUseCase ()

Regards,
Sujith

Hi Sujith,

I added codes in function chains_srvCalibration_vip_SetAppPrms() and startCalibUseCase (), I still couldn't get any values of OutWidth, OutHeight, etc. so I guess that won't work.

Then I tried to adjust cropping image parameters. I changed chPrms->scCropCfg.cropStartY in function setVpeLinkParams() and setVpeSv_CscPrm(). But no any obvious change. What does chPrms->scCropCfg.cropStartY do?

I found this problem was not present in the 3.02 hlos version of the SDK. So I want to know what's the difference between 3.02 and 3.04 in hlos? Thank you.

Regards,
Daniel

Hi Daniel,

I will have to check on this and get back to you.

Regards,
Sujith

Hi Sujith,

Thank you, I will wait for your response.

Regards,
Daniel

Hi Sujith,

Do you have any update about this problem?

Regards,
Daniel

Daniel,

The difference is due to different cropping parameters. The camera outputs a 1280x1080 image. The BIOS sw is cropping the central 1280x720 portion of the 1280x1080 input image, the Linux version appears to be taking the top 1280x720 portion. The code that is doing this is 

if (pObj->chainsCfg->captureSrc == CHAINS_CAPTURE_SRC_OV490)
{
ChainsCommon_MultiCam_SetCroppingPrms(&pUcObj->CapturePrm,
SRV_OV490_SENSOR_WIDTH,
SRV_OV490_SENSOR_HEIGHT,
SRV_LVDS_CAPTURE_WIDTH,
SRV_LVDS_CAPTURE_HEIGHT
);
}

located on line 307 of vision_sdk/apps/src/rtos/usecases/lvds_vip_sv_standalone/chains_lvdsVipSurroundViewStandalone.c

Cheers,

Ben

Hi Ben,
Thank you, please give me some time to check it.

Regards,
Daniel

Hi Daniel,
Could you please let us know the status ?

Regards
Surya