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 <borneo.antonio@gmail.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Change-Id: I2e51fdbd8756f156551e589c748c3a338afa655c
Reviewed-on: https://review.openocd.org/c/openocd/+/6615
Tested-by: jenkins
Reviewed-by: Antonio Borneo <borneo.antonio@gmail.com>

diff --git a/tcl/target/ti_k3.cfg b/tcl/target/ti_k3.cfg
index 325ee00042a02242e2744f49998d4475e980449f..8fb71482c9e9160b6ca5a348ce90c1f447ddeba2 100644 (file)
--- 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
+       }
 }