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.

PROCESSOR-SDK-J721E: What Could Be the Reason the TI DCC Tuning Tool-Generated File Isn't Being Applied?

Part Number: PROCESSOR-SDK-J721E

Tool/software:

Using the AWB plugin of TI's DCC tuning tool, a DCC file was generated and applied to the J721E evaluation board; however,
no changes were observed in the camera's video output.

The DCC file has been copied to the following folder on the SD card:
/roofs/opt/vision_apps/dcc/IMX390-UB953-DISCOVERY/wdr

What factors could be responsible for the changes not taking effect?

Additionally, the input image settings of the DCC tuning tool at that time are as follows:

  • Hi Shinya,

    Using the AWB plugin of TI's DCC tuning tool, a DCC file was generated and applied to the J721E evaluation board; however,
    no changes were observed in the camera's video output.

    That depends which application you use in general.
    We typically use the single-cam app with the script below to include the tuning data into a header which in turn gets compiled into the single-cam app.

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

    You would copy the xml file over, update and run the script, recompile SDK and re-install to SD card.

    The DCC file has been copied to the following folder on the SD card:
    /roofs/opt/vision_apps/dcc/IMX390-UB953-DISCOVERY/wdr

    That depends on if single-cam app reads the binary file properly.
    There was also some bug regarding loading the binary file and updating AWB calibration data for single-cam app in previous releases.