In the integrated development environment of the Realview MDK. By default, you can generate debug Files in *.axf format and executable files in *.hex format.
Although these two-format files are very helpfulULINK2Emulator for download and commissioning, butADSusers are more accustomed to using*.binformatted file. Even some embedded software developers already have*.binDebug or burn-write tool for format files. In order to make full use of existing tools. At the same time playRealview MDKThe benefits of an integrated development environment*.AXFformat file or*.hexThe format file is converted into*.binformat of the file is a very natural idea. This paper will discuss the conversion method in detail.
Before you go into a specific introduction to this approach, let's look atARMCompany'sRVCTin the development kitFromelf.exeThe conversion tool is very necessary due to theRealviewMDKgenerated in*.binthe tool for format files is exactly it.
Fromelf.exeThe syntax format for the conversion tool is as follows:
fromelf [Options] Input_file
Of[Options]the included options and specific descriptive narratives are shown in the following table:
In the grasp offromelfafter the syntax format of the conversion tool. The following will describe it inRealview MDKin the usage:
1: You can produce a running file (that is, configure Output) First
AA for the generated executable file. (That is, a AA.AXF file will be generated after compilation ) The resulting bin file is generated from this file.
2: Generate . bin file from a executable file ( that is, configure User)
C:\Keil\ARM\BIN40\fromelf.exe --bin-o: command indicates that a bin file is generated from a running file
D:\1\out\33.bin : The path and file name of the production bin file
D:\1\OUT\AA.AXF : The path and file name of the executable file
33.bin files can be produced after compilation (note that the path is variable)
How to generate *.bin formatted files in MDK?