JTAG - Revision history

JulienB: /* Debugging the Kernel with OpenOCD and GDB on APF28 */

2016-06-03T16:23:22Z

‎Debugging the Kernel with OpenOCD and GDB on APF28

2016-06-03T15:23:56Z

‎Debugging the Kernel with OpenOCD and GDB on APF28

2016-06-03T15:20:03Z

‎Debugging the Kernel with OpenOCD and GDB on APF28

2016-06-03T15:11:14Z

‎Install and configure OpenOCD to work with a jtagkey

2016-06-03T15:10:20Z

‎Building a JTAG connector for APF27Dev board

2016-06-03T15:08:49Z

2014-10-07T10:26:18Z

‎Debugging the Kernel with OpenOCD and GDB on APF28

2014-10-07T10:15:28Z

‎Debugging the Kernel with OpenOCD and GDB on APF28

2014-10-07T10:14:47Z

‎Debugging the Kernel with OpenOCD and GDB on APF28

2014-10-07T10:13:04Z

‎Debugging the Kernel with OpenOCD and GDB on APF28

@@ Line 602: / Line 602: @@
 Hint: in order to get back to start_armboot(), you don't have to reset the board. Disconnect GDB from OpenOCD, then in OpenOCD telnet window, set the program counter back to the start address of start_armboot(), and then re-attach GDB.
-== Debugging the Kernel with OpenOCD and GDB on APF28 ==
+== Debugging the Kernel with OpenOCD and GDB on APF28/APF6 ==
 {{Note|Openocd version 0.8.0 (default Debian version (apt-get install openocd)) and Linux Kernel 3.16 are used here.}}
-The APF28Dev has a standard JTAG connector so just connect your JTAG probe on it.
+The [[APF28Dev]]/[[APF6Dev]] has a standard JTAG connector so just connect your JTAG probe on it.
 Compile the kernel with debug symbols. To do so:

@@ Line 603: / Line 603: @@
 == Debugging the Kernel with OpenOCD and GDB on APF28 ==
-{{Note|Openocd version 0.8.0 and Linux Kernel 3.16 are used here.}}
+{{Note|Openocd version 0.8.0 (default Debian version (apt-get install openocd)) and Linux Kernel 3.16 are used here.}}
 The APF28Dev has a standard JTAG connector so just connect your JTAG probe on it.

@@ Line 605: / Line 605: @@
 {{Note|Openocd version 0.8.0 and Linux Kernel 3.16 are used here.}}
-The APF28 already has a JTAG connector so just connect your JTAG probe on it.
+The APF28Dev has a standard JTAG connector so just connect your JTAG probe on it.
-Compile the kernel with debug symbols. To do so, in the linux menuconfig: Kernel hacking --> Compile-time checks and compiler options --> [*] Compile the kernel with debug info.
+Compile the kernel with debug symbols. To do so:
-Now create a new file apf28-openocd.cfg with the following content:
+Now create a new file ''apf28-openocd.cfg'' with the following content:
 <pre>

@@ Line 83: / Line 83: @@
 </pre>
-== Install and configure OpenOCD to work with a jtagkey==
+== Install and configure OpenOCD to work with an Amontec JTAGkey==
 Yet to be done. First it requires 2 libraries libusb and libftdi (libftd2xxx from ftdi).

@@ Line 7: / Line 7: @@
 == Building a JTAG connector for APF27Dev board ==
-First you need a decent JTAG connector. The description below produces a 20-pin male JTAG connectior with standard ARM pinout.
+First you need a decent JTAG connector (the APF27Dev has a non standard JTAG port).
 List of material and part numbers at [http://www.conrad.ch Conrad]:

@@ Line 3: / Line 3: @@
 JTAG interface is useful in debugging some complicated issues with U-Boot, like [http://txlab.wordpress.com/2009/04/25/big-endian-for-imx27-found-the-problem/ this example here], during Linux kernel portage or for FPGA debugging with ChipScope.
-{{Note|However, most of the usual debugging functionalities are provided from within Armadeus BSP without the need for a JTAG interface. You won't also need JTAG to reflash an Armadeus board, even if you bricked U-Boot; serial connection should be enough (see [[Bootstrap]]).}}
+{{Note|However, most of the usual debugging functionalities are provided from within Armadeus BSP without the need for a JTAG interface. You won't also need JTAG to reflash an Armadeus board, even if you bricked U-Boot; serial connection should be enough (see [[Bootstrap]]). For debugging Linux applications directly on the APF you also can do without JTAG, see [[GDB]]}}
 == Building a JTAG connector for APF27Dev board ==

@@ Line 744: / Line 744: @@
 </pre>
-To resume and still having the gdb prompt:
+To resume and still have the gdb prompt:
 <pre>

@@ Line 702: / Line 702: @@
 </pre>
-To make a move of on step:
+To make a move of one step:
 <pre>

@@ Line 687: / Line 687: @@
 </pre>
-In another terminal, connect on your board via the debug interface. Logging and show the alarm date of the RTC:
+In another terminal, connect on your board via the debug interface. Log in and show the alarm date of the RTC:
 <pre>
 Welcome to Armadeus development platform !