From c280c9835705a7d104996569068826a73b665010 Mon Sep 17 00:00:00 2001 From: Nishanth Menon Date: Fri, 1 Oct 2021 22:48:34 -0500 Subject: [PATCH] tcl/target/ti_k3: Add a gdb-attach event hook for m3 and m4 Add gdb-attach event to call the "up" function of m3 and m4 allowing for more seamless integration with gdb for end users. We still retain _up functions for non-gdb functionality. NOTE: we add a halt 1000 to retain the default gdb-attach hook behavior Suggested-by: Antonio Borneo Signed-off-by: Nishanth Menon Change-Id: I2e51fdbd8756f156551e589c748c3a338afa655c Reviewed-on: https://review.openocd.org/c/openocd/+/6615 Tested-by: jenkins Reviewed-by: Antonio Borneo --- tcl/target/ti_k3.cfg | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/tcl/target/ti_k3.cfg b/tcl/target/ti_k3.cfg index 325ee0004..8fb71482c 100644 --- a/tcl/target/ti_k3.cfg +++ b/tcl/target/ti_k3.cfg @@ -161,6 +161,12 @@ proc m3_up {} { $::_TARGETNAME.m3 arp_examine } +$_TARGETNAME.m3 configure -event gdb-attach { + m3_up + # gdb-attach default rule + halt 1000 +} + set _v8_smp_targets "" for { set _core 0 } { $_core < $_armv8_cores } { incr _core } { @@ -253,4 +259,10 @@ if { $_mcu_m4_cores != 0 } { $::_TARGETNAME.m4 arp_examine } + + $_TARGETNAME.m4 configure -event gdb-attach { + m4_up + # gdb-attach default rule + halt 1000 + } } -- 2.30.2