16. Hex Conversion Utility Description

The Arm assembler and linker create object files which are in binary formats that encourage modular programming and provide powerful and flexible methods for managing code segments and target system memory.

Most EPROM programmers do not accept object files as input. The hex conversion utility converts an object file into one of several standard ASCII hexadecimal formats, suitable for loading into an EPROM programmer. The utility is also useful in other applications requiring hexadecimal conversion of an object file (for example, when using debuggers and loaders).

The hex conversion utility can produce these output file formats:

• ASCII-Hex, supporting 16-bit addresses (see ASCII-Hex Object Format (--ascii Option))

• Binary file in 8-bit format (see Specifying the Memory Width)

• Extended Tektronix (Tektronix) (see Extended Tektronix Object Format (--tektronix Option))

• Intel MCS-86 (Intel) (see Intel MCS-86 Object Format (--intel Option))

• Motorola Exorciser (Motorola-S), supporting 16-bit addresses (see Motorola Exorciser Object Format (--motorola Option))

• Texas Instruments SDSMAC (TI-Tagged), supporting 16-bit addresses (see Texas Instruments SDSMAC (TI-Tagged) Object Format (--ti_tagged Option))

• Texas Instruments TI-TXT format, supporting 16-bit addresses (see TI-TXT Hex Format (--ti_txt Option))

• C arrays

Table of Contents

• 16.1. The Hex Conversion Utility’s Role in the Software Development Flow
• 16.2. Invoking the Hex Conversion Utility
  • 16.2.1. Invoking the Hex Conversion Utility From the Command Line
  • 16.2.2. Hex Conversion Utility Options
  • 16.2.3. Invoking the Hex Conversion Utility With a Command File
• 16.3. Understanding Memory Widths
  • 16.3.1. Target Width
  • 16.3.2. Specifying the Memory Width
  • 16.3.3. Partitioning Data Into Output Files
• 16.4. The ROMS Directive
  • 16.4.1. When to Use the ROMS Directive
  • 16.4.2. An Example of the ROMS Directive
• 16.5. The SECTIONS Directive
• 16.6. The Load Image Format (--load_image Option)
  • 16.6.1. Load Image Section Formation
  • 16.6.2. Load Image Characteristics
• 16.7. Excluding a Specified Section
• 16.8. Assigning Output Filenames
• 16.9. Image Mode and the --fill Option
  • 16.9.1. Generating a Memory Image
  • 16.9.2. Specifying a Fill Value
  • 16.9.3. Steps to Follow in Using Image Mode
• 16.10. Array Output Format
• 16.11. Building a Table for an On-Chip Boot Loader
  • 16.11.1. Description of the Boot Table
  • 16.11.2. The Boot Table Format
  • 16.11.3. How to Build the Boot Table
    • 16.11.3.1. Building the Boot Table
    • 16.11.3.2. Leaving Room for the Boot Table
  • 16.11.4. Booting From a Device Peripheral
  • 16.11.5. Setting the Entry Point for the Boot Table
  • 16.11.6. Using the Arm Boot Loader
• 16.12. Using Secure Flash Boot on TMS320F2838x Devices
• 16.13. Controlling the ROM Device Address
• 16.14. Control Hex Conversion Utility Diagnostics
• 16.15. Description of the Object Formats
  • 16.15.1. Array Object Format (--array Option)
  • 16.15.2. ASCII-Hex Object Format (--ascii Option)
  • 16.15.3. Binary Object Format (--binary Option)
  • 16.15.4. Intel MCS-86 Object Format (--intel Option)
  • 16.15.5. Motorola Exorciser Object Format (--motorola Option)
  • 16.15.6. Extended Tektronix Object Format (--tektronix Option)
  • 16.15.7. Texas Instruments SDSMAC (TI-Tagged) Object Format (--ti_tagged Option)
  • 16.15.8. TI-TXT Hex Format (--ti_txt Option)
• 16.16. Hex Conversion Utility Examples
  • 16.16.1. Scenario 1 – Hex Conversion Command File for a Single 8-Bit EPROM
  • 16.16.2. Scenario 2 – Hex Conversion Command File for 16-BIS Code
  • 16.16.3. Scenario 3 – Hex Conversion Command File for Two 8-Bit EPROMs