imi415
/
openocd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Dirk Behme <dirk.behme@googlemail.com> document post TAP reset event 

git-svn-id: svn://svn.berlios.de/openocd/trunk@2700 b42882b7-edfa-0310-969c-e2dbd0fdcd60
This commit is contained in:
oharboe 2009-09-12 13:05:20 +00:00
parent 40f361dd94
commit a17eb667a3
1 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/openocd.texi
View File

@ -2289,14 +2289,14 @@ does include a kind of JTAG router functionality.
@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 configure CHIP.cpu -event tap-disable @{
... 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