aboutsummaryrefslogtreecommitdiff
path: root/doc/develop/index.rst
diff options
context:
space:
mode:
authorAlexander Dahl2024-06-26 12:47:18 +0200
committerHeinrich Schuchardt2024-06-30 13:58:31 +0200
commit636480e4e7088d05d7ff77af72ca00443c62b3e9 (patch)
tree442d43287378579a6f8fff99ca6c0dfa4d6eab21 /doc/develop/index.rst
parent43b6b577bceda5f75204352b3dc4f0613b14e7d4 (diff)
doc: develop: Add a general section on gdb usage
Mashed up from different sources linked below, including the now gone Wiki and doc/README.arm-relocation file. Tested on a custom board with AT91 SAMA5D2 SoC and Segger J-Link Base adapter. This is only generic advice here, the usage is not board specific. Some board docs have more specific instructions on using gdb with a particular board. Link: https://www.slideshare.net/slideshow/embedded-recipes-2019-introduction-to-jtag-debugging/177511981 Link: https://boundarydevices.com/debugging-using-segger-j-link-jtag/ Link: https://web.archive.org/web/20141224200032/http://www.denx.de/wiki/view/DULG/DebuggingUBoot Link: https://web.archive.org/web/20141206064148/http://www.denx.de/wiki/view/DULG/GDBScripts1 Suggested-by: Marek Vasut <marex@denx.de> Signed-off-by: Alexander Dahl <ada@thorsis.com> Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Diffstat (limited to 'doc/develop/index.rst')
-rw-r--r--doc/develop/index.rst1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/develop/index.rst b/doc/develop/index.rst
index f82e148b101..f9c4bf839ee 100644
--- a/doc/develop/index.rst
+++ b/doc/develop/index.rst
@@ -60,6 +60,7 @@ Debugging
:maxdepth: 1
crash_dumps
+ gdb
trace
Packaging