zcy
/
tinyriscv-openocd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

David Brownell <david-b@pacbell.net> Add a short chapter on boundary scan support, which currently 

just documents the SVF and XSVF commands.

git-svn-id: svn://svn.berlios.de/openocd/trunk@2404 b42882b7-edfa-0310-969c-e2dbd0fdcd60
__archive__
oharboe 2009-06-26 07:30:21 +00:00
parent 374f6c8b70
commit 37b15fb2c4
1 changed files with 49 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

50
doc/openocd.texi
View File

@ -78,6 +78,7 @@ Free Documentation License''.
* General Commands:: General Commands * General Commands:: General Commands
* Architecture and Core Commands:: Architecture and Core Commands * Architecture and Core Commands:: Architecture and Core Commands
* JTAG Commands:: JTAG Commands * JTAG Commands:: JTAG Commands
* Boundary Scan Commands:: Boundary Scan Commands
* TFTP:: TFTP * TFTP:: TFTP
* GDB and OpenOCD:: Using GDB and OpenOCD * GDB and OpenOCD:: Using GDB and OpenOCD
* Tcl Scripting API:: Tcl Scripting API * Tcl Scripting API:: Tcl Scripting API
@ -850,7 +851,7 @@ There are many ways you can configure OpenOCD and start it up.
A simple way to organize them all involves keeping a A simple way to organize them all involves keeping a
single directory for your work with a given board. single directory for your work with a given board.
When you start OpenOCD from that directory, When you start OpenOCD from that directory,
it searches there first for configuration files it searches there first for configuration files, scripts,
and for code you upload to the target board. and for code you upload to the target board.
It is also the natural place to write files, It is also the natural place to write files,
such as log files and data you download from the board. such as log files and data you download from the board.
@ -5353,6 +5354,53 @@ levels, such as advancing the ARM9E-S instruction pipeline.
Consult the documentation for the TAP(s) you are working with. Consult the documentation for the TAP(s) you are working with.
@end itemize @end itemize
@node Boundary Scan Commands
@chapter Boundary Scan Commands
One of the original purposes of JTAG was to support
boundary scan based hardware testing.
Although its primary focus is to support On-Chip Debugging,
OpenOCD also includes some boundary scan commands.
@section SVF: Serial Vector Format
@cindex Serial Vector Format
@cindex SVF
The Serial Vector Format, better known as @dfn{SVF}, is a
way to represent JTAG test patterns in text files.
OpenOCD supports running such test files.
@deffn Command {svf} filename [@option{quiet}]
This issues a JTAG reset (Test-Logic-Reset) and then
runs the SVF script from @file{filename}.
Unless the @option{quiet} option is specified,
each command is logged before it is executed.
@end deffn
@section XSVF: Xilinx Serial Vector Format
@cindex Xilinx Serial Vector Format
@cindex XSVF
The Xilinx Serial Vector Format, better known as @dfn{XSVF}, is a
binary representation of SVF which is optimized for use with
Xilinx devices.
OpenOCD supports running such test files.
@quotation Important
Not all XSVF commands are supported.
@end quotation
@deffn Command {xsvf} (tapname|@option{plain}) filename [@option{virt2}] [@option{quiet}]
This issues a JTAG reset (Test-Logic-Reset) and then
runs the XSVF script from @file{filename}.
When a @var{tapname} is specified, the commands are directed at
that TAP.
When @option{virt2} is specified, the @sc{xruntest} command counts
are interpreted as TCK cycles instead of microseconds.
Unless the @option{quiet} option is specified,
messages are logged for comments and some retries.
@end deffn
@node TFTP @node TFTP
@chapter TFTP @chapter TFTP
@cindex TFTP @cindex TFTP