SPRACU7A December   2020  – March 2021 TDA4VM , TDA4VM-Q1

 

  1.   Trademarks
  2. 1 Introduction
  3. 2 Getting Started
    1. 2.1 Hardware Requirements
    2. 2.2 Software Requirements
    3. 2.3 Lab Requirements
  4. 3 IQ Tuning Prerequisites
    1. 3.1 Requirements for Tuning on Target
    2. 3.2 Requirements for Tuning on Simulator
  5. 4 VPAC Overview
    1. 4.1 Block Diagram
    2. 4.2 IP Overview
      1. 4.2.1 Lens Distortion Correction (LDC)
        1. 4.2.1.1 Features
      2. 4.2.2 Bilateral Noise Filter (BNF)
        1. 4.2.2.1 Features
      3. 4.2.3 Multi Scalar (MSC)
      4. 4.2.4 Vision Imaging Subsystem (VISS)
      5. 4.2.5 Subblocks
        1. 4.2.5.1 Raw Front End (RAWFE)
          1. 4.2.5.1.1 WDR Decompanding
          2. 4.2.5.1.2 WDR Merge
          3. 4.2.5.1.3 Defect Pixel Correction (DPC)
          4. 4.2.5.1.4 Lens Shading Correction (LSC)
          5. 4.2.5.1.5 Hardware 3A (H3A)
          6. 4.2.5.1.6 White Balance (WB)
        2. 4.2.5.2 NSF4 – 4th Generation Noise Filter
        3. 4.2.5.3 Global and Local Brightness Contrast Enhancement (GLBCE)
        4. 4.2.5.4 Flexible Color Processing (FCP)
  6. 5 Dataflow
  7. 6 IQ Tuning Process
    1. 6.1 Expectations of the Tool
      1. 6.1.1 User Expertise
      2. 6.1.2 Ease of Use
      3. 6.1.3 Troubleshooting
  8. 7 Imaging Software Architecture
    1. 7.1 Auto White Balance
    2. 7.2 AutoExposure
    3. 7.3 Dynamic Camera Configuration (DCC) Algorithm
  9. 8 Computing Tuning Parameters
  10. 9 Testing Tuning Parameters
    1. 9.1 On Target Platform – Compile Time Update
    2. 9.2 On Target Platform – Run Time Update From File System
  11. 10Live Tuning
    1. 10.1 Supported Features
      1. 10.1.1 RAW Capture
      2. 10.1.2 YUV Capture
      3. 10.1.3 AutoExposure Control
      4. 10.1.4 AutoWhiteBalance Control
      5. 10.1.5 Sensor Register Read/Write
      6. 10.1.6 Live DCC Update
        1. 10.1.6.1 Update Single Plugin
        2. 10.1.6.2 Update Multiple Plugins
  12. 11Revision History

9.1 On Target Platform – Compile Time Update

Application app_single_cam starts with DCC database from sensor driver header file. This can be overridden at runtime by reading DCC binary files from file system on the SD card. app_single_cam has a runtime menu as shown below

    " =========================="
    " Demo : Single Camera w/ 2A"
    " =========================="
    " p: Print performance statistics"
    " s: Save Sensor RAW, VISS Output and H3A output images to File System"
    ""
    " e: Export performance statistics"
    " u: Update DCC from File System"
    " x: Exit"
    " Enter Choice: "

Option ‘u’ instructs the application to find the DCC binary files in the folder:

/opt/vision_apps/dcc/<sensor_name>/<wdr_mode>

Where

  • sensor_name = string containing the sensor name as defined in sensor driver. For e.g. IMX390 name is “IMX390-UB953_D3”
  • wdr_mode = “wdr” or “linear”

Before giving the command ‘u’, make sure that this folder exists and contains the DCC files in binary format. If this folder contains partial DCC database, then only that part will be overridden. Example:

  • User launches app_single_cam
  • User selects sensor IMX390. Application selects WDR mode by default
    • Application code can be modified to change the default to linear, if needed
  • Applications reads default DCC profile from sensor driver and starts streaming
  • User copies RGB2RGB and AWB into the folder

/opt/vision_apps/dcc/IMX390-UB953_D3/wdr/

  • User presses ‘u’
  • Applications updates RGB2RGB and AWB tuning, leaving rest of the tuning same as initial tuning read from sensor driver. The effect of new tuning parameters can be seen immediately.