DevGuide/GDB OpenOCD Debug - Revision history

NeoFromMatrix at 10:31, 14 April 2015

2015-04-14T10:31:41Z

← Older revision		Revision as of 04:31, 14 April 2015
Line 71:		Line 71:
	=== Useful GDB commands ===		=== Useful GDB commands ===

	Also look at [DevGuide/GDB_OpenOCD_Debug#GDB] for general GDB commands		Also look at [[DevGuide/GDB_OpenOCD_Debug#GDB]] for general GDB commands

	To display some commands for BMP		To display some commands for BMP

NeoFromMatrix at 10:29, 14 April 2015

2015-04-14T10:29:59Z

← Older revision		Revision as of 04:29, 14 April 2015
Line 1:		Line 1:
	== ~~Debugging with~~ GDB ~~over JTAG~~ ==		== GDB ==

	==~~= Procedure =~~==		Commands can often be issued without typing the entire command. Here are some commonly used commands; many of them can be invoked using only the first letter:
			(gdb) quit – exit the debugger
			(gdb) file – load an executable file
			(gdb) break line-number/function name -- Set a break-point on a line/at start of function
			(gdb) run <args> -- start running the program; if there are command-line arguments, put them after the run invocation
			(gdb) cont -- continue running, after a break
			(gdb) next -- Next program line (step over function calls)
			(gdb) step -- Step into function calls.
			(gdb) finish - Step out of the present function
			(gdb) print expression -- Show value of a variable or expression
			(gdb) list – List 10 lines of the program being debugged. The sixth line is the preset statement. Subsequent, consecutive entry of list will list the next 10 lines.
			(gdb) where – obtain a backtrace showing all function calls before the current statement
			(gdb) up – Move to the function that called the present function. Useful if your program crashes in a library function; use up to get to the last function call in your program
			(gdb) down – Reverses the action of up
			(gdb) delete – Removes breakpoint by number (see example following). If no number, all deleted.
			(gdb) kill – Terminates the program.

			== GDB - OpenOCD - Floss JTAG ==

			Connecting OpenOCD to a Floss JTAG (Lisa/L in this case) an GDB to OpenOCD.

	# Start openocd in a new shell since this process needs to remain running.		# Start openocd in a new shell since this process needs to remain running.
Line 35:		Line 54:
	#:<pre>continue</pre>		#:<pre>continue</pre>

	== Black Magic Probe ==		== Black Magic Probe specific ==

	# Start GDB for arm		# Start GDB for arm
	#: Open GDB with the correct binary file		#: Open GDB with the correct binary file
Line 49:		Line 69:
	# Happy Debugging!		# Happy Debugging!

	-~~this information was merged from~~:		=== Useful GDB commands ===
	--~~ht tp~~ :~~// sourceforge. net/apps/mediawiki/blackmagicdebug/index.php?title=Main_Page~~
	--~~[[JTAG]]~~		Also look at [DevGuide/GDB_OpenOCD_Debug#GDB] for general GDB commands

			To display some commands for BMP
			monitor help
			example output fot STM32F4
			<pre>
			General commands:
			version -- Display firmware version info
			help -- Display help for monitor commands
			jtag_scan -- Scan JTAG chain for devices
			swdp_scan -- Scan SW-DP for devices
			targets -- Display list of available targets
			morse -- Display morse error message
			connect_srst -- Configure connect under SRST: (enable\|disable)
			ARM Cortex-M specific commands:
			vector_catch -- Catch exception vectors
			STM32F4 specific commands:
			erase_mass -- Erase entire flash memory
			option -- Manipulate option bytes

			</pre>

	~~=== Useful commands ===~~
	* We probably want to ignore the interrupt calls for the moment so we can step through the code as it's being called. Note that we don't always want to do this. (STM32 command only)		* We probably want to ignore the interrupt calls for the moment so we can step through the code as it's being called. Note that we don't always want to do this. (STM32 command only)
	*:<pre>monitor cortex_m3 maskisr on</pre>		*:<pre>monitor cortex_m3 maskisr on</pre>
Line 65:		Line 104:
	*:<pre>set mem inaccessible-by-default off</pre>		*:<pre>set mem inaccessible-by-default off</pre>

	~~Commands can often be issued without typing the entire command~~. ~~Here are some commonly used~~ commands~~; many of them~~ can be ~~invoked using only the first letter:~~		=== .gdbinit for BMP ===
	~~(gdb) quit – exit the debugger~~
	~~(gdb) file – load an executable file~~		The standard commands like setting the ttyACM0 port, searching for targets and attaching one can be automated. Either with a ".gdbinit" file or if your work with Eclipse, there is a box at Debug configutations/Startup.
	~~(gdb) break line~~-~~number/function name~~ -- ~~Set a break~~-~~point on a line/at start of function~~
	~~(gdb) run~~ <~~args~~> ~~-- start running the program; if there are command-line arguments, put them after the run invocation~~		One Example from [http://docs.armstrap.org/en/latest/getting-started-eclipse-development-tools.html\| armstrap]
	~~(gdb) cont~~ -~~- continue running, after a break~~
	~~(gdb) next -- Next program line (step over function calls)~~		<pre>
	~~(gdb) step -- Step into function calls.~~		target extended-remote /dev/ttyACM0
	~~(gdb) finish - Step out of the present function~~		mon swdp_scan
	~~(gdb) print expression~~ -- ~~Show value of a variable or expression~~		attach 1
	~~(gdb) list – List 10 lines of the program being debugged. The sixth line is the preset statement. Subsequent, consecutive entry of list will list the next 10 lines.~~		monitor vector_catch disable hard
	~~(gdb) where – obtain a backtrace showing all function calls before the current statement~~		set mem inaccessible-by-default off
	~~(gdb) up – Move to the function that called the present function. Useful if your program crashes in a library function; use up to get to the last function call in your program~~		set print pretty
	~~(gdb) down – Reverses the action of up~~		</pre>
	~~(gdb) delete – Removes breakpoint by number (see example following). If no number, all deleted.~~
	~~(gdb) kill – Terminates the program.~~

	=== Setting up .gdbinit for BMP and gdb-regview ===		=== Setting up .gdbinit for BMP and gdb-regview ===

	If you use gdb just with a BMP, you can set some initialization commands in ~/.gdbinit that will run when gdb is started, improving workflow.		If you use gdb just with a BMP, you can set some initialization commands in ~/.gdbinit that will run when gdb is started, improving workflow.

Line 105:		Line 143:
	<pre>(gdb) regview show ADC_CR1</pre>		<pre>(gdb) regview show ADC_CR1</pre>

	=== ~~Easily load~~ new ~~binaries~~ from ~~inside~~ gdb with BMP ===		=== Load new binary from gdb with BMP ===

	It is also easy to rebuild and reload a program from inside gdb. Calling make from the gdb command line will call make in your current directory:		It is also easy to rebuild and reload a program from inside gdb. Calling make from the gdb command line will call make in your current directory:
	<pre>(gdb) make</pre>		<pre>(gdb) make</pre>

NeoFromMatrix: NeoFromMatrix moved page DevGuide/GDB OOCD Debug to DevGuide/GDB OpenOCD Debug

2015-04-02T19:52:13Z

NeoFromMatrix moved page DevGuide/GDB OOCD Debug to DevGuide/GDB OpenOCD Debug

← Older revision	Revision as of 13:52, 2 April 2015
(No difference)

NeoFromMatrix: NeoFromMatrix moved page DevGuide/GDB-Debug to DevGuide/GDB OOCD Debug

2015-04-02T19:51:27Z

NeoFromMatrix moved page DevGuide/GDB-Debug to DevGuide/GDB OOCD Debug

← Older revision	Revision as of 13:51, 2 April 2015
(No difference)

NeoFromMatrix at 21:16, 30 March 2015

2015-03-30T21:16:51Z

← Older revision		Revision as of 15:16, 30 March 2015
Line 1:		Line 1:
	~~===JTAG Adapters===~~

	~~'''TODO: Merge to [[Programming_adapter]]'''~~

	~~There are multiple Paparazzi-compatible devices available that support JTAG.~~

	~~====[[Programming_adapter#FLOSS_JTAG\|FLOSS JTAG]]====~~

	~~The FLOSS JTAG is based on an FTDI chip that allows two simultaneous USB connections, which means that FLOSS JTAG allows JTAG and UART/COM connections.~~

	Let's take a look at upper side of the board. It contains JTAG connector (which is connected on photo) and two sets of RX/TX LEDs for JTAG and UART/COM interface separately. The JTAG connector is 2x5 pins, 0.05-inch pitch, and is compatible with the Samtec FFSD-05-D-06.00-01-N-RW-R ribbon cable.

	~~[[Image:Jtag-up.jpg]]~~

	~~On the other side of the board there is 4 pin UART/COM connector, which contains (from top to bottom in the image below): Ground (black), RX (orange), TX (yellow), and +5V (red)~~

	~~[[Image:Jtag-down.jpg]]~~

	Usage of board is pretty simple: JTAG can be used to upload firmware into the board and/or repair board with broken bootloader, and UART/COM interfaced can be used to make "COM port style" connection to the board. COM connection can be used for example for telemetry debug.

	~~More info available on the [http://randomprojects.org/wiki/Floss-JTAG randomprojects.org wiki].~~

	~~====[[Programming_adapter#Black_Magic_Probe\|Black Magic Probe]]====~~

	~~[[Image:BMPM_1_top.jpg\|500x500px]][[Image:BMPM_1_bottom.jpg\|500x500px]]~~

	~~Some additional info about the Black Magic Probe is available at the [http://www.blacksphere.co.nz/main/blackmagic Black Sphere Technology website].~~

	~~To use Black Magic Probe instead of FLOSS-JTAG or Luftboot for firmware flashing, append the following string to the upload command:~~

	~~On Linux:~~
	~~FLASH_MODE=JTAG_BMP BMP_PORT=/dev/ttyACM0~~
	~~On Mac OS:~~
	~~FLASH_MODE=JTAG_BMP BMP_PORT=/dev/cu.usbmodem<serial>~~

	~~To make this the default flash method add this in the airframe file firmware section:~~
	~~<configure name="FLASH_MODE" value="JTAG_BMP"/>~~
	~~<configure name="BMP_PORT" value="/dev/ttyACM0"/>~~

	~~See the [[FirmwareFlashing]] page for other methods.~~


	~~==== FT2232H Mini Module ====~~

	~~Use ftdi prog to change the Description String into: FLOSS-JTAG. <br/>~~
	~~More information for this board at [[Serial_Adapter]].~~
	~~[[File:AlternativeFlossJtag.png\|300px]]~~


	== Debugging with GDB over JTAG ==		== Debugging with GDB over JTAG ==

NeoFromMatrix at 20:44, 30 March 2015

2015-03-30T20:44:51Z

@@ Line 1: / Line 1: @@
-== JTAG adapters ==
+===JTAG Adapters===
-Recently some new [[JTAG]] adapters that use the FTDI2232 USB-parallel converter were introduced through OpenOCD (you can try your Wiggler with that, too). USB JTAG adapters include Floss-JTAG, Olimex or Amontec and also fine with Windows (Yagarto).
 == Debugging with GDB over JTAG ==
 === Procedure ===
 # Start openocd in a new shell since this process needs to remain running.
 #* STM targets
@@ Line 38: / Line 84: @@
 #:<pre>continue</pre>
-=== Black Magic Probe ===
+== Black Magic Probe ==
 # Start GDB for arm
 #: Open GDB with the correct binary file

NeoFromMatrix: NeoFromMatrix moved page DevGuide/JTAG-Debug to DevGuide/GDB-Debug: also SWD and not just JTAG compatible, GDB covers the text on the page nice

2015-03-30T19:47:35Z

NeoFromMatrix moved page DevGuide/JTAG-Debug to DevGuide/GDB-Debug: also SWD and not just JTAG compatible, GDB covers the text on the page nice

← Older revision	Revision as of 13:47, 30 March 2015
(No difference)

BartSlinger: swdp_scan inead of jtag_scan for lisa/s

2015-01-11T19:31:24Z

swdp_scan inead of jtag_scan for lisa/s

← Older revision		Revision as of 13:31, 11 January 2015
Line 46:		Line 46:
	#: Probe via JTAG to get a list of devices:		#: Probe via JTAG to get a list of devices:
	#:<pre>mon jtag_scan</pre>		#:<pre>mon jtag_scan</pre>
			#: (for [[Lisa/S]], use ''swdp_scan'' instead of ''jtag_scan'')
			#:
	#: Attach to a device:		#: Attach to a device:
	#:<pre>attach 1</pre>		#:<pre>attach 1</pre>

Olri: /* Procedure */

2013-02-13T15:51:42Z

Procedure

← Older revision		Revision as of 09:51, 13 February 2013
Line 17:		Line 17:
	#: To connect to the LPC based board via OLIMEX ARM-USB-OCD-H dongle run the command:		#: To connect to the LPC based board via OLIMEX ARM-USB-OCD-H dongle run the command:
	#:<pre>openocd -f interface/olimex-arm-usb-ocd-h.cfg -f target/lpc2148.cfg</pre>		#:<pre>openocd -f interface/olimex-arm-usb-ocd-h.cfg -f target/lpc2148.cfg</pre>

			# Compiler Debug Options
			#: On LPC target build your ap file with debug options. See https://github.com/elemhsb/paparazzi/blob/v4.0/conf/Makefile.lpc21 .

	# 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.
Line 22:		Line 25:
	#:<pre>/opt/paparazzi/arm-multilib/bin/arm-none-eabi-gdb var/<airframe>/ap/ap.elf</pre>		#:<pre>/opt/paparazzi/arm-multilib/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.

	# Now connect GDB to the board		# Now connect GDB to the board
	#:<pre>target remote localhost:3333</pre>		#:<pre>target remote localhost:3333</pre>

Olri: /* Procedure */

2013-02-13T15:18:11Z

Procedure

← Older revision		Revision as of 09:18, 13 February 2013
Line 7:		Line 7:
	=== Procedure ===		=== Procedure ===
	# Start openocd in a new shell since this process needs to remain running.		# Start openocd in a new shell since this process needs to remain running.
			#* STM targets
	#: To connect to the Lisa/L board run the command		#: To connect to 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>
	#: To connect to the Lisa/M board via FLOSS-JTAG run the command:		#: To connect to the Lisa/M board via FLOSS-JTAG 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>
			#* NXP LPC targets
			#: To connect to the LPC based board via OLIMEX ARM-USB-OCD dongle run the command:
			#:<pre>openocd -f interface/olimex-arm-usb-ocd.cfg -f target/lpc2148.cfg</pre>
			#: To connect to the LPC based board via OLIMEX ARM-USB-OCD-H dongle run the command:
			#:<pre>openocd -f interface/olimex-arm-usb-ocd-h.cfg -f target/lpc2148.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.