Descriptions - flashtool\flashtool.exe

flashtool.exe - Aptina Imaging SPI interface tool

This is a SPI flash utility to support Aptina image sensors.

• It can program the SPI flash device with a given flash image (mode 0)
• It can generate a flash image with a user defined .fcfg file (mode 1)

Command line parameters - Mode 0

Usage:

    flashtool.exe -0 -bin <flash-image-path> [-flash_size <flash-device-size>] [-max_size <max-image-size>] [-startaddr <start-address>] [-erase] [-memory <type>] [-pagesize <pagesize>] [-blocksize <blocksize>] [-sdat <sensor-data-file-path>] [-farsdat <far-sensor-data-file-path>]

-bin <flash-image-path>
The path to the file where the flash image will be stored for subsequent programming.

-flash_size <flash-device-size>
The size of Flash device.
This parameter is optional, default is 0x200000

-max_size <max-image-size>
The maximum binary size that can be generated.
This parameter is optional, default is 0x200000

startaddr <start-address>
The starting address of the device where the binary will load.
This parameter is optional, default is 0x00.

-erase
To erase the device before writing.
This parameter is optional, default is no-erase.

-memory <type>
The memory device connected.
Example: "M25P10" for M25P10 SPI device and "24-bit" for M95M01 EEPROM.
This parameter is optional, default is "M25P05".

-pagesize <pagesize>
The page size of the device connected.
This parameter is optional, default is 32.

-blocksize <blocksize>
The page size of the device connected.
This parameter is optional, default is 0x1000

-sdat <sensor-data-file-path>
The path and name of the far sensor XSDAT file. Skip this option when the device does not have a far sensor.
This parameter is optional; if sensor is connected it will automatically load XSDAT.

-farsdat <sensor-data-file-path>
The path and name of the XSDAT file.
This parameter is optional; if sensor is connected it will automatically load the far XSDAT.

Example

 flashtool.exe -0

 -bin \"C:\Aptina Imaging\flashtool\A-0356SOC_files\sample_command_list.bin -erase

OUTPUT:  Program the specified binary file to SPI Device.

Command line parameters - Mode 1

Usage:

flashtool.exe -1 -fcfg <config-file-path> -sdat <sensor-data-file-path> [-farsdat <far-sensor-data-file-path>] -bin <flash-image-path> [-flash_size <flash-device-size>] [-max_size <max-image-size>] [-extension | -base <address>] [-spaces] [-mapping]

-fcfg <config-file-path>
The path to the text file(*.fcfg) which contains the details of the flash image which should be created.

-sdat <sensor-data-file-path>
The path and name of the XSDAT file.

-farsdat <sensor-data-file-path>
The path and name of the XSDAT file.
This parameter is optional; if sensor is connected it will automatically load the far XSDAT.

-bin <flash-image-path>
The path to the file where the flash image will be stored for subsequent programming.

-flash_size <flash-device-size>
The size of Flash device.
This parameter is optional, default is 0x200000

-max_size <max-image-size>
The maximum binary size that can be generated.
This parameter is optional, default is 0x200000

-extension | -base <address>
Produces a full base flash image, including tables of contents.
  -extension produces only an image of assets which could be used for extension of the flash.
  -base <address> applies only to Extension images and defines the address in memory where the image will be written. If the Extension image contains command sequences, this is used to adjust the pointers.
This parameter is optional, default is -base 0

-spaces
To generate binary file with extra blank space after every TOC
This parameter is optional, default is no space

-mapping
To generate a text file that maps all binary records with their respective address.
This parameter is optional, default is no mapping file created.

-output <filename>
File name of the output data, a comma-separated data table.

The "-input" and "-output" prefixing the filenames are optional. You can just list all the filenames on the command line. The last filename is taken to be the output file, all the rest are inputs.

Example

 flashtool.exe -1

 -fcfg \"C:\Aptina Imaging\flashtool\A-0356SOC_files\sample_command_list.fcfg

 -sdat \"C:\Aptina Imaging\sensor_data\MT9V126-REV1.sdat\"

 -bin \"my_flash_image.bin\"

OUTPUT:  Generates flash image my_flash_image.bin, with input file sample_command_list.fcfg.