How to generate a *. BIN file in MDK?

In the integrated development environment of realview MDK, debugging files in *. axf format and executable files in *. hex format can be generated by default. Although the files in these two formats are very helpful for downloading and debugging the ulink2 simulator, ADS users are more accustomed to using *. bin files, even some embedded software developers already have *. debugging or burning tools for Bin files. To fully utilize the existing tools and leverage the advantages of the integrated development environment of realview MDK *. axf format file or *. convert the hex format file *. bin files are a natural idea. This article will discuss in detail this conversion method.
Before detailed introduction, it is necessary to understand the fromelf.exe conversion tool in the rvctdevelopment kit of arms', because it is exactly the tool used to generate *. Bin files in realview MDK.

The syntax format of the fromelf.exe Conversion Tool is as follows:
Fromelf [Options] input_file

The [Options] includes the following options and detailed descriptions:


After understanding the syntax format of the fromelf Conversion Tool, the following describes how to use it in realview MDK:

1: You must first be able to produce executable files (that is, configure output)

AA indicates the generated executable file (that is, a file of AA. axf will be generated after compilation). The generated binfile is generated from this file.

2: generate a. binfile from the executable file (that is, configure the user)

C: \ Keil \ Arm \ bin40 \ fromelf.exe -- bin-O: Command to generate a binfile from an executable file

D: \ 1 \ out \ 33.bin: path and file name of the produced binfile

D: \ 1 \ out \ AA. axf: path and file name of the executable file

After compilation, 33. binfiles can be produced (note that the path is variable)