From aea132ca48f33a98299f2a3013f0fdde9fe6103b Mon Sep 17 00:00:00 2001 From: oharboe Date: Sat, 30 May 2009 07:53:40 +0000 Subject: more reset_config texts git-svn-id: svn://svn.berlios.de/openocd/trunk@1947 b42882b7-edfa-0310-969c-e2dbd0fdcd60 --- doc/openocd.texi | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/openocd.texi b/doc/openocd.texi index 0e2c2b82..60987a99 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -1699,7 +1699,20 @@ nTRST (active-low JTAG TAP reset) before starting new JTAG operations. @deffn {Command} reset_config mode_flag ... This command tells OpenOCD the reset configuration -of your combination of JTAG interface, board, and target. +of your combination of JTAG board and target in target +configuration scripts. + +If you have an interface that does not support SRST and +TRST(unlikely), then you may be able to work around that +problem by using a reset_config command to override any +settings in the target configuration script. + +SRST and TRST has a fairly well understood definition and +behaviour in the JTAG specification, but vendors take +liberties to achieve various more or less clearly understood +goals. Sometimes documentation is available, other times it +is not. OpenOCD has the reset_config command to allow OpenOCD +to deal with the various common cases. The @var{mode_flag} options can be specified in any order, but only one of each type -- @var{signals}, @var{combination}, @var{trst_type}, -- cgit v1.2.3