summaryrefslogtreecommitdiff
path: root/src/target/target/aduc702x.cfg
diff options
context:
space:
mode:
Diffstat (limited to 'src/target/target/aduc702x.cfg')
-rw-r--r--src/target/target/aduc702x.cfg38
1 files changed, 38 insertions, 0 deletions
diff --git a/src/target/target/aduc702x.cfg b/src/target/target/aduc702x.cfg
new file mode 100644
index 00000000..4269f38a
--- /dev/null
+++ b/src/target/target/aduc702x.cfg
@@ -0,0 +1,38 @@
+## -*- tcl -*-
+##
+
+# This is for the case that TRST/SRST is not wired on your JTAG adaptor.
+# Don't really need them anyways.
+reset_config none
+
+## JTAG scan chain
+#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
+jtag_device 4 0x1 0xf 0xe
+
+##
+## Target configuration
+##
+target arm7tdmi little 0
+
+## software initiated reset (if your SRST isn't wired)
+#proc target_0_reset {} { mwb 0x0ffff0230 04 }
+
+# use top 1k of SRAM for as temporary JTAG memory
+#working_area 0 0x11C00 0x400 backup
+
+## flash configuration
+## AdUC702x not yet spported :(
+
+## If you use the watchdog, the following code makes sure that the board
+## doesn't reboot when halted via JTAG. Yes, on the older generation
+## AdUC702x, timer3 continues running even when the CPU is halted.
+
+proc watchdog_service {} {
+ global watchdog_hdl
+ mww 0xffff036c 0
+# puts "watchdog!!"
+ set watchdog_hdl [after 500 watchdog_service]
+}
+
+proc target_0_post_halt {} { watchdog_service }
+proc arget_0_pre_resume {} { global watchdog_hdl; after cancel $watchdog_hdl }