| commit | e276400e0ed81262bc6c1a195216d71eaf63ff1b | [log] [tgz] |
|---|---|---|
| author | Alexander Dahl <ada@thorsis.com> | Wed Jun 26 12:47:18 2024 +0200 |
| committer | Heinrich Schuchardt <heinrich.schuchardt@canonical.com> | Sun Jun 30 13:58:31 2024 +0200 |
| tree | 442d43287378579a6f8fff99ca6c0dfa4d6eab21 | |
| parent | 6ac346c52e64537539641f0c76bd1e3a534b3b22 [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>