• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 815 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Problems encountered with tuning images using DCC

wang zhili
Intellectual 915 points

Part Number: TDA4VM

Hello,

There are several problems when I use DCC to tuning images:

1. After changing the exposure time in manual AE mode, the image does not change. Is that normal?

2. When I calibrate the AWB and modify the "tuning radius", the Cb-Cr plot scheme does not change, as shown in below. And I can't find the "Red/Green/Blue scaler for flourescent" mentioned in the AWB guide.

There are no change after I update AWB calibration and tuning parameters to the camera.

3. I copied the bin and XML files generated by DCC to the directory: /opt/vision_apps/dcc/<sensor_name>/<wdr_mode> , ran the "run_app_single_cam.sh" and pressed the u command, the image did not change. The whole process was done according to the manual: https://www.ti.com/lit/pdf/spracu7.

The camera I used is AR0820, and the version of SDK is 7.03. Please give me some help on these problems, thanks.

  • 0
    TI__Mastermind 24525 points

    Hello Wang,

    Let's take one issue at a time.

    >>After changing the exposure time in manual AE mode, the image does not change. Is that normal?

    No, this is not normal. Can you please let me know what values are you trying? Out of range values are discarded by sensor driver. Can you please put some prints inside the function AR0820_SetAeParams and see what I2C settings are being sent to the sensor?

    Regards,

    Mayank

  • 0 in reply to Mayank Mangla
    Intellectual 915 points

    The range of valves I tried is 100-40000us, which is not out of range.

    Below is the logs when set different values:

    Fullscreen Logs of exposure time.txt Download 
    The logs when exposure time set at 40000us
[MCU2_0]    811.092510 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x3022 0x0001
[MCU2_0]    811.092837 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2020 0x08f8
[MCU2_0]    811.093151 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2022 0x08f8
[MCU2_0]    811.093437 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2024 0x08f8

The logs when exposure time set at 4000us
[MCU2_0]    580.521060 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x3022 0x0001
[MCU2_0]    580.521383 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2020 0x08f8
[MCU2_0]    580.521700 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2022 0x08f8
[MCU2_0]    580.522027 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2024 0x012e

The logs when exposure time set at 1000us
[MCU2_0]    861.597183 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x3022 0x0001
[MCU2_0]    861.597543 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2020 0x08f8
[MCU2_0]    861.597846 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2022 0x0279
[MCU2_0]    861.598138 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2024 0x0046

The logs when exposure time set at 400us
[MCU2_0]    652.975154 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x3022 0x0001
[MCU2_0]    652.975477 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2020 0x08f8
[MCU2_0]    652.975869 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2022 0x00fd
[MCU2_0]    652.976160 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2024 0x001c

The logs when exposure time set at 100us
[MCU2_0]    699.810157 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x3022 0x0001
[MCU2_0]    699.810478 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2020 0x02bf
[MCU2_0]    699.810873 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2022 0x003f
[MCU2_0]    699.811276 s: [AR0820_MAX_MULTI_WriteReg] :rawRegVal: 0x2024 0x0006

  • 0 in reply to wang zhili
    TI__Mastermind 24525 points

    Can you please capture raw images with 40000us and 100us each?

  • 0 in reply to Mayank Mangla
    Intellectual 915 points

    Mayank,

    The raw image attached in the zip file below:

    7571.raw images of 100 and 40000us.zip

    The resolution is 3840x2160 and the bit depth is 12.

  • 0 in reply to wang zhili
    TI__Mastermind 24525 points

    Raw images have the same brightness. It seems like I2C commands are not going to the sensor. I would recommend the following

    1. Read the exposure registers back after write to see if the written values have taken effect.

    2. If this test fails, then please check with your camera/serdes supplier.

    Regards,

    Mayank

  • 0 in reply to Mayank Mangla
    Intellectual 915 points

    Mayank,

    The written values have not taken effect, is it a sensor problem? And the AR0233 have not the same problem, is DCC not supporting AR0820 for changing exposure time or is there a problem with AR0820 itself? But I have the same problem when using another AR0820.

    If there is a problem with AR0820 sensor, could you please tell me which part is the problem?

  • 0 in reply to wang zhili
    TI__Mastermind 24525 points

    Hello Wang,

    This is not a DCC problem. DCC has taken the user input and sent it correctly to the sensor driver. Sensor driver has also issued correct I2C commands to set exposure/gain registers. If registers are not being written, it seems like a hardware problem with the camera - either the sensor or SerDes. I recommend working with your module/sensor/serdes supplier.

    Regards,

    Mayank

  • 0 in reply to Mayank Mangla
    TI__Guru 57203 points

    Hello Mayank and Wang,

    wang zhili said:
    2. When I calibrate the AWB and modify the "tuning radius", the Cb-Cr plot scheme does not change, as shown in below. And I can't find the "Red/Green/Blue scaler for flourescent" mentioned in the AWB guide.

    Let's continue the discussion for this next question in this E2E: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1061607/tda4vm-about-awb-plugin-of-dcc. 

    Regards,

    Takuma