STM32 Learning Tour ① Development Environment Construction
[Copy link]
1. Similarities and differences There are currently two mainstream development environments for STM32, one is RealViewMDK (based on keil), and the other is Embedded Workbench (based on IAR). For a comparison of the two, you can refer to the comparison of Keil MDK and IAR, two ARM development tools. The main differences are as follows: Similarities: Integrated commercial IDE Differences: MDK does not support cascading folders, and the next level of the folder must be a file; IAR supports cascading, which can be more convenient to manage code and sort out the hierarchy. MDK connects to the library and directly adds it to the folder; IAR needs to be set from the project options. The relative file path in IAR needs to be located through the current folder, that is, it starts with $PROJ_DIR$. MDK only creates a project by default, and the workspace will not be created directly. Default status bar, MDK's toolbar has more functions and is a bit complicated; IAR's is relatively simple, but also relatively thin. Considering the above reasons, I chose IAR as the development environment. 2. Materials required for environment construction. The official website of IAR Embedded Workbench for Arm has the password: 917t. Of course, you can also go directly to the official website to download the registration machine, including the cracking tutorial. The password is: njxi. 3. Start the installation. It is basically a brainless fool tutorial. NEXT all the way. Follow the tutorial. If you have not installed the driver before, many driver installations will pop up. Just install them all. 4. Start cracking. Open the registration machine. Follow the tutorial. There is no problem. 5. Notes. The version we use is the latest official IAR Embedded Workbench for Arm. This is slightly different from the one in the tutorial, but it is roughly the same. Of course, other versions can also be used. This cracking tutorial can be used. Finished!
|