Repository : ssh://git@diktynna/doc

On branches: backup-redmine/2021-08-07,backup-redmine/2021-09-11,backup-redmine/2021-10-09,backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main

commit c9fd8a79d77d661b6f2b81564ef759c62048032f Author: Sven Eckelmann sven@narfation.org Date: Tue Jul 27 07:51:54 2021 +0000

doc: open-mesh/Kernel_debugging_over_JTAG

c9fd8a79d77d661b6f2b81564ef759c62048032f open-mesh/Kernel_debugging_over_JTAG.textile | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/open-mesh/Kernel_debugging_over_JTAG.textile b/open-mesh/Kernel_debugging_over_JTAG.textile index 838686d5..c3fe0b5f 100644 --- a/open-mesh/Kernel_debugging_over_JTAG.textile +++ b/open-mesh/Kernel_debugging_over_JTAG.textile @@ -18,7 +18,7 @@ Requirements: * On Chip Debugger for JTAG/SWD ** "OpenOCD":http://openocd.org/

-h2. Preparing an debug adapter board +h2. Preparing an debug adapter hardware

The connection between the debug adapter and the target board must established by connecting a couple of pins with each other. The color schema used here is from the "Sparkfun Bus Pirate cable":https://antibore.wordpress.com/2011/06/22/quick-reference-for-sparkfun-bus-p...

@@ -31,17 +31,17 @@ The debug and target board via at least following of the debug adapter hardware: * GND (common ground) * VTG (voltage reference)

-The adapter boards must then also be select in the OpenOCD configuration. +The adapter hardware must also be selected in the OpenOCD configuration.

-Only one adapter board must be attached. But some example configurations are shown as reference. +Only one adapter hardware must be attached. But some example configurations are shown as reference.

-h3. Bus Blaster adapter board +h3. Bus Blaster adapter hardware

The Bus Blaster v3 with the 20 pin header and the default buffer logic the usage of the pins already written next to header. Just make sure to leave the board in self powered (not closed 2 pin header)

!/attachments/download/943/jtag-busblaster.svg!

-The configuration of the adapter board and the target board is also straight forward since the release of OpenOCD 0.11 +The configuration of the adapter hardware and the target board is also straight forward since the release of OpenOCD 0.11

<pre><code class="diff"> cat > jtag_debug.cfg << "EOF" @@ -60,9 +60,9 @@ EOF </code></pre>

-h3. Raspberry PI (4 B) adapter board +h3. Raspberry PI (4 B) adapter hardware

-The Raspberry PI 4B can be used as a simple adapter board because there are plenty of GPIOs available and OpenOCD is able to control them directly. Only the correctly "raw GPIO number for each Pin":https://www.raspberrypi-spy.co.uk/2012/06/simple-guide-to-the-rpi-gpio-heade... has to be found. A good way to connect them (while keeping the SPI pins free for reflashing SPI chips) is: +The Raspberry PI 4B can be used as a simple adapter hardware because there are plenty of GPIOs available and OpenOCD is able to control them directly. Only the correctly "raw GPIO number for each Pin":https://www.raspberrypi-spy.co.uk/2012/06/simple-guide-to-the-rpi-gpio-heade... has to be found. A good way to connect them (while keeping the SPI pins free for reflashing SPI chips) is:

* GND: Pin 9 * TDO: GPIO17 (Pin 11) @@ -72,7 +72,7 @@ The Raspberry PI 4B can be used as a simple adapter board because there are plen

The hardest part is to find the "correct base of the GPIO controller and to set the speed settings":https://openwrt.org/toh/meraki/mr18/jtag

-The configuration of the adapter board and the target board is also possible since the release of OpenOCD 0.11 +The configuration of the adapter hardware and the target board is also possible since the release of OpenOCD 0.11

<pre><code class="diff"> cat > jtag_debug.cfg << "EOF" @@ -103,9 +103,9 @@ bindto 0.0.0.0 EOF </code></pre>

-h3. Bus Pirate adapter board +h3. Bus Pirate adapter hardware

-The Bus Pirate's SPI pins can also be used for JTAG. But it is an extremely slow debug adapter compared to the previously mentioned ones. For example a <code>flash read_bank 0 flash.img 0 65536</code> takes 35682s when using the 8devices lima as target board - for example, an Raspberry Pi 4B as debug adapter board will only need 2 minutes for the same operations. +The Bus Pirate's SPI pins can also be used for JTAG. But it is an extremely slow debug adapter compared to the previously mentioned ones. For example a <code>flash read_bank 0 flash.img 0 65536</code> takes 35682s when using the 8devices lima as target board - for example, an Raspberry Pi 4B as debug adapter hardware will only need 2 minutes for the same operations.

Just connect:

@@ -115,7 +115,7 @@ Just connect: * TCK: SCK * GND: GND

-The configuration of the adapter board and the target board is also straight forward since the release of OpenOCD 0.11 +The configuration of the adapter hardware and the target board is also straight forward since the release of OpenOCD 0.11

<pre><code class="diff"> cat > jtag_debug.cfg << "EOF"