ARMCC: Arm Compiler Output Formats
Information in this article applies to:
A third-party emulator cannot load the output file create by MDK-ARM. The Keil project uses the ARM Compiler toolchain. What is the output file format of the executable image that is generated by this compiler?
The Compiler creates standard ELF/DWARF files for the executable image. These files have a *.AXF file extension. ELF/DWARF files can be directly loaded by all popular emulators and several other third-party utilities.
ARM Compiler 6 generates DWARF 4 (DWARF Debugging Standard
Version 4) debug tables with the
ARM Compiler 5 generates DWARF 3 (DWARF Debugging Standard Version 3) debug tables. The compiler can also generate DWARF 2 for backwards compatibility with legacy and third-party tools.
Use the Fromelf Image Converter utility to create output files of different formats. µVision only loads ELF, AXF or HEX files. µVision does not load binary BIN Files.
For Evaluation Version users: with For MDK-ARM Lite, the assembler and linker create Symbolic Output Format objects which cannot be linked with third-party linker utilities. Fully licensed tools generate standard ELF/DWARF files which may be used with third-party utilities.
For older versions: In MDK-ARM Version 3.00 and Version 2.50, the RealView Compiler creates an encrypted executable image that can be only loaded by the µVision Debugger. This was also the output format of the Evaluation Version. When you have entered a valid license for MDK-ARM Version 3.01 or higher, the RealView Compiler creates standard ELF/DWARF files for the executable image.
The following Discussion Forum threads may provide information related to this topic.
Last Reviewed: Monday, May 7, 2018
of your data.