Version history
- (24 March 2017) Update links and new installation method.
- (9 August 2015) Original article.
Brief
- References:
- Install toolchain (
gcc-arm-none-eabi-4_9-2015q2-20150609-win32.exe) and build tools (gnuarmeclipse-build-tools-win32-2.4-201503242026-setup.exe)
- Install Eclipse (
eclipse-cpp-mars-R-win32-x86_64.zip)
- Install GNU ARM Eclipse plugin
Help - Install New Software…Add new repo: GNU ARM Eclipse Plug-ins (http://gnuarmeclipse.sourceforge.net/updates)- Help - Eclipse Marketplace…
- Search for
gnu arm eclipse
- Install the plugins
- It may fail with
GNU ARM Eclipse plug-ins: Received fatal alert: handshake_failure – see this link for solution
- Basically installs update to the JRE by replacing two files
local_policy.jar and US_export_policy.jar in C:\Program Files\Java\jre1.8.0_111\lib\security
- Set workspace preferences
Setup Packs – optional
- Reference: Packs manager
- Go to Packs perspective, click refresh
- Install the packs needed (STM32F1xx_DFP)
- To see the progress, look at the status bar on the bottom right
- Back to C/C++ perspective, assign device to project
- Note: it seems that Packs is still not used in build process in current version of GNU ARM Eclipse plugin (
1.0.0.7X7s7icNPLHh8Ecy9dreSyo_r)
Hello Blinky
- Reference: STM32F template
- New C (or C++) project, use type STM32F10x C/C++ project using Cross ARM GCC
- Chip family: STM32f10x Medium Density Value Line
- Flash size (KB): 128
- RAM size (KB): 8
- External clock (Hz): 8000000
- Content: Blinky (blink a led)
- Use system calls: Freestanding (no POSIX system calls)
- Trace output: None (no trace output)
- Build the project, verify that the build succeeded
- Q: where is the linker script?
- Use STM32 ST-LINK Utility to Program the .hex file to the device –> Nothing happens . . .
- Need to modify GPIO assignment, in
src/BlinkLed.h:
- Set
#define BLINK_PORT_NUMBER to (2) – PORTC
- Set
#define BLINK_PIN_NUMBER to (8) or (9) – blue or green LED on STM32VLDISCOVERY board, respectively
- Clock setup, see
system/src/cmsis/system_stm32f10x.c
- For
STM32F10X_MD_VL, the system clock is default to SYSCLK_FREQ_24MHz
- This macro enables
SetSysClockTo24() function definition which configures the registers (including the PLL) accordingly
- Also,
HSE_VALUE macro is set in the compiler preprocessor, in this case it is set to 8000000 (which is the external crystal frequency)
- Another option when a crystal is not available is to use HSI (high speed internal oscillator, 8 MHz nominal)
Install OpenOCD
- Reference: OpenOCD install
- Install STLINK driver (
stsw-link009/stlink_winusb_install.bat)
- Using Zadig (
zadig_2.1.2.exe)
- Options - List All Devices
- Select STM32 STLink from the dropdown
- Change the driver to WinUSB (v6.1.7600.16385) – or later version, click Replace Driver
- On the first time, Zadig reported failed to install the driver (timeout after ~5 minutes), but after reconnecting the board now it is listed as Universal Serial Bus devices - STM32 STLink in Device Manager
- Not sure if this is a normal behavior
- Also now the board is not detected by STM32 ST-LINK Utility
- To restore the original driver: uninstall driver in Device Manager, make sure that Delete the driver software for this device is checked
- Second time using Zadig, driver installed successfully
- Install OpenOCD (
gnuarmeclipse-openocd-win32-0.9.0-201505190955-setup.exe)
- Verify that OpenOCD works:
C:\Program Files (x86)\GNU ARM Eclipse\OpenOCD\0.9.0-201505190955\bin>openocd -f board/stm32vldiscovery.cfg
GNU ARM Eclipse 32-bits Open On-Chip Debugger 0.9.0-00073-gdd34716-dirty (2015-05-19-09:56)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v1 JTAG v13 API v2 SWIM v0 VID 0x0483 PID 0x3744
Info : using stlink api v2
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
Using the OpenOCD plugin
- Reference: OpenOCD debugging
- Setup debugging configuration using Run - Debug Configurations…, then start debugging using Debug
- Debugging works! Single step, breakpoint, watch expression . . .
- The debugging speed is rather slow
- To increase, edit
C:\Program Files (x86)\GNU ARM Eclipse\OpenOCD\0.9.0-201505190955\scripts\board\stm32vldiscovery.cfg, add this line: adapter_khz 20000
- 20000 is just an arbitrary large number
- When running the OpenOCD, now the debugger runs at 4000 kHz (apparently it is limited to half of clock frequency)
C:\Program Files (x86)\GNU ARM Eclipse\OpenOCD\0.9.0-201505190955\bin>openocd.exe -f board/stm32vldiscovery.cfg
GNU ARM Eclipse 32-bits Open On-Chip Debugger 0.9.0-00073-gdd34716-dirty (2015-05-19-09:56)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
adapter speed: 20000 kHz
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 20000 kHz, using 4000 kHz
Info : Unable to match requested speed 20000 kHz, using 4000 kHz
Info : clock speed 4000 kHz
Info : STLINK v1 JTAG v13 API v2 SWIM v0 VID 0x0483 PID 0x3744
Info : using stlink api v2
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
- Since the program is written to flash, to jump to free running mode simply exit debugging and reset the board
Optimization
- Optimization can be set in Project properties, C/C++ Build - Settings, Optimization
- Default is -Og for Debug configuration, and -Os for Release configuration