ATM i have not tested flash and debugging, just make configuration.
For everything else, all is working, code completion with doxygen, build is ok and post-build create necessary .bin and .hex files.
Should works under linux without problem, just get a toolchain, and build the two tools “st-util” and “st-flash”, sources at bottom
Executable path | C:\Program Files (x86)\GNU Tools ARM Embedded\4.8 2014q2\bin\arm-none-eabi-gdb.exe |
Debugger initialization commands | target extended-remote localhost:4242 |
Compiler install directory | C:\Program Files (x86)\GNU Tools ARM Embedded\4.8 2014q2 |
C compiler | arm-none-eabi-gcc.exe |
C++ compiler | arm-none-eabi-g++.exe |
Linker for dynamic libraries | arm-none-eabi-gcc.exe |
Linker for static libraries | arm-none-eabi-ar.exe |
Debugger | Select the ARM one |
Make program | make.exe |
Conversion to .elf, flash to board and GDB bridge
arm-none-eabi-objcopy -O ihex bin\Debug\shell.elf bin\Debug\output.hex
arm-none-eabi-objcopy -O binary bin\Debug\shell.elf bin\Debug\output.bin
cmd /c arm-none-eabi-objdump -x --syms bin\Debug\shell.elf > bin\Debug\shell.dmp
Tool name | STM32 Flash Debug |
Command line | C:\Users\Dashie\dev\ARM\stlink-20130324-win\bin\st-flash.exe write bin\Debug\output.bin 0x08000000 |
Working directory | $(PROJECT_DIR)\ |
Output to | Tools output window |
The bridge can be used as a tool too, launching it using Tools+ menu and then starting debugging in Code::Blocks, which will use “extended-target” remote to connect to the bridge.
Tool name | STM32 GDB Bridge |
Command line | C:\Users\Dashie\dev\ARM\stlink-20130324-win\bin\st-util.exe |
Working directory | $(PROJECT_DIR)\ |
Output to | Tools output window |