Debugging M4 on STM32MP15xxxx: Difference between revisions
Renglbrecht (talk | contribs) No edit summary |
Renglbrecht (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
For general information about the STM32MP15xxxx | 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__ | __TOC__ | ||
| Line 9: | Line 9: | ||
== Debugging with STM32CubeIDE == | == 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]. | 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 === | === Without console or lan connection === | ||
| Line 17: | Line 17: | ||
# Debug Configuration | # Debug Configuration | ||
# Then to the Startup tab | # Then to the Startup tab | ||
# | # Double click your elf file in "Load Image and Symbols" | ||
# Uncheck "Download" | # 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) == | == Debugging with GDB (without IDE) == | ||
Revision as of 09:45, 11 February 2021
For general information about the STM32MP15xxxx please refer to the official Wiki. This page describes ways to debug the M4 on STM32MP15xxxx from ST.
Debugging modes
Production mode and Engineering mode are described here in the ST Wiki. To enter Engineering mode with the Avenger96 read the chapter "Boot Mode" in the Getting started guide and look for "NoBoot".
Debugging with STM32CubeIDE
Debugging for both modes is also described in the ST wiki 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"
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.
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
