MDK compilation process and arm compilation tool chain

Welcome to join 【Linux C/C++/Python Community 】 Discuss and share together Linux C/C++/Python/Shell Programming 、 robotics 、 machine learning 、 Machine vision 、 The embedded AI Knowledge and technology in related fields .

---

---

Links to related articles

• C/C++ The process of compiling a program
• How to generate a source file to an executable file ：GCC Detailed explanation of compilation tool chain and compilation parameters

---

MDK-ARM It's also called KEIL MDK-ARM、KEIL ARM、Realview MDK、I-MDK、uVision5 etc. .

MDK The build process

Windows/Linux Using linker, you can directly generate executable image files elf And run , And development board / The SCM platform needs to load this content onto the chip , adopt formelf The converter will elf The image file is converted to .bin perhaps .hex file , And downloaded to the chip by the downloader FLASH/ROM in .
After compilation, all data with the same nature in the application is grouped into one domain , When the program is stored or running , Different domains will present different states .

• code： Code field , Store the machine instructions generated by compilation , That is, the space occupied by the code , These contents are stored in ROM District ;
• RO-data： Read only data field , Refers to the read-only data used in the program , The data is stored in ROM District ;
• RW-data： Read / write data fields , It refers to initialization as non 0 Readable and writable data of values , When the program is just running , Data has non 0 The initial value of the , When the program is running , These data will reside RAM District ;
• ZI-data： Initialize to 0 Or uninitialized read-write data fields , Uninitialized data will be initialized by the compiler as 0, When the program just runs, the initial value of these data is 0, Follow up meeting with RW-data data , permanent RAM District ;
• ZI-data Stack space ： Stack space and heap space in the program belong to ZI-data Area , These spaces will be initialized to 0 value , Given by the compiler ZI-data The occupied space also includes the stack size , Local variables are stored in the stack , Store in the heap malloc/new Requested memory .

ARM Compile toolchain

ARM The compilation tool chain mainly includes ：

• ARM C/C++ compiler (armcc)
• Microlib
• ARM Macro Assembler (armasm)
• ARM The linker (armLink)
• ARM Tools (Librarian and FromELF)

ARM Compiler will C/C++ Metafile compiled into relocatable （Relocatable） Target module , And embedded in it for uVision Symbol information debugged by debugger or online debugger . meanwhile ,ARM The compiler can help generate listing file, It can contain symbol table( The symbol table ) And cross reference information .
ARM The path of the compilation tool is Keil Under the installation path of “D:\keil_v5\ARM\ARMCC\bin”, Configure this path to the environment variables of the computer “ Computer → attribute → Advanced system setup → environment variable → User variables → newly build PATH And separate it with a semicolon ”, After configuration, you can Windows The command line cmd Use tool chain .

*ARM C/C++ compiler ( armcc )

armcc Mainly responsible for C/C++ Program compiled as ARM Instruction code .
Usage method ：

• cmd Command line
• keil Magic wand →c/c++→Compiler control string

* MicroLib

MicroLib It's a use. C A highly optimized library of embedded applications written in （ be based on ARM framework ）. Relatively contained in ARM Traditional standards in compilers C library ,MicroLib Have the advantage of better code size , It can meet the requirements of most embedded systems .
Microlib With the standard C The main difference between libraries is ：

• MicroLib Mainly designed for advanced embedded applications ;
• MicroLib Has been optimized , Use the same as ARM Compared with the standard library , Use less code and data memory ;
• MicroLib Designed to work independently of the operating system , Of course, this does not prevent it from communicating with any OS or RTOS( for example Keil RTX) Used together ;
• MicroLib Do not include files I/O Or wide character support ;
  because MicroLib Has been optimized , Reduced code size , So compared with ARM Standards in compilation tools C Library routines , Some functions will execute more slowly .MicroLib and ARM Both standard libraries are included in Keil MDK-ARM in .
  Want to use MicroLib, In the first keil Check... In the settings MicroLib Option box , Then compile the program .keil Will use MicroLib To link programs , It can quickly reduce the size of program code .
  

*ARM Macro assembler ( armasm )

Compile the assembly file into .o file .
Usage method ：

• cmd Command line
• keil Magic wand →Asm→Assembler control string

*ARM The linker ( armLink )

hold .o File links are combined to generate elf Format axf file ,axf Files are executable files .
Usage method ：

• cmd Command line
• keil Magic wand →Linker→Linker control string

*armar

Package the project files into library files .lib.

*formelf Format converter

according to axf File generation hex Documents or bin file .

---

---