summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authoroharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-09-17 11:23:41 +0000
committeroharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-09-17 11:23:41 +0000
commit016e7ebbfa034926c980b4b33b964f6078541690 (patch)
treef5bf6aaba52e21262ee88b4cf70c999c55bf9f6c /doc
parentcb7ad25c0404147a0a60f04c3b8fa8ac7386bb29 (diff)
downloadopenocd+libswd-016e7ebbfa034926c980b4b33b964f6078541690.tar.gz
openocd+libswd-016e7ebbfa034926c980b4b33b964f6078541690.tar.bz2
openocd+libswd-016e7ebbfa034926c980b4b33b964f6078541690.tar.xz
openocd+libswd-016e7ebbfa034926c980b4b33b964f6078541690.zip
srst_gates_jtag option. at91sam9260 needs retesting, and possibly srst_gates_jtag added to reset_config. Could i.MX27 be a case where srst does not pull trst, but really srst gates jtag clock?
git-svn-id: svn://svn.berlios.de/openocd/trunk@2720 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'doc')
-rw-r--r--doc/openocd.texi4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/openocd.texi b/doc/openocd.texi
index 0b6ecf02..9f7314b0 100644
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -2018,6 +2018,10 @@ haven't seen hardware with such a bug, and can be worked around).
@option{combined} implies both @option{srst_pulls_trst} and
@option{trst_pulls_srst}.
+@option{srst_gates_jtag} indicates that asserting SRST gates the
+JTAG clock. This means that no communication can happen on JTAG
+while SRST is asserted.
+
The optional @var{trst_type} and @var{srst_type} parameters allow the
driver mode of each reset line to be specified. These values only affect
JTAG interfaces with support for different driver modes, like the Amontec