From 1df2a13cc32dee0dfb6d5b4867ba1eaeb47afc5e Mon Sep 17 00:00:00 2001 From: Randy Mackay Date: Tue, 11 Feb 2025 20:46:06 +0900 Subject: [PATCH] Dev: debugging on stm32 gets vimdrones debugger --- .../docs/debugging-with-gdb-on-stm32.rst | 24 ++++++++----------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/dev/source/docs/debugging-with-gdb-on-stm32.rst b/dev/source/docs/debugging-with-gdb-on-stm32.rst index 1406c27063..9d9375f6df 100644 --- a/dev/source/docs/debugging-with-gdb-on-stm32.rst +++ b/dev/source/docs/debugging-with-gdb-on-stm32.rst @@ -9,23 +9,19 @@ This page describes how to setup GDB on Linux to debug issues on STM32. The spec Introduction ============ -GDB (the GNU Debugger) "allows you to see what is going on \`inside' +GDB (the GNU Debugger) allows you to see what is going on inside another program while it executes or what another program was doing at -the moment it crashed." which can be useful when investigating very -low-level failures with the STM32 (it cannot be used with the -APM1/APM2) +the moment it crashed which can be useful when investigating very +low-level failures with the STM32 This guide assumes that you have already successfully built the firmware -on your machine following the instructions for -:ref:`Windows `, -:ref:`Mac ` or -:ref:`Linux `. - -A `BlackMagic probe `__ or `ST-Link V2 JST debugger `__ is -also required. A BlackMagic probe can be purchased in the US from `Transition Robotics `__, -`1 Bit Squared `__ -or in NewZealand from -`Greenstage `__. +on your machine following the instructions for :ref:`Windows `, :ref:`Mac ` or :ref:`Linux `. + +One the the following debuggers is required: + +- `BlackMagic probe `__ (available from `1 Bit Squared `__) +- `ST-Link V2 JST debugger `__ +- `VM Probe `__ A small plug (`FTSH-105-04-L-DV `__) may be required to solder on to the JTAG port of the flight controller.