Linux under Arm-none-eabi-gdb debug STM32

I. Description of the Environment

Hardware Development Board: Wildfire STM32 Development Board

Downloader and Debug Interface: Jlink + JTAG

Operating system: Virtual machine VMware6.5 + Ubuntu12.0.4

Debugging Tools: Arm-none-eabi-gdb

Debug server: Jlink GDB Server

Debug Project target file: led_test.elf

Second, step

1, install Jlink Drive

Refer to the construction of STM32 development environment under Linux

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

Refer to the construction of STM32 development environment under Linux

3. Compile the project to generate elf files

Refer to the construction of STM32 development environment under Linux

4. Create the. Gdbinit initialization file in the root directory

The contents are:

set auto-load safe-path/

5. Create the. gdbinit file in the Debug directory of the project

The contents are:

 target Remote: 2331  set  Mem Inaccessible-by-default   Offmonitor speed Automonitor endian littlemonitor resetmonitor flash device  = Stm32f103zemonitor Flash breakpoints  = 1  monitor Flash Download  = 1  loadmonitor reg SP  = ( Span style= "color: #800080;" >0x08000000   = (0x08000004   )  break   break   main  continue  

6. Open a terminal to start Jlinkgdbserver

[Email protected]:~# jlinkgdbserver

7, start debugging in the Debug directory of the project

Debug interface

References: GNU ARM Eclipse (for STM32)

　　　　　　STM32 Discovery Development on Linux