...
Self-explanatory really; edit or delete existing records. Note: no warning is given when selecting "Delete Record", and there is no "Undo" function.
1.2.4 Global Table
This dialog is used to define register and variable settings that don't apply to the other specific areas (such as Patch or Calibration).
1.2.5 Patch Table
In this table specify the list of firmware patches that need to be included in the flash image. Please note that when you locate a .bin file which includes the patch, the tool will also look for a file with a similar name ending with the extension .info. The .info file has to be the correct information file for the intended patch file.
...
Select the Command "Load_Patch" to create the record and use the associated index from the "Patch Table", and then add the associated patch to match that record.
1.2.6 Calibration Table
This table contains the calibration-specific settings for the device.
1.2.7 Distortion Correction Table
This table contains records for defining multiple Lens Distortion Correction settings. This will contain with DeWarp or STE Command records, and associated Lens Distortion Correction Table entries (either from .bin or .xml files).
It is assumed that the reader of this document has understanding of the Lens Distortion features and controls of the product they are working on.
1.2.8 Graphics Overlay
1.2.2 Bitmap Table
| Anchor | ||||
|---|---|---|---|---|
|
Use this table to specify the list of graphics overlay string bitmap file paths that need to be included in the flash image. The string bitmap files have to be in binary format. They Aptina RLE format, and they can be created using DevWare or makeover.exe.
...
| Anchor |
|---|
...
|
...
|
...
3 String Table
| Anchor | ||||
|---|---|---|---|---|
|
This Use this table is used to specify the list of graphics overlay string file paths that need to the distortion correction configuration filesbe included in the flash image. The configuration files string files have to be in binary format. They can be created using the DevWare Distortion Correction plug-in.
Each of the assets that have been included in their corresponding tables will be referenced using their index number. The indexes start with 0. A host command which makes use of one of these assets will use as part of its parameter list a reference to the asset index in the appropriate table.
...
The initialization table specifies the instructions that are executed by the sensor firmware during its initialization process after power-up.
The initialization process consists of several stages and it follows this order:
- Global
- Patch
- Calibration
- Distortion Corection (Dewarp) – AP100 and A-356SOC (MT9V126-138) and ASX343
- Graphics Overlay – all sensors except AP101
During each one of these stages the firmware accesses the corresponding flash image block, retrieves the initialization sequences and executes them. In addition you can create additional sequences that are referred to as Command Sequences. Command sequences are not automatically invoked during the firmware initialization process. It is possible to invoke command sequences only by using the explicit Invoke_Command_Sequence host command.
The types of initialization tables that can be included will depend on the features of sensor you are using, and may be different from those depicted in these images.DevWare.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
This table is used to specify the paths to the distortion correction configuration files. The configuration files can be created using the DevWare Distortion Correction plug-in.
Each of the assets that have been included in their corresponding tables will be referenced using their index number. The indexes start with 0. A host command which makes use of one of these assets will use as part of its parameter list a reference to the asset index in the appropriate table.
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Select the type of record. You may add comments in the comments section, and the parameter list in the Record Parameters section, if applicable. The top most section will show some helpful hints about the selected record type, and any additional information.
For records which require numeric parameters, you may enter a sequence of parameters as necessary with a space or a comma delimiter between them.
The Test button allows you to verify the record in terms of consistency of the parameter list with the requirements for the record. If an incorrec number of parameters is provided for the record you will get an error.
When finished press the Finish button in order to insert the new record into the selected table.
Once the records of a table have been created it is possible to change their relative location by uding the Up and Down arrow buttons. It is also possible to edit or delete records as necessary.
In order to view the content of a record, select it. Its contents will be displayed inside the window Details of Selected Record. The record content will be displayed in the format of the configuration file which the flash tool uses to store and restore its contents.
Comments that may have been entered for the record will appear at the top of the record details where each comment line starts with the symbols #@. Anchor
Vendor-Specific Records in Initialization Tables
The flash contents specification defines the VENDOR_SPECIFIC_00 to VENDOR_SPECIFIC_15 record types, which may contain any arbitrary data of your choosing. When creating a vendor-specific record, select the sub-type of the record from 00 to 15, and enter the data in the Parameters window as a list of byte values.
Unfortunately, as of this writing, the firmware on the Aptina SOC chips does not recognize the vendor-specific record type, and triggers an error condition if it encounters one. It is possible to include vendor-specific records in an initialization table if the vendor-specific records are preceded by a Command record
...