aboutsummaryrefslogtreecommitdiff
path: root/doc/media
diff options
context:
space:
mode:
authorJason Kacines2023-08-03 01:29:22 -0500
committerHeinrich Schuchardt2023-08-09 08:41:52 +0200
commiteffe50854a6964b6cf0f30e2716bec052a770d10 (patch)
tree5bbead3fb2b5f96895972dd7eb23c48bdde07df3 /doc/media
parentef8336e2705fce2502383f25d68188c6b1f94dd0 (diff)
doc: board: ti: k3: Add a guide to debugging with OpenOCD
Bootloader debug usually tends to be a bit dicey prior to DDR and serial port getting active in the system. JTAG typically remains the only practical debug option during the initial bringup. OpenOCD is one of the most popular environment for providing debug capability via a GDB compatible interface for developers to work with. Debugging U-Boot and bootloaders on K3 platform does have a bit of tribal knowledge that is better documented in our common platform documentation. Signed-off-by: Jason Kacines <j-kacines@ti.com> Signed-off-by: Nishanth Menon <nm@ti.com>
Diffstat (limited to 'doc/media')
0 files changed, 0 insertions, 0 deletions