Dev/Debugging - Revision history

NeoFromMatrix: delete this page

2014-04-21T16:34:22Z

delete this page

← Older revision		Revision as of 10:34, 21 April 2014
Line 6:		Line 6:


	[[Category:Software]] [[Category:Developer_Documentation]]		[[Category:Software]] [[Category:Developer_Documentation]] [[Category:DeleteMe]]

Flixr: moved gdb/jtag content to DevGuide/JTAG-Debug

2012-02-12T13:35:44Z

moved gdb/jtag content to DevGuide/JTAG-Debug

@@ Line 1: / Line 1: @@
-= Introduction =
+== GDB via JTAG ==
-GDB can be used for debugging the code on the boards. Here are a couple of words on [[JTAG]] itself and [[DevGuide/JTAG-Debug#JTAG_debugging|debugging process]].
+GDB and JTAG can be used for debugging the code directly on the boards. Here are a couple of words on [[JTAG]] itself and the [[DevGuide/JTAG-Debug|debugging process]].
-= Procedure =
+== Test programs ==
-# Start openocd in a new shell since this process needs to remain running.
+ :-)
 [[Category:Software]] [[Category:Developer_Documentation]]

Esden at 10:34, 12 February 2012

2012-02-12T10:34:51Z

← Older revision		Revision as of 04:34, 12 February 2012
Line 44:		Line 44:
	* Show (eXamine) the value of the 9 bytes hardware register at address 0x40005800 and show them in hex format:		* Show (eXamine) the value of the 9 bytes hardware register at address 0x40005800 and show them in hex format:
	*:<pre>x/9x 0x40005800</pre>		*:<pre>x/9x 0x40005800</pre>
			* In some cases you may not be able to access some memory areas in the mcu, in that case you should try:
			*:<pre>set mem inaccessible-by-default off</pre>

	[[Category:Software]] [[Category:Developer_Documentation]]		[[Category:Software]] [[Category:Developer_Documentation]]

P0rc0 r0ss0: /* Procedure */

2012-02-12T08:57:16Z

Procedure

← Older revision		Revision as of 02:57, 12 February 2012
Line 10:		Line 10:
	#: To program the Lisa/M board via JTAG change dir to "<paparazzi root>/arm-multilib/share/openocd/scripts", and run the command:		#: To program the Lisa/M board via JTAG change dir to "<paparazzi root>/arm-multilib/share/openocd/scripts", and run the command:
	#:<pre>openocd -f interface/flossjtag.cfg -f board/lisa-l.cfg</pre>		#:<pre>openocd -f interface/flossjtag.cfg -f board/lisa-l.cfg</pre>

			''NOTICE:'' For lisa/m boards file lisa-m.cfg should look like:
			<pre># the Lost Illusions Serendipitous Autopilot
			# http://paparazzi.enac.fr/wiki/Lisa
			# Work-area size (RAM size) = 64kB for STM32F103RB device
			set WORKAREASIZE 0xFA00
			source [find target/stm32f1x.cfg]</pre>
	# Start GDB with an argument of the elf file created and uploaded to the board.		# Start GDB with an argument of the elf file created and uploaded to the board.
	#: If you programmed with the ap target then the command would be along the lines of		#: If you programmed with the ap target then the command would be along the lines of

P0rc0 r0ss0: /* Introduction */

2011-12-04T20:33:00Z

Introduction

← Older revision		Revision as of 14:33, 4 December 2011
Line 1:		Line 1:
	= Introduction =		= Introduction =
	GDB can be used for debugging the code on the boards. Here are a couple of words on [[JTAG]] itself and [[DevGuide/JTAG-Debug#JTAG_debugging\|debugging ~~itself~~]].		GDB can be used for debugging the code on the boards. Here are a couple of words on [[JTAG]] itself and [[DevGuide/JTAG-Debug#JTAG_debugging\|debugging process]].

	= Procedure =		= Procedure =

P0rc0 r0ss0: /* Introduction */

2011-12-04T20:32:47Z

Introduction

← Older revision		Revision as of 14:32, 4 December 2011
Line 1:		Line 1:
	= Introduction =		= Introduction =
	GDB can be used for debugging the code on the boards. Here are a couple of words ~~concerning~~ [[JTAG]] debugging ~~interface~~.		GDB can be used for debugging the code on the boards. Here are a couple of words on [[JTAG]] itself and [[DevGuide/JTAG-Debug#JTAG_debugging\|debugging itself]].

	= Procedure =		= Procedure =

P0rc0 r0ss0: /* Introduction */

2011-12-04T20:27:48Z

Introduction

@@ Line 1: / Line 1: @@
 = Introduction =
-GDB can be used for debugging the code on the boards.
+GDB can be used for debugging the code on the boards. Here are a couple of words concerning [[JTAG]] debugging interface.
 = Procedure =

P0rc0 r0ss0: /* Introduction */

2011-12-02T20:38:57Z

Introduction

@@ Line 1: / Line 1: @@
 = Introduction =
 GDB can be used for debugging the code on the boards.
 = Procedure =

Cdewagter at 13:38, 24 November 2011

2011-11-24T13:38:56Z

← Older revision		Revision as of 07:38, 24 November 2011
Line 33:		Line 33:
	* A stack trace can be printed with the command		* A stack trace can be printed with the command
	*:<pre>bt</pre>		*:<pre>bt</pre>
			* show the variable of a variable
			*:<pre>print i2c1.status</pre>
			* Show (eXamine) the value of the 9 bytes hardware register at address 0x40005800 and show them in hex format:
			*:<pre>x/9x 0x40005800</pre>

	[[Category:Software]] [[Category:Developer_Documentation]]		[[Category:Software]] [[Category:Developer_Documentation]]

Flixr: /* Procedure */

2011-11-24T12:20:06Z

Procedure

← Older revision		Revision as of 06:20, 24 November 2011
Line 6:		Line 6:
	#: To program the Lisa/L board run the command		#: To program the Lisa/L board run the command
	#:<pre>openocd -f interface/lisa-l.cfg -f board/lisa-l.cfg</pre>		#:<pre>openocd -f interface/lisa-l.cfg -f board/lisa-l.cfg</pre>
	#:or if your path is not set properly		#:or if you are still using the old paparazzi-stm32 package and your path is not set properly
	#:<pre>cd /opt/paparazzi/stm32/share/openocd/scripts/; /opt/paparazzi/stm32/bin/openocd -f interface/lisa-l.cfg -f board/lisa-l.cfg</pre>		#:<pre>cd /opt/paparazzi/stm32/share/openocd/scripts/; /opt/paparazzi/stm32/bin/openocd -f interface/lisa-l.cfg -f board/lisa-l.cfg</pre>
	#: To program the Lisa/M board via JTAG change dir to "<paparazzi root>/arm-multilib/share/openocd/scripts", and run the command:		#: To program the Lisa/M board via JTAG change dir to "<paparazzi root>/arm-multilib/share/openocd/scripts", and run the command:
Line 13:		Line 13:
	#: If you programmed with the ap target then the command would be along the lines of		#: If you programmed with the ap target then the command would be along the lines of
	#:<pre>arm-none-eabi-gdb var/<airframe>/ap/ap.elf</pre>		#:<pre>arm-none-eabi-gdb var/<airframe>/ap/ap.elf</pre>
	#:or		#:or (if you are using the old paparazzi-stm32 package)
	#:<pre>/opt/paparazzi/stm32/bin/arm-none-eabi-gdb ./var/<airframe>/ap/ap.elf</pre>		#:<pre>/opt/paparazzi/stm32/bin/arm-none-eabi-gdb ./var/<airframe>/ap/ap.elf</pre>
	#: Replace <airframe> with the name of the airframe that has been built.		#: Replace <airframe> with the name of the airframe that has been built.