From 5b3db97c42b62e4c2559f3384120626b28401b4e Mon Sep 17 00:00:00 2001 From: Tomas Vanek Date: Sun, 1 Mar 2026 17:41:12 +0100 Subject: [PATCH] tcl/target/nordic/nrf53: fix empty event handler reset-assert of network CPU should be handled by empty dummy handler to prevent the Cortex-M target native processing. Unfortunately configuring the empty string does not define a new handler, it drops the existing one. Use semicolon to fix configuration and to make the emtpy handler clearly visible. Fixes: commit 17be341d38bd ("tcl/target: add nRF53 and nRF91 config files") Reported-by: Lawrence King Change-Id: I3bd229a78860ed05d694e708ab62cb1670a77010 Signed-off-by: Tomas Vanek Reviewed-on: https://review.openocd.org/c/openocd/+/9492 Tested-by: jenkins Reviewed-by: Lawrence King --- tcl/target/nordic/nrf53.cfg | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/tcl/target/nordic/nrf53.cfg b/tcl/target/nordic/nrf53.cfg index ce2eaf045..137897c57 100644 --- a/tcl/target/nordic/nrf53.cfg +++ b/tcl/target/nordic/nrf53.cfg @@ -72,9 +72,11 @@ if { ![using_hla] } { flash bank $_CHIPNAME.net.uicr nrf5 0x01FF8000 0 0 0 $_TARGETNAME_NET # System reset sets NETWORK.FORCEOFF which keeps the network core in reset - # Don't touch network core during reset - $_TARGETNAME_NET configure -event reset-assert {} - # and start it after application core reset is finished to make all flash accessible + # Don't touch network core during reset - the event handler is + # intentionally empty and prevents native processing + $_TARGETNAME_NET configure -event reset-assert {;} + # and start it after application core reset is finished to make + # all flash accessible $_TARGETNAME_APP configure -event reset-init "nrf53_cpunet_release $_CHIPNAME" $_TARGETNAME_APP cortex_m reset_config sysresetreq