STM32 Getting Started

  1. Install the MDK environment and download the third-party software mcuisp of the program.

       Turn the BOOT0 switch to VCC, automatically search the serial port, and start programming. If the program is downloaded successfully, the information in the red box below will be printed out. After the program is downloaded successfully, you need to
turn the BOOT0 switch to GND, and then press our reset button to see the experimental imagination (you can also set it as follows).

       When you start programming the button, the MCUISP will be in a connected state, which will cause the program to fail to download, as shown in the screenshot below. The solution is to just press the reset button on the development board.

   2. Online debugger, JLINK driver installation and MDK environment construction.

   3. How to create a new project template.

     Create a new project, select the chip model, and the next window asks us whether we need to copy the STM32 startup code to the project file. This startup code is applicable to the M3 series. Generally, we click Yes, but we are using the ST library here, and the library file also comes with this startup code. So in order to maintain the integrity of the library, we do not need the startup code that comes with the development environment.

     You need to create a startup folder in CMSIS first to store these startup files written in assembly. Copy core_cm3.c and core_cm3.h to the \CMSIS folder. Copy stm32f10x.h, system_stm32f10x.c, and system_stm32f10x.h to the \CMSIS folder. (These are all STM32 library functions, startup codes, etc.)

     Basically done, right-click the project name to open the "Manage Components" window, or click the "Product" icon on the toolbar. Rename the Target under Project Targets to what you want.

     Then we need to create user groups. Right-click and select Add Group... to create the four user groups we need.

     Next, add files to each user group.

     Finally, set up the software: The project has been basically built. Now let's configure the MDK configuration options. Click the magic wand button in the toolbar and select Output in the pop-up window. Then click Select Folder for Objects... to set the location where the compiled output file will be saved. At the same time, check the Create HEX File and Browse information options. (The path folder we set before)

    Select the "C++" tab, and enter "use_stdperiph_driver,stm3210x_hd" in define. add use_stdperiph_driver is to shield the default search path of the compiler, and use the st library we added to the project instead. add stm32f10x_hd because the chip we use is large capacity. after adding the stm32f10x_hd macro, we can use the registers defined for large capacity in the library file. add use_stdperiph_driver is to shield the default search path of the compiler, and use the st library we added to the project instead. add stm32f10x_hd because the chip we use is large capacity. after adding the stm32f10x_hd macro, we can use the registers defined for large capacity in the library file.

    Click on the Include Paths column and add the search path for library files here, so that the default search path can be blocked. But when the compiler cannot find the path we specify, it will still return to the standard directory to search, just like some ANSI C library files, such as stdin.h and stdio.h. But when the compiler cannot find the path we specify, it will still return to the standard directory to search, just like some ANSI C library files, such as stdin.h and stdio.h.

The last step is to modify the main.c file.

   #include "stm32f10x.h"   

    int main(void)    
 {    
 while(1);    
 // add your code here ^_^。    
 } At this point, our project template is built.