diff options
| author | Spencer Oliver <spen@spen-soft.co.uk> | 2012-11-26 12:42:41 +0000 |
|---|---|---|
| committer | Freddie Chopin <freddie.chopin@gmail.com> | 2012-12-10 16:13:52 +0000 |
| commit | c91dbd41ba5490b1b63617bab42624e45f5cd3ad (patch) | |
| tree | 1d313f3cd1bd04c79a766e57f2285863a7bfe462 /doc | |
| parent | 539a9cf20831c96588c0db62b871f7438067b509 (diff) | |
| download | riscv-openocd-c91dbd41ba5490b1b63617bab42624e45f5cd3ad.zip riscv-openocd-c91dbd41ba5490b1b63617bab42624e45f5cd3ad.tar.gz riscv-openocd-c91dbd41ba5490b1b63617bab42624e45f5cd3ad.tar.bz2 | |
jtag: add connect_type reset_config mode flag
This adds the ability to request to the adapter how we want to connect to
the target, eg. while srst is asserted or not.
This ability can very handy for connecting to unresponsive targets.
A prerequisite is that the target supports srst_nogate.
Change-Id: I0f7c9475160048e8a963e16077754f5403ac8325
Signed-off-by: Spencer Oliver <spen@spen-soft.co.uk>
Reviewed-on: http://openocd.zylin.com/976
Reviewed-by: Paul Fertser <fercerpav@gmail.com>
Tested-by: jenkins
Reviewed-by: Freddie Chopin <freddie.chopin@gmail.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/openocd.texi | 19 |
1 files changed, 15 insertions, 4 deletions
diff --git a/doc/openocd.texi b/doc/openocd.texi index c2ee20d..f2b2ffe 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -3156,10 +3156,9 @@ from a particular combination of interface and board. with a board that only wires up SRST.) The @var{mode_flag} options can be specified in any order, but only one -of each type -- @var{signals}, @var{combination}, -@var{gates}, -@var{trst_type}, -and @var{srst_type} -- may be specified at a time. +of each type -- @var{signals}, @var{combination}, @var{gates}, +@var{trst_type}, @var{srst_type} and @var{connect_type} +-- may be specified at a time. If you don't provide a new value for a given type, its previous value (perhaps the default) is unchanged. For example, this means that you don't need to say anything at all about @@ -3201,6 +3200,18 @@ JTAG clock. This means that no communication can happen on JTAG while SRST is asserted. Its converse is @option{srst_nogate}, indicating that JTAG commands can safely be issued while SRST is active. + +@item +The @var{connect_type} tokens control flags that describe some cases where +SRST is asserted while connecting to the target. @option{srst_nogate} +is required to use this option. +@option{connect_deassert_srst} (default) +indicates that SRST will not be asserted while connecting to the target. +Its converse is @option{connect_assert_srst}, indicating that SRST will +be asserted before any target connection. +Only some targets support this feature, STM32 and STR9 are examples. +This feature is useful if you are unable to connect to your target due +to incorrect options byte config or illegal program execution. @end itemize The optional @var{trst_type} and @var{srst_type} parameters allow the |