Better explanation for the TAP "-ircapture" parameter.
---
doc/openocd.texi | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -2198,7 +2198,10 @@ Every TAP requires at least the followin
@itemize @bullet
@item @code{-ircapture} @var{NUMBER}
-...@*the IDCODE capture command, such as 0x01.
+...@*the bit pattern loaded by the TAP into the JTAG shift register
+on entry to the @sc{ircapture} state, such as 0x01.
+JTAG requires the two LSBs of this value to be 01.
+The value is used to verify that instruction scans work correctly.
@item @code{-irlen} @var{NUMBER}
@*The length in bits of the
instruction register, such as 4 or 5 bits.
Better explanation for the TAP "-ircapture" parameter.
---
doc/openocd.texi | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -2198,7 +2198,10 @@ Every TAP requires at least the followin
@itemize @bullet
@item @code{-ircapture} @var{NUMBER}
-...@*the IDCODE capture command, such as 0x01.
+...@*the bit pattern loaded by the TAP into the JTAG shift register
+on entry to the @sc{ircapture} state, such as 0x01.
+JTAG requires the two LSBs of this value to be 01.
+The value is used to verify that instruction scans work correctly.
@item @code{-irlen} @var{NUMBER}
@*The length in bits of the
instruction register, such as 4 or 5 bits.
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
