[Openocd-svn] r2700 - trunk/doc

[oharboe at B. <oh...@ma...>]

Author: oharboe
Date: 2009-09-12 15:05:20 +0200 (Sat, 12 Sep 2009)
New Revision: 2700

Modified:
   trunk/doc/openocd.texi
Log:
Dirk Behme <dir...@go...> document post TAP reset event

Modified: trunk/doc/openocd.texi
===================================================================
--- trunk/doc/openocd.texi	2009-09-12 08:11:45 UTC (rev 2699)
+++ trunk/doc/openocd.texi	2009-09-12 13:05:20 UTC (rev 2700)
@@ -2289,14 +2289,14 @@
 
 @deffn Command {jtag cget} dotted.name @option{-event} name
 @deffnx Command {jtag configure} dotted.name @option{-event} name string
-At this writing this mechanism is used only for event handling,
-and the only two events relate to TAP enabling and disabling.
+At this writing this mechanism is used only for event handling.
+Three events are available. Two events relate to TAP enabling
+and disabling, one to post reset handling.
 
 The @code{configure} subcommand assigns an event handler,
 a TCL string which is evaluated when the event is triggered.
 The @code{cget} subcommand returns that handler.
-The two possible values for an event @var{name}
-are @option{tap-disable} and @option{tap-enable}.
+The three possible values for an event @var{name} are @option{tap-disable}, @option{tap-enable} and @option{post-reset}.
 
 So for example, when defining a TAP for a CPU connected to
 a JTAG router, you should define TAP event handlers using
@@ -2312,6 +2312,15 @@
   ... jtag operations using CHIP.jrc
 @}
 @end example
+
+If you need some post reset action, you can do:
+
+@example
+jtag configure CHIP.cpu -event post-reset @{
+  echo "Reset done"
+  ... jtag operations to be done after reset
+@}
+@end example
 @end deffn
 
 @deffn Command {jtag tapdisable} dotted.name