From 8bf5482754715f2e1b05be03de8780f26c305955 Mon Sep 17 00:00:00 2001 From: Nishanth Menon Date: Thu, 14 Jul 2022 16:37:54 -0500 Subject: [PATCH] tcl/target/ti_k3: Handle swd vs jtag Since all the device definition when accessing device from jtag is also valid when accessing from swd, lets make sure the configuration can handle the same. Signed-off-by: Nishanth Menon Change-Id: I5af071137fd8c3b52cc4ef72401f8eba952f9cad Reviewed-on: https://review.openocd.org/c/openocd/+/7090 Tested-by: jenkins Reviewed-by: Antonio Borneo --- tcl/target/ti_k3.cfg | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tcl/target/ti_k3.cfg b/tcl/target/ti_k3.cfg index 254bb69716..2454357fc3 100644 --- a/tcl/target/ti_k3.cfg +++ b/tcl/target/ti_k3.cfg @@ -12,6 +12,8 @@ # Has 2 ARMV8 Cores and 4 R5 Cores, M4F and an M3 # +source [find target/swj-dp.tcl] + if { [info exists SOC] } { set _soc $SOC } else { @@ -164,7 +166,8 @@ switch $_soc { } } -jtag newtap $_CHIPNAME cpu -irlen 4 -expected-id $_K3_DAP_TAPID -ignore-version +swj_newdap $_CHIPNAME cpu -irlen 4 -expected-id $_K3_DAP_TAPID -ignore-version + dap create $_CHIPNAME.dap -chain-position $_CHIPNAME.cpu set _TARGETNAME $_CHIPNAME.cpu -- 2.30.2