Keil™, An ARM® Company

RealView Linker and Utilities Guide

code_output_format

7.2.2. code_output_format

Selects the binary output file options. code_output_format can be one of:

‑‑bin

Plain binary. You can split output from this option into multiple files with the memory_config option.

‑‑i32

Intel Hex-32 format. This option generates one output file for each load region in the image. You can specify the base address of the output with the ‑‑base option.

‑‑i32combined

Intel Hex-32 format. This option generates one output file for an image containing multiple load regions. You can specify the base address of the output with the ‑‑base option.

‑‑m32

Motorola 32-bit format (32-bit S-records). This option generates one output file for each load region in the image. You can specify the base address of the output with the ‑‑base option.

‑‑m32combined

Motorola 32-bit format (32-bit S-records). This option generates one output file for an image containing multiple load regions. You can specify the base address of the output with the ‑‑base option.

‑‑vhx

Byte oriented (Verilog Memory Model) hexadecimal format. This format is suitable for loading into the memory models of Hardware Description Language (HDL) simulators. You can split output from this option into multiple files with the memory_config option.

If you convert an ELF image containing multiple load regions, fromelf creates an output directory named output_file and generates one or more binary output file(s) for each load region in the input image. fromelf places the file(s) in the output_file directory.

For ‑‑bin, ‑‑m32, ‑‑i32, or ‑‑vhx, fromelf creates a separate file for each load region.

For ‑‑m32combined or ‑‑i32combined, fromelf creates a single file containing all load regions.

Note

For multiple load regions, the name of the first non-empty execution region in the corresponding load-region is used for the file name.

Copyright © 2007 ARM Limited. All rights reserved.ARM DUI 0377A