stm32f030R8 environment configuration under keil environment

Steps:

1. Select the chip model

2. External crystal oscillator 8M, check "Use MicroLIB",

   microlib is an alternative to the default C library. It is intended for use with deeply embedded applications that need to fit into a very small amount of memory. These applications do not run within an operating system.

    microlib is highly optimized to keep the code small. It has fewer features than the default C library and does not have some ISO C features at all.

   The functions in microlib are responsible for:

• Create an environment in which C programs can be executed. This includes:

• Create a stack

• Create a heap (if necessary)

• Initializes parts of the library used by the program.

• Call main() to start executing the program, which is often used for mapping pritf functions.

     The access area generally does not need to be set, unless it is used for IAP or the APP needs to adjust the area space;

3. Generate a hex file, i.e. the burning file.

1. Write the program in keil and compile and connect it into a .hex file that can be downloaded to the development board, and then download it with the jlink emulator; 2. Write and compile the code in the uboot APP, and generate a .bin file that can be downloaded with uboot.

4. Used to generate bin files. If not needed, you can skip this step.

C:\Keil_v5\ARM\ARMCC\bin\fromelf.exe --bin -o E:\bootloader_030test\OBJ\bootloader_030.bin E:\bootloader_030test\OBJ\bootloader_030.axf

Format: CMD command fromelf.exe --bin --output a.bin a.axf 

5.

#ifdef USE_STDPERIPH_DRIVER
  #include "stm32f0xx_conf.h"
#endif 

stm32f0xx_conf.h contains the library function header file. Generally, you need to enter: USE_STDPERIPH_DRIVER;

To ensure that your code runs correctly after optimization, be sure to add volatile before variables that cannot be optimized.

The main function of the option One ELF Section per Function is to optimize redundant functions. With this option, redundant functions can be excluded from the final binary file (although the file where they are located has participated in the compilation and linking) in order to optimize the final binary code to the greatest extent. 
The mechanism implemented by this option is to treat each function as an optimization unit, rather than the entire file as a unit participating in the optimization. 
This optimization function of the option One ELF Section per Function is particularly important, especially in situations where there are strict requirements on the size of the generated binary file. People are accustomed to putting a series of interface functions in one file and then including it in the project as a whole, even if only one function in this file will be used. In this way, the final binary file may contain many redundant functions, resulting in a waste of valuable storage space. 

The option One ELF Section per Function is particularly effective for optimizing a large project, sometimes even halving the number of functions. Of course, for small projects or projects with few redundant functions, the optimization effect is not so obvious.

The option One ELF Section per Function compiles only used functions.

Include Paths: Includes the file paths used

6. Hardware download debugging configuration, use JTAG debugger SW mode to download, that is, 3.3V, SWDIO, SWDCLK, GND (these four are enough, usually the download is successful; if the download is abnormal, connect RST to solve it)

Attachment:

Keil MDK generates BIN process

In the integrated development environment of Realview MDK, by default, debug files in *.axf format and executable files in *.hex format can be generated. Although these two file formats are very useful for downloading and debugging the ULINK2 simulator, ADS users are more accustomed to using *.bin format files, and some embedded software developers even have debugging or burning tools for *.bin format files. In order to make full use of existing tools and take advantage of the integrated development environment of Realview MDK, it is a natural idea to convert *.axf format files or *.hex format files into *.bin format files. This article will explore this conversion method in detail.

Before introducing this method in detail, it is necessary to first understand the fromelf.exe conversion tool in ARM's RVCT development kit, because it is the tool that generates *.bin format files in Realview MDK.

The syntax format of the fromelf.exe conversion tool is as follows:

fromelf [options] input_file

The options included in [options] and their detailed descriptions are shown in Table 1.

Table 1 Options and descriptions of the fromelf tool