For STR7x flash, the device cannot be queried for the protect status.
The solution is to remove the protection on reset init. The driver
also initialises the sector protect field to unprotected.
Signed-off-by: Edgar Grimberg <edgar.grimb...@zylin.com>
---
tcl/target/str730.cfg | 9 ++++++++-
tcl/target/str750.cfg | 10 +++++++++-
2 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/tcl/target/str730.cfg b/tcl/target/str730.cfg
index 381fa5f..fc2f2d0 100644
--- a/tcl/target/str730.cfg
+++ b/tcl/target/str730.cfg
@@ -34,7 +34,14 @@ set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME arm7tdmi -endian little -chain-position 0 -variant
arm7tdmi
$_TARGETNAME configure -event reset-start { jtag_khz 10 }
-$_TARGETNAME configure -event reset-init { jtag_khz 3000 }
+$_TARGETNAME configure -event reset-init {
+ jtag_khz 3000
+
+# Because the hardware cannot be interrogated for the protection state of
sectors,
+# initialize all the sectors to be unprotected. The initial state is reflected
by
+# the driver, too.
+ flash protect 0 0 last off
+}
$_TARGETNAME configure -event gdb-flash-erase-start {
flash protect 0 0 7 off
}
diff --git a/tcl/target/str750.cfg b/tcl/target/str750.cfg
index 5df968b..f9a2e2e 100644
--- a/tcl/target/str750.cfg
+++ b/tcl/target/str750.cfg
@@ -36,7 +36,15 @@ set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME arm7tdmi -endian little -chain-position 0 -variant
arm7tdmi
$_TARGETNAME configure -event reset-start { jtag_khz 10 }
-$_TARGETNAME configure -event reset-init { jtag_khz 3000 }
+$_TARGETNAME configure -event reset-init {
+ jtag_khz 3000
+
+# Because the hardware cannot be interrogated for the protection state of
sectors,
+# initialize all the sectors to be unprotected. The initial state is reflected
by
+# the driver, too.
+ flash protect 0 0 last off
+ flash protect 1 0 last off
+}
$_TARGETNAME configure -event gdb-flash-erase-start {
flash protect 0 0 7 off
flash protect 1 0 1 off
--
1.6.3.3
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
