doc: board: ti: k3: Fix up OpenOCD references and debug info
PATCH 1/1 doc: board: ti: k3: Fix up OpenOCD references and debug info
From: Jonathan Humphreys <[email protected]>
Fix minor path and config macro name updates to sync with latest OpenOCD and U-Boot configurations.
Fixes effe50854a69 ("doc: board: ti: k3: Add a guide to debugging with OpenOCD")
Signed-off-by Jonathan Humphreys <[email protected]>
Signed-off-by Nishanth Menon <[email protected]>
---
Cc: Heinrich Schuchardt <[email protected]>
doc/board/ti/k3.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
doc/board/ti/k3.rst +3 -3
@@ -601,7 +601,7 @@ correctly to ensure a sane system. $ cd openocd # Copy the udev rules to the correct system location $ sudo cp ./contrib/60-openocd.rules \ - ./src/JTAG/drivers/libjaylink/contrib/99-libjaylink.rules \ + ./src/jtag/drivers/libjaylink/contrib/99-libjaylink.rules \ /etc/udev/rules.d/ # Get Udev to load the new rules up $ sudo udevadm control --reload-rules
@@ -792,7 +792,7 @@ Code modification In this example, we will debug ``board_init_f`` inside ``arch/arm/mach-k3/{soc}_init.c``. Since some sections of U-Boot will be executed multiple times during the bootup process of K3 - devices, we will need to include either ``CONFIG_CPU_ARM64`` or + devices, we will need to include either ``CONFIG_ARM64`` or ``CONFIG_CPU_V7R`` to catch the CPU at the desired place during the bootup process (Main or Wakeup domains). For example, modify the file as follows (depending on need):
@@ -810,7 +810,7 @@ Code modification } ... /* Code to run on the ARMV8 (Main Domain) */ - if (IS_ENABLED(CONFIG_CPU_ARM64)) { + if (IS_ENABLED(CONFIG_ARM64)) { volatile int x = 1; while(x) {}; }
Signature · 1 line
2.40.0