Debugging M4 on STM32MP15xxxx - Revision history

Renglbrecht at 13:03, 22 November 2021

2021-11-22T13:03:27Z

@@ Line 12: / Line 12: @@
 === Without console or lan connection ===
-If you have no console or lan connection STM32CubeIDE don't let you start the debugging session.
+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)".
 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.
@@ Line 31: / Line 22: @@
 [[File:STM32CubeIDE-M4-Start Script-Position.png|200px]]
 == Debugging with GDB (without IDE) ==

Renglbrecht at 10:36, 7 July 2021

2021-07-07T10:36:21Z

← Older revision		Revision as of 12:36, 7 July 2021
Line 19:		Line 19:
	# Double click your elf file in "Load Image and Symbols"		# Double click your elf file in "Load Image and Symbols"
	# Uncheck "Download"		# Uncheck "Download"
			# Then in "Initialization Commands" remove "monitor reset" and "monitor halt"

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

Renglbrecht: Typo corrected and picture sizes adjusted.

2021-06-30T06:55:35Z

Typo corrected and picture sizes adjusted.

← Older revision		Revision as of 08:55, 30 June 2021
Line 13:		Line 13:
	=== Without console or lan connection ===		=== Without console or lan connection ===
	If you have no console or lan connection STM32CubeIDE don't let you start the debugging session.		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)".		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:		Therefor go to:
	# Debug Configuration		# Debug Configuration
Line 20:		Line 20:
	# Uncheck "Download"		# Uncheck "Download"

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

	As next step we have to start the M4 manually.		As next step we have to start the M4 manually.
Line 29:		Line 29:
	To stop the M4 run <code>./fw_cortex_m4.sh stop</code>.		To stop the M4 run <code>./fw_cortex_m4.sh stop</code>.

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

	== Debugging with GDB (without IDE) ==		== Debugging with GDB (without IDE) ==

Renglbrecht at 08:54, 11 February 2021

2021-02-11T08:54:44Z

← Older revision		Revision as of 10:54, 11 February 2021
Line 23:		Line 23:

	As next step we have to start the M4 manually.		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.		Therefore copy your elf file and the <code>fw_cortex_m4.sh</code> script to the same folder in Linux running on the A7.
	Next start the M4 with ./fw_cortex_m4.sh start.		You can find <code>fw_cortex_m4.sh</code> in the M4 project of STM32CubeIDE, see picture below.
	./fw_cortex_m4.sh stop ~~stops the M4~~.		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]]		[[File:STM32CubeIDE-M4-Start Script-Position.png]]

Renglbrecht at 08:45, 11 February 2021

2021-02-11T08:45:29Z

← Older revision		Revision as of 10:45, 11 February 2021
Line 1:		Line 1:
	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.		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
	# ~~Doppleclick~~ your .elf file in "Load Image and Symbols"		# 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) ==

Renglbrecht at 15:31, 10 February 2021

2021-02-10T15:31:50Z

← Older revision		Revision as of 17:31, 10 February 2021
Line 19:		Line 19:
	# Doppleclick your .elf file in "Load Image and Symbols"		# Doppleclick your .elf file in "Load Image and Symbols"
	# Uncheck "Download"		# Uncheck "Download"

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

	== Debugging with GDB (without IDE) ==		== Debugging with GDB (without IDE) ==

Renglbrecht at 15:23, 10 February 2021

2021-02-10T15:23:37Z

← Older revision		Revision as of 17:23, 10 February 2021
Line 20:		Line 20:
	# Uncheck "Download"		# Uncheck "Download"

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

	== Debugging with GDB (without IDE) ==		== Debugging with GDB (without IDE) ==

Renglbrecht at 14:50, 10 February 2021

2021-02-10T14:50:28Z

@@ Line 10: / Line 10: @@
 == 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 with GDB (without IDE) ==
@@ Line 15: / Line 25: @@
 == Debugging with trace output on Linux ==

Renglbrecht at 12:34, 10 February 2021

2021-02-10T12:34:33Z

← Older revision		Revision as of 14:34, 10 February 2021
Line 3:		Line 3:
	__TOC__		__TOC__

	~~== Debugging in Engineering mode ==~~

	== Debugging in ~~Production~~ mode ==		== 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].

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

	== Debugging with trace output on Linux ==		== Debugging with trace output on Linux ==

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..."

2021-02-09T12:53:16Z

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..."

New page

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 ==