Construction of STM32 development environment under Windows

I. Overview

1. Description

The author has written a Linux under the STM32 development environment, the two articles the most difference is that the development environment in the system platform is not the same, but in fact, the difference for the development of the environment of the building actually has little impact, the production of local operations have changed. In view of this, this article does not need to set up the STM32 development environment in Windows to elaborate the detailed process, the reader can be combined with Linux under the STM32 development environment of the building and this article for the Windows STM32 development environment.

2. Development environment Description

Hardware Development Board: Wildfire STM32 Development Board

CORTEX-M3 Model: Stm32f103vet6

Downloader and Debug Interface: Jlink + JTAG

Operating system: Windows XP

Integrated development Environment platform: Eclipse IDE for C + + developers

Cross-compilation chain: ARM-NONE-EABI-GCC

Debug server: Jlink GDB Server

Second, the construction steps

1. Installing the Eclipse IDE for C + + developers

• : https://www.eclipse.org/downloads/
• Select the installation package: Eclipse IDE for C + + developers (Windows version)

After installation, Eclipse is not functioning properly because eclipse is running on a Java virtual machine, so you also need to install a JDK or JRE to create a Java virtual machine that provides an environment for Eclipse to run.

2. Installing the JDK

Refer to installing the JDK, after installing the JDK successfully, restart Eclipse to see that it will run successfully.

3, install cross-compilation chain ARM-NONE-EABI-GCC

• : Https://launchpad.net/gcc-arm-embedded/+download
• Select version: Windows installer

• Double-click Install, note that the installation path is not added to the environment variable at the end of the installation (otherwise the installation path will be added to the user's environment variable path, name collisions may occur when other versions of the toolchain are installed in the future)

• Test whether the installation was successful

4. Install the build tool (Make & RM)

Make and RM are tools under Linux and OS X, and there is no such tool on Windows, but you need to invoke the makefile script when using a cross-compilation chain that uses these tools. Therefore, you need to install such a tool on Windows.

• : http://sourceforge.net/projects/gnuarmeclipse/files/Miscellaneous/
• Can be used after decompression, rename before use, remove the "cs-" prefix
• Check version

• Add the directory of this compilation tool to eclipse's environment variable, and Eclipse's environment variable is in option Window->preference

The echo command

The archive also contains an executable for the Echo command. It's not mandatory for the build to succeed, but it's recommended to has it in the build path, to avoid an annoying CDT Bug, that's triggers an error during the first build of a new project, claiming this ' program ' GCC ' not found in PATH '.

Reference: Build tools (Make & RM) on Windows

5. Installing Jlink Software

Jlink software includes: GDB Server, Jlink driver, and other tools

• : http://www.segger.com/jlink-software.html
• Double-click Install

Note: JLinkGDBServer.exe, JLinkGDBServerCL.exe is actually the same tool, is the GDB debug server. The difference is that the former is a graphical interface, and the latter is the command line interface. For use on Windows, it is recommended to use the command-line mode tool.

6. Install the GNU ARM Eclipse plug-in package

This plug-in package contains 6 plugins that enable different functions. The first plug-in was designed to allow eclipse to support cross-compiling, and the last two were hardware debugging support.

Reference: Plug-ins Install

6, create a new Led_test project and configure, compile

　　

6. Install gdb Debug plugin--c/c++ gdb HardWare debugging

7. Set up the Eclipse debugging environment and debug