User Options: HEX Files Tab

To go to this tab, click the User Options button and select the Hex Files tab.

The settings in this tab become valid immediately.

You can make the following settings for HEX files:

Hex post-treatment messages

INCA provides the possibility to posttreat hex files during downloading. To activate the posttreatment, the user must complete the following preparations:

• Install DLL with the hex posttreatment algorithm
• Add SYSTEM_CONSTANT to the A2L file with the name of the DLL
• Add SYSTEM_CONSTANT for parameters

Example entry to A2L file

SYSTEM_CONSTANT "EXTERNAL HEXFILE POST TREATMENT NAME" "MyHexPostTreatment.dll"

SYSTEM_CONSTANT "EXTERNAL HEXFILE POST TREATMENT PARAMETER" "Blk_Start=0x80606000"

If the DLL cannot be found, although the system constant for posttreatment was set, the reason could be that unusable hex files are being generated.

With this setting, you can define how INCA behaves in the case of a missing DLL for the posttreatment of HEX files.

Dialog	INCA displays a warning when the DLL necessary for the posttreatment is not found (default setting). You can decide whether the procedure should be canceled or continued. Should you continue the procedure, the HEX files will be created without any posttreatment.
Monitor	INCA displays a warning that the file necessary for the posttreatment was not found.The procedure is continued without any prompt. In this case unusable HEX files can be created.

DLLs designed for the posttreatment of hex files are not part of the INCA product contents.

• S-Record format

  Defines the Motorola S-Record address format.

• S-Record termination

  Activates or deactivates the Motorola S-Record termination record for each segment.

• S-Record count

  Activates or deactivates the Motorola S-Record count record for each segment.

• S-Record size

  Defines the Motorola S-Record size.

• Intel HEX record size

  Defines the Intel HEX record size.

• Intel HEX offset record

  Defines the Intel HEX offset record type.

  linear	Addresses are saved in linear format (continuous).
  segment	Addresses are saved in segments.

• Intel HEX EOF

  Specifies whether an end of file EOF marker is used in the INTEL HEX files.

• File output unused fill sections

  Defines how the unused address section is displayed in the file.

  No	The fill section is not displayed.
  Starting At Zero	The fill section is displayed starting at zero.
  Starting At Lowest Address	The fill section is displayed starting at the lowest address.
  User Defined	The address of the fill section can be chosen freely and is displayed accordingly.

• Start address for fill section

  Defines the offset address of the fill section.

• Fill byte

  Specification of the fill byte. This setting is valid only if the FileoutUnusedFillSections option is enabled. The value range is from 0x00 to 0xFF.

• File output default offset

  Defines the base offset of the fill section.

  Null	Null is used as the base offset.
  Lowest Address	The lowest address is used as the base offset.
  Lowest Data Address	The lowest address of the data area is used as the base offset.
  Lowest Code Address	The lowest address of the code area is used as the base offset.
  User Defined	The basis offset is freely definable.

• File output offset

  Specification of address area offset (by which the fill section is offset).

• Intel HEX file extensions

  Defines the file name extension of Intel HEX files to be set for reading a HEX file.

• Motorola HEX file extensions

  Defines the file name extension of Motorola HEX files to be set for reading a HEX file.

• Bytes to write in HEX file

  Defines the address sections to be filed out.

  Defined	Output contains the address ranges which are defined in the A2L file and contained in the original HEX file.
  Defined and fill bytes	Output contains the address ranges which are defined in the A2L file and contained in the original HEX file. Moreover, it contains address ranges defined in the A2L file but not contained in the original HEX file. These address ranges are filled with fill bytes.

• Write CR/LF at EOF

  Inserts a carriage return (CR) and a line feed (LF) at the end of a file (EOF).

• File output ranges

  ASAP2 defines memory segments for different usage. This option defines which memory segments are written by INCA to the hex file.

  Before INCA can write a hex file, it must read the data, either from a hex file or by upload from the ECU. INCA handles the data ranges according to the ASAP2 description MEMORY_SEGMENT (MEMORY_LAYOUT).

  all defined ranges	Output contains all ranges that INCA has originally found in the hex file and that have a valid MEMORY_SEGMENT (MEMORY_LAYOUT) description. This can be more than what is filed out with the option setting code & data, e.g. DATA located in RAM.
  code + data	Output contains memory segments described with CODE and with DATA (see option settings code and data).
  code	The output contains memory segments described with CODE (PRG_CODE), located in EEPROM, EPROM, FLASH, ROM or REGISTER.
  data	The output contains memory segments described with DATA (PRG_DATA), OFFLINE_DATA, RESERVED or CALIBRATION_VARIABLES, located in EEPROM, EPROM, FLASH, ROM or REGISTER.
  all ranges	Output contains all ranges that INCA has originally found in the hex file. This can be more than described in the A2L file.

  Note
  In accordance with the ASAP2 specification, RESERVED will be written to the hex file (i.e. flashing is possible), but it will generally not be downloaded.

See

User Options Dialog Box