Machine Translated by Google
Rockchip IQ Tools Guide ISP2x
Document identification: RK-SM-YF-602
Release version: V1.2.2
Date: 2021-02-08
Document confidentiality level: ÿTop secret ÿSecret ÿInternal information ÿOpen
disclaimer
This document is provided on an "as is" basis, and Rockchip Co., Ltd. ("the company", the same below) does not have any representations, accuracy, reliability, completeness,
merchantability, and specific purpose of any statement, information and content in this document. and non-infringement make no representations or warranties, express or implied.
This document is only used as a reference for guidance.
Due to product version upgrades or other reasons, this document may be updated or modified from time to time without any notice.
Trademark Statement
"Rockchip", "Rockchip" and "Rockchip" are registered trademarks of our company and are owned by our company.
All other registered trademarks or trademarks that may be mentioned in this document are owned by their respective owners.
Copyright © 2020 Rockchip Microelectronics Co., Ltd.
Beyond the scope of reasonable use, without the written permission of the company, no unit or individual may excerpt, copy part or all of the content of this document, and
shall not spread it in any form.
Rockchip Microelectronics Co., Ltd.
Rockchip Electronics Co., Ltd.
Address: No. 18, Area A, Software Park, Tongpan Road, Fuzhou City, Fujian Province
Website: www.rock-chips.com
Customer Service Phone: +86-4007-700-590
Customer Service Fax: +86-591-83951833
Customer service email: fae@rock-chips.com
foreword
overview
This article aims to introduce how to use RKISP2 Tuner and the ISP debugging process. It mainly helps engineers who use RKISP2 Tuner for IQ debugging to get started
quickly and provides reference.
product version
chip name
kernel version
RV1126/RV1109
Linux 4.19
Readers
This document (this guide) is primarily intended for engineers who:
Machine Translated by Google
ISP debugging engineer
Image quality debugging engineer
revision history
Version Number Author Modification Date
Modify the description
V1.0.0 Chen Yu2020-09-30
initial version
v1.1.0 Chen Yu 2020-10-20
Adaptation tool version v0.3.0
v1.2.0 Chen Yu 2020-11-03 Added RNDIS configuration method (section 3.3), added version number matching rule description
v1.2.1 Chen Yu 2020-12-02
v1.2.2 Chen Yu 2021-02-08
Table of contents
Rockchip IQ Tools Guide ISP2x 1 Overview 1.1 About RKISP2.x
Tuner 1.2
Applicable Platform & Version Number
Matching Rules 1.3 Debugging Environment 1.4 Tool
Installation and
Configuration 2 Function Introduction
2.1 Overview 2.2
Snapshot Tool
2.3 Calibration Tool 3
Quick Start 3.1 Establish
Tuning Project 3.2
For Create a new CIS Tuning project
3.3 Connect the device 3.4 Use the Capture Tool to
capture the Raw image
3.5 Use the emulator 4 Calibration process description 4.1
Capture the raw image 4.2
BLC calibration
4.2.1 Basic principles of BLC calibration 4.2.2
BLC calibration Raw image shooting requirements
4.2.3 BLC Calibration Raw Image Shooting Method 4.2.4
BLC Calibration Method 4.3 LSC
Calibration
4.3.1 Basic Principles of LSC Calibration
4.3.2 Requirements for LSC Calibration Raw Image Shooting
4.3.3 LSC calibration Raw image shooting method 4.3.4
LSC calibration steps 4.4. AWB
calibration 4.4.1 AWB
calibration content 4.4.2 AWB
calibration Raw image shooting steps and requirements
4.4.3 Interface description of AWB calibration tool 4.4.4
AWB calibration steps 4.4.5. Example
of AWB calibration results 4.6 NR calibration
4.6.1 Raw image shooting method 4.6.2
NR calibration steps
Modify the description of the calibration diagram of the NR module
Add description of XML2Bin function
Machine Translated by Google
4.7 FEC/LDCH
4.7.1 Requirements for shooting FEC/LDCH calibration charts
4.7.2 FEC/LDCH Calibration Procedure
5 Online debugging interface and function
introduction 5.1
Debugging interface
5.2 Connecting devices 5.3
Import XML file 5.4 Real-time
parameter reading and writing function 5.5
Register and algorithm parameter
adjustment 5.6 Save parameters to XML file 5.6.1 Scene mode and ISO gear selection
5.7 Commissioning Assistant
5.7.1 Debugging assistant: AE control
5.7.2 Debugging assistant: scene/working mode control
5.8 XML2Bin conversion function
5.9 AEC debugging
interface 5.9.1. AEC manual exposure
configuration method 5.10 Bayer NR
debugging interface 5.10.1 Bayer NR enabling
5.11 MFNR
5.11.1 MFNR NR enable
5.12 UVNR
5.12.1 UVNR NR enable
5.13 YNR
5.13.1 YNR enable
5.14 Sharpen 5.14.1
Enable Sharpen
5.15 Edge Filter 5.15.1
Enable Edge Filter
5.16 Gamma
5.16.1 Gamma Visual Debugging
5.16.2 Gamma Enable
5.16.3 Gamma curve basic debugging method
5.17 Dehaze
5.17.1 Enable Dehaze
5.18 HDR
5.18.1 Enable HDR-TMO
5.19 DPCCs
5.19.1 DPCC Enable 6 Offline
Debugging Interface and Function Introduction
6.1 Demosaic
1 Overview
1.1 About RKISP2.x Tuner
RKISP2.x Tuner (hereinafter referred to as Tuner) provides a set of tools for users to debug ISP parameters. Users can
perform calibration (Calibration) and debugging (Tuning) on all ISP modules in Tuner. Users can use the Capture Tool provided by
the Tuner to capture Raw pictures; complete the calibration of the basic module in the Calibration Tool; connect the device
in the Tuner, and perform online ISP parameter debugging.
Machine Translated by Google
1.2 Applicable Platform & Version Number Matching Rules
chip name
ISP platform version
RV1109
RKISP2.x
RV1126
RKISP2.x
The version matching rules of AIQ, Tuner and ISP Driver are as follows:
vA.BC
Among them, B is a hexadecimal representation, bit[0:3] identifies the matching version of AIQ and Tuner, and bit[4:7] identifies the matching version of AIQ and ISPDriver, for
example:
ISP Driver: v1.0x3.0 matches AIQ: v1.0x30.0, does not match AIQ: v1.0x40.0
Tuner: v1.0x3.0 matches AIQ: v1.0x33.0, does not match AIQ: v1.0x30.0
Note that when the AIQ version number C is not 0, there may be a version mismatch, and it is recommended to use the AIQ version with the C version number 0 for
Tuner matching.
1.3 Debugging environment
*Computer environment requirements:*
The computer running Tuner must be installed with x64 version of Windows 7 or above 64-bit Windows operating system;
The 64-bit version of MCR_R2016a (9.0.1) should be pre-installed before running Tuner, download link:
https://ww2.mathworks.cn/products/compiler/matlab-runtime
Chinese characters should be avoided in the path of Tuner's path and Tuning project during use;
*Device-side environmental requirements:*
1. Make sure that the ADB service is enabled by default when the device is turned on, and the Tuner will start the Tuning service on the device through ADB;
2. Make sure that the camera application in the device is not started by default, otherwise it will conflict with the Tuning service process;
3. If it is difficult to enable the ADB service, you can also directly package rkaiq_tool_server into the firmware, and configure it to start by default when booting, and
also package librkmedia.so into the same path as libaiq.so;
4. Since the device and the computer will use network communication to interact, the user can use either of the following two connection methods to
Connected devices:
1. For a device with an Ethernet card, the UDHCPC service should be enabled by default in the device to automatically obtain an IP address, so that the
user only needs to connect the PC and the device to the same router, and then use RK IPCamera Tool-V1.5 to obtain the device's IP address. initial IP
address;
2. For devices without an Ethernet card, the RNDIS service should be enabled in the firmware to simulate the USB as an Ethernet card, and then use the same
UDHCPC to obtain the initial IP address; 3. In
addition, if there is no router, it can also be directly connected by network cable. In the case of direct connection, the user can configure the static IP address
in two ways. The first one is the simplest, and the serial port is led out from the device to configure the static IP address directly in the serial port. The
second is to modify the firmware to give an initial default static IP address. Both of these methods need to manually change the IP address of the PC to
the same network segment as the IP address configured in the device;
Machine Translated by Google
1.4 Tool installation and configuration
The main body of RKISP2.x Tuner does not need to be installed, and it can be used directly by decompressing to any directory with the decompression tool, but avoid decompressing to
a path with Chinese characters.
It is mentioned in Section 3 that MCR_R2016a needs to be pre-installed before running the Tuner. The installation steps are as follows:
1. Open MCR_R2016a_x64.exe and wait for its self-extraction to complete;
Figure 1-4-1
2. Click Next, choose to agree to the terms, Next, click Install;
Figure 1-4-2
3. Wait for the installation to complete;
Machine Translated by Google
Figure 1-4-3
4. The installation is complete;
Figure 1-4-4
2 Function Introduction
2.1 Overview
In the actual Tuning project, the user should perform the Tuning work according to the flow shown in the figure below:
Machine Translated by Google
Figure 2-1-1
After the first step of the new project is completed, the tool will generate an XML file under the project path, which records all the adjustable parameters opened by the ISP, whether it is the calibration parameters
output in the subsequent calibration process or the user during the debugging process. The debugging results will be recorded in the XML file, and finally the user should replace the file with the corresponding
XML in the firmware or device.
The purpose of shooting Raw images is to calibrate the basic modules, and at the same time, you can also collect scenes with abnormal effects and troubleshoot problems in the emulator.
The calibration of the basic module needs to be carried out according to a certain process, as shown in the figure below:
Figure 2-1-2
Since the calibration of some modules will depend on the calibration results of the previous module, the user should complete the calibration work in the order of the process. After completing the calibration
calculation of a certain module, you should confirm whether the parameters are correct, so as not to affect the subsequent modules due to wrong results.
2.2 Capture tool
Machine Translated by Google
Figure 2-2-1
The main interface of RKISP Tuner Capture Tool is shown in Figure 2-2-1. The interface is mainly divided into the following four parts:
1. Device-side connection configuration: used to configure the IP address and port number of the device, control the device to switch to Tuning mode, also provide the Connect and Ping functions for
testing the connection, and the Preview On/Off button for pausing/resuming the preview;
2. Module/Sensor parameter setting and module/light source name selection: After reading the XML, the Sensor name, resolution and gain/exposure will be displayed
parameter range;
3. Exposure control: It supports manual exposure and automatic exposure. Manual exposure allows the configuration of steps to traverse and shoot multiple exposure groups
Combined, automatic exposure allows users to set the target maximum brightness to select exposure parameters;
4. Raw image preview and statistics function: Here, the captured Raw image will be displayed in the window in the form of a grayscale image, and the corresponding direct view will be displayed.
Square diagram, luminance information and simple white balance gain;
2.3 Calibration tools
Machine Translated by Google
Figure 2-3-1
The main interface of RKISP Tuner Calibration Tool is shown in Figure 2-3-1, which mainly includes the calibration functions of the following modules:
BLC: Black Level Correction
LSC: Lens Shading Correction
CCM: Color Correction Matrix
AWB: automatic white balance correction
GIC: Green Channel Balance Correction
Bayer NR: Raw domain noise reduction
YNR: Y channel noise reduction
MFNR: Multi-Frame Noise Reduction
FEC: Fisheye Correction
It is recommended that the user import the corresponding raw image into the corresponding module to calculate the calibration parameters according to the calibration workflow.
3 Quick Start
3.1 Establish Tuning project
1. After opening RKISP2.x Tuner, the main interface of Tuner will be displayed, as shown in Figure 3-1-1;
Figure 3-1-1
2. Click the new project button in the red box in the upper left corner to create a new Tuning project;
Machine Translated by Google
Figure 3-1-2
3. Fill in the project name and select the project storage path. Pay attention to avoid Chinese characters in the name and path; 4. Select the sensor used by
the current project or product, and the Tuner will automatically load the corresponding configuration (resolution, exposure table, etc.), Fill in at the same time
Write the lens model and module model, which is easy to distinguish the project or product name;
Figure 1-1-3
5. If there is no currently used sensor in the sensor list, click the New CIS Information button, and in the pop-up interface, root
Configure the corresponding parameters according to the sensor
manual; 6. Click OK to save;
Machine Translated by Google
3.2 Create a Tuning project for the new CIS
When the sensor model debugged by the current project cannot be found in the CIS list, the user can fill in the corresponding parameters in the interface of adding CIS
to add the sensor to the list.
1. Click the New CIS Information button;
Figure 3-2-1
2. The interface for creating a new CIS pops up
Machine Translated by Google
Figure 3-2-2
3. The following is the definition of each parameter, the user should refer to the datasheet of the sensor to fill in (this part is recommended to drive the debugger):
Machine Translated by Google
parameter name
Parameter Description
The exposure time row of each frame of the sensor is not equal to the limit switch; En=0: the exposure time row of each frame of the sensor
CISTimeRegUnEqualEn
Can be equal; En=1: Equality is not allowed;
CISMinFps
Minimum frame rate allowed, used in auto drop frame mode
TimeRegMin
The sensor exposure time line allows the minimum value
DCGRatio
Conversion Gain multiple
Bayer Pattern
Raw output Bayer array
Full Resolution
full size resolution
TimeFactor
Sensor exposure time conversion number formula
Gain Range
Sensor gain register conversion formula
CISTimeRegSumFac
The sum limit of sensor exposure time rows
CISTimeRegOdevity
sensor exposure time row parity
Sensor analog gain/range supported by LCG, the minimum value shall not be lower than 1; when the sensor supports
CISAgainRange
During dual conversion gain, this item indicates the LCG range supported by the sensor; if encountered
When the digital gain is used to complement the accuracy, this item can represent the total gain range of the sensor;
Sensor analog gain (HCG) range, the minimum value shall not be lower than 1; when the sensor supports dual
When converting gain, this item indicates the HCG range supported by the sensor; Range range
CISExtraAgainRange
General = CISAgainRange * dcg_ratio; when the sensor does not support dual conversion
When gain, the maximum and minimum values of this item can be filled with 1;
The digital gain range supported by the Sensor, the minimum value shall not be lower than 1. If the digital gain is used for
CISDgainRange
When supplementing the accuracy, the maximum and minimum values of this item can be filled with 1
CISIspDgainRange
ISP digital gain range, the minimum value must not be lower than 1
4. After completing the filling, click the Save button to save and return to the new project interface. After that, you can directly select the
sensor, no need to add repeatedly.
3.3 Connecting Devices
1. Connect the device to the LAN, use the device search tool to search for the device IP, if you use a network cable to connect directly, you need to modify the device IP through the serial port
Address, or modify the IP of the local PC to ensure that the PC and the device are in the same network segment;
2. For devices without network ports or WIFI, the device should refer to the following steps to configure the RNDIS environment
Default IP of RNDIS device: 172.16.110.6
Modify usb_config.sh in the /oem/ directory to ensure that the adb service is available:
ADB_EN=off of usb_config.sh is changed to ADB_EN=on
Use usb adb or network adb, and use network adb to configure the RNDIS network card address of the PC.
PC-side IP configuration:
Machine Translated by Google
Figure 3-3-1
Note that the network segment configuration of this IP should be in the same network segment as
that of the device. After configuration, you can try to ping 172.16.110.6 on the PC through the cmd terminal to confirm whether the network access is normal.
Modify the adb_shell_script.txt script, and modify the run rkaiq_tool_server command as follows: nohup /tmp/rkaiq_tool_server -rtsp_en=0 -m 0 -i /oem/etc/iqfiles/ & sleep 1 Add --rtsp_en=0 (turn off RTSP service)
3. Click Connect Network in the upper left toolbar to open the connection configuration interface, as shown in the figure below
Figure 3-3-2
Machine Translated by Google
Figure 3-3-3
Fill in the device IP address, the default port number is 5543, click Connect To Device, the tool will push rkaiq_tool_server into the device and execute the corresponding script
command, the executed command will be determined by the configuration of rkaiq_tool_server/adb_shell_script.txt.
Figure 3-3-4
As shown in the figure above, the configuration in adb_shell_script.txt is divided into 5 parts:
1. get AIQ version: used to query the AIQ version on the device, check whether it corresponds to the tool version, the path of librkaiq.so
If the path changes, the user should pay attention to modify the path here at the same time;
2. tool_server execute path: the execution path of rkaiq_tool_server, which is under /tmp by default;
3. windows command: Extensible custom commands in the windows command line, users can add or delete this part of the command, for example, the command to push the
dependent library to the device through the adb command is configured in Figure 5-2-3;
4. adb shell command: Extensible custom commands in the adb shell, the tool will be executed on the device through the adb shell
Execute this command, for example, the commands for killing processes and configuring permissions are configured in Figure 5-2-3;
5. run rkaiq_tool_server: Execute the command, this part should be kept in the last paragraph, the following is the parameter description:
Machine Translated by Google
-m: normal/HDR mode selection, 0/1/2 correspond to normal/HDR2 frame/HDR3 frame respectively, if not matched, the default is normal;
-i: XML storage path, if the path is changed, the path here should be modified synchronously;
-w and -h: rtsp preview resolution, which will be scaled based on the ISP output size to meet the requirements;
-r: Whether to enable RTSP service, 0/1 correspond to disable/enable respectively, and devices that only support UVC should be configured as 0;
-d: sensor selection. When there are multiple sensors in the device that need to be debugged, you can use numbers such as 0/1/2 to select which sensor to use. The order of the numbers is
the same as that of the v4l2 topology list;
The commands in parts 3 and 4 above support multiple configurations, and the execution interval of each command is 1s, and are executed sequentially from top to bottom.
Users should pay attention to configure the following points according to the actual situation of the device:
1. **Confirm the path where librkaiq.so is located, and the path to query the AIQ version should be the same as the push path of librkmedia.so;**
2. **Whether it is necessary to kill the user application, if necessary, the kill command should be extended to the adb shell command Part;
** 3. ** The parameters carried by the execution command, whether it is normal or HDR (even if it is HDR, it is recommended to use normal for calibration and shooting raw), etc.; *
After the execution is completed, the result returned by the execution command will be displayed, as shown in the figure below
Figure 3-3-5
Wait for 5-10 seconds for the initialization to end, and click the Test button to test whether the application is running normally.
Figure 3-3-6
After ensuring its normal operation, you can use a third-party playback tool to open rtsp://192.168.1.100 (the specific IP is subject to the actual debugging device) to view the preview screen.
Click Save and Exit to save and exit.
4. Click Capture Tool on the Tuner main interface to open the capture tool;
Machine Translated by Google
Figure 3-3-7
5. Fill in the device IP address in the IP Address box, as shown in the figure below;
Figure 3-3-8
6. At this time, you can click the Connect button or the Ping button. If the service starts correctly, it will display Connect success;
3.4 Use Capture Tool to capture Raw images
1. Click File—Load XML File in the menu bar to load the XML file;
Figure 3-4-1
2. After loading, the tool will initialize the shooting configuration interface according to the configuration in XML;
Machine Translated by Google
Figure 3-4-2
3. Select the correct resolution, light source, and module name for easy identification in subsequent
use; 4. Configure parameters such as gain, exposure time, and number
of shots; 5. Click the Start Manual Capture button; 6. The
captured raw image will be displayed in It is displayed on the Raw Preview & Statistics interface on the right; 7.
The histogram information, maximum/minimum/average brightness, global white balance gain, etc. corresponding to the raw image are displayed
below; 8. The raw image is stored in the ./raw_capture/ module by default name/below;
Figure 3-4-3 Shoot Gain=2x ExpTime=0.03s single frame Raw image
Machine Translated by Google
3.5 Using the emulator
1. On the Tuner main interface, click ISP Calibration Tool to open the calibration tool;
Figure 3-5-1
2. Click IQ File->Load IQ File in the upper left menu bar to load the XML file, and the emulator will use the XML parameters for simulation;
Figure 3-5-2
3. Click the Edit Options button to configure Raw image resolution, BPP and other parameters; 4. Select
the Simulator tab, click the Load Raw File button to import the Raw image, and then click Start Simulation to start the simulation.
Execute the ISP process;
Figure 3-5-3
5) The user can select the modules participating in the simulation in the list on the left, and whether to output the results after the corresponding process;
The simulation process takes about several seconds to tens of seconds (depending on the CPU and resolution), and the user can view the simulation output results in the result folder
under the root directory of the tool after completion;
4 Calibration process description
The calibration work of each module can be divided into three parts:
Machine Translated by Google
Shoot the calibration map: according to the requirements of each module, take a raw picture of the calibration board or scene with an appropriate exposure;
Calculation of calibration parameters: Import the raw image, calculate the calibration parameters, individual modules can fine-tune some parameters according to needs;
Confirm the effect and save the parameters: According to the standards of each module, judge whether the calibration parameters are correct;
4.1 Shoot raw pictures
1. After obtaining the IP address, fill in the IP Address, as shown in Figure 4-1-1, the default port number is 5543;
Figure 4-1-1
2. Click the Switch To Tuning Mode button to start the Tuning service on the device side;
Figure 4-1-2
3. At this time, you can click the Connect button or the Ping button. If the service starts correctly, it will display Connect success and Device is
ready;
Figure 4-1-3
4.2 BLC Calibration
4.2.1 Basic principle of BLC calibration
There is a dark current in the sensor circuit, which causes the pixel unit to have a certain output voltage when there is no light, and the digital signal output by the A/D is
not 0. Dark current is mainly affected by gain and temperature, so it needs to be calibrated separately at different ISOs. Since BLC is an offset, other modules need to
deduct this offset during calibration, otherwise the correct calibration parameters cannot be obtained.
4.2.2 BLC Calibration Raw Image Shooting Requirements
1. Cover the lens black when shooting to ensure that no light enters; 2.
Shooting needs to traverse Gain=1x, 2x, 4x, 8x, 16x...Max (if the maximum Gain of the driver supports 40x, then Max=32); 3 . The exposure time does not affect
the BLC calibration, and can be unified to 10ms;
Machine Translated by Google
4.2.3 BLC Calibration Raw Image Shooting Method
1. Open the RKISP Tuner Capture Tool, refer to the method in Section 1, connect the device, select unknown (no light) for the light source name, and
Select BLC for the block name;
2. Place the device or module in a dark environment, and cover the lens tightly with a black cloth, lens cap, etc.; 3. Configure Gain=1.0
ExpTime=0.010 Frame Number=1 on the Manual Exposure page; 4. Click Start Manual Capture shoots Raw images; 5. The captured raw images will be displayed
on the right, and after confirming that the raw images are basically normal, take
the next one; 6. Adjust the Gain value, Gain=2, repeat steps c, d, e until the traversal Finish;
Figure 4-2-3-1
4.2.4 BLC calibration method
Figure 4-2-4-1 BLC calibration results
Calibration method:
1. Open the Calibration Tool, click the Edit Options button in the upper left corner of the interface, open the configuration interface, enter the size of the raw image,
Bit width and bayer order; 2. Select
the BLC tab, click the Load Raw Files button below, and select the folder where the Raw image is stored;
Machine Translated by Google
3. The imported Raw image will be displayed in the list on the right; 4. Click
the Calibrate button to start the calibration calculation; 5. The curve of
the dark current value of each channel changed with ISO will be displayed on the upper axis after calibration; 6 . Click Save to save the
parameters;
Precautions:
1. If the device itself has power light, status indicator light, etc., you should pay attention to whether there will be light
leakage; 2. Wrong BLC value will affect the calibration results of all subsequent modules. Please make sure that the BLC result is correct before proceeding to subsequent module calibration.
fixed work;
4.3 LSC Calibration
4.3.1 Basic principle of LSC calibration
Lens Shading is generally called vignetting or vignetting effect, which can be subdivided into Luma Shading (brightness uniformity) and Color Shading (color uniformity).
Luma Shading is caused by the optical properties of the lens. For the whole lens, it can be regarded as a convex lens. Since the light-gathering ability of the center of the convex lens is much
greater than that of its edge, the light intensity at the center of the Sensor is greater than that at the surroundings. This phenomenon is also called edge light falloff. For a camera without distortion,
the light falloff around the image follows
law of attenuation.
The cause of Color Shading is relatively complicated. The transmittance of different types of IR-Cut (infrared cut filter) is different, and when the incident angle ÿ changes, the transmittance of
different bands will also change, so there will be a phenomenon that the center and surrounding colors are not uniform . On the other hand, the mismatch between the CRA (main ray incidence
angle) of the Micro Lens (micro lens) and the CRA of the lens will also cause Color Shading.
4.3.2 LSC Calibration Raw Image Shooting Requirements
1. Cover the lens with frosted glass and uniform light film (or use DNP light box, integrating sphere, etc.); D65, D75; 3. To prevent flicker from
AC light sources, it is recommended to use an integer multiple of 10ms to configure the exposure time; 4. The maximum brightness of the Raw image is about 200 (8bit),
and the minimum brightness should be significantly greater than the black level value calibrated in the previous section ; 5. It is
recommended to use the uniform film as shown in the figure below;
Figure 4-3-2-1 Opal Diffuser
4.3.3 Shooting method of LSC calibration Raw image
1. Open the RKISP Tuner Capture Tool, refer to the steps in Section 2, connect the device, select LSC as the module name; 2. Put the module in the light box,
switch to HZ light, and attach the homogenizing film to the lens; 3. The name of the light source Select HZ,
check Search Exposure By Max Luma(8bit) on the Auto Exposure page, check Anti
Flicker (50hz), the target maximum brightness configuration on the right is 200±10%, Frame Number = 1;
4. Click Start Auto Capture to shoot Raw images, during which the tool will automatically select the appropriate exposure until the preset maximum brightness is met
Spend;
5. Switch the light source to A light, modify the name of the light source to A, and repeat step 4 until all light sources are shot;
Machine Translated by Google
Figure 4-3-3-1
4.3.4 LSC calibration steps
1. Open the Calibration Tool, click the Edit Options button in the upper left corner of the interface, open the configuration interface, enter the size of the Raw image,
Bit width and bayer order;
2. Select the LSC tab, click the Load Raw Files button below to import all raw images; 3. The imported Raw images
will be displayed in the upper window, switch the drop-down list to view images of different light sources; 4. Click the Calibrate button,
Start the calibration calculation; 5. After the calibration is
completed, you can view the Raw image of each light source on the result page after applying the correction parameters; 6.
Click Save to save the parameters;
Figure 4-3-3-2
Machine Translated by Google
Figure 4-3-3-3
Precautions:
1. When shooting, it may happen that the ambient light is too bright or too dark, and the appropriate exposure parameters cannot be searched. At this time, you can
Refer to the solutions listed below:
Adjust the brightness of the light source;
Use light reduction film;
Adjust the camera orientation;
Modify the range of Gain Range or Exp Range on the interface;
Adjust the maximum brightness or threshold of automatic exposure;
Switch to manual exposure (the minimum standard for selection is that the minimum brightness is significantly greater than the black level value calibrated in the previous section);
4.4. AWB Calibration
4.4.1 AWB calibration content
It mainly calibrates the white point conditions of Raw in XY, UV, and YUV, the pure color algorithm parameters and the white balance gain under the standard light source
4.4.2 AWB Calibration Raw Image Shooting Steps and Requirements
The preparation environment for Raw image collection is as follows:
1. Equipment: x-rite 24 color cards, light box (including D75, D65, D50, TL84, CWF, A, HZ) 2. Adjust the exposure parameters so that the maximum value of
the brightest white block in the color is [150-240 ], the brighter the better within this range (if you want to
CCM share the raw image, the image should be darker) 3. The
color card occupies more than 1/9 of the screen
Raw image shooting method:
1. Open RKISP Tuner Capture Tool, refer to the steps in Section 2, connect the device, select CCM_AWB as the module name; 2. Place the device and color card in the light box, adjust the
position of the device and color card so that the color card is in the center of the screen , shoot as large as possible,
After adjustment, try not to move the device; 3. Turn on
the light box and switch the light source to HZ light; 4. Select HZ
for the light source name, check Search Exposure By Max Luma(8bit) and Anti Flicker(50hz) on the Auto Exposure page, The maximum brightness configuration of the target on the right is 200±10%,
Frame Number = 1; (If under 1x Gain, the integer multiple of 10ms cannot capture the raw image, you can remove Anti-Flicker (50hz)ÿ)
Machine Translated by Google
Figure 4-4-2-1
1. Click Start Auto Capture to shoot Raw pictures, during which the tool will automatically select the appropriate exposure until the preset maximum brightness is met
Spend;
2. Switch the light source to A light, modify the name of the light source to A, and repeat step d until all light sources are shot;
Shoot x-rite 24 color cards under A, CWF, D50, D65, D75, HZ, TL84 light sources in turn, and the mosaic diagram is as follows:
Figure 4-4-2-2
4.4.3 Interface Description of AWB Calibration Tool
1. When calibrating, it is mainly to adjust the white point boundary of the UV and XY domains, and the TH value of the YUV domain
Machine Translated by Google
Figure 4-4-3-1
Figure 4-4-3-2
2. Operation instructions for adjusting the white point interval in UV and XY domains
a) Use the mouse to drag the four corners of the white point condition in the coordinate system to adjust the position and size of the
white point interval b) Drag the mouse to drag the blank area in the coordinate system to drag the entire white
point interval c) Use the scroll wheel to zoom in
and out to view 3 . The information display of each light source can be selected through the check box in front of LightX in the Display Control panel.
4. The Exclude WPC Range panel can be used to increase the non-white point range and the white point range of additional light sources.
5. AWB Simulaton is used to detect the white point of the raw image and count the white point gain
Machine Translated by Google
Figure 4-4-3-3
a) After LoadImage imports the Raw image, as shown below, the white point information will be printed out. The white point of different light sources is displayed in
different colors. The RGain accumulation and BGain accumulation sum of the white points of the medium frame, large frame, and small frame will be displayed in the three text
boxes of Detected WP Number, RGain, and BGain
Machine Translated by Google
Figure 4-4-3-4
b) Click any position in the image, it will be mapped to the UV domain white point condition interface and the XY domain condition interface, marked with a black square point,
so that it is easy to check whether the point falls within the white point interval, and the RGBUVXY of the point at the same time RGain BGain Dis Th will be displayed in the Stats of the interface
On the Point Track panel
Figure 4-4-3-5
Machine Translated by Google
4.4.4 AWB calibration steps
1. Open the Calibration Tool, click the Edit Options button in the upper left corner of the interface to open the configuration interface, enter the size of the Raw image,
Bit width and bayer order;
2. AWB calibration needs to complete the calibration of BLC
and LSC 3. Click Load Raw Files to import the raw images under A, CWF, D50, D65, D75, HZ, TL84 (it is recommended to calibrate these seven light sources
raw picture)
4. Click Find Chart to identify the color card
Figure 4-4-4-1
a) Click the 1st block, the 6th block, the 19th block, and the 20th block
in turn b) Click FindChart to identify the color card color blocks of all light sources in batches, as shown below (display the white point detection result of the last light source)
Figure 4-4-4-2
c) Select other light sources from the drop-down menu to confirm the correctness of the color block recognition. It is found that only the last block recognition of
TL84 is a bit to the right. At this time , you only need to re-detect it separately. Select Find chart one by one in the solid Mode to repeat Step 12, until the color block of
TL84 is correctly identified, as shown below
Machine Translated by Google
Figure 4-4-4-3
d) Click Save to complete the recognition
5. Click Calibrate to start the calibration calculation. This module takes a long time, about 30s; get the following initial white point conditions and other parameters; the dots of
different colors in the UV domain and XY domain coordinate system represent each light source The positions of the color blocks in the captured color card in the UV and XY
color spaces; the quadrangular boxes represent the white point conditions of different light sources;
Figure 4-4-4-4
Machine Translated by Google
Figure 4-4-4-5
6. Click AWB Simulaton, and then import the raw images under A, CWF, D50, D65, D75, HZ, TL84 to view the white point detection
accuracy.
7. Modify the frame of UV domain or XY domain or TH of YUV to make the white point detection of color cards under each light source more
accurate. 8. Click
Save 9. Repeat steps 5 to 7 until the white point detection of each light source is reasonable.
Precautions:
Adjust the border as far as possible so that the white points (marked as 19, 20, 21, and 22 blocks) are inside the frame, and the non-white points are outside the frame (generally impossible)
The intervals surrounded by medium or large frames of all light sources must be adjacent (three line types represent three large and small frames)
Error demonstration (the intervals of the large boxes are closely connected, but there is an interval between the middle boxes, as shown by the arrow below):
Correct example:
Machine Translated by Google
a and hz light sources can be more compact in the Y direction of the XY domain, and d50 d65 can be relaxed in the Y direction of the XY domain
The intervals enclosed by all light sources in the UV domain must be contiguous
Boundaries of different light sources can overlap, but do not overlap in XY and UV space at the same time
Divide the UV space with reference to the XY space to exclude non-white spots
If the seventh block of the circled D75 light source falls within the hz range, it will be recognized as a white point
After readjustment, the 7th block of the D75 light source is not in the same light source in the xy and uv space, and will not be recognized as a white point
When the non-white point falls in the white point interval of XY and UV, it can also be excluded by reducing TH, or increasing the non-white point interval.
When the white point falls in the white point interval of XY and UV, but it is still not a white point, it may be because it exceeds the brightness range and is excluded, or it falls in the non-white point interval,
or it does not fall in YUV because it is less than TH in the white dot interval of the domain
4.4.5. Example of AWB Calibration Results
Final white point condition:
Machine Translated by Google
Figure 4-4-5-1
The white point detection results of each light source are:
Figure 4-4-5-1A
Machine Translated by Google
Figure 4-4-5-2 CWF
Figure 4-4-5-3 D50
Machine Translated by Google
Figure 4-4-5-4 D65
Figure 4-4-5-5 D75
Machine Translated by Google
Figure 4-4-5-6 HZ
Figure 4-4-5-7 TL84
4.6 NR Calibration
NR module Raw image shooting requirements:
Shooting in a light box with a standard light source, it is recommended to use a DC light source with adjustable brightness;
A gray scale gradient card must be used, as shown in Figure 4-6-1;
Exposure needs to traverse Gain=1x, 2x, 4x, 8x, 16x...Max (if the driver's maximum Gain supports 40x, then Max=32);
Under each Gain, four Raw images need to be taken, which are highlight-overlapped frame, highlight-single frame, low light-overlapped frame, and low-light single frame;
Machine Translated by Google
Highlights and low lights can be distinguished by adjusting the exposure time or the brightness of the ambient light, while overlapping frames and single frames are automatically completed by the tool;
Low-light shooting requirements: the brightness of the brightest pixel is in the range of 120~140;
Highlight shooting requirements: at least one overexposed block in the 3x3 block centered on the brightest block in Figure 4-6-1, and no overexposed block is allowed except the 3x3 block;
The brightest pixel value can be judged by the histogram or the Max Luma obtained from the statistics below. Max Luma=255 means that at least one point in the picture has reached the
saturation value;
The HDR Sensor using DCG mode needs to shoot two sets of Raw images of LCG and HCG respectively;
Figure 4-6-1
4.6.1 Raw image shooting method
1. Open RKISP Tuner Capture Tool, refer to the steps in Section 2, and connect the device;
2. Put the device or module in the light box, and stick the gradient card on the back panel of the light box;
3. Adjust the position of the device so that the gradient card moves to the center of the screen, and as close as possible to make it larger;
4. Turn on the light box and switch the light source to TL84 or CWF;
5. Modify the name of the light source in the interface as TL84 or CWF, and the module name as NR_Normal;
6. Assuming the sensor in the example supports Gain=1-24, you need to shoot 1x 2x 4x 8x 16x;
7. Shooting in low light:
The brightness of the light box is adjusted to about 800lux;
Change the value of Gain Range in the interface to 1.0 - 1.0, and keep Exp Range unchanged;
Check Multi-Frame and Low-Light;
Select the Auto Exposure page, check Search Exposure By Max Luma, and set the value to 165±10%
Turn off Anti-Flicker (50hz);
Set Frame Number=32;
Machine Translated by Google
Figure 4-6-1-2
8. Click the Start Auto Capture button to start shooting, and the tool will automatically select the appropriate exposure value so that the Raw image meets the
set value; 9. After shooting, you will get a Raw image with Multiple and Single suffixes;
Figure 4-6-1-3
10) Capture highlights:
Adjust the brightness of the
light box to about 800lux; modify the value of Gain Range in the interface to 1.0 1.0, and leave Exp Range unchanged;
check Multi-Frame and High-Light; select the Auto Exposure page, check Search Exposure By Max Luma,
and The set value is 255±1% to
turn off Anti-Flicker (50hz); set Frame Number=32;
Machine Translated by Google
Figure 4-6-4
Click the Start Auto Capture button to start shooting, the tool will automatically select the appropriate exposure value, so that the Raw image meets
the set value; after shooting, you will get a Raw image with Multiple and Single suffixes; too
many overexposure blocks are not allowed due to highlights appears, the user needs to check whether only the 3x3 with the brightest block
as the center is overexposed; if the brightness needs to be reduced, you can switch to the Manual Exposure page, fine-tune according to the results of the automatic exposure, and shoot again;
Figure 4-6-1-5
11. Modify the Gain Range value to 2x, repeat steps g and h until all Gain shots are completed;
Machine Translated by Google
12. Since the Gain will continue to increase, it may happen that the automatic exposure cannot select a suitable exposure value, as shown in Figure 4-6-6, the printed message
The information indicates that the tool uses the combination of Gain=4x ExpTime=0.03s (this combination is the maximum value within the current setting range), and the
maximum brightness of the captured Raw image is 166.375, which cannot reach the target value of 255. At this time, the light box should be increased Brightness and try again;
Figure 4-6-1-6
4.6.2 NR calibration steps
GIC & BayerNR and YNR & MFNR modules share the same set of Raw images:
1. Open the Calibration Tool, click the Edit Options button in the upper left corner of the interface, open the configuration interface, enter the size of the Raw image,
Bit width and bayer order;
2. Select the GIC & Bayer NR page, click the Load Raw Files button above to import all Raw images, and the imported Raw images will be displayed
shown in the list below;
3. Click the Calibration button to calculate the calibration parameters;
4. Click the Save button to save the
parameters; 5. Select the YNR&MFNR tab page, click the Load Raw Files button above to import all Raw images, and the imported Raw images will be displayed
in the list below;
6. Click the Calculate YUV button, and the Raw image will be processed into a YUV image by the emulator; 7.
Click the Calibration button to calculate the calibration parameters; 8.
The noise curve obtained after the calibration is completed will be displayed in the right
window; 9. Click The Save button saves the parameters;
Figure 4-6-2-1
Precautions:
Machine Translated by Google
If Auto Exposure still cannot select the appropriate exposure parameters, it is recommended to use Manual Exposure to adjust the exposure.
The histogram and statistical value of the Raw image can be
used to judge whether the brightness is appropriate; if the calibrated curve is far from the shape shown in Figure 4-6-7, it indicates that the
brightness of the high light or low light is
wrong, and the abnormal position of the curve
can be used to find out Judgment: If the shape on the left is wrong , the low-light brightness is inappropriate ; Adjusting the minimum brightness of the
light source is no longer sufficient for shooting. It is recommended to use filters that do not affect the color such as light reduction films to assist in shooting;
4.7 FEC/LDCH
4.7.1 Requirements for shooting FEC/LDCH calibration charts
Shoot the checkerboard, the size of the checkerboard can be changed, and the calibration image only supports jpg, bmp, png formats;
Two methods of shooting are allowed:
1. Four calibration maps, the checkerboards occupy the upper left, upper right, lower left, and lower right positions in the calibration graph, and there is no specific order requirement;
Machine Translated by Google
Figure 4-7-1-1
2. A calibration map with a checkerboard covering the upper left, upper right, lower left and lower right corners;
Figure 4-7-1-2
4.7.2 FEC/LDCH Calibration Procedure
Machine Translated by Google
Figure 4-7-2-1
1. Configure the resolution in the Raw Options property. Bit and Bayer Pattern can be ignored.
2. Import the folder where the calibration map is located. Support jpg, bmp, png image reading.
3. Adjust the calibration configuration parameters.
a) Confirm the actual size of the checkerboard, the number of corner points in the horizontal and vertical directions. b)
Select the number of checkerboard sheets included in the
calibration map. c) Confirm the correction level and the correction direction of FEC.
4. Click the "Calibrate" button to calibrate.
5. Click the "Save" button to save the calibration results.
Precautions
1. The outermost circle of the checkerboard does not participate in the calculation. However, when shooting the calibration image, the black and white blocks in the outermost circle cannot be completely covered
by the preview. 2. The number of corner points in the horizontal direction and vertical direction is the number of black and white blocks in each direction plus one after excluding the black and white blocks in the outermost circle of the checkerboard.
get.
3. FEC is corrected in both directions by default. When calibrating, you can choose the direction to be corrected according to the
actual situation. 4. The folder for storing calibration images should be named after sensor name + lens name/focal length + resolution.
folder of positive files.
5 Online debugging interface and function introduction
5.1 Debug interface
After opening RKISP2x Tuner, the main interface is the online debugging function interface. The current version supports AEC, BayerNR, MFNR,
Online debugging function of UVNR, YNR, Sharpen, EdgeFilter, Gamma, Dehaze, HDR, DPCC modules, Demosaic module is offline static parameter debugging.
Machine Translated by Google
Figure 5-1-1 RKISP2x Tuner main interface
5.2 Connecting devices
Click Connect Network in the upper left toolbar to open the connection configuration interface, as shown in the figure below
Figure 5-2-1
Figure 5-2-2
Machine Translated by Google
Fill in the device IP address, the default port number is 5543, click Connect To Device, the tool will push rkaiq_tool_server into the device and execute the corresponding script command, the
executed command will be determined by the configuration of rkaiq_tool_server/adb_shell_script.txt.
Figure 5-2-3
As shown in the figure above, the configuration in adb_shell_script.txt is divided into 5 parts:
1. get AIQ version: used to query the AIQ version on the device and check whether it corresponds to the tool version. If the path of librkaiq.so changes, the user should pay attention to modify
the path here at the same time;
2. tool_server execute path: the execution path of rkaiq_tool_server, which is under /tmp by default;
3. windows command: Extensible custom commands in the windows command line, users can add or delete this part by themselves
Command, for example, the command to push the dependent library to the device through the adb command is configured in Figure 5-2-3;
4. adb shell command: an extensible custom command in the adb shell, the tool will execute the command in the device through the adb shell
Commands, such as the commands for killing processes and configuring permissions in Figure 5-2-3;
5. run rkaiq_tool_server: Execute the command, this part should be kept in the last paragraph, the following is the parameter description:
-m: normal/HDR mode selection, 0/1/2 correspond to normal/HDR2 frame/HDR3 frame respectively, if not matched, the default is normal;
-i: XML storage path, if the path is changed, the path here should be modified synchronously;
-w and -h: rtsp preview resolution, the resolution will be scaled based on the ISP output size to meet the requirements; -r: whether to enable
RTSP service, 0/1 correspond to disable/enable respectively, devices that only support UVC should be configured is 0;
-d: sensor selection. When there are multiple sensors in the device that need to be debugged, you can use numbers such as 0/1/2 to select which sensor to use. The order of the numbers
is the same as that of the v4l2 topology list;
The commands in parts 3 and 4 above support multiple configurations, and the execution interval of each command is 1s, and are executed sequentially from top to bottom.
Users should pay attention to configure the following points according to the actual situation of the device:
1. Confirm the path where librkaiq.so is located, and the path for querying the AIQ version should be the same as the push path for
librkmedia.so; 2. Whether it is necessary to kill the user application, and if so, extend the kill command to the adb shell command;
3. Execute the command The parameters included, whether it is normal or HDR (even if it is HDR, it is recommended to use normal for calibration and shooting raw), etc.;
Machine Translated by Google
After the execution is completed, the result returned by the execution command will be displayed, as shown in the figure below
Figure 5-2-4
Wait for 5-11 seconds for the initialization to end, and click the Test button to test whether the application is running normally.
Figure 5-2-5
After ensuring its normal operation, you can use a third-party playback tool to open rtsp://192.168.1.100 (the specific IP is subject to the actual debugging device) to view the preview
screen.
Click Save and Exit to save and exit.
5.3 Import XML file
Click IQFiles -- Load IQ File in the menu bar to import the XML file of the project
Figure 5-3-1
After importing, the parameters on the interface of each module will be initialized, as shown in the following figure:
Machine Translated by Google
Figure 5-3-2
5.4 Real-time parameter reading and writing function
Figure 5-4-1
As shown in the figure above, there are three buttons above each module page, which are
Read: Get the parameters currently used by the device in real time;
Write: Set the parameters on the interface to the device side;
Save: Save the parameters to the cache, and then use IQ Files -- Save IQ File to save the parameters as the new parameters;
5.5 Register and algorithm parameter adjustment
Each module page contains registers and algorithm parameters. According to the different parameter forms and value ranges, different controls are used, which are mainly divided
into the following categories:
Value: an integer or floating-point value with a certain value range;
Modify the value of the text box directly;
use the small up and down arrows on the right side of the text box to
adjust the value; use the slide bar on the right side to adjust the value;
Machine Translated by Google
Figure 5-5-1
A small number of parameters only support manual input because the range cannot be determined;
Figure 5-5-2
Boolean: A parameter with a value of 0 or 1, mainly various function switches, etc.;
Take 1 when Enable, take 0 when Disable;
Figure 5-5-3
List: Choose one of the preset options, mainly various function modes, ISO, Day/Night and LCG/HCG gear selection;
Figure 5-5-4
Table: NxM matrix parameters, matrix elements may be integer or floating point;
Figure 5-5-5
Machine Translated by Google
5.6 Save parameters to XML file
Whenever a module is debugged, the user should click Save to save the parameters to the cache. When all the modules are debugged, or the parameters need to be backed up
halfway, you can click IQ Files - SaveIQFIle in the menu bar to save the XML file to a certain path or overwrite the original XML file of the project.
Figure 5-6-1
Figure 5-6-2
5.6.1 Scene mode and ISO gear selection
Some modules (such as NR modules) have parameters configured for different ISOs, different Conversion Gain modes (effective when the sensor supports DCG) and different
scene modes. When debugging, you should ensure that the current status of the preview matches the mode and gear selected on the current interface . Debugging does not support
When using the Sensor in DCG mode, only adjust the LCG.
Conversion Gain mode is divided into two types: LCG and HCG
Machine Translated by Google
Figure 5-6-1-1
Scene modes: Normal, HDR and Gray
Machine Translated by Google
Figure 5-6-1-2
The ISO gear is not fixed, the range is from 50 to 204800, and the maximum value depends on the maximum gain of the sensor.
Machine Translated by Google
Figure 5-6-1-3
It is convenient for users to fix the ISO gear. You can refer to the method in section 5.6.1, configure AEC as manual exposure, and adjust the parameters under the
corresponding ISO gear. For example, if the ISO setting is 50, you should set the manual exposure gain to 1x, and then adjust the parameters.
5.7 Commissioning Assistant
Figure 5-7-1-1 Debug assistant entry
5.7.1 Commissioning assistant: AE control
Machine Translated by Google
Figure 5-7-1-2 AE control interface
This part of the function mainly provides users with convenient AE control and query functions, which are divided into Normal mode and HDR mode.
Mainly for modules that need to be debugged one by one ISO files, such as NR, Sharp, etc., you can lock Gain separately first, as shown in the figure below:
Figure 5-7-1-2 AE control interface
At the same time, you can click Get Current Gain and ExpTime below, and the current exposure information will be continuously obtained and updated in the interface.
Machine Translated by Google
5.7.2 Commissioning Assistant: Scene/Work Mode Control
Figure 5-7-2-1 Sensor working mode control interface
Figure 5-7-2-2 Scene mode control interface
This part of the function mainly provides users with the configuration function of sensor working mode and scene mode. For modules that need to distinguish between scenes and
sensor working modes, such as NR, Sharp, etc., it is recommended that users lock the scene and sensor working modes first, and then configure the module parameters. debugging.
5.8 XML2Bin conversion function
Machine Translated by Google
Figure 5-7-1 XML2Bin function entry
Figure 5-7-2 XML2Bin function interface
This function supports the user to load an XML file and specify a generation path, and the tool will generate the corresponding bin file according to the platform digits
selected by the user.
The currently supported 32-bit Platforms are as follows:
RV1126/RV1109
The currently supported 64-bit Platforms are as follows:
RK356x
Machine Translated by Google
The generated Bin file should have the same file name as the XML except for the suffix. After the generation is complete, replace the XML file on the board with the bin
file and restart the camera application.
It should be noted that when there are XML files and Bin files with matching names in the IQ directory, AIQ will use the XML files first.
5.9 AEC debugging interface
Figure 5-8-1 AEC module debugging interface
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
5.9.1. How to configure AEC manual exposure
1. Use the debugging assistant to control manual exposure (the internal implementation mechanism
is the same); 2. Modify the OpType to MANUAL;
3. Modify the TimeValue and GainValue in AecManualCtrl to the target value; 4. Click Write, and the
parameters will be set to the device;
Figure 5-8-1-1 Manual exposure Gain=2x ExpTime=0.03s
Machine Translated by Google
5.10 Bayer NR debugging interface
Figure 5-9-1 Bayer NR module debugging interface
Note that the Bayer Nr Curve shown here is a calibration value and is for reference only, and does not support user modification.
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
5.10.1 Bayer NR enable
In the interface, select the Enable column to Enable or Disable, and click Write.
Figure 5-9-1-1
5.11 MFNR
Machine Translated by Google
Figure 5-10-1 MFNR module debugging interface
Note that the MFNR Sigma Curve and the noise profile shown here are calibration values, which are for reference only and do not support user modification.
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
5.11.1 MFNR NR enable
In the interface, select the Enable column to Enable or Disable, and click Write.
Figure 5-10-1-1 MFNR module debugging interface
5.12 UVNR
Machine Translated by Google
Figure 5-11-1 UVNR module debugging interface
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
5.12.1 UVNR NR enable
In the interface, select the YNR & UVNR Enable column to Enable or Disable, and click Write.
Figure 5-11-1-1
Here, since the enable bits of UVNR and YNR share the same bit, YNR will also be affected in the same way when UVNR is enabled or enabled.
5.13 YNR
Machine Translated by Google
Figure 5-12-1 YNR module debugging interface
Note that the YNR Sigma Curve shown here and the ynr_xxci parameters below are calibration values, which are for reference only and do not support user modification.
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
5.13.1 YNR enable
In the interface, select the YNR & UVNR Enable column to Enable or Disable, and click Write.
Figure 5-12-1-1
Here, since the enable bits of UVNR and YNR share the same bit, UVNR will also be affected in the same way when YNR is enabled or enabled.
5.14 Sharpens
Figure 5-13 Sharp module debugging interface
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
Machine Translated by Google
5.14.1 Enable Sharpen
In the interface, select the column of Sharpen & Edge Filter Enable to Enable or Disable, and click Write.
Figure 5-13-1-1
Here, since the enable bits of Sharpen and Edge Filter share the same bit, Edge Filter will also be affected in the same way when Sharpen is enabled or
enabled.
5.15 Edge Filter
Figure 5-14 Edge Filter module debugging interface
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
5.15.1 Enable Edge Filter
In the interface, select the column of Sharpen & Edge Filter Enable to Enable or Disable, and click Write.
Figure 5-14-1-1
Machine Translated by Google
Here, since the enable bits of Sharpen and Edge Filter share the same bit, Edge Filter will also be affected in the same way when Sharpen is
enabled or enabled.
5.16 Gamma
5.16.1 Gamma Visual Debugging
Figure 5-15-1-1 Gamma visual debugging interface
5.16.2 Enable Gamma
In the interface, select the Curve - Enable column to Enable or Disable, and click Write.
Figure 5-15-2-1
5.16.3 Gamma curve basic debugging method
Move the mouse to the coordinate system displayed by the curve, and the pointer will be displayed as a cross star. At this time, you can left-click to select an area, and after releasing the mouse, the
coordinates will be enlarged to the selected area, as shown in the figure below
Machine Translated by Google
Figure 5-15-3-1 Select the zoom area
Figure 5-15-3-2 The enlarged coordinate system
Click the right mouse button in the blank space to restore the display scale of the coordinate system.
When the pointer moves to a dot on the curve, it will be displayed as an up and down arrow. At this time, you can drag the dot to move up and down, and the curve will change with the position of
the dot .
Figure 5-15-3-3 Curve after dragging the dot
Machine Translated by Google
5.17 Dehaze
Figure 5-16 Dehaze module debugging interface
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
5.17.1 Enable Dehaze
In the interface, select the Dehaze Enable column to Enable or Disable, and click Write.
Figure 5-16-1-1
5.18 HDR
Figure 5-17-1 HDR Merge module debugging interface
Machine Translated by Google
Figure 5-17-2 HDR TMO module debugging interface
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
5.18.1 Enable HDR-TMO
In the interface, select the TMO Enable column to Enable or Disable, and click Write.
Figure 5-13-1-1
HDR-TMO supports independent configuration of Enable for different scenes/working modes. Here you can select and configure the corresponding scene/working mode
through the Working Mode list.
HDR-Merge does not take effect in Normal mode, and is always enabled in HDR mode.
5.19 DPCCs
Machine Translated by Google
Figure 5-18-1 DPCC-Fast module debugging interface
Figure 5-18-2 DPCC-Expert module debugging interface
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".
Machine Translated by Google
5.19.1 DPCC enable
In the interface, select the DPCC Enable column to Enable or Disable, and click Write.
Figure 5-18-1-1
6 Offline debugging interface and function introduction
The modules involved in this chapter only support offline debugging due to the low frequency of debugging and most of the parameters are statically configured. The modification
results will be updated to the XML file after clicking the Save button.
6.1 Demosaic
Figure 6-1 Demosaic module debugging interface
For specific parameter tuning methods, please refer to the document "Rockchip_Tuning_Guide_ISP2x".