u-boot/doc/develop/index.rst
Alexander Dahl 636480e4e7 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>
2024-06-30 13:58:31 +02:00

101 lines
1.1 KiB
ReStructuredText

.. SPDX-License-Identifier: GPL-2.0+
Develop U-Boot
==============
General
-------
.. toctree::
:maxdepth: 1
board_best_practices
codingstyle
designprinciples
docstyle
patman
process
release_cycle
security
sending_patches
system_configuration
ide_integration
Implementation
--------------
.. toctree::
:maxdepth: 1
directories
bloblist
bootstd
ci_testing
commands
config_binding
cyclic
devicetree/index
distro
driver-model/index
environment
expo
cedit
event
global_data
logging
makefiles
menus
printf
smbios
spl
falcon
uefi/index
vbe
version
Debugging
---------
.. toctree::
:maxdepth: 1
crash_dumps
gdb
trace
Packaging
---------
.. toctree::
:maxdepth: 1
package/index
Testing
-------
.. toctree::
:maxdepth: 1
testing
py_testing
tests_writing
tests_sandbox
Refactoring
-----------
.. toctree::
:maxdepth: 1
checkpatch
coccinelle
qconfig
Code quality
------------
.. toctree::
:maxdepth: 1
python_cq