auracaster/openocd
3
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

tcl/target/nordic/nrf53: fix empty event handler

Browse Source 
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 17be341d38 ("tcl/target: add nRF53 and nRF91 config files")
Reported-by: Lawrence King <lawrencek52@gmail.com>
Change-Id: I3bd229a78860ed05d694e708ab62cb1670a77010
Signed-off-by: Tomas Vanek <vanekt@fbl.cz>
Reviewed-on: https://review.openocd.org/c/openocd/+/9492
Tested-by: jenkins
Reviewed-by: Lawrence King <lawrencek52@gmail.com>
This commit is contained in:
Tomas Vanek
2026-03-01 17:41:12 +01:00
parent 84f8814003
commit 5b3db97c42
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
tcl/target/nordic/nrf53.cfg
View File

@@ -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