summaryrefslogtreecommitdiff
path: root/tcl
diff options
context:
space:
mode:
Diffstat (limited to 'tcl')
-rw-r--r--tcl/target/lpc1768.cfg8
1 files changed, 4 insertions, 4 deletions
diff --git a/tcl/target/lpc1768.cfg b/tcl/target/lpc1768.cfg
index 9a813f5b..f0093ad4 100644
--- a/tcl/target/lpc1768.cfg
+++ b/tcl/target/lpc1768.cfg
@@ -33,11 +33,11 @@ target create $_TARGETNAME cortex_m3 -endian $_ENDIAN -chain-position $_TARGETNA
# LPC1768 has 32kB of SRAM on its main system bus (so-called Local On-Chip SRAM)
$_TARGETNAME configure -work-area-phys 0x10000000 -work-area-size 0x8000 -work-area-backup 0
+# REVISIT is there any good reason to have this reset-init event handler??
+# Normally they should set up (board-specific) clocking then probe the flash...
$_TARGETNAME configure -event reset-init {
- # Force target into ARM state
- arm core_state arm
- #do not remap 0x0000-0x0020 to anything but the flash
-# mwb 0xE01FC040 0x01
+ # Force NVIC.VTOR to point to flash at 0 ...
+ # WHY? This is it's reset value; we run right after reset!!
mwb 0xE000ED08 0x00
}