GDB

This message will disappear after all relevant tasks have been resolved.

Semantic MediaWiki

There are 1 incomplete or pending task to finish installation of Semantic MediaWiki. An administrator or user with sufficient rights can complete it. This should be done before adding new data to avoid inconsistencies.

1. Article purpose[edit source]

This article provides the basic information needed to start using the GDB^[1] application tool.

It explains how to use this GNU debugger tool connected to your ST board target via Ethernet or via ST-LINK, and how to perform cross-debugging (IDE, gdb viewer tool or command line) on Arm^® Cortex^®-A7 side for Linux^® application, Linux^® kernel (including external modules), or Arm^® Cortext^®-M4 firmware.

2. Introduction[edit source]

The following table provides a brief description of the tool, as well as its availability depending on the software packages:

: this tool is either present (ready to use or to be activated), or can be integrated and activated on the software package.

: this tool is not present and cannot be integrated, or it is present but cannot be activated on the software package.

Tool			STM32MPU Embedded Software distribution			STM32MPU Embedded Software distribution for Android™
Name	Category	Purpose	Starter Package	Developer Package	Distribution Package	Starter Package	Developer Package	Distribution Package
GDB	Debugging tools	The GNU Project debugger, GDB^[1], allows monitoring program execution, or what the program was doing at the moment it crashed.	*		**			**
GDB	Debugging tools		* Cross compile gdb and openocd binaries are required and only available from Developer Package. ** It is recommended to use the Developer Package to run the gdb debug session, which provided all dependencies			* Cross compile gdb and openocd binaries are required and only available from Distribution Package.

The GDB can perform four main types of actions (plus other corollary actions) to help you detect bugs when running your software or application:

Start the program, specifying anything that might affect its behaviour.
Make the program stop on specific conditions.
Examine what happened when the program stopped.
Update the program in order to test a bug correction, and jump to the next one.

3. Overview of GDB setup for STM32MPU[edit source]

3.1. GDB setup paths[edit source]

Two paths can be used in the STM32MPU environment for GDB setup:

gdb ↔ gdbserver path through Ethernet, used for Cortex-A7 Linux applications.

In that case, two software components are required, one on the target and the other on the host PC.

gdb ↔ JTAG/SWD path through OpenOCD and ST-LINK, used both for Cortex-M4 firmware and Cortex-A7 Linux kernel.

In that case, only one software component is required on the host PC.

GDB paths scheme

Two components are included in OpenSTLinux Developer Package for GDB setup:

gdbserver: embedded on target rootfs and used as remote access for a host connection
arm-openstlinux_weston-linux-gdb: embedded on host PC side, cross-compiled gdb binary that manages the connexion between the host computer and the target board

3.2. JTAG and SWD debug port[edit source]

The STM32MPU features two debug ports through the embedded CoreSight™ component that implements an external access port for connecting debugging equipment:

A 5-pin standard JTAG interface (JTAG-DP)
A 2-pin (clock + data) “serial-wire debug” port (SW-DP)

These two modes are mutually exclusive since they share the same I/O pins.

Refer to STM32MP15 reference manuals for information related to JTAG and SWD.

4. Installing the GDB tool[edit source]

This tool is made of two parts, one on the host PC, and a second on the target (only for debugging Linux applications).

4.1. Installing the GDB tool on your host PC[edit source]

Below is the list of required components:

The cross-compiled GDB binary
The OpenOCD binary and configuration files
The symbols files of all BSP components (TF-A, U-Boot and Linux kernel), corresponding to the images of the OpenSTLinux Starter Package.

4.1.1. Using the STM32MPU Embedded Software distribution[edit source]

4.1.1.1. Developer Package[edit source]

Only the Developer Package can be used, since it is the only one which provides all the required components.

4.1.2. Using the STM32MPU Embedded Software distribution for Android™[edit source]

4.1.2.1. Distribution Package[edit source]

Only Distribution Package can be used, since it is the only one which provides all the required components.

4.2. Installing the GDB on your target board[edit source]

On the target board, only the gdbserver binary is required for debugging Linux applications.

It is available by default within the Starter Package, which provides images linked to the Developer Package.

Below information is related to the Android™ distribution
Also the case for Starter Package for Android™

5. Getting started[edit source]

This chapter describes the two ways for debugging OpenSTLinux BSP components (TF-A, U-Boot and Linux kernel including external modules), Linux applications and Cortex-M4 firmware: by using GDB commands or by using a GDB user interface such as gdbgui, DDD or IDE.

5.1. Prerequisites[edit source]

The target board is up and running.

5.2. Debug OpenSTLinux BSP components[edit source]

5.2.1. Setting up GDB / OpenOCD debug path environment[edit source]

Architecture

The figure below shows the architecture corresponding to the GDB/OpenOCD connected to Cortex-A7 and Cortex-M4 cores.
Note: The ST-LINK probes available on the STM32MP1 board can be used through a USB interface, as well as any other external probes through the Trace or JTag connector.

Prerequisites

The Developer Package must be installed. It provides the SDK, the debug symbol files and the source files for TF-A, U-Boot and Linux kernel (refer to STM32MP1 Developer Package).

Below information is related to the Android™ distribution
The Distribution Package must be installed:

to get the debug symbol files for TF-A and U-Boot.
to get the source files for TF-A, U-Boot and Linux kernel
to generate the symbol file for Linux kernel (vmlinux file not present by default): please refer to article How_to_build_kernel_for_Android

The debug symbol files contain the symbols for the TF-A, U-Boot and Linux kernel binaries (from the Starter Package image) that have been flashed on the board.

Environment configuration files

To speed up environment setup for debugging with GDB, download two configuration files, and install them on your PC (under the home directory: $HOME/gdbscripts/). You can then customize them:

- Setup.gdb: main configuration file in which you can define the debug context you want to use (Refer to Boot chains overview for details). Possible combinations are:

Trusted boot chain:

Debug mode	(1) Cortex-A7 TF-A(BL2)	(2) Cortex-A7 TF-A(BL32)	(3) Cortex-A7 SSBL(U-Boot)	(4) Cortext-A7 Linux kernel
(0) - Boot
(1) - Running target

Trusted boot chain with OP-TEE:

Debug mode	(1) Cortex-A7 TF-A(BL2)	(2) Cortex-A7 OP-TEE	(3) Cortex-A7 SSBL(U-Boot)	(4) Cortext-A7 Linux kernel
(0) - Boot
(1) - Running target

- Path_env.gdb: customization file to define all the paths to source and symbol files, which can either be directly retrieved from the Developer Package (refer to the Example of directory structure for Packages), or result from a new compilation. In both cases, update the paths corresponding to your environment.
Please read carefully the comments provided in this file to help you updating source and symbol paths.

Store these files locally on your host PC, check for name cast (Setup.gdb and Path_env.gdb) and update them accordingly.

5.2.2. Configuring GDB and OpenOCD for attachment on a running target[edit source]

When the target board is running, you can attach the GDB only during one of following phases:

5.2.2.1. U-Boot execution phase[edit source]

Select the right configuration in Setup.gdb:

# Set debug phase:
#	1: Attach at Cortex-A7 / TF-A(BL2)
#	2: Attach at Cortex-A7 / TF-A(BL32) or OP-TEE
#	3: Attach at Cortex-A7 / U-Boot
#	4: Attach at Cortex-A7 / Linux kernel
set $debug_phase = 3

#	0: Attach at boot
#	1: Attach running target
set $debug_mode = 1

# Set debug trusted bootchain:
#	0: TF-A BL2 / TF-A BL32 / U-Boot / Linux kernel
#	1: TF-A BL2 / OP-TEE / U-Boot / Linux kernel
set $debug_trusted_bootchain = 0 or 1 #depending on your software boot chain configuration

When the configuration is complete, jump to Running OpenOCD and GDB.

5.2.2.2. Linux kernel execution phase[edit source]

Select the right configuration in Setup.gdb:

# Set debug phase:
#	1: Attach at Cortex-A7 / TF-A(BL2)
#	2: Attach at Cortex-A7 / TF-A(BL32) or OP-TEE
#	3: Attach at Cortex-A7 / U-Boot
#	4: Attach at Cortex-A7 / Linux kernel
set $debug_phase = 4

#	0: Attach at boot
#	1: Attach running target
set $debug_mode = 1

# Set debug trusted bootchain:
#	0: TF-A BL2 / TF-A BL32 / U-Boot / Linux kernel
#	1: TF-A BL2 / OP-TEE / U-Boot / Linux kernel
set $debug_trusted_bootchain = 0 or 1 #depending on your software boot chain configuration

When the configuration is complete, jump to Running OpenOCD and GDB.

5.2.3. Configuring GDB and OpenOCD for attachment on boot[edit source]

You can attach the GDB during target boot only in the following cases:

Warning

In that case, the target board will automatically reboots when the GDB starts.

5.2.3.1. TF-A(BL2) boot case[edit source]

In that case, the GDB breaks in bl2_entrypoint function.

Select the right configuration in Setup.gdb:

# Set debug phase:
#	1: Attach at Cortex-A7 / TF-A(BL2)
#	2: Attach at Cortex-A7 / TF-A(BL32) or OP-TEE
#	3: Attach at Cortex-A7 / U-Boot
#	4: Attach at Cortex-A7 / Linux kernel
set $debug_phase = 1

#	0: Attach at boot
#	1: Attach running target
set $debug_mode = 0

# Set debug trusted bootchain:
#	0: TF-A BL2 / TF-A BL32 / U-Boot / Linux kernel
#	1: TF-A BL2 / OP-TEE / U-Boot / Linux kernel
set $debug_trusted_bootchain = 0 or 1 #depending on your software boot chain configuration

When this operation is complete, jump to Running OpenOCD and GDB.

5.2.3.2. TF-A(BL32) boot case[edit source]

In that case, the GDB breaks in sp_min_entrypoint function.

Select the right configuration in Setup.gdb:

# Set debug phase:
#	1: Attach at Cortex-A7 / TF-A(BL2)
#	2: Attach at Cortex-A7 / TF-A(BL32) or OP-TEE
#	3: Attach at Cortex-A7 / U-Boot
#	4: Attach at Cortex-A7 / Linux kernel
set $debug_phase = 2

#	0: Attach at boot
#	1: Attach running target
set $debug_mode = 0

# Set debug trusted bootchain:
#	0: TF-A BL2 / TF-A BL32 / U-Boot / Linux kernel
#	1: TF-A BL2 / OP-TEE / U-Boot / Linux kernel
set $debug_trusted_bootchain = 0

When this operation is complete, jump to Running OpenOCD and GDB.

5.2.3.3. OP-TEE boot case[edit source]

In that case, the GDB breaks in _start function.

Select the right configuration in Setup.gdb:

# Set debug phase:
#	1: Attach at Cortex-A7 / TF-A(BL2)
#	2: Attach at Cortex-A7 / TF-A(BL32) or OP-TEE
#	3: Attach at Cortex-A7 / U-Boot
#	4: Attach at Cortex-A7 / Linux kernel
set $debug_phase = 2

#	0: Attach at boot
#	1: Attach running target
set $debug_mode = 0

# Set debug trusted bootchain:
#	0: TF-A BL2 / TF-A BL32 / U-Boot / Linux kernel
#	1: TF-A BL2 / OP-TEE / U-Boot / Linux kernel
set $debug_trusted_bootchain = 1

When this operation is complete, jump to Running OpenOCD and GDB.

5.2.3.4. U-Boot boot case[edit source]

In that case, the GDB breaks in in _start function.

Select the right configuration in Setup.gdb:

# Set debug phase:
#	1: Attach at Cortex-A7 / TF-A(BL2)
#	2: Attach at Cortex-A7 / TF-A(BL32) or OP-TEE
#	3: Attach at Cortex-A7 / U-Boot
#	4: Attach at Cortex-A7 / Linux kernel
set $debug_phase = 3

#	0: Attach at boot
#	1: Attach running target
set $debug_mode = 0

# Set debug trusted bootchain:
#	0: TF-A BL2 / TF-A BL32 / U-Boot / Linux kernel
#	1: TF-A BL2 / OP-TEE / U-Boot / Linux kernel
set $debug_trusted_bootchain = 0 or 1 #depending on your software boot chain configuration

When this operation is complete, jump to Running OpenOCD and GDB.

5.2.3.5. Linux kernel boot case[edit source]

In that case, the GDB breaks in stext function.

Select the right configuration in Setup.gdb:

# Set debug phase:
#	1: Attach at Cortex-A7 / TF-A(BL2)
#	2: Attach at Cortex-A7 / TF-A(BL32) or OP-TEE
#	3: Attach at Cortex-A7 / U-Boot
#	4: Attach at Cortex-A7 / Linux kernel
set $debug_phase = 4

#	0: Attach at boot
#	1: Attach running target
set $debug_mode = 0

# Set debug trusted bootchain:
#	0: TF-A BL2 / TF-A BL32 / U-Boot / Linux kernel
#	1: TF-A BL2 / OP-TEE / U-Boot / Linux kernel
set $debug_trusted_bootchain = 0 or 1 #depending on your software boot chain configuration

When this operation is complete, jump to Running OpenOCD and GDB.

5.2.4. Running OpenOCD and GDB[edit source]

Prerequisites

Before running OpenOCD and GDB, check that the target board is in the right state.

For all configurations except GDB attachment to a running SSBL (U-Boot), the board has to operate in OpenSTLinux running mode.

In case of attachment to a running SSBL (U-Boot) configuration, the board target must be in U-Boot console mode:

#Reboot the target board

#Press any key to stop at U-Boot execution when booting the board
 ...
 Hit any key to stop autoboot:  0

When you are in the expected configuration, two different consoles must be started: one for OpenOCD and one for GDB.
The SDK environment must be installed on both console terminals.

OpenOCD console

For ecosystem release ≥ v1.2.0 :

# First console for starting openocd with configuration file

 source <Your_SDK_path>/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
 $OECORE_NATIVE_SYSROOT/usr/bin/openocd -s $OECORE_NATIVE_SYSROOT/usr/share/openocd/scripts -f <board.cfg>

For ecosystem release ≤ v1.1.0 :

# First console for starting openocd with configuration file

 source <Your_SDK_path>/environment-setup-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
 $OECORE_NATIVE_SYSROOT/usr/bin/openocd -s $OECORE_NATIVE_SYSROOT/usr/share/openocd/scripts -f <board.cfg>

Below information is related to the Android™ distribution

# First console for starting openocd with configuration file
 cd <Your_Android_distribution_path>
 ./device/stm/stm32mp1-openocd/prebuilt/openocd -s ./device/stm/stm32mp1-openocd/prebuilt/scripts -f <board.cfg>

Possible target configuration files for <board.cfg>:

Target board	Adapter	SWD mode board.cfg	JTAG mode board.cfg
STM32MP157C-EV1	ST-LINK *	board/stm32mp15x_ev1_stlink_swd.cfg	board/stm32mp15x_ev1_stlink_jtag.cfg
STM32MP157C-EV1	U-LINK2	board/stm32mp15x_ev1_ulink2_swd.cfg	board/stm32mp15x_ev1_ulink2_jtag.cfg
STM32MP157C-EV1	J-LINK	board/stm32mp15x_ev1_jlink_swd.cfg	board/stm32mp15x_ev1_jlink_jtag.cfg
STM32MP157X-DK2	ST-LINK *	board/stm32mp15x_dk2.cfg	**

* Both v2 and v3 are supported.

** JTAG wires are not connected in DK2.

Note: It is recommended to use SWD, which is faster than JTAG.

GDB console

Warning

The GDB must be executed from the directory where the scripts have been installed (i.e. $HOME/gdbscripts/)

# Second console for starting the GDB

For ecosystem release ≥ v1.2.0 :

 cd $HOME/gdbscripts/
 source <Your_SDK_path>/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
 $OECORE_NATIVE_SYSROOT/usr/bin/arm-ostl-linux-gnueabi/arm-ostl-linux-gnueabi-gdb -x=$HOME/gdbscripts/Setup.gdb

For ecosystem release ≤ v1.1.0 :

 cd $HOME/gdbscripts/
 source <Your_SDK_path>/environment-setup-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
 $OECORE_NATIVE_SYSROOT/usr/bin/arm-openstlinux_weston-linux-gnueabi/arm-openstlinux_weston-linux-gnueabi-gdb -x=$HOME/gdbscripts/Setup.gdb

Below information is related to the Android™ distribution

Ensure the GCC toolchain is installed using bspsetup command in your Distribution Package

# Second console for starting the GDB
 cd $HOME/gdbscripts/
 <Your_Android_distribution_path>/prebuilts/gcc/linux-x86/arm/<toolchain_version>-x86_64-arm-eabi/bin/arm-eabi-gdb -x=$HOME/gdbscripts/Setup.gdb

5.2.5. To know more about Linux kernel debug with GDB[edit source]

Please refer to Debugging the Linux kernel using the GDB.

5.2.6. Access to STM32MP registers[edit source]

5.2.6.1. Using gdb command line[edit source]

- The following monitoring commands can be used to read a register value:

 monitor mdb <phys_address> [count] #Display target memory as 8-bit bytes
 monitor mdh <phys_address> [count] #Display target memory as 16-bit bytes
 monitor mdw <phys_address> [count] #Display target memory as 32-bit bytes

For example: Read RCC_MP_APB1ENSETR register on STM32MP1 to check RCC APB1 peripheral enable status.

 monitor mdw phys 0x50000a00 #full 32bits value result requested
0x50000a00: 00010000 --> UART4 is enable as explained in STM32MP15 reference manuals

- The following monitoring commands can be used to set a register value:

 monitor mwb <phys_address> <value> [count] #Write byte(s) to target memory
 monitor mwh <phys_address> <value> [count] #Write 16-bit half-word(s) to target memory
 monitor mww <phys_address> <value> [count] #Write 32-bit word(s) to target memory

For example: Write RCC_MP_APB1ENCLRR register on STM32MP1 to clear the UART4 RCC of APB1 peripheral, then reenable it:

 monitor mww phys 0x50000a04 0x00010000 #full 32bits value given

# You can then check that UART4 is disable by reading the RCC_MP_APB1ENSETR register:
 monitor mdw phys 0x50000a00
0x50000a00: 00000000

# You can also check that the console is disabled by going on running the GDB
 c

# When the GBD has stopped running, you can re-enable UART4 RCC:
 monitor mww phys 0x50000a00 0x00010000

5.2.6.2. Using CMSIS-SVD environment[edit source]

The CMSIS-SVD environment is useful to get detailed information on registers, such as name and bit descriptions.

It is based on python scripts and svd files which contain the description of all registers.

Refer to CMSIS-SVD environment and scripts for more details.

5.3. Debug Linux application with gdbserver[edit source]

5.3.1. Enable debug information[edit source]

Once your program is built using the sdk toolchain, make sure that the -g option is enabled to debug your program and add the necessary debug information.

Note: If an issue occurs during debugging, you can also force gcc to "not optimize code" using the -O0 option.

Example of a simple test program build:

 $CC -g -o myappli myappli.c

Example based on Hello World: refer to "hello world" user space example

Edit and update the makefile for the user space example:

...
# Add / change option in CFLAGS if needed
-# CFLAGS += <new option>
+ CFLAGS += -g
...

5.3.2. Remote debugging using gdbserver[edit source]

In this setup, an ethernet link must be set between the host PC and the target board.

Once your program is installed on the target (using ssh or copied from an SDcard), you can start debugging it.

On target side: based on "Hello world" user space example

 cd /usr/local/bin
 ls
   hello_world_example
 gdbserver host:1234 hello_world_example
  Process main created; pid = 11832 (this value depends on your target)
  Listening on port 1234

Your target waits for remote PC connection, and then starts debugging.

Launch the GDB command from your source file folder (easier source loading)

The SDK environment must be installed.

For ecosystem release ≥ v1.2.0 :

 cd <source file folder path>
 ls
    hello_world_example  hello_world_example.c  hello_world_example.o  kernel_install_dir  Makefile
 source <Your_SDK_path>/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
 $OECORE_NATIVE_SYSROOT/usr/bin/arm-ostl-linux-gnueabi/arm-ostl-linux-gnueabi-gdb
   GNU gdb (GDB) X.Y.Z
   ...
   This GDB was configured as "--host=x86_64-ostl_sdk-linux --target=arm-ostl-linux-gnueabi".
   ...

For ecosystem release ≤ v1.1.0 :

 cd <source file folder path>
 ls
    hello_world_example  hello_world_example.c  hello_world_example.o  kernel_install_dir  Makefile
 source <Your_SDK_path>/environment-setup-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
 $OECORE_NATIVE_SYSROOT/usr/bin/arm-openstlinux_weston-linux-gnueabi/arm-openstlinux_weston-linux-gnueabi-gdb
   GNU gdb (GDB) X.Y.Z
   ...
   This GDB was configured as "--host=x86_64-openstlinux_weston_sdk-linux --target=arm-openstlinux_weston-linux-gnueabi".
   ...

Connect to the target and load the source file:

 target remote <IP_Addr_of_Board>:1234
  Remote debugging using <IP_Addr_of_Board>:1234
  Reading /home/root/test from remote target...
  ...
 break 16 (line number in the source file)
 continue

The target program breaks on the breakpoint. Proceed until the end of the program:

 continue
  Continuing.
  [Inferior 1 (process 16204) exited normally]
 quit

5.4. User interface application[edit source]

5.4.1. Text user interface (TUI) mode[edit source]

This user interface mode is the first step before using the graphical UI as GDBGUI or DDD.

The TUI can be very useful to map source code with instruction.

Please go through the online documentation ^[2] ^[3].

5.4.2. Debugging with GDBGUI[edit source]

Please refer to the dedicated gdbgui article.

5.4.3. Debugging with DDD[edit source]

GNU DDD is a graphical front-end for command-line debuggers. Please refer to dedicated web page for details^[4].

5.4.4. Debugging with IDE[edit source]

Please refer to STM32-CoPro-MPU plugin for SW4STM32.

6. To go further[edit source]

6.1. Useful GDB commands[edit source]

When using the GDB in command line mode, it is important to know some basic GDB commands, such as run software, set breakpoints, execute step by step, print variables and display information.

Please refer to GDB commands article.

6.2. Core dump analysis using GDB[edit source]

The core dump generated for an application crash can be analysed by using the GDB.

Developer Package components, such as SDK and symbol files, must installed. Please refer to STM32MP1 Developer Package.

The symbol file containing the debug symbol of the application in which the crash occurred must also be available.

First enable the SDK environment:

For ecosystem release ≥ v1.2.0 :

 source <Your_SDK_path>/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi

For ecosystem release ≤ v1.1.0 :

 source <Your_SDK_path>/environment-setup-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi

Then play the core dump with GDB:

For ecosystem release ≥ v1.2.0 :

 $OECORE_NATIVE_SYSROOT/usr/bin/arm-ostl-linux-gnueabi/arm-ostl-linux-gnueabi-gdb <path_to_the_binary> <path_to_the_core_dump_file>

For ecosystem release ≤ v1.1.0 :

 $OECORE_NATIVE_SYSROOT/usr/bin/arm-openstlinux_weston-linux-gnueabi/arm-openstlinux_weston-linux-gnueabi-gdb <path_to_the_binary> <path_to_the_core_dump_file>

6.3. Tips[edit source]

Managing multiple debug setups

To manage multiple debug setups for different software versions, create different Path_env.gdb files with different names, and call the expected file in the Setup.gdb file:

...
####################################################################

# Set environment configuration
#Path_env.gdb
source Path_env_dk2_18_12_14.gdb

####################################################################
...

7. References[edit source]

Useful external links

Document link	Document Type	Description
Using kgdb, kdb and the kernel debugger internals	User Guide	KGDB documentation guide
Welcome to the GDB Wiki	User guide	GDB Wiki
Building GDB and GDBserver for cross debugging	User Guide	Explain how to build gdb for target and host
A GDB Tutorial with Examples	Training	Debugging a simple application

[gdbgnudotorg-1] 1.0 ^1.1 https://www.gnu.org/software/gdb

[2] ttps://sourceware.org/gdb/onlinedocs/gdb/TUI.html#TUI

[3] ttps://ftp.gnu.org/old-gnu/Manuals/gdb/html_chapter/gdb_19.html

[4] ttps://www.gnu.org/software/ddd

[1]

[2]

[3]

[4]