• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 101 subscribers
  • Views 290 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: Strange H3A value when testing x3c sensor

Hua Jianxiong
Intellectual 400 points
Part Number: TDA4VM

Hi, TI experts,

We have integrated our sensor driver (including AR0820 and OVX3C) from sdk0703 to sdk0805, but we have met some problem.

The raw images of 0820 and x3c are shown below, and both of them are normal.

However, when I print the h3a data of green channel, 0820 and x3c results look quite different. It seems that the h3a data value of x3c is quite small.

Do you think this is a normal phenomenon? If not, what could cause this phenomenon?

0820 raw img

 

X3c raw img

 

0820 h3a data print

 

X3c h3a data print

 

Best regards, 

Jianxiong Hua

 

  • 0
    TI__Guru 51665 points

    Hi Jianxiong,

    H3A output depends on your sensor raw image and VISS settings.
    If we assume you have roughly the same raw image input from 820 and x3c after decompanding, then the difference is in VISS settings.

    Do you see any changes in your dcc xml files related to H3A?

  • 0 in reply to Gang Hua
    Intellectual 400 points

    Hi Gang, 

    We have met with a very strange phenomenon. 

    In sdk0703, our x3c sensor works well and we can get normal image after VPAC. 

    However, after we intergrate the same sensor driver and VPAC parameters to sdk0805, the output image of VPAC is abnormal, but the raw is still normal. 

    Is there any differences of VPAC between sdk0703 and sdk0805. (We can ensure that the driver settings and VPAC parameters we use remain the same)

    DP output on sdk0805

    saved raw img on sdk0805

    best regards, 

    Jianxiong Hua

  • 0 in reply to Hua Jianxiong
    TI__Guru 51665 points

    Hi Jianxiong,

    I don't recall anything special for causing this issue.
    Could you please capture some VISS output YUV image to confirm?

    If the issue is in YUV, then most likely something went wrong in reusing your 7.3 VISS parameters.