Wiki-DB - User contributions [en]

Debugging M4 on STM32MP15xxxx

2021-11-22T13:03:27Z

Renglbrecht:

For general information about the STM32MP15xxxx please refer to the official [https://wiki.st.com/stm32mpu/wiki/Main_Page Wiki]. This page describes ways to debug the M4 on STM32MP15xxxx from ST.

__TOC__

== Debugging modes ==
Production mode and Engineering mode are described [https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Introduction_to_boot_mode here] in the ST Wiki.
To enter Engineering mode with the Avenger96 read the chapter "Boot Mode" in the [https://wiki.dh-electronics.com/index.php/Avenger96#Documentation Getting started guide] and look for "NoBoot".

== Debugging with STM32CubeIDE ==
Debugging for both modes is also described in the ST wiki [https://wiki.st.com/stm32mpu/wiki/STM32CubeIDE#Arm-C2-AE_Cortex-C2-AE-M_debug_on_STM32_MPU_device here]. If you have problems debugging in Production mode, see next subcaption.

=== Without console or lan connection ===
If you have no console or lan connection, STM32CubeIDE does not let you start the debugging session in Production mode.
In this case it is possible to manually start the M4 on the target and start the debugging session with "thruJTAG/SWD (Engineering mode)".

====1. Manually start the M4====
Therefore copy your elf file and the <code>fw_cortex_m4.sh</code> script to the same folder in Linux running on the A7.
You can find <code>fw_cortex_m4.sh</code> in the M4 project of STM32CubeIDE, see picture below.
Next start the M4 with <code>./fw_cortex_m4.sh start</code>.
To stop the M4 run <code>./fw_cortex_m4.sh stop</code>.

[[File:STM32CubeIDE-M4-Start Script-Position.png|200px]]

====2. Debug the manually started M4====
Therefor navigate in the STM32CubeIDE to:
# Debug Configuration and choose "thruJTAG/SWD (Engineering mode)" in the Debugger tab
# Then go to the Startup tab
# Double click your elf file in "Load Image and Symbols"
# Uncheck "Download"
# Then in "Initialization Commands" remove "monitor reset" and "monitor halt"
# Now you can click the blue Debug button
# The M4 will be running (not stoped at main()), therefor you have to set a break point or click the pause button to stop the M4. From there you can single step like normal

[[File:STM32CubeIDE-Debug-Configuration-M4.png|700px]]

== Debugging with GDB (without IDE) ==
https://wiki.st.com/stm32mpu/wiki/GDB#Debug_Cortex-M4_firmware_with_GDB

== Debugging with trace output on Linux ==
https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Logging_in_production_mode

Debugging M4 on STM32MP15xxxx

2021-07-07T10:36:21Z

Renglbrecht:

For general information about the STM32MP15xxxx please refer to the official [https://wiki.st.com/stm32mpu/wiki/Main_Page Wiki]. This page describes ways to debug the M4 on STM32MP15xxxx from ST.

__TOC__

== Debugging modes ==
Production mode and Engineering mode are described [https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Introduction_to_boot_mode here] in the ST Wiki.
To enter Engineering mode with the Avenger96 read the chapter "Boot Mode" in the [https://wiki.dh-electronics.com/index.php/Avenger96#Documentation Getting started guide] and look for "NoBoot".

== Debugging with STM32CubeIDE ==
Debugging for both modes is also described in the ST wiki [https://wiki.st.com/stm32mpu/wiki/STM32CubeIDE#Arm-C2-AE_Cortex-C2-AE-M_debug_on_STM32_MPU_device here]. If you have problems debugging in Production mode, see next subcaption.

=== Without console or lan connection ===
If you have no console or lan connection STM32CubeIDE don't let you start the debugging session.
In this case it is possible to manually start the M4 on the target and start the debugging session with "thruJTAG/SWD (Engineering mode)".
Therefor go to:
# Debug Configuration
# Then to the Startup tab
# Double click your elf file in "Load Image and Symbols"
# Uncheck "Download"
# Then in "Initialization Commands" remove "monitor reset" and "monitor halt"

[[File:STM32CubeIDE-Debug-Configuration-M4.png|700px]]

As next step we have to start the M4 manually.

Therefore copy your elf file and the <code>fw_cortex_m4.sh</code> script to the same folder in Linux running on the A7.
You can find <code>fw_cortex_m4.sh</code> in the M4 project of STM32CubeIDE, see picture below.
Next start the M4 with <code>./fw_cortex_m4.sh start</code>.
To stop the M4 run <code>./fw_cortex_m4.sh stop</code>.

[[File:STM32CubeIDE-M4-Start Script-Position.png|200px]]

== Debugging with GDB (without IDE) ==
https://wiki.st.com/stm32mpu/wiki/GDB#Debug_Cortex-M4_firmware_with_GDB

== Debugging with trace output on Linux ==
https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Logging_in_production_mode

Debugging M4 on STM32MP15xxxx

2021-06-30T06:55:35Z

Renglbrecht: Typo corrected and picture sizes adjusted.

For general information about the STM32MP15xxxx please refer to the official [https://wiki.st.com/stm32mpu/wiki/Main_Page Wiki]. This page describes ways to debug the M4 on STM32MP15xxxx from ST.

__TOC__

== Debugging modes ==
Production mode and Engineering mode are described [https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Introduction_to_boot_mode here] in the ST Wiki.
To enter Engineering mode with the Avenger96 read the chapter "Boot Mode" in the [https://wiki.dh-electronics.com/index.php/Avenger96#Documentation Getting started guide] and look for "NoBoot".

== Debugging with STM32CubeIDE ==
Debugging for both modes is also described in the ST wiki [https://wiki.st.com/stm32mpu/wiki/STM32CubeIDE#Arm-C2-AE_Cortex-C2-AE-M_debug_on_STM32_MPU_device here]. If you have problems debugging in Production mode, see next subcaption.

=== Without console or lan connection ===
If you have no console or lan connection STM32CubeIDE don't let you start the debugging session.
In this case it is possible to manually start the M4 on the target and start the debugging session with "thruJTAG/SWD (Engineering mode)".
Therefor go to:
# Debug Configuration
# Then to the Startup tab
# Double click your elf file in "Load Image and Symbols"
# Uncheck "Download"

[[File:STM32CubeIDE-Debug-Configuration-M4.png|700px]]

As next step we have to start the M4 manually.

Therefore copy your elf file and the <code>fw_cortex_m4.sh</code> script to the same folder in Linux running on the A7.
You can find <code>fw_cortex_m4.sh</code> in the M4 project of STM32CubeIDE, see picture below.
Next start the M4 with <code>./fw_cortex_m4.sh start</code>.
To stop the M4 run <code>./fw_cortex_m4.sh stop</code>.

[[File:STM32CubeIDE-M4-Start Script-Position.png|200px]]

== Debugging with GDB (without IDE) ==
https://wiki.st.com/stm32mpu/wiki/GDB#Debug_Cortex-M4_firmware_with_GDB

== Debugging with trace output on Linux ==
https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Logging_in_production_mode

Debugging M4 on STM32MP15xxxx

2021-02-11T08:54:44Z

Renglbrecht:

For general information about the STM32MP15xxxx please refer to the official [https://wiki.st.com/stm32mpu/wiki/Main_Page Wiki]. This page describes ways to debug the M4 on STM32MP15xxxx from ST.

__TOC__

== Debugging modes ==
Production mode and Engineering mode are described [https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Introduction_to_boot_mode here] in the ST Wiki.
To enter Engineering mode with the Avenger96 read the chapter "Boot Mode" in the [https://wiki.dh-electronics.com/index.php/Avenger96#Documentation Getting started guide] and look for "NoBoot".

== Debugging with STM32CubeIDE ==
Debugging for both modes is also described in the ST wiki [https://wiki.st.com/stm32mpu/wiki/STM32CubeIDE#Arm-C2-AE_Cortex-C2-AE-M_debug_on_STM32_MPU_device here]. If you have problems debugging in Production mode, see next subcaption.

=== Without console or lan connection ===
If you have no console or lan connection STM32CubeIDE don't let you start the debugging session.
In this case it is possible to manually start th M4 on the target and start the debugging session with "thruJTAG/SWD (Engineering mode)".
Therefor go to:
# Debug Configuration
# Then to the Startup tab
# Double click your elf file in "Load Image and Symbols"
# Uncheck "Download"

[[File:STM32CubeIDE-Debug-Configuration-M4.png]]

As next step we have to start the M4 manually.

Therefore copy your elf file and the <code>fw_cortex_m4.sh</code> script to the same folder in Linux running on the A7.
You can find <code>fw_cortex_m4.sh</code> in the M4 project of STM32CubeIDE, see picture below.
Next start the M4 with <code>./fw_cortex_m4.sh start</code>.
To stop the M4 run <code>./fw_cortex_m4.sh stop</code>.

[[File:STM32CubeIDE-M4-Start Script-Position.png]]

== Debugging with GDB (without IDE) ==
https://wiki.st.com/stm32mpu/wiki/GDB#Debug_Cortex-M4_firmware_with_GDB

== Debugging with trace output on Linux ==
https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Logging_in_production_mode

Debugging M4 on STM32MP15xxxx

2021-02-11T08:45:29Z

Renglbrecht:

For general information about the STM32MP15xxxx please refer to the official [https://wiki.st.com/stm32mpu/wiki/Main_Page Wiki]. This page describes ways to debug the M4 on STM32MP15xxxx from ST.

__TOC__

== Debugging modes ==
Production mode and Engineering mode are described [https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Introduction_to_boot_mode here] in the ST Wiki.
To enter Engineering mode with the Avenger96 read the chapter "Boot Mode" in the [https://wiki.dh-electronics.com/index.php/Avenger96#Documentation Getting started guide] and look for "NoBoot".

== Debugging with STM32CubeIDE ==
Debugging for both modes is also described in the ST wiki [https://wiki.st.com/stm32mpu/wiki/STM32CubeIDE#Arm-C2-AE_Cortex-C2-AE-M_debug_on_STM32_MPU_device here]. If you have problems debugging in Production mode, see next subcaption.

=== Without console or lan connection ===
If you have no console or lan connection STM32CubeIDE don't let you start the debugging session.
In this case it is possible to manually start th M4 on the target and start the debugging session with "thruJTAG/SWD (Engineering mode)".
Therefor go to:
# Debug Configuration
# Then to the Startup tab
# Double click your elf file in "Load Image and Symbols"
# Uncheck "Download"

[[File:STM32CubeIDE-Debug-Configuration-M4.png]]

As next step we have to start the M4 manually.
Therefore copy your elf file and the fw_cortex_m4.sh script to the same folder in Linux running on the A7.
You can find fw_cortex_m4.sh in the M4 project of STM32CubeIDE, see picture below.
Next start the M4 with ./fw_cortex_m4.sh start.
./fw_cortex_m4.sh stop stops the M4.

[[File:STM32CubeIDE-M4-Start Script-Position.png]]

== Debugging with GDB (without IDE) ==
https://wiki.st.com/stm32mpu/wiki/GDB#Debug_Cortex-M4_firmware_with_GDB

== Debugging with trace output on Linux ==
https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Logging_in_production_mode

File:STM32CubeIDE-M4-Start Script-Position.png

2021-02-11T08:43:11Z

Renglbrecht:

File:STM32CubeIDE-Debug-Configuration-M4.jpg

2021-02-11T08:23:57Z

Renglbrecht:

File:STM32CubeIDE-Debug-Configuration-M4.png

2021-02-11T08:11:31Z

Renglbrecht: Renglbrecht uploaded a new version of File:STM32CubeIDE-Debug-Configuration-M4.png

Debugging M4 on STM32MP15xxxx

2021-02-10T15:31:50Z

Renglbrecht:

For general information about the STM32MP15xxxx pleas refer to the official [https://wiki.st.com/stm32mpu/wiki/Main_Page Wiki]. This page describes various ways to debug the M4 on STM32MP15xxxx from ST.

__TOC__

== Debugging modes ==
Production mode and Engineering mode are described [https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Introduction_to_boot_mode here] in the ST Wiki.
To enter Engineering mode with the Avenger96 read the chapter "Boot Mode" in the [https://wiki.dh-electronics.com/index.php/Avenger96#Documentation Getting started guide] and look for "NoBoot".

== Debugging with STM32CubeIDE ==
Debugging for both modes is also described in the ST wiki [https://wiki.st.com/stm32mpu/wiki/STM32CubeIDE#Arm-C2-AE_Cortex-C2-AE-M_debug_on_STM32_MPU_device here].

=== Without console or lan connection ===
If you have no console or lan connection STM32CubeIDE don't let you start the debugging session.
In this case it is possible to manually start th M4 on the target and start the debugging session with "thruJTAG/SWD (Engineering mode)".
Therefor go to:
# Debug Configuration
# Then to the Startup tab
# Doppleclick your .elf file in "Load Image and Symbols"
# Uncheck "Download"

== Debugging with GDB (without IDE) ==
https://wiki.st.com/stm32mpu/wiki/GDB#Debug_Cortex-M4_firmware_with_GDB

== Debugging with trace output on Linux ==
https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Logging_in_production_mode

Debugging M4 on STM32MP15xxxx

2021-02-10T15:23:37Z

Renglbrecht:

For general information about the STM32MP15xxxx pleas refer to the official [https://wiki.st.com/stm32mpu/wiki/Main_Page Wiki]. This page describes various ways to debug the M4 on STM32MP15xxxx from ST.

__TOC__

== Debugging modes ==
Production mode and Engineering mode are described [https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Introduction_to_boot_mode here] in the ST Wiki.
To enter Engineering mode with the Avenger96 read the chapter "Boot Mode" in the [https://wiki.dh-electronics.com/index.php/Avenger96#Documentation Getting started guide] and look for "NoBoot".

== Debugging with STM32CubeIDE ==
Debugging for both modes is also described in the ST wiki [https://wiki.st.com/stm32mpu/wiki/STM32CubeIDE#Arm-C2-AE_Cortex-C2-AE-M_debug_on_STM32_MPU_device here].

=== Without console or lan connection ===
If you have no console or lan connection STM32CubeIDE don't let you start the debugging session.
In this case it is possible to manually start th M4 on the target and start the debugging session with "thruJTAG/SWD (Engineering mode)".
Therefor go to:
# Debug Configuration
# Then to the Startup tab
# Doppleclick your .elf file in "Load Image and Symbols"
# Uncheck "Download"

[[File:STM32CubeIDE-Debug-Configuration-M4.png]]

== Debugging with GDB (without IDE) ==
https://wiki.st.com/stm32mpu/wiki/GDB#Debug_Cortex-M4_firmware_with_GDB

== Debugging with trace output on Linux ==
https://wiki.st.com/stm32mpu/wiki/STM32CubeMP1_Package#Logging_in_production_mode

File:STM32CubeIDE-Debug-Configuration-M4.png

2021-02-10T15:09:27Z

Renglbrecht:

Debugging M4 on STM32MP15xxxx

2021-02-10T14:50:28Z

Renglbrecht:

Debugging M4 on STM32MP15xxxx

2021-02-10T12:34:33Z

Renglbrecht:

Debugging M4 on STM32MP15xxxx

2021-02-09T12:53:16Z

Renglbrecht: Created page with "For general information about the STM32MP15xxxx pleas refer to the official [https://wiki.st.com/stm32mpu/wiki/Main_Page Wiki]. This page describes various ways to debug the M..."

For general information about the STM32MP15xxxx pleas refer to the official [https://wiki.st.com/stm32mpu/wiki/Main_Page Wiki]. This page describes various ways to debug the M4 on STM32MP15xxxx from ST.

__TOC__

== Debugging in Engineering mode ==

== Debugging in Production mode ==

== Debugging with trace output on Linux ==