X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=tcl%2Ftarget%2Fem357.cfg;h=24ffb04f92378db7333182489a71f638875cf353;hp=f44b2985aa6a745447aee8c9d278242d3ecd9ac6;hb=33d220d10a069be34095313f51ae22052a079b34;hpb=18d6c0b02bf5e1318d5f5484b5ba68b476a418f0

diff --git a/tcl/target/em357.cfg b/tcl/target/em357.cfg
index f44b2985aa..24ffb04f92 100644
--- a/tcl/target/em357.cfg
+++ b/tcl/target/em357.cfg
@@ -34,7 +34,7 @@ if { [info exists CPUTAPID] } {
 if { [info exists BSTAPID] } {
    set _BSTAPID $BSTAPID
 } else {
-  set _BSTAPID 0x069aa62b
+  set _BSTAPID 0x069a962b
 }
 
 if { [info exists CHIPNAME] } {
@@ -63,5 +63,14 @@ set _FLASHNAME $_CHIPNAME.flash
 flash bank $_FLASHNAME em357 0x08000000 $_FLASHSIZE 0 0 $_TARGETNAME
 
 if { ![using_hla]} {
-    cortex_m reset_config sysresetreq
+# according to errata, we need to use vectreset rather than sysresetreq to avoid lockup
+# There is a bug in the chip, which means that when using external debuggers the chip
+# may lock up in certain CPU clock modes. Affected modes are operating the CPU at
+# 24MHz derived from the 24MHz crystal, or 12MHz derived from the high frequency RC
+# oscillator. If an external debugger tool asserts SYSRESETREQ, the chip will lock up and
+# require a pin reset or power cycle.
+#
+# for details, refer to:
+# http://www.silabs.com/Support%20Documents/TechnicalDocs/EM35x-Errata.pdf
+    cortex_m reset_config vectreset
 }