1 \input texinfo @c -*-texinfo-*-
3 @setfilename openocd.info
4 @settitle Open On-Chip Debugger (OpenOCD)
5 @dircategory Development
8 * OpenOCD: (openocd). Open On-Chip Debugger.
17 @item Copyright @copyright{} 2008 The OpenOCD Project
18 @item Copyright @copyright{} 2007-2008 Spen @email{spen@@spen-soft.co.uk}
19 @item Copyright @copyright{} 2008 Oyvind Harboe @email{oyvind.harboe@@zylin.com}
20 @item Copyright @copyright{} 2008 Duane Ellis @email{openocd@@duaneellis.com}
24 Permission is granted to copy, distribute and/or modify this document
25 under the terms of the GNU Free Documentation License, Version 1.2 or
26 any later version published by the Free Software Foundation; with no
27 Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
28 Texts. A copy of the license is included in the section entitled ``GNU
29 Free Documentation License''.
34 @title Open On-Chip Debugger (OpenOCD)
35 @subtitle Edition @value{EDITION} for OpenOCD version @value{VERSION}
36 @subtitle @value{UPDATED}
38 @vskip 0pt plus 1filll
45 @node Top, About, , (dir)
48 This manual documents edition @value{EDITION} of the Open On-Chip Debugger
49 (OpenOCD) version @value{VERSION}, @value{UPDATED}.
54 * About:: About OpenOCD.
55 * Developers:: OpenOCD developers
56 * Building:: Building OpenOCD
57 * JTAG Hardware Dongles:: JTAG Hardware Dongles
58 * Running:: Running OpenOCD
59 * Simple Configuration Files:: Simple Configuration Files
60 * Config File Guidelines:: Config File Guidelines
61 * About JIM-Tcl:: About JIM-Tcl
62 * Daemon Configuration:: Daemon Configuration
63 * Interface - Dongle Configuration:: Interface - Dongle Configuration
64 * Reset Configuration:: Reset Configuration
65 * Tap Creation:: Tap Creation
66 * Target Configuration:: Target Configuration
67 * Flash Configuration:: Flash Configuration
68 * General Commands:: General Commands
69 * JTAG Commands:: JTAG Commands
70 * Sample Scripts:: Sample Target Scripts
72 * GDB and OpenOCD:: Using GDB and OpenOCD
73 * TCL scripting API:: Tcl scripting API
74 * Upgrading:: Deprecated/Removed Commands
75 * Target library:: Target library
76 * FAQ:: Frequently Asked Questions
77 * TCL Crash Course:: TCL Crash Course
78 * License:: GNU Free Documentation License
79 @comment DO NOT use the plain word ``Index'', reason: CYGWIN filename
80 @comment case issue with ``Index.html'' and ``index.html''
81 @comment Occurs when creating ``--html --no-split'' output
82 @comment This fix is based on: http://sourceware.org/ml/binutils/2006-05/msg00215.html
83 * OpenOCD Index:: Main index.
90 The Open On-Chip Debugger (OpenOCD) aims to provide debugging,
91 in-system programming and boundary-scan testing for embedded target
94 @b{JTAG:} OpenOCD uses a ``hardware interface dongle'' to communicate
95 with the JTAG (IEEE 1149.1) complient taps on your target board.
97 @b{Dongles:} OpenOCD currently many types of hardware dongles: USB
98 Based, Parallel Port Based, and other standalone boxes that run
99 OpenOCD internally. See the section titled: @xref{JTAG Hardware
102 @b{GDB Debug:} It allows ARM7 (ARM7TDMI and ARM720t), ARM9 (ARM920t,
103 ARM922t, ARM926ej--s, ARM966e--s), XScale (PXA25x, IXP42x) and
104 Cortex-M3 (Luminary Stellaris LM3 and ST STM32) based cores to be
105 debugged via the GDB Protocol.
107 @b{Flash Programing:} Flash writing is supported for external CFI
108 compatible flashes (Intel and AMD/Spansion command set) and several
109 internal flashes (LPC2000, AT91SAM7, STR7x, STR9x, LM3 and
110 STM32x). Preliminary support for using the LPC3180's NAND flash
111 controller is included.
117 OpenOCD was created by Dominic Rath as part of a diploma thesis written at the
118 University of Applied Sciences Augsburg (@uref{http://www.fh-augsburg.de}).
119 Others interested in improving the state of free and open debug and testing technology
120 are welcome to participate.
122 Other developers have contributed support for additional targets and flashes as well
123 as numerous bugfixes and enhancements. See the AUTHORS file for regular contributors.
125 The main OpenOCD web site is available at @uref{http://openocd.berlios.de/web/}
129 @cindex building OpenOCD
131 If you are interested in getting actual work done rather than building
132 OpenOCD, then check if your interface supplier provides binaries for
133 you. Chances are that that binary is from some SVN version that is more
134 stable than SVN trunk where bleeding edge development takes place.
137 You can download the current SVN version with SVN client of your choice from the
138 following repositories:
140 (@uref{svn://svn.berlios.de/openocd/trunk})
144 (@uref{http://svn.berlios.de/svnroot/repos/openocd/trunk})
146 Using the SVN command line client, you can use the following command to fetch the
147 latest version (make sure there is no (non-svn) directory called "openocd" in the
151 svn checkout svn://svn.berlios.de/openocd/trunk openocd
154 Building OpenOCD requires a recent version of the GNU autotools.
155 On my build system, I'm using autoconf 2.13 and automake 1.9. For building on Windows,
156 you have to use Cygwin. Make sure that your @env{PATH} environment variable contains no
157 other locations with Unix utils (like UnxUtils) - these can't handle the Cygwin
158 paths, resulting in obscure dependency errors (This is an observation I've gathered
159 from the logs of one user - correct me if I'm wrong).
161 You further need the appropriate driver files, if you want to build support for
162 a FTDI FT2232 based interface:
164 @item @b{ftdi2232} libftdi (@uref{http://www.intra2net.com/opensource/ftdi/})
165 @item @b{ftd2xx} libftd2xx (@uref{http://www.ftdichip.com/Drivers/D2XX.htm})
166 @item When using the Amontec JTAGkey, you have to get the drivers from the Amontec
167 homepage (@uref{www.amontec.com}), as the JTAGkey uses a non-standard VID/PID.
170 libftdi is supported under windows. Versions earlier than 0.13 will require patching.
171 see contrib/libftdi for more details.
173 In general, the D2XX driver provides superior performance (several times as fast),
174 but has the draw-back of being binary-only - though that isn't that bad, as it isn't
175 a kernel module, only a user space library.
177 To build OpenOCD (on both Linux and Cygwin), use the following commands:
181 Bootstrap generates the configure script, and prepares building on your system.
185 Configure generates the Makefiles used to build OpenOCD.
189 Make builds OpenOCD, and places the final executable in ./src/.
191 The configure script takes several options, specifying which JTAG interfaces
196 @option{--enable-parport}
198 @option{--enable-parport_ppdev}
200 @option{--enable-parport_giveio}
202 @option{--enable-amtjtagaccel}
204 @option{--enable-ft2232_ftd2xx}
205 @footnote{Using the latest D2XX drivers from FTDI and following their installation
206 instructions, I had to use @option{--enable-ft2232_libftd2xx} for OpenOCD to
209 @option{--enable-ft2232_libftdi}
211 @option{--with-ftd2xx=/path/to/d2xx/}
213 @option{--enable-gw16012}
215 @option{--enable-usbprog}
217 @option{--enable-presto_libftdi}
219 @option{--enable-presto_ftd2xx}
221 @option{--enable-jlink}
224 If you want to access the parallel port using the PPDEV interface you have to specify
225 both the @option{--enable-parport} AND the @option{--enable-parport_ppdev} option since
226 the @option{--enable-parport_ppdev} option actually is an option to the parport driver
227 (see @uref{http://forum.sparkfun.com/viewtopic.php?t=3795} for more info).
229 Cygwin users have to specify the location of the FTDI D2XX package. This should be an
230 absolute path containing no spaces.
232 Linux users should copy the various parts of the D2XX package to the appropriate
233 locations, i.e. /usr/include, /usr/lib.
235 Miscellaneous configure options
239 @option{--enable-gccwarnings} - enable extra gcc warnings during build
242 @node JTAG Hardware Dongles
243 @chapter JTAG Hardware Dongles
252 Defined: @b{dongle}: A small device that plugins into a computer and serves as
253 an adapter .... [snip]
255 In the OpenOCD case, this generally refers to @b{a small adapater} one
256 attaches to your computer via USB or the Parallel Printer Port. The
257 execption being the Zylin ZY1000 which is a small box you attach via
261 @section Choosing a Dongle
263 There are three things you should keep in mind when choosing a dongle.
266 @item @b{Voltage} What voltage is your target? 1.8, 2.8, 3.3, or 5V? Does your dongle support it?
267 @item @b{Connection} Printer Ports - Does your computer have one?
268 @item @b{Connection} Is that long printer bit-bang cable practical?
269 @item @b{RTCK} Do you require RTCK? Also known as ``adaptive clocking''
272 @section Stand alone Systems
274 @b{ZY1000} See: @url{http://www.zylin.com/zy1000.html} Technically, not a
275 dongle, but a standalone box.
277 @section USB FT2232 Based
279 There are many USB jtag dongles on the market, many of them are based
280 on a chip from ``Future Technology Devices International'' (FTDI)
281 known as the FTDI FT2232.
283 See: @url{http://www.ftdichip.com} or @url{http://www.ftdichip.com/Products/FT2232H.htm}
285 As of 28/Nov/2008, the following are supported:
289 @* Link @url{www.ixo.de/info/usb_jtag}
291 @* See: @url{http://www.amontec.com/jtagkey.shtml}
293 @* See: @url{http://www.oocdlink.com} By Joern Kaipf
295 @* See: @url{http://www.signalyzer.com}
296 @item @b{evb_lm3s811}
297 @* See: @url{http://www.luminarymicro.com} - The Luminary Micro Stellaris LM3S811 eval board has an FTD2232C chip built in.
298 @item @b{olimex-jtag}
299 @* See: @url{http://www.olimex.com}
301 @* See: @url{http://www.tincantools.com}
302 @item @b{turtelizer2}
303 @* See: @url{http://www.ethernut.de}, or @url{http://www.ethernut.de/en/hardware/turtelizer/index.html}
305 @* Link: @url{http://www.hitex.com/index.php?id=383}
307 @* Link @url{http://www.hitex.com/stm32-stick}
308 @item @b{axm0432_jtag}
309 @* Axiom AXM-0432 Link @url{http://www.axman.com}
312 @section USB JLINK based
313 There are several OEM versions of the Segger @b{JLINK} adapter. It is
314 an example of a micro controller based JTAG adapter, it uses an
315 AT91SAM764 internally.
318 @item @b{ATMEL SAMICE} Only works with ATMEL chips!
319 @* Link: @url{http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3892}
320 @item @b{SEGGER JLINK}
321 @* Link: @url{http://www.segger.com/jlink.html}
323 @* Link: @url{http://www.iar.com/website1/1.0.1.0/369/1/index.php}
329 @* Link: @url{http://www.embedded-projects.net/usbprog} - which uses an Atmel MEGA32 and a UBN9604
331 @item @b{USB - Presto}
332 @* Link: @url{http://tools.asix.net/prg_presto.htm}
335 @section IBM PC Parallel Printer Port Based
337 The two well known ``JTAG Parallel Ports'' cables are the Xilnx DLC5
338 and the MacGraigor Wiggler. There are many clones and variations of
343 @item @b{Wiggler} - There are many clones of this.
344 @* Link: @url{http://www.macraigor.com/wiggler.htm}
346 @item @b{DLC5} - From XILINX - There are many clones of this
347 @* Link: Search the web for: ``XILINX DLC5'' - it is no longer
348 produced, PDF schematics are easily found and it is easy to make.
350 @item @b{Amontec - JTAG Accelerator}
351 @* Link: @url{http://www.amontec.com/jtag_accelerator.shtml}
354 @* Link: @url{http://www.gateworks.com/products/avila_accessories/gw16042.php}
357 @* Link: @url{http://www.ccac.rwth-aachen.de/~michaels/index.php/hardware/armjtag}
359 @item @b{Wiggler_ntrst_inverted}
360 @* Yet another variation - See the source code, src/jtag/parport.c
362 @item @b{old_amt_wiggler}
363 @* Unknown - probably not on the market today
366 @* Link: Most likely @url{http://www.olimex.com/dev/arm-jtag.html} [another wiggler clone]
369 @* Link: @url{http://www.amontec.com/chameleon.shtml}
375 @* ispDownload from Lattice Semiconductor @url{http://www.latticesemi.com/lit/docs/devtools/dlcable.pdf}
378 @* From ST Microsystems, link:
379 @url{http://www.st.com/stonline/products/literature/um/7889.pdf}
380 Title: FlashLINK JTAG programing cable for PSD and uPSD
388 @* An EP93xx based linux machine using the GPIO pins directly.
391 @* Like the EP93xx - but an ATMEL AT91RM9200 based solution using the GPIO pins on the chip.
397 @cindex running OpenOCD
399 @cindex --debug_level
403 The @option{--help} option shows:
407 --help | -h display this help
408 --version | -v display OpenOCD version
409 --file | -f use configuration file <name>
410 --search | -s dir to search for config files and scripts
411 --debug | -d set debug level <0-3>
412 --log_output | -l redirect log output to file <name>
413 --command | -c run <command>
416 By default openocd reads the file configuration file ``openocd.cfg''
417 in the current directory. To specify a different (or multiple)
418 configuration file, you can use the ``-f'' option. For example:
421 openocd -f config1.cfg -f config2.cfg -f config3.cfg
424 Once started, OpenOCD runs as a daemon, waiting for connections from
425 clients (Telnet, GDB, Other).
427 If you are having problems, you can enable internal debug messages via
430 Also it is possible to interleave commands w/config scripts using the
431 @option{-c} command line switch.
433 To enable debug output (when reporting problems or working on OpenOCD
434 itself), use the @option{-d} command line switch. This sets the
435 @option{debug_level} to "3", outputting the most information,
436 including debug messages. The default setting is "2", outputting only
437 informational messages, warnings and errors. You can also change this
438 setting from within a telnet or gdb session using @option{debug_level
439 <n>} @xref{debug_level}.
441 You can redirect all output from the daemon to a file using the
442 @option{-l <logfile>} switch.
444 Search paths for config/script files can be added to OpenOCD by using
445 the @option{-s <search>} switch. The current directory and the OpenOCD
446 target library is in the search path by default.
448 Note! OpenOCD will launch the GDB & telnet server even if it can not
449 establish a connection with the target. In general, it is possible for
450 the JTAG controller to be unresponsive until the target is set up
451 correctly via e.g. GDB monitor commands in a GDB init script.
453 @node Simple Configuration Files
454 @chapter Simple Configuration Files
455 @cindex configuration
458 There are 4 basic ways of ``configurating'' openocd to run, they are:
461 @item A small openocd.cfg file which ``sources'' other configuration files
462 @item A monolithic openocd.cfg file
463 @item Many -f filename options on the command line
464 @item Your Mixed Solution
467 @section Small configuration file method
469 This is the prefered method, it is simple and is works well for many
470 people. The developers of OpenOCD would encourage you to use this
471 method. If you create a new configuration please email new
472 configurations to the development list.
474 Here is an example of an openocd.cfg file for an ATMEL at91sam7x256
477 source [find interface/signalyzer.cfg]
479 # Change the default telnet port...
483 # GDB can also flash my flash!
484 gdb_memory_map enable
485 gdb_flash_program enable
487 source [find target/sam7x256.cfg]
490 There are many example configuration scripts you can work with. You
491 should look in the directory: @t{$(INSTALLDIR)/lib/openocd}. You
495 @item @b{board} - eval board level configurations
496 @item @b{interface} - specific dongle configurations
497 @item @b{target} - the target chips
498 @item @b{tcl} - helper scripts
499 @item @b{xscale} - things specific to the xscale.
502 Look first in the ``boards'' area, then the ``targets'' area. Often a board
503 configuration is a good example to work from.
505 @section Many -f filename options
506 Some believe this is a wonderful solution, others find it painful.
508 You can use a series of ``-f filename'' options on the command line,
509 OpenOCD will read each filename in sequence, for example:
512 openocd -f file1.cfg -f file2.cfg -f file2.cfg
515 You can also intermix various commands with the ``-c'' command line
518 @section Monolithic file
519 The ``Monolithic File'' dispenses with all ``source'' statements and
520 puts everything in one self contained (monolithic) file. This is not
523 Please try to ``source'' various files or use the multiple -f
526 @section Advice for you
527 Often, one uses a ``mixed approach''. Where possible, please try to
528 ``source'' common things, and if needed cut/paste parts of the
529 standard distribution configuration files as needed.
531 @b{REMEMBER:} The ``important parts'' of your configuration file are:
534 @item @b{Interface} - Defines the dongle
535 @item @b{Taps} - Defines the JTAG Taps
536 @item @b{GDB Targets} - What GDB talks to
537 @item @b{Flash Programing} - Very Helpful
540 Some key things you should look at and understand are:
543 @item The RESET configuration of your debug environment as a hole
544 @item Is there a ``work area'' that that OpenOCD can use?
545 @* For ARM - work areas mean up to 10x faster downloads.
546 @item For MMU/MPU based ARM chips (ie: ARM9 and later) will that work area still be available?
547 @item For complex targets (multiple chips) the JTAG SPEED becomes an issue.
552 @node Config File Guidelines
553 @chapter Config File Guidelines
555 This section/chapter is aimed at developers and integrators of
556 OpenOCD. These are guidelines for creating new boards and new target
557 configurations as of 28/Nov/2008.
559 However, you the user of OpenOCD should be some what familiar with
560 this section as it should help explain some of the internals of what
561 you might be looking at.
563 The user should find under @t{$(INSTALLDIR)/lib/openocd} the
564 following directories:
568 @*Think JTAG Dongle. Files that configure the jtag dongle go here.
570 @* Thing Circuit Board, PWA, PCB, they go by many names. Board files
571 contain initialization items that are specific to a board - for
572 example: The SDRAM initialization sequence for the board, or the type
573 of external flash and what address it is found at. Any initialization
574 sequence to enable that external flash or sdram should be found in the
575 board file. Boards may also contain multiple targets, ie: Two cpus, or
576 a CPU and an FPGA or CPLD.
578 @* Think CHIP. The ``target'' directory represents a jtag tap (or
579 chip) OpenOCD should control, not a board. Two common types of targets
580 are ARM chips and FPGA or CPLD chips.
583 @b{If needed...} The user in their ``openocd.cfg'' file or the board
584 file might override a specific feature in any of the above files by
585 setting a variable or two before sourcing the target file. Or adding
586 various commands specific to their situation.
588 @section Interface Config Files
590 The user should be able to source one of these files via a command like this:
593 source [find interface/FOOBAR.cfg]
595 openocd -f interface/FOOBAR.cfg
598 A preconfigured interface file should exist for every interface in use
599 today, that said, perhaps some interfaces have only been used by the
600 sole developer who created it.
602 @b{FIXME/NOTE:} We need to add support for a variable like TCL variable
603 tcl_platform(platform), it should be called jim_platform (because it
604 is jim, not real tcl) and it should contain 1 of 3 words: ``linux'',
605 ``cygwin'' or ``mingw''
607 Interface files should be found in @t{$(INSTALLDIR)/lib/openocd/interface}
609 @section Board Config Files
611 @b{Note: BOARD directory NEW as of 28/nov/2008}
613 The user should be able to source one of these files via a command like this:
616 source [find board/FOOBAR.cfg]
618 openocd -f board/FOOBAR.cfg
622 The board file should contain one or more @t{source [find
623 target/FOO.cfg]} statements along with any board specific things.
625 In summery the board files should contain (if present)
628 @item External flash configuration (ie: the flash on CS0)
629 @item SDRAM configuration (size, speed, etc)
630 @item Board specific IO configuration (ie: GPIO pins might disable a 2nd flash)
631 @item Multiple TARGET source statements
632 @item All things that are not ``inside a chip''
633 @item Things inside a chip go in a 'target' file
636 @section Target Config Files
638 The user should be able to source one of these files via a command like this:
641 source [find target/FOOBAR.cfg]
643 openocd -f target/FOOBAR.cfg
646 In summery the target files should contain
651 @item Reset Configuration
653 @item CPU/Chip/CPU-Core Specific features
657 @subsection Important variable names
659 By default, the end user should never need to set these
660 variables. However, if the user needs to override a setting they only
661 need to set the variable in a simple way.
665 @* This gives a name to the overall chip, and is used as part of the
666 tap identifier dotted name.
668 @* By default little - unless the chip or board is not normally used that way.
670 @* When OpenOCD examines the JTAG chain, it will attempt to identify
671 every chip. If the @t{-expected-id} is nonzero, OpenOCD attempts
672 to verify the tap id number verses configuration file and may issue an
673 error or warning like this. The hope is this will help pin point
674 problem openocd configurations.
677 Info: JTAG tap: sam7x256.cpu tap/device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
678 Error: ERROR: Tap: sam7x256.cpu - Expected id: 0x12345678, Got: 0x3f0f0f0f
679 Error: ERROR: expected: mfg: 0x33c, part: 0x2345, ver: 0x1
680 Error: ERROR: got: mfg: 0x787, part: 0xf0f0, ver: 0x3
683 @item @b{_TARGETNAME}
684 @* By convention, this variable is created by the target configuration
685 script. The board configuration file may make use of this variable to
686 configure things like a ``reset init'' script, or other things
687 specific to that board and that target.
689 If the chip has 2 targets, use the names @b{_TARGETNAME0},
690 @b{_TARGETNAME1}, ... etc.
692 @b{Remember:} The ``board file'' may include multiple targets.
694 At no time should the name ``target0'' (the default target name if
695 none was specified) be used. The name ``target0'' is a hard coded name
696 - the next target on the board will be some other number.
698 The user (or board file) should reasonably be able to:
701 source [find target/FOO.cfg]
702 $_TARGETNAME configure ... FOO specific parameters
704 source [find target/BAR.cfg]
705 $_TARGETNAME configure ... BAR specific parameters
710 @subsection TCL Variables Guide Line
711 The Full Tcl/Tk language supports ``namespaces'' - JIM-Tcl does not.
713 Thus the rule we follow in OpenOCD is this: Variables that begin with
714 a leading underscore are temporal in nature, and can be modified and
715 used at will within a ?TARGET? configuration file
717 @b{EXAMPLE:} The user should be able to do this:
721 # PXA270 #1 network side, big endian
722 # PXA270 #2 video side, little endian
726 source [find target/pxa270.cfg]
727 # variable: _TARGETNAME = network.cpu
728 # other commands can refer to the "network.cpu" tap.
729 $_TARGETNAME configure .... params for this cpu..
733 source [find target/pxa270.cfg]
734 # variable: _TARGETNAME = video.cpu
735 # other commands can refer to the "video.cpu" tap.
736 $_TARGETNAME configure .... params for this cpu..
740 source [find target/spartan3.cfg]
742 # Since $_TARGETNAME is temporal..
743 # these names still work!
744 network.cpu configure ... params
745 video.cpu configure ... params
749 @subsection Default Value Boiler Plate Code
751 All target configuration files should start with this (or a modified form)
755 if @{ [info exists CHIPNAME] @} @{
756 set _CHIPNAME $CHIPNAME
758 set _CHIPNAME sam7x256
761 if @{ [info exists ENDIAN] @} @{
767 if @{ [info exists CPUTAPID ] @} @{
768 set _CPUTAPID $CPUTAPID
770 set _CPUTAPID 0x3f0f0f0f
775 @subsection Creating Taps
776 After the ``defaults'' are choosen, [see above], the taps are created.
778 @b{SIMPLE example:} such as an Atmel AT91SAM7X256
782 set _TARGETNAME [format "%s.cpu" $_CHIPNAME]
783 jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID
788 This is an SNIP/example for an STR912 - which has 3 internal taps. Key features shown:
791 @item @b{Unform tap names} - See: Tap Naming Convention
792 @item @b{_TARGETNAME} is created at the end where used.
796 if @{ [info exists FLASHTAPID ] @} @{
797 set _FLASHTAPID $FLASHTAPID
799 set _FLASHTAPID 0x25966041
801 jtag newtap $_CHIPNAME flash -irlen 8 -ircapture 0x1 -irmask 0x1 -expected-id $_FLASHTAPID
803 if @{ [info exists CPUTAPID ] @} @{
804 set _CPUTAPID $CPUTAPID
806 set _CPUTAPID 0x25966041
808 jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0xf -irmask 0xe -expected-id $_CPUTAPID
811 if @{ [info exists BSTAPID ] @} @{
812 set _BSTAPID $BSTAPID
814 set _BSTAPID 0x1457f041
816 jtag newtap $_CHIPNAME bs -irlen 5 -ircapture 0x1 -irmask 0x1 -expected-id $_BSTAPID
818 set _TARGETNAME [format "%s.cpu" $_CHIPNAME]
821 @b{Tap Naming Convention}
823 See the command ``jtag newtap'' for detail, but in breif the names you should use are:
831 @item @b{unknownN} - it happens :-(
834 @subsection Reset Configuration
836 Some chips have specific ways the TRST and SRST signals are
837 managed. If these are @b{CHIP SPECIFIC} they go here, if they are
838 @b{BOARD SPECIFIC} they go in the board file.
840 @subsection Work Areas
842 Work areas are small RAM areas used by OpenOCD to speed up downloads,
843 and to download small snippits of code to program flash chips.
845 If the chip includes an form of ``on-chip-ram'' - and many do - define
846 a reasonable work area and use the ``backup'' option.
848 @b{PROBLEMS:} On more complex chips, this ``work area'' may become
849 inaccessable if/when the application code enables or disables the MMU.
851 @subsection ARM Core Specific Hacks
853 If the chip has a DCC, enable it. If the chip is an arm9 with some
854 special high speed download - enable it.
856 If the chip has an ARM ``vector catch'' feature - by defeault enable
857 it for Undefined Instructions, Data Abort, and Prefetch Abort, if the
858 user is really writing a handler for those situations - they can
859 easily disable it. Experiance has shown the ``vector catch'' is
860 helpful - for common programing errors.
862 If present, the MMU, the MPU and the CACHE should be disabled.
864 @subsection Internal Flash Configuration
866 This applies @b{ONLY TO MICROCONTROLLERS} that have flash built in.
868 @b{Never ever} in the ``target configuration file'' define any type of
869 flash that is external to the chip. (For example the BOOT flash on
870 Chip Select 0). The BOOT flash information goes in a board file - not
871 the TARGET (chip) file.
875 @item at91sam7x256 - has 256K flash YES enable it.
876 @item str912 - has flash internal YES enable it.
877 @item imx27 - uses boot flash on CS0 - it goes in the board file.
878 @item pxa270 - again - CS0 flash - it goes in the board file.
882 @chapter About JIM-Tcl
886 OpenOCD includes a small ``TCL Interpreter'' known as JIM-TCL. You can
887 learn more about JIM here: @url{http://jim.berlios.de}
890 @item @b{JIM vrs TCL}
891 @* JIM-TCL is a stripped down version of the well known Tcl language,
892 which can be found here: @url{http://www.tcl.tk}. JIM-Tcl has far
893 fewer features. JIM-Tcl is a single .C file and a single .H file and
894 impliments the basic TCL command set along. In contrast: Tcl 8.6 is a
895 4.2MEG zip file containing 1540 files.
897 @item @b{Missing Features}
898 @* Our practice has been: Add/clone the Real TCL feature if/when
899 needed. We welcome JIM Tcl improvements, not bloat.
902 @* OpenOCD configuration scripts are JIM Tcl Scripts. OpenOCD's
903 command interpretor today (28/nov/2008) is a mixture of (newer)
904 JIM-Tcl commands, and (older) the orginal command interpretor.
907 @* At the openocd telnet command line (or via the GDB mon command) one
908 can type a Tcl for() loop, set variables, etc.
910 @item @b{Historical Note}
911 @* JIM-Tcl was introduced to OpenOCD in Spring 2008.
913 @item @b{Need a Crash Course In TCL?}
914 @* See: @xref{TCL Crash Course}.
918 @node Daemon Configuration
919 @chapter Daemon Configuration
920 The commands here are commonly found inthe openocd.cfg file and are
921 used to specify what TCP/IP ports are used, and how GDB should be
925 This command terminates the configuration stage and
926 enters the normal command mode. This can be useful to add commands to
927 the startup scripts and commands such as resetting the target,
928 programming flash, etc. To reset the CPU upon startup, add "init" and
929 "reset" at the end of the config script or at the end of the OpenOCD
930 command line using the @option{-c} command line switch.
932 If this command does not appear in any startup/configuration file
933 OpenOCD executes the command for you after processing all
934 configuration files and/or command line options.
936 @b{NOTE:} This command normally occurs at or near the end of your
937 openocd.cfg file to force OpenOCD to ``initialize'' and make the
938 targets ready. For example: If your openocd.cfg file needs to
939 read/write memory on your target - the init command must occur before
940 the memory read/write commands.
942 @section TCP/IP Ports
944 @item @b{telnet_port} <@var{number}>
946 @*Intended for a human. Port on which to listen for incoming telnet connections.
948 @item @b{tcl_port} <@var{number}>
950 @*Intended as a machine interface. Port on which to listen for
951 incoming TCL syntax. This port is intended as a simplified RPC
952 connection that can be used by clients to issue commands and get the
953 output from the TCL engine.
955 @item @b{gdb_port} <@var{number}>
957 @*First port on which to listen for incoming GDB connections. The GDB port for the
958 first target will be gdb_port, the second target will listen on gdb_port + 1, and so on.
963 @item @b{gdb_breakpoint_override} <@var{hard|soft|disabled}>
964 @cindex gdb_breakpoint_override
965 @anchor{gdb_breakpoint_override}
966 @*Force breakpoint type for gdb 'break' commands.
967 The raison d'etre for this option is to support GDB GUI's without
968 a hard/soft breakpoint concept where the default OpenOCD and
969 GDB behaviour is not sufficient. Note that GDB will use hardware
970 breakpoints if the memory map has been set up for flash regions.
972 This option replaces older arm7_9 target commands that addressed
975 @item @b{gdb_detach} <@var{resume|reset|halt|nothing}>
977 @*Configures what OpenOCD will do when gdb detaches from the daeman.
978 Default behaviour is <@var{resume}>
980 @item @b{gdb_memory_map} <@var{enable|disable}>
981 @cindex gdb_memory_map
982 @*Set to <@var{enable}> to cause OpenOCD to send the memory configuration to gdb when
983 requested. gdb will then know when to set hardware breakpoints, and program flash
984 using the gdb load command. @option{gdb_flash_program enable} will also need enabling
985 for flash programming to work.
986 Default behaviour is <@var{enable}>
987 @xref{gdb_flash_program}.
989 @item @b{gdb_flash_program} <@var{enable|disable}>
990 @cindex gdb_flash_program
991 @anchor{gdb_flash_program}
992 @*Set to <@var{enable}> to cause OpenOCD to program the flash memory when a
993 vFlash packet is received.
994 Default behaviour is <@var{enable}>
995 @comment END GDB Items
998 @node Interface - Dongle Configuration
999 @chapter Interface - Dongle Configuration
1000 Interface commands are normally found in an interface configuration
1001 file which is sourced by your openocd.cfg file. These commands tell
1002 OpenOCD what type of JTAG dongle you have and how to talk to it.
1003 @section Simple Complete Interface Examples
1004 @b{A Turtelizer FT2232 Based JTAG Dongle}
1008 ft2232_device_desc "Turtelizer JTAG/RS232 Adapter A"
1009 ft2232_layout turtelizer2
1010 ft2232_vid_pid 0x0403 0xbdc8
1021 parport_cable wiggler
1024 @section Interface Conmmand
1026 The interface command tells OpenOCD what type of jtag dongle you are
1027 using. Depending upon the type of dongle, you may need to have one or
1028 more additional commands.
1032 @item @b{interface} <@var{name}>
1034 @*Use the interface driver <@var{name}> to connect to the
1035 target. Currently supported interfaces are
1040 @* PC parallel port bit-banging (Wigglers, PLD download cable, ...)
1042 @item @b{amt_jtagaccel}
1043 @* Amontec Chameleon in its JTAG Accelerator configuration connected to a PC's EPP
1047 @* FTDI FT2232 (USB) based devices using either the open-source libftdi or the binary only
1048 FTD2XX driver. The FTD2XX is superior in performance, but not available on every
1049 platform. The libftdi uses libusb, and should be portable to all systems that provide
1053 @*Cirrus Logic EP93xx based single-board computer bit-banging (in development)
1056 @* ASIX PRESTO USB JTAG programmer.
1059 @* usbprog is a freely programmable USB adapter.
1062 @* Gateworks GW16012 JTAG programmer.
1065 @* Segger jlink usb adapter
1066 @comment - End parameters
1068 @comment - End Interface
1070 @subsection parport options
1073 @item @b{parport_port} <@var{number}>
1074 @cindex parport_port
1075 @*Either the address of the I/O port (default: 0x378 for LPT1) or the number of
1076 the @file{/dev/parport} device
1078 When using PPDEV to access the parallel port, use the number of the parallel port:
1079 @option{parport_port 0} (the default). If @option{parport_port 0x378} is specified
1080 you may encounter a problem.
1081 @item @b{parport_cable} <@var{name}>
1082 @cindex parport_cable
1083 @*The layout of the parallel port cable used to connect to the target.
1084 Currently supported cables are
1088 The original Wiggler layout, also supported by several clones, such
1089 as the Olimex ARM-JTAG
1092 Same as original wiggler except an led is fitted on D5.
1093 @item @b{wiggler_ntrst_inverted}
1094 @cindex wiggler_ntrst_inverted
1095 Same as original wiggler except TRST is inverted.
1096 @item @b{old_amt_wiggler}
1097 @cindex old_amt_wiggler
1098 The Wiggler configuration that comes with Amontec's Chameleon Programmer. The new
1099 version available from the website uses the original Wiggler layout ('@var{wiggler}')
1102 The Amontec Chameleon's CPLD when operated in configuration mode. This is only used to
1103 program the Chameleon itself, not a connected target.
1106 The Xilinx Parallel cable III.
1109 The parallel port adapter found on the 'Karo Triton 1 Development Board'.
1110 This is also the layout used by the HollyGates design
1111 (see @uref{http://www.lartmaker.nl/projects/jtag/}).
1114 The ST Parallel cable.
1117 Same as original wiggler except SRST and TRST connections reversed and
1118 TRST is also inverted.
1121 Altium Universal JTAG cable.
1123 @item @b{parport_write_on_exit} <@var{on}|@var{off}>
1124 @cindex parport_write_on_exit
1125 @*This will configure the parallel driver to write a known value to the parallel
1126 interface on exiting OpenOCD
1129 @subsection amt_jtagaccel options
1131 @item @b{parport_port} <@var{number}>
1132 @cindex parport_port
1133 @*Either the address of the I/O port (default: 0x378 for LPT1) or the number of the
1134 @file{/dev/parport} device
1136 @subsection ft2232 options
1139 @item @b{ft2232_device_desc} <@var{description}>
1140 @cindex ft2232_device_desc
1141 @*The USB device description of the FTDI FT2232 device. If not
1142 specified, the FTDI default value is used. This setting is only valid
1143 if compiled with FTD2XX support.
1145 @b{TODO:} Confirm the following: On windows the name needs to end with
1146 a ``space A''? Or not? It has to do with the FTD2xx driver. When must
1147 this be added and when must it not be added? Why can't the code in the
1148 interface or in openocd automatically add this if needed? -- Duane.
1150 @item @b{ft2232_serial} <@var{serial-number}>
1151 @cindex ft2232_serial
1152 @*The serial number of the FTDI FT2232 device. If not specified, the FTDI default
1154 @item @b{ft2232_layout} <@var{name}>
1155 @cindex ft2232_layout
1156 @*The layout of the FT2232 GPIO signals used to control output-enables and reset
1157 signals. Valid layouts are
1160 "USBJTAG-1" layout described in the original OpenOCD diploma thesis
1162 Amontec JTAGkey and JTAGkey-tiny
1163 @item @b{signalyzer}
1165 @item @b{olimex-jtag}
1168 American Microsystems M5960
1169 @item @b{evb_lm3s811}
1170 Luminary Micro EVB_LM3S811 as a JTAG interface (not onboard processor), no TRST or
1171 SRST signals on external connector
1174 @item @b{stm32stick}
1175 Hitex STM32 Performance Stick
1176 @item @b{flyswatter}
1177 Tin Can Tools Flyswatter
1178 @item @b{turtelizer2}
1179 egnite Software turtelizer2
1184 @item @b{ft2232_vid_pid} <@var{vid}> <@var{pid}>
1185 @*The vendor ID and product ID of the FTDI FT2232 device. If not specified, the FTDI
1186 default values are used. Multiple <@var{vid}>, <@var{pid}> pairs may be given, eg.
1188 ft2232_vid_pid 0x0403 0xcff8 0x15ba 0x0003
1190 @item @b{ft2232_latency} <@var{ms}>
1191 @*On some systems using ft2232 based JTAG interfaces the FT_Read function call in
1192 ft2232_read() fails to return the expected number of bytes. This can be caused by
1193 USB communication delays and has proved hard to reproduce and debug. Setting the
1194 FT2232 latency timer to a larger value increases delays for short USB packages but it
1195 also reduces the risk of timeouts before receiving the expected number of bytes.
1196 The OpenOCD default value is 2 and for some systems a value of 10 has proved useful.
1199 @subsection ep93xx options
1200 @cindex ep93xx options
1201 Currently, there are no options available for the ep93xx interface.
1205 @item @b{jtag_khz} <@var{reset speed kHz}>
1208 It is debatable if this command belongs here - or in a board
1209 configuration file. In fact, in some situations the jtag speed is
1210 changed during the target initialization process (ie: (1) slow at
1211 reset, (2) program the cpu clocks, (3) run fast)
1213 Speed 0 (khz) selects RTCK method. A non-zero speed is in KHZ. Hence: 3000 is 3mhz.
1215 Not all interfaces support ``rtck''. If the interface device can not
1216 support the rate asked for, or can not translate from kHz to
1217 jtag_speed, then an error is returned.
1219 Make sure the jtag clock is no more than @math{1/6th × CPU-Clock}. This is
1220 especially true for synthesized cores (-S). Also see RTCK.
1222 @b{NOTE: Script writers} If the target chip requires/uses RTCK -
1223 please use the command: 'jtag_rclk FREQ'. This TCL proc (in
1224 startup.tcl) attempts to enable RTCK, if that fails it falls back to
1225 the specified frequency.
1228 # Fall back to 3mhz if RCLK is not supported
1232 @item @b{DEPRICATED} @b{jtag_speed} - please use jtag_khz above.
1234 @*Limit the maximum speed of the JTAG interface. Usually, a value of zero means maximum
1235 speed. The actual effect of this option depends on the JTAG interface used.
1237 The speed used during reset can be adjusted using setting jtag_speed during
1238 pre_reset and post_reset events.
1241 @item wiggler: maximum speed / @var{number}
1242 @item ft2232: 6MHz / (@var{number}+1)
1243 @item amt jtagaccel: 8 / 2**@var{number}
1244 @item jlink: maximum speed in kHz (0-12000), 0 will use RTCK
1245 @comment end speed list.
1248 @comment END command list
1251 @node Reset Configuration
1252 @chapter Reset Configuration
1253 @cindex reset configuration
1255 Every system configuration may require a different reset
1256 configuration. This can also be quite confusing. Please see the
1257 various board files for example.
1259 @section jtag_nsrst_delay <@var{ms}>
1260 @cindex jtag_nsrst_delay
1261 @*How long (in milliseconds) OpenOCD should wait after deasserting
1262 nSRST before starting new JTAG operations.
1264 @section jtag_ntrst_delay <@var{ms}>
1265 @cindex jtag_ntrst_delay
1266 @*Same @b{jtag_nsrst_delay}, but for nTRST
1268 The jtag_n[st]rst_delay options are useful if reset circuitry (like a
1269 big resistor/capacitor, reset supervisor, or on-chip features). This
1270 keeps the signal asserted for some time after the external reset got
1273 @section reset_config
1275 @b{Note:} To maintainer types and integrators. Where exactly the
1276 ``reset configuration'' goes is a good question. It touches several
1277 things at once. In the end, if you have a board file - the board file
1278 should define it and assume 100% that the DONGLE supports
1279 anything. However, that does not mean the target should not also make
1280 not of something the silicon vendor has done inside the
1281 chip. @i{Grr.... nothing is every pretty.}
1285 @item Every JTAG Dongle is slightly different, some dongles impliment reset differently.
1286 @item Every board is also slightly different; some boards tie TRST and SRST together.
1287 @item Every chip is slightly different; some chips internally tie the two signals together.
1288 @item Some may not impliment all of the signals the same way.
1289 @item Some signals might be push-pull, others open-drain/collector.
1291 @b{Best Case:} OpenOCD can hold the SRST (push-button-reset), then
1292 reset the TAP via TRST and send commands through the JTAG tap to halt
1293 the CPU at the reset vector before the 1st instruction is executed,
1294 and finally release the SRST signal.
1295 @*Depending upon your board vendor, your chip vendor, etc, these
1296 signals may have slightly different names.
1298 OpenOCD defines these signals in these terms:
1300 @item @b{TRST} - is Tap Reset - and should reset only the TAP.
1301 @item @b{SRST} - is System Reset - typically equal to a reset push button.
1307 @item @b{reset_config} <@var{signals}> [@var{combination}] [@var{trst_type}] [@var{srst_type}]
1308 @cindex reset_config
1309 @* The @t{reset_config} command tells OpenOCD the reset configuration
1310 of your combination of Dongle, Board, and Chips.
1311 If the JTAG interface provides SRST, but the target doesn't connect
1312 that signal properly, then OpenOCD can't use it. <@var{signals}> can
1313 be @option{none}, @option{trst_only}, @option{srst_only} or
1314 @option{trst_and_srst}.
1316 [@var{combination}] is an optional value specifying broken reset
1317 signal implementations. @option{srst_pulls_trst} states that the
1318 testlogic is reset together with the reset of the system (e.g. Philips
1319 LPC2000, "broken" board layout), @option{trst_pulls_srst} says that
1320 the system is reset together with the test logic (only hypothetical, I
1321 haven't seen hardware with such a bug, and can be worked around).
1322 @option{combined} imples both @option{srst_pulls_trst} and
1323 @option{trst_pulls_srst}. The default behaviour if no option given is
1326 The [@var{trst_type}] and [@var{srst_type}] parameters allow the
1327 driver type of the reset lines to be specified. Possible values are
1328 @option{trst_push_pull} (default) and @option{trst_open_drain} for the
1329 test reset signal, and @option{srst_open_drain} (default) and
1330 @option{srst_push_pull} for the system reset. These values only affect
1331 JTAG interfaces with support for different drivers, like the Amontec
1332 JTAGkey and JTAGAccelerator.
1334 @comment - end command
1340 @chapter Tap Creation
1341 @cindex tap creation
1342 @cindex tap configuration
1344 In order for OpenOCD to control a target, a JTAG tap must be
1347 Commands to create taps are normally found in a configuration file and
1348 are not normally typed by a human.
1350 When a tap is created a @b{dotted.name} is created for the tap. Other
1351 commands use that dotted.name to manipulate or refer to the tap.
1355 @item @b{Debug Target} A tap can be used by a GDB debug target
1356 @item @b{Flash Programing} Some chips program the flash via JTAG
1357 @item @b{Boundry Scan} Some chips support boundry scan.
1361 @section jtag newtap
1362 @b{@t{jtag newtap CHIPNAME TAPNAME configparams ....}}
1367 @cindex tap geometry
1369 @comment START options
1372 @* is a symbolic name of the chip.
1374 @* is a symbol name of a tap present on the chip.
1375 @item @b{Required configparams}
1376 @* Every tap has 3 required configparams, and several ``optional
1377 parameters'', the required parameters are:
1378 @comment START REQUIRED
1380 @item @b{-irlen NUMBER} - the length in bits of the instruction register
1381 @item @b{-ircapture NUMBER} - the ID code capture command.
1382 @item @b{-irmask NUMBER} - the corrisponding mask for the ir register.
1383 @comment END REQUIRED
1385 An example of a FOOBAR Tap
1387 jtag newtap foobar tap -irlen 7 -ircapture 0x42 -irmask 0x55
1389 Creates the tap ``foobar.tap'' with the instruction register (IR) is 7
1390 bits long, during Capture-IR 0x42 is loaded into the IR, and bits
1391 [6,4,2,0] are checked.
1393 FIXME: The IDCODE - this was not used in the old code, it should be?
1395 @item @b{Optional configparams}
1396 @comment START Optional
1398 @item @b{-expected-id NUMBER}
1399 @* By default it is zero. If non-zero represents the
1400 expected tap ID used when the Jtag Chain is examined. See below.
1403 @* By default not specified the tap is enabled. Some chips have a
1404 jtag route controller (JRC) that is used to enable and/or disable
1405 specific jtag taps. You can later enable or disable any JTAG tap via
1406 the command @b{jtag tapenable DOTTED.NAME} or @b{jtag tapdisable
1408 @comment END Optional
1411 @comment END OPTIONS
1414 @comment START NOTES
1416 @item @b{Technically}
1417 @* newtap is a sub command of the ``jtag'' command
1418 @item @b{Big Picture Background}
1419 @*GDB Talks to OpenOCD using the GDB protocol via
1420 tcpip. OpenOCD then uses the JTAG interface (the dongle) to
1421 control the JTAG chain on your board. Your board has one or more chips
1422 in a @i{daisy chain configuration}. Each chip may have one or more
1423 jtag taps. GDB ends up talking via OpenOCD to one of the taps.
1424 @item @b{NAME Rules}
1425 @*Names follow ``C'' symbol name rules (start with alpha ...)
1426 @item @b{TAPNAME - Conventions}
1428 @item @b{tap} - should be used only FPGA or CPLD like devices with a single tap.
1429 @item @b{cpu} - the main cpu of the chip, alternatively @b{foo.arm} and @b{foo.dsp}
1430 @item @b{flash} - if the chip has a flash tap, example: str912.flash
1431 @item @b{bs} - for boundary scan if this is a seperate tap.
1432 @item @b{jrc} - for jtag route controller (example: OMAP3530 found on Beagleboards)
1433 @item @b{unknownN} - where N is a number if you have no idea what the tap is for
1434 @item @b{Other names} - Freescale IMX31 has a SDMA (smart dma) with a JTAG tap, that tap should be called the ``sdma'' tap.
1435 @item @b{When in doubt} - use the chip makers name in their data sheet.
1437 @item @b{DOTTED.NAME}
1438 @* @b{CHIPNAME}.@b{TAPNAME} creates the tap name, aka: the
1439 @b{Dotted.Name} is the @b{CHIPNAME} and @b{TAPNAME} combined with a
1440 dot (period); for example: @b{xilinx.tap}, @b{str912.flash},
1441 @b{omap3530.jrc}, or @b{stm32.cpu} The @b{dotted.name} is used in
1442 numerous other places to refer to various taps.
1444 @* The order this command appears via the config files is
1446 @item @b{Multi Tap Example}
1447 @* This example is based on the ST Microsystems STR912. See the ST
1448 document titled: @b{STR91xFAxxx, Section 3.15 Jtag Interface, Page:
1449 28/102, Figure 3: Jtag chaining inside the STR91xFA}.
1451 @url{http://eu.st.com/stonline/products/literature/ds/13495.pdf}
1452 @*@b{checked: 28/nov/2008}
1454 The diagram shows the TDO pin connects to the flash tap, flash TDI
1455 connects to the CPU debug tap, CPU TDI connects to the boundary scan
1456 tap which then connects to the TDI pin.
1460 # create tap: 'str912.flash'
1461 jtag newtap str912 flash ... params ...
1462 # create tap: 'str912.cpu'
1463 jtag newtap str912 cpu ... params ...
1464 # create tap: 'str912.bs'
1465 jtag newtap str912 bs ... params ...
1468 @item @b{Note: Deprecated} - Index Numbers
1469 @* Prior to 28/nov/2008, JTAG taps where numbered from 0..N this
1470 feature is still present, however its use is highly discouraged and
1471 should not be counted upon.
1472 @item @b{Multiple chips}
1473 @* If your board has multiple chips, you should be
1474 able to @b{source} two configuration files, in the proper order, and
1475 have the taps created in the proper order.
1478 @comment at command level
1479 @comment DOCUMENT old command
1480 @section jtag_device - REMOVED
1482 @b{jtag_device} <@var{IR length}> <@var{IR capture}> <@var{IR mask}> <@var{IDCODE instruction}>
1486 @* @b{Removed: 28/nov/2008} This command has been removed and replaced
1487 by the ``jtag newtap'' command. The documentation remains here so that
1488 one can easily convert the old syntax to the new syntax. About the old
1489 syntax: The old syntax is positional, ie: The 4th parameter is the
1490 ``irmask'' The new syntax requires named prefixes, and supports
1491 additional options, for example ``-irmask 4'' Please refer to the
1492 @b{jtag newtap} command for deails.
1494 OLD: jtag_device 8 0x01 0x0e3 0xfe
1495 NEW: jtag newtap CHIPNAME TAPNAME -irlen 8 -ircapture 0xe3 -irmask 0xfe
1498 @section Enable/Disable Taps
1499 @b{Note:} These commands are intended to be used as a machine/script
1500 interface. Humans might find the ``scan_chain'' command more helpful
1501 when querying the state of the JTAG taps.
1503 @b{By default, all taps are enabled}
1506 @item @b{jtag tapenable} @var{DOTTED.NAME}
1507 @item @b{jtag tapdisable} @var{DOTTED.NAME}
1508 @item @b{jtag tapisenabled} @var{DOTTED.NAME}
1513 @cindex route controller
1515 These commands are used when your target has a JTAG Route controller
1516 that effectively adds or removes a tap from the jtag chain in a
1519 The ``standard way'' to remove a tap would be to place the tap in
1520 bypass mode. But with the advent of modern chips, this is not always a
1521 good solution. Some taps operate slowly, others operate fast, and
1522 there are other JTAG clock syncronization problems one must face. To
1523 solve that problem, the JTAG Route controller was introduced. Rather
1524 then ``bypass'' the tap, the tap is completely removed from the
1525 circuit and skipped.
1528 From OpenOCDs view point, a JTAG TAP is in one of 3 states:
1531 @item @b{Enabled - Not In ByPass} and has a variable bit length
1532 @item @b{Enabled - In ByPass} and has a length of exactly 1 bit.
1533 @item @b{Disabled} and has a length of ZERO and is removed from the circuit.
1536 The IEEE JTAG definition has no concept of a ``disabled'' tap.
1537 @b{Historical note:} this feature was added 28/nov/2008
1539 @b{jtag tapisenabled DOTTED.NAME}
1541 This command return 1 if the named tap is currently enabled, 0 if not.
1542 This command exists so that scripts that manipulate a JRC (like the
1543 Omap3530 has) can determine if OpenOCD thinks a tap is presently
1544 enabled, or disabled.
1547 @node Target Configuration
1548 @chapter Target Configuration
1550 This chapter discusses how to create a GDB Debug Target. Before
1551 creating a ``target'' a JTAG Tap DOTTED.NAME must exist first.
1553 @section targets [NAME]
1554 @b{Note:} This command name is PLURAL - not singular.
1556 With NO parameter, this pural @b{targets} command lists all known
1557 targets in a human friendly form.
1559 With a parameter, this pural @b{targets} command sets the current
1560 target to the given name. (ie: If there are multiple debug targets)
1565 CmdName Type Endian ChainPos State
1566 -- ---------- ---------- ---------- -------- ----------
1567 0: target0 arm7tdmi little 0 halted
1570 @section target COMMANDS
1571 @b{Note:} This command name is SINGULAR - not plural. It is used to
1572 manipulate specific targets, to create targets and other things.
1574 Once a target is created, a TARGETNAME (object) command is created;
1575 see below for details.
1577 The TARGET command accepts these sub-commands:
1579 @item @b{create} .. parameters ..
1580 @* creates a new target, See below for details.
1582 @* Lists all supported target types (perhaps some are not yet in this document).
1584 @* Lists all current debug target names, for example: 'str912.cpu' or 'pxa27.cpu' example usage:
1586 foreach t [target names] {
1587 puts [format "Target: %s\n" $t]
1591 @* Returns the current target. OpenOCD always has, or refers to the ``current target'' in some way.
1592 By default, commands like: ``mww'' (used to write memory) operate on the current target.
1593 @item @b{number} @b{NUMBER}
1594 @* Internally OpenOCD maintains a list of targets - in numerical index
1595 (0..N-1) this command returns the name of the target at index N.
1598 set thename [target number $x]
1599 puts [format "Target %d is: %s\n" $x $thename]
1602 @* Returns the number of targets known to OpenOCD (see number above)
1605 set c [target count]
1606 for { set x 0 } { $x < $c } { incr x } {
1607 # Assuming you have created this function
1608 print_target_details $x
1614 @section TARGETNAME (object) commands
1615 @b{Use:} Once a target is created, an ``object name'' that represents the
1616 target is created. By convention, the target name is identical to the
1617 tap name. In a multiple target system, one can preceed many common
1618 commands with a specific target name and effect only that target.
1620 str912.cpu mww 0x1234 0x42
1621 omap3530.cpu mww 0x5555 123
1624 @b{Model:} The Tcl/Tk language has the concept of object commands. A
1625 good example is a on screen button, once a button is created a button
1626 has a name (a path in TK terms) and that name is useable as a 1st
1627 class command. For example in TK, one can create a button and later
1628 configure it like this:
1632 button .foobar -background red -command @{ foo @}
1634 .foobar configure -foreground blue
1636 set x [.foobar cget -background]
1638 puts [format "The button is %s" $x]
1641 In OpenOCDs terms, the ``target'' is an object just like a Tcl/Tk
1642 button. Commands avaialble as a ``target object'' are:
1644 @comment START targetobj commands.
1646 @item @b{configure} - configure the target; see Target Config/Cget Options below
1647 @item @b{cget} - query the target configuration; see Target Config/Cget Options below
1648 @item @b{curstate} - current target state (running, halt, etc)
1650 @* Intended for a human to see/read the currently configure target events.
1651 @item @b{Various Memory Commands} See the ``mww'' command elsewhere.
1652 @comment start memory
1662 @item @b{Memory To Array, Array To Memory}
1663 @* These are aimed at a machine interface to memory
1665 @item @b{mem2array ARRAYNAME WIDTH ADDRESS COUNT}
1666 @item @b{array2mem ARRAYNAME WIDTH ADDRESS COUNT}
1668 @* @b{ARRAYNAME} is the name of an array variable
1669 @* @b{WIDTH} is 8/16/32 - indicating the memory access size
1670 @* @b{ADDRESS} is the target memory address
1671 @* @b{COUNT} is the number of elements to process
1673 @item @b{Used during ``reset''}
1674 @* These commands are used internally by the OpenOCD scripts to deal
1675 with odd reset situations and are not documented here.
1677 @item @b{arp_examine}
1681 @item @b{arp_waitstate}
1683 @item @b{invoke-event} @b{EVENT-NAME}
1684 @* Invokes the specific event manually for the target
1687 @section Target Events
1688 At various times, certian things happen, or you want to happen.
1692 @item What should happen when GDB connects? Should your target reset?
1693 @item When GDB tries to flash the target, do you need to enable the flash via a special command?
1694 @item During reset, do you need to write to certian memory locations to reconfigure the SDRAM?
1697 All of the above items are handled by target events.
1699 To specify an event action, either during target creation, or later
1700 via ``$_TARGETNAME configure'' see this example.
1702 Syntactially, the option is: ``-event NAME BODY'' where NAME is a
1703 target event name, and BODY is a tcl procedure or string of commands
1706 The programers model is the: ``-command'' option used in Tcl/Tk
1707 buttons and events. Below are two identical examples, the first
1708 creates and invokes small procedure. The second inlines the procedure.
1711 proc my_attach_proc @{ @} @{
1715 mychip.cpu configure -event gdb-attach my_attach_proc
1716 mychip.cpu configure -event gdb-attach @{ puts "Reset..." ; reset halt @}
1722 @item @b{debug-halted}
1723 @* The target has halted for debug reasons (ie: breakpoint)
1724 @item @b{debug-resumed}
1725 @* The target has resumed (ie: gdb said run)
1726 @item @b{early-halted}
1727 @* Occurs early in the halt process
1728 @item @b{examine-end}
1729 @* Currently not used (goal: when JTAG examine completes)
1730 @item @b{examine-start}
1731 @* Currently not used (goal: when JTAG examine starts)
1732 @item @b{gdb-attach}
1733 @* When GDB connects
1734 @item @b{gdb-detach}
1735 @* When GDB disconnects
1737 @* When the taret has halted and GDB is not doing anything (see early halt)
1738 @item @b{gdb-flash-erase-start}
1739 @* Before the GDB flash process tries to erase the flash
1740 @item @b{gdb-flash-erase-end}
1741 @* After the GDB flash process has finished erasing the flash
1742 @item @b{gdb-flash-write-start}
1743 @* Before GDB writes to the flash
1744 @item @b{gdb-flash-write-end}
1745 @* After GDB writes to the flash
1747 @* Before the taret steps, gdb is trying to start/resume the tarfget
1749 @* The target has halted
1750 @item @b{old-gdb_program_config}
1751 @* DO NOT USE THIS: Used internally
1752 @item @b{old-pre_resume}
1753 @* DO NOT USE THIS: Used internally
1754 @item @b{reset-assert-pre}
1755 @* Before reset is asserted on the tap.
1756 @item @b{reset-assert-post}
1757 @* Reset is now asserted on the tap.
1758 @item @b{reset-deassert-pre}
1759 @* Reset is about to be released on the tap
1760 @item @b{reset-deassert-post}
1761 @* Reset has been released on the tap
1763 @* Currently not used.
1764 @item @b{reset-halt-post}
1765 @* Currently not usd
1766 @item @b{reset-halt-pre}
1767 @* Currently not used
1768 @item @b{reset-init}
1769 @* Currently not used
1770 @item @b{reset-start}
1771 @* Currently not used
1772 @item @b{reset-wait-pos}
1773 @* Currently not used
1774 @item @b{reset-wait-pre}
1775 @* Currently not used
1776 @item @b{resume-start}
1777 @* Before any target is resumed
1778 @item @b{resume-end}
1779 @* After all targets have resumed
1783 @* Target has resumed
1787 @section target create
1789 @cindex target creation
1792 @b{target} @b{create} <@var{NAME}> <@var{TYPE}> <@var{PARAMS ...}>
1794 @*This command creates a GDB debug target that refers to a specific JTAG tap.
1795 @comment START params
1798 @* Is the name of the debug target. By convention it should be the tap
1799 DOTTED.NAME, this name is also used to create the target object
1802 @* Specifies the target type, ie: arm7tdmi, or cortexM3. Currently supported targes are:
1803 @comment START types
1820 @*PARAMs are various target configure parameters, the following are manditory
1822 @comment START manditory
1824 @item @b{-endian big|little}
1825 @item @b{-chain-position DOTTED.NAME}
1826 @comment end MANDITORY
1831 @section Target Config/Cget Options
1832 These options can be specified when the target is created, or later
1833 via the configure option or to query the target via cget.
1835 @item @b{-type} - returns the target type
1836 @item @b{-event NAME BODY} see Target events
1837 @item @b{-work-area-virt [ADDRESS]} specify/set the work area
1838 @item @b{-work-area-phys [ADDRESS]} specify/set the work area
1839 @item @b{-work-area-size [ADDRESS]} specify/set the work area
1840 @item @b{-work-area-backup [0|1]} does the work area get backed up
1841 @item @b{-endian [big|little]}
1842 @item @b{-variant [NAME]} some chips have varients openocd needs to know about
1843 @item @b{-chain-position DOTTED.NAME} the tap name this target refers to.
1847 for @{ set x 0 @} @{ $x < [target count] @} @{ incr x @} @{
1848 set name [target number $x]
1849 set y [$name cget -endian]
1850 set z [$name cget -type]
1851 puts [format "Chip %d is %s, Endian: %s, type: %s" $x $y $z]
1855 @section Target Varients
1858 @* Unknown (please write me)
1860 @* Unknown (please write me) (simular to arm7tdmi)
1862 @* Varients: @option{arm920t}, @option{arm922t} and @option{arm940t}
1863 This enables the hardware single-stepping support found on these
1868 @* None (this is also used as the ARM946)
1870 @* use variant <@var{-variant lm3s}> when debugging luminary lm3s targets. This will cause
1871 openocd to use a software reset rather than asserting SRST to avoid a issue with clearing
1872 the debug registers. This is fixed in Fury Rev B, DustDevil Rev B, Tempest, these revisions will
1873 be detected and the normal reset behaviour used.
1875 @* Supported variants are @option{ixp42x}, @option{ixp45x}, @option{ixp46x},@option{pxa250}, @option{pxa255}, @option{pxa26x}.
1877 @* Supported variants are @option{arm1136}, @option{arm1156}, @option{arm1176}
1879 @* Use variant @option{ejtag_srst} when debugging targets that do not
1880 provide a functional SRST line on the EJTAG connector. This causes
1881 openocd to instead use an EJTAG software reset command to reset the
1882 processor. You still need to enable @option{srst} on the reset
1883 configuration command to enable openocd hardware reset functionality.
1884 @comment END varients
1886 @section working_area - Command Removed
1887 @cindex working_area
1888 @*@b{Please use the ``$_TARGETNAME configure -work-area-... parameters instead}
1889 @* This documentation remains because there are existing scripts that
1890 still use this that need to be converted.
1892 working_area target# address size backup| [virtualaddress]
1894 @* The target# is a the 0 based target numerical index.
1896 This command specifies a working area for the debugger to use. This
1897 may be used to speed-up downloads to target memory and flash
1898 operations, or to perform otherwise unavailable operations (some
1899 coprocessor operations on ARM7/9 systems, for example). The last
1900 parameter decides whether the memory should be preserved
1901 (<@var{backup}>) or can simply be overwritten (<@var{nobackup}>). If
1902 possible, use a working_area that doesn't need to be backed up, as
1903 performing a backup slows down operation.
1905 @node Flash Configuration
1906 @chapter Flash Programing
1907 @cindex Flash Configuration
1909 @b{Note:} As of 28/nov/2008 OpenOCD does not know how to program a SPI
1910 flash that a micro may boot from. Perhaps you the reader would like to
1911 contribute support for this.
1915 @item Configure via the command @b{flash bank}
1916 @* Normally this is done in a configuration file.
1917 @item Operate on the flash via @b{flash SOMECOMMAND}
1918 @* Often commands to manipulate the flash are typed by a human, or run
1919 via a script in some automated way. For example: To program the boot
1920 flash on your board.
1922 @* Flashing via GDB requires the flash be configured via ``flash
1923 bank'', and the GDB flash features be enabled. See the Daemon
1924 configuration section for more details.
1927 @section Flash commands
1928 @cindex Flash commands
1929 @subsection flash banks
1932 @*List configured flash banks
1933 @*@b{NOTE:} the singular form: 'flash bank' is used to configure the flash banks.
1934 @subsection flash info
1935 @b{flash info} <@var{num}>
1937 @*Print info about flash bank <@option{num}>
1938 @subsection flash probe
1939 @b{flash probe} <@var{num}>
1941 @*Identify the flash, or validate the parameters of the configured flash. Operation
1942 depends on the flash type.
1943 @subsection flash erase_check
1944 @b{flash erase_check} <@var{num}>
1945 @cindex flash erase_check
1946 @*Check erase state of sectors in flash bank <@var{num}>. This is the only operation that
1947 updates the erase state information displayed by @option{flash info}. That means you have
1948 to issue an @option{erase_check} command after erasing or programming the device to get
1949 updated information.
1950 @subsection flash protect_check
1951 @b{flash protect_check} <@var{num}>
1952 @cindex flash protect_check
1953 @*Check protection state of sectors in flash bank <num>.
1954 @option{flash erase_sector} using the same syntax.
1955 @subsection flash erase_sector
1956 @b{flash erase_sector} <@var{num}> <@var{first}> <@var{last}>
1957 @cindex flash erase_sector
1958 @anchor{flash erase_sector}
1959 @*Erase sectors at bank <@var{num}>, starting at sector <@var{first}> up to and including
1960 <@var{last}>. Sector numbering starts at 0. Depending on the flash type, erasing may
1961 require the protection to be disabled first (e.g. Intel Advanced Bootblock flash using
1963 @subsection flash erase_address
1964 @b{flash erase_address} <@var{address}> <@var{length}>
1965 @cindex flash erase_address
1966 @*Erase sectors starting at <@var{address}> for <@var{length}> bytes
1967 @subsection flash write_bank
1968 @b{flash write_bank} <@var{num}> <@var{file}> <@var{offset}>
1969 @cindex flash write_bank
1970 @anchor{flash write_bank}
1971 @*Write the binary <@var{file}> to flash bank <@var{num}>, starting at
1972 <@option{offset}> bytes from the beginning of the bank.
1973 @subsection flash write_image
1974 @b{flash write_image} [@var{erase}] <@var{file}> [@var{offset}] [@var{type}]
1975 @cindex flash write_image
1976 @anchor{flash write_image}
1977 @*Write the image <@var{file}> to the current target's flash bank(s). A relocation
1978 [@var{offset}] can be specified and the file [@var{type}] can be specified
1979 explicitly as @option{bin} (binary), @option{ihex} (Intel hex), @option{elf}
1980 (ELF file) or @option{s19} (Motorola s19). Flash memory will be erased prior to programming
1981 if the @option{erase} parameter is given.
1982 @subsection flash protect
1983 @b{flash protect} <@var{num}> <@var{first}> <@var{last}> <@option{on}|@option{off}>
1984 @cindex flash protect
1985 @*Enable (@var{on}) or disable (@var{off}) protection of flash sectors <@var{first}> to
1986 <@var{last}> of @option{flash bank} <@var{num}>.
1988 @subsection mFlash commands
1989 @cindex mFlash commands
1991 @item @b{mflash probe}
1992 @cindex mflash probe
1994 @item @b{mflash write} <@var{num}> <@var{file}> <@var{offset}>
1995 @cindex mflash write
1996 Write the binary <@var{file}> to mflash bank <@var{num}>, starting at
1997 <@var{offset}> bytes from the beginning of the bank.
1998 @item @b{mflash dump} <@var{num}> <@var{file}> <@var{offset}> <@var{size}>
2000 Dump <size> bytes, starting at <@var{offset}> bytes from the beginning of the <@var{num}> bank
2004 @section flash bank command
2005 The @b{flash bank} command is used to configure one or more flash chips (or banks in openocd terms)
2008 @b{flash bank} <@var{driver}> <@var{base}> <@var{size}> <@var{chip_width}>
2009 <@var{bus_width}> <@var{target#}> [@var{driver_options ...}]
2012 @*Configures a flash bank at <@var{base}> of <@var{size}> bytes and <@var{chip_width}>
2013 and <@var{bus_width}> bytes using the selected flash <driver>.
2015 @subsection External Flash - cfi options
2017 CFI flash are external flash chips - often they are connected to a
2018 specific chip select on the micro. By default at hard reset most
2019 micros have the ablity to ``boot'' from some flash chip - typically
2020 attached to the chips CS0 pin.
2022 For other chip selects: OpenOCD does not know how to configure, or
2023 access a specific chip select. Instead you the human might need to via
2024 other commands (like: mww) configure additional chip selects, or
2025 perhaps configure a GPIO pin that controls the ``write protect'' pin
2028 @b{flash bank cfi} <@var{base}> <@var{size}> <@var{chip_width}> <@var{bus_width}>
2029 <@var{target#}> [@var{jedec_probe}|@var{x16_as_x8}]
2030 @*CFI flashes require the number of the target they're connected to as an additional
2031 argument. The CFI driver makes use of a working area (specified for the target)
2032 to significantly speed up operation.
2034 @var{chip_width} and @var{bus_width} are specified in bytes.
2036 The @var{jedec_probe} option is used to detect certain non-CFI flash roms, like AM29LV010 and similar types.
2040 @subsection Internal Flash (Micro Controllers)
2041 @subsubsection lpc2000 options
2042 @cindex lpc2000 options
2044 @b{flash bank lpc2000} <@var{base}> <@var{size}> 0 0 <@var{target#}> <@var{variant}>
2045 <@var{clock}> [@var{calc_checksum}]
2046 @*LPC flashes don't require the chip and bus width to be specified. Additional
2047 parameters are the <@var{variant}>, which may be @var{lpc2000_v1} (older LPC21xx and LPC22xx)
2048 or @var{lpc2000_v2} (LPC213x, LPC214x, LPC210[123], LPC23xx and LPC24xx), the number
2049 of the target this flash belongs to (first is 0), the frequency at which the core
2050 is currently running (in kHz - must be an integral number), and the optional keyword
2051 @var{calc_checksum}, telling the driver to calculate a valid checksum for the exception
2055 @subsubsection at91sam7 options
2056 @cindex at91sam7 options
2058 @b{flash bank at91sam7} 0 0 0 0 <@var{target#}>
2059 @*AT91SAM7 flashes only require the @var{target#}, all other values are looked up after
2060 reading the chip-id and type.
2062 @subsubsection str7 options
2063 @cindex str7 options
2065 @b{flash bank str7x} <@var{base}> <@var{size}> 0 0 <@var{target#}> <@var{variant}>
2066 @*variant can be either STR71x, STR73x or STR75x.
2068 @subsubsection str9 options
2069 @cindex str9 options
2071 @b{flash bank str9x} <@var{base}> <@var{size}> 0 0 <@var{target#}>
2072 @*The str9 needs the flash controller to be configured prior to Flash programming, eg.
2074 str9x flash_config 0 4 2 0 0x80000
2076 This will setup the BBSR, NBBSR, BBADR and NBBADR registers respectively.
2078 @subsubsection str9 options (str9xpec driver)
2080 @b{flash bank str9xpec} <@var{base}> <@var{size}> 0 0 <@var{target#}>
2081 @*Before using the flash commands the turbo mode will need enabling using str9xpec
2082 @option{enable_turbo} <@var{num>.}
2084 Only use this driver for locking/unlocking the device or configuring the option bytes.
2085 Use the standard str9 driver for programming. @xref{STR9 specific commands}.
2087 @subsubsection stellaris (LM3Sxxx) options
2088 @cindex stellaris (LM3Sxxx) options
2090 @b{flash bank stellaris} <@var{base}> <@var{size}> 0 0 <@var{target#}>
2091 @*stellaris flash plugin only require the @var{target#}.
2093 @subsubsection stm32x options
2094 @cindex stm32x options
2096 @b{flash bank stm32x} <@var{base}> <@var{size}> 0 0 <@var{target#}>
2097 @*stm32x flash plugin only require the @var{target#}.
2099 @subsubsection aduc702x options
2100 @cindex aduc702x options
2102 @b{flash bank aduc702x} <@var{base}> <@var{size}> 0 0 <@var{target#}>
2103 @*aduc702x flash plugin require the flash @var{base}, @var{size} and @var{target#}.
2105 @subsection mFlash configuration
2106 @cindex mFlash configuration
2107 @b{mflash bank} <@var{soc}> <@var{base}> <@var{chip_width}> <@var{bus_width}>
2108 <@var{RST pin}> <@var{WP pin}> <@var{DPD pin}> <@var{target #}>
2110 @*Configures a mflash for <@var{soc}> host bank at
2111 <@var{base}>. <@var{chip_width}> and <@var{bus_width}> are bytes
2112 order. Pin number format is dependent on host GPIO calling convention.
2113 If WP or DPD pin was not used, write -1. Currently, mflash bank
2114 support s3c2440 and pxa270.
2116 (ex. of s3c2440) mflash <@var{RST pin}> is GPIO B1, <@var{WP pin}> and <@var{DPD pin}> are not used.
2118 mflash bank s3c2440 0x10000000 2 2 1b -1 -1 0
2120 (ex. of pxa270) mflash <@var{RST pin}> is GPIO 43, <@var{DPD pin}> is not used and <@var{DPD pin}> is GPIO 51.
2122 mflash bank pxa270 0x08000000 2 2 43 -1 51 0
2125 @section Micro Controller Specific Flash Commands
2127 @subsection AT91SAM7 specific commands
2128 @cindex AT91SAM7 specific commands
2129 The flash configuration is deduced from the chip identification register. The flash
2130 controller handles erases automatically on a page (128/265 byte) basis so erase is
2131 not necessary for flash programming. AT91SAM7 processors with less than 512K flash
2132 only have a single flash bank embedded on chip. AT91SAM7xx512 have two flash planes
2133 that can be erased separatly. Only an EraseAll command is supported by the controller
2134 for each flash plane and this is called with
2136 @item @b{flash erase} <@var{num}> @var{first_plane} @var{last_plane}
2137 @*bulk erase flash planes first_plane to last_plane.
2138 @item @b{at91sam7 gpnvm} <@var{num}> <@var{bit}> <@option{set}|@option{clear}>
2139 @cindex at91sam7 gpnvm
2140 @*set or clear a gpnvm bit for the processor
2143 @subsection STR9 specific commands
2144 @cindex STR9 specific commands
2145 @anchor{STR9 specific commands}
2146 These are flash specific commands when using the str9xpec driver.
2148 @item @b{str9xpec enable_turbo} <@var{num}>
2149 @cindex str9xpec enable_turbo
2150 @*enable turbo mode, simply this will remove the str9 from the chain and talk
2151 directly to the embedded flash controller.
2152 @item @b{str9xpec disable_turbo} <@var{num}>
2153 @cindex str9xpec disable_turbo
2154 @*restore the str9 into jtag chain.
2155 @item @b{str9xpec lock} <@var{num}>
2156 @cindex str9xpec lock
2157 @*lock str9 device. The str9 will only respond to an unlock command that will
2159 @item @b{str9xpec unlock} <@var{num}>
2160 @cindex str9xpec unlock
2161 @*unlock str9 device.
2162 @item @b{str9xpec options_read} <@var{num}>
2163 @cindex str9xpec options_read
2164 @*read str9 option bytes.
2165 @item @b{str9xpec options_write} <@var{num}>
2166 @cindex str9xpec options_write
2167 @*write str9 option bytes.
2170 Note: Before using the str9xpec driver here is some background info to help
2171 you better understand how the drivers works. Openocd has two flash drivers for
2175 Standard driver @option{str9x} programmed via the str9 core. Normally used for
2176 flash programming as it is faster than the @option{str9xpec} driver.
2178 Direct programming @option{str9xpec} using the flash controller, this is
2179 ISC compilant (IEEE 1532) tap connected in series with the str9 core. The str9
2180 core does not need to be running to program using this flash driver. Typical use
2181 for this driver is locking/unlocking the target and programming the option bytes.
2184 Before we run any cmds using the @option{str9xpec} driver we must first disable
2185 the str9 core. This example assumes the @option{str9xpec} driver has been
2186 configured for flash bank 0.
2188 # assert srst, we do not want core running
2189 # while accessing str9xpec flash driver
2191 # turn off target polling
2194 str9xpec enable_turbo 0
2196 str9xpec options_read 0
2197 # re-enable str9 core
2198 str9xpec disable_turbo 0
2202 The above example will read the str9 option bytes.
2203 When performing a unlock remember that you will not be able to halt the str9 - it
2204 has been locked. Halting the core is not required for the @option{str9xpec} driver
2205 as mentioned above, just issue the cmds above manually or from a telnet prompt.
2207 @subsection STR9 configuration
2208 @cindex STR9 configuration
2210 @item @b{str9x flash_config} <@var{bank}> <@var{BBSR}> <@var{NBBSR}>
2211 <@var{BBADR}> <@var{NBBADR}>
2212 @cindex str9x flash_config
2213 @*Configure str9 flash controller.
2215 eg. str9x flash_config 0 4 2 0 0x80000
2217 BBSR - Boot Bank Size register
2218 NBBSR - Non Boot Bank Size register
2219 BBADR - Boot Bank Start Address register
2220 NBBADR - Boot Bank Start Address register
2224 @subsection STR9 option byte configuration
2225 @cindex STR9 option byte configuration
2227 @item @b{str9xpec options_cmap} <@var{num}> <@option{bank0}|@option{bank1}>
2228 @cindex str9xpec options_cmap
2229 @*configure str9 boot bank.
2230 @item @b{str9xpec options_lvdthd} <@var{num}> <@option{2.4v}|@option{2.7v}>
2231 @cindex str9xpec options_lvdthd
2232 @*configure str9 lvd threshold.
2233 @item @b{str9xpec options_lvdsel} <@var{num}> <@option{vdd}|@option{vdd_vddq}>
2234 @cindex str9xpec options_lvdsel
2235 @*configure str9 lvd source.
2236 @item @b{str9xpec options_lvdwarn} <@var{bank}> <@option{vdd}|@option{vdd_vddq}>
2237 @cindex str9xpec options_lvdwarn
2238 @*configure str9 lvd reset warning source.
2241 @subsection STM32x specific commands
2242 @cindex STM32x specific commands
2244 These are flash specific commands when using the stm32x driver.
2246 @item @b{stm32x lock} <@var{num}>
2248 @*lock stm32 device.
2249 @item @b{stm32x unlock} <@var{num}>
2250 @cindex stm32x unlock
2251 @*unlock stm32 device.
2252 @item @b{stm32x options_read} <@var{num}>
2253 @cindex stm32x options_read
2254 @*read stm32 option bytes.
2255 @item @b{stm32x options_write} <@var{num}> <@option{SWWDG}|@option{HWWDG}>
2256 <@option{RSTSTNDBY}|@option{NORSTSTNDBY}> <@option{RSTSTOP}|@option{NORSTSTOP}>
2257 @cindex stm32x options_write
2258 @*write stm32 option bytes.
2259 @item @b{stm32x mass_erase} <@var{num}>
2260 @cindex stm32x mass_erase
2261 @*mass erase flash memory.
2264 @subsection Stellaris specific commands
2265 @cindex Stellaris specific commands
2267 These are flash specific commands when using the Stellaris driver.
2269 @item @b{stellaris mass_erase} <@var{num}>
2270 @cindex stellaris mass_erase
2271 @*mass erase flash memory.
2275 @node General Commands
2276 @chapter General Commands
2279 The commands documented in this chapter here are common commands that
2280 you a human may want to type and see the output of. Configuration type
2281 commands are documented elsewhere.
2285 @item @b{Source Of Commands}
2286 @* OpenOCD commands can occur in a configuration script (discussed
2287 elsewhere) or typed manually by a human or supplied programatically,
2288 or via one of several Tcp/Ip Ports.
2290 @item @b{From the human}
2291 @* A human should interact with the Telnet interface (default port: 4444,
2292 or via GDB, default port 3333)
2294 To issue commands from within a GDB session, use the @option{monitor}
2295 command, e.g. use @option{monitor poll} to issue the @option{poll}
2296 command. All output is relayed through the GDB session.
2298 @item @b{Machine Interface}
2299 The TCL interface intent is to be a machine interface. The default TCL
2304 @section Daemon Commands
2307 @b{sleep} <@var{msec}>
2309 @*Wait for n milliseconds before resuming. Useful in connection with script files
2310 (@var{script} command and @var{target_script} configuration).
2315 @*Close the OpenOCD daemon, disconnecting all clients (GDB, Telnet, Other).
2317 @subsection debug_level [@var{n}]
2319 @anchor{debug_level}
2320 @*Display or adjust debug level to n<0-3>
2322 @subsection fast [@var{enable|disable}]
2324 @*Default disabled. Set default behaviour of OpenOCD to be "fast and dangerous". For instance ARM7/9 DCC memory
2325 downloads and fast memory access will work if the JTAG interface isn't too fast and
2326 the core doesn't run at a too low frequency. Note that this option only changes the default
2327 and that the indvidual options, like DCC memory downloads, can be enabled and disabled
2330 The target specific "dangerous" optimisation tweaking options may come and go
2331 as more robust and user friendly ways are found to ensure maximum throughput
2332 and robustness with a minimum of configuration.
2334 Typically the "fast enable" is specified first on the command line:
2337 openocd -c "fast enable" -c "interface dummy" -f target/str710.cfg
2340 @subsection log_output <@var{file}>
2342 @*Redirect logging to <file> (default: stderr)
2344 @subsection script <@var{file}>
2346 @*Execute commands from <file>
2347 Also see: ``source [find FILENAME]''
2349 @section Target state handling
2350 @subsection power <@var{on}|@var{off}>
2352 @*Turn power switch to target on/off.
2353 No arguments: print status.
2354 Not all interfaces support this.
2356 @subsection reg [@option{#}|@option{name}] [value]
2358 @*Access a single register by its number[@option{#}] or by its [@option{name}].
2359 No arguments: list all available registers for the current target.
2360 Number or name argument: display a register
2361 Number or name and value arguments: set register value
2363 @subsection poll [@option{on}|@option{off}]
2365 @*Poll the target for its current state. If the target is in debug mode, architecture
2366 specific information about the current state is printed. An optional parameter
2367 allows continuous polling to be enabled and disabled.
2369 @subsection halt [@option{ms}]
2371 @*Send a halt request to the target and wait for it to halt for up to [@option{ms}] milliseconds.
2372 Default [@option{ms}] is 5 seconds if no arg given.
2373 Optional arg @option{ms} is a timeout in milliseconds. Using 0 as the [@option{ms}]
2374 will stop OpenOCD from waiting.
2376 @subsection wait_halt [@option{ms}]
2378 @*Wait for the target to enter debug mode. Optional [@option{ms}] is
2379 a timeout in milliseconds. Default [@option{ms}] is 5 seconds if no
2382 @subsection resume [@var{address}]
2384 @*Resume the target at its current code position, or at an optional address.
2385 OpenOCD will wait 5 seconds for the target to resume.
2387 @subsection step [@var{address}]
2389 @*Single-step the target at its current code position, or at an optional address.
2391 @subsection reset [@option{run}|@option{halt}|@option{init}]
2393 @*Perform a hard-reset. The optional parameter specifies what should happen after the reset.
2395 With no arguments a "reset run" is executed
2399 @*Let the target run.
2402 @*Immediately halt the target (works only with certain configurations).
2405 @*Immediately halt the target, and execute the reset script (works only with certain
2409 @subsection soft_reset_halt
2411 @*Requesting target halt and executing a soft reset. This often used
2412 when a target cannot be reset and halted. The target, after reset is
2413 released begins to execute code. OpenOCD attempts to stop the CPU and
2414 then sets the Program counter back at the reset vector. Unfortunatlly
2415 that code that was executed may have left hardware in an unknown
2419 @section Memory access commands
2421 display available ram memory.
2422 @subsection Memory Peek/Poke type commands
2423 These commands allow accesses of a specific size to the memory
2424 system. Often these are used to configure the current target in some
2425 special way. For example - one may need to write certian values to the
2426 SDRAM controller to enable SDRAM.
2429 @item To change the current target see the ``targets'' (plural) command
2430 @item In system level scripts these commands are depricated, please use the TARGET object versions.
2434 @item @b{mdw} <@var{addr}> [@var{count}]
2436 @*display memory words (32bit)
2437 @item @b{mdh} <@var{addr}> [@var{count}]
2439 @*display memory half-words (16bit)
2440 @item @b{mdb} <@var{addr}> [@var{count}]
2442 @*display memory bytes (8bit)
2443 @item @b{mww} <@var{addr}> <@var{value}>
2445 @*write memory word (32bit)
2446 @item @b{mwh} <@var{addr}> <@var{value}>
2448 @*write memory half-word (16bit)
2449 @item @b{mwb} <@var{addr}> <@var{value}>
2451 @*write memory byte (8bit)
2454 @section Image Loading Commands
2455 @subsection load_image
2456 @b{load_image} <@var{file}> <@var{address}> [@option{bin}|@option{ihex}|@option{elf}]
2459 @*Load image <@var{file}> to target memory at <@var{address}>
2460 @subsection fast_load_image
2461 @b{fast_load_image} <@var{file}> <@var{address}> [@option{bin}|@option{ihex}|@option{elf}]
2462 @cindex fast_load_image
2463 @anchor{fast_load_image}
2464 @*Normally you should be using @b{load_image} or GDB load. However, for
2465 testing purposes or when IO overhead is significant(OpenOCD running on embedded
2466 host), then storing the image in memory and uploading the image to the target
2467 can be a way to upload e.g. multiple debug sessions when the binary does not change.
2468 Arguments as @b{load_image}, but image is stored in OpenOCD host
2469 memory, i.e. does not affect target. This approach is also useful when profiling
2470 target programming performance as IO and target programming can easily be profiled
2472 @subsection fast_load
2476 @*Loads image stored in memory by @b{fast_load_image} to current target. Must be preceeded by fast_load_image.
2477 @subsection dump_image
2478 @b{dump_image} <@var{file}> <@var{address}> <@var{size}>
2481 @*Dump <@var{size}> bytes of target memory starting at <@var{address}> to a
2482 (binary) <@var{file}>.
2483 @subsection verify_image
2484 @b{verify_image} <@var{file}> <@var{address}> [@option{bin}|@option{ihex}|@option{elf}]
2485 @cindex verify_image
2486 @*Verify <@var{file}> against target memory starting at <@var{address}>.
2487 This will first attempt comparison using a crc checksum, if this fails it will try a binary compare.
2490 @section Breakpoint commands
2491 @cindex Breakpoint commands
2493 @item @b{bp} <@var{addr}> <@var{len}> [@var{hw}]
2495 @*set breakpoint <address> <length> [hw]
2496 @item @b{rbp} <@var{addr}>
2498 @*remove breakpoint <adress>
2499 @item @b{wp} <@var{addr}> <@var{len}> <@var{r}|@var{w}|@var{a}> [@var{value}] [@var{mask}]
2501 @*set watchpoint <address> <length> <r/w/a> [value] [mask]
2502 @item @b{rwp} <@var{addr}>
2504 @*remove watchpoint <adress>
2507 @section Misc Commands
2508 @cindex Other Target Commands
2510 @item @b{profile} <@var{seconds}> <@var{gmon.out}>
2512 Profiling samples the CPU PC as quickly as OpenOCD is able, which will be used as a random sampling of PC.
2515 @section Target Specific Commands
2516 @cindex Target Specific Commands
2520 @section Architecture Specific Commands
2521 @cindex Architecture Specific Commands
2523 @subsection ARMV4/5 specific commands
2524 @cindex ARMV4/5 specific commands
2526 These commands are specific to ARM architecture v4 and v5, like all ARM7/9 systems
2527 or Intel XScale (XScale isn't supported yet).
2529 @item @b{armv4_5 reg}
2531 @*Display a list of all banked core registers, fetching the current value from every
2532 core mode if necessary. OpenOCD versions before rev. 60 didn't fetch the current
2534 @item @b{armv4_5 core_mode} [@var{arm}|@var{thumb}]
2535 @cindex armv4_5 core_mode
2536 @*Displays the core_mode, optionally changing it to either ARM or Thumb mode.
2537 The target is resumed in the currently set @option{core_mode}.
2540 @subsection ARM7/9 specific commands
2541 @cindex ARM7/9 specific commands
2543 These commands are specific to ARM7 and ARM9 targets, like ARM7TDMI, ARM720t,
2544 ARM920t or ARM926EJ-S.
2546 @item @b{arm7_9 dbgrq} <@var{enable}|@var{disable}>
2547 @cindex arm7_9 dbgrq
2548 @*Enable use of the DBGRQ bit to force entry into debug mode. This should be
2549 safe for all but ARM7TDMI--S cores (like Philips LPC).
2550 @item @b{arm7_9 fast_memory_access} <@var{enable}|@var{disable}>
2551 @cindex arm7_9 fast_memory_access
2552 @anchor{arm7_9 fast_memory_access}
2553 @*Allow OpenOCD to read and write memory without checking completion of
2554 the operation. This provides a huge speed increase, especially with USB JTAG
2555 cables (FT2232), but might be unsafe if used with targets running at a very low
2556 speed, like the 32kHz startup clock of an AT91RM9200.
2557 @item @b{arm7_9 dcc_downloads} <@var{enable}|@var{disable}>
2558 @cindex arm7_9 dcc_downloads
2559 @*Enable the use of the debug communications channel (DCC) to write larger (>128 byte)
2560 amounts of memory. DCC downloads offer a huge speed increase, but might be potentially
2561 unsafe, especially with targets running at a very low speed. This command was introduced
2562 with OpenOCD rev. 60.
2565 @subsection ARM720T specific commands
2566 @cindex ARM720T specific commands
2569 @item @b{arm720t cp15} <@var{num}> [@var{value}]
2570 @cindex arm720t cp15
2571 @*display/modify cp15 register <@option{num}> [@option{value}].
2572 @item @b{arm720t md<bhw>_phys} <@var{addr}> [@var{count}]
2573 @cindex arm720t md<bhw>_phys
2574 @*Display memory at physical address addr.
2575 @item @b{arm720t mw<bhw>_phys} <@var{addr}> <@var{value}>
2576 @cindex arm720t mw<bhw>_phys
2577 @*Write memory at physical address addr.
2578 @item @b{arm720t virt2phys} <@var{va}>
2579 @cindex arm720t virt2phys
2580 @*Translate a virtual address to a physical address.
2583 @subsection ARM9TDMI specific commands
2584 @cindex ARM9TDMI specific commands
2587 @item @b{arm9tdmi vector_catch} <@var{all}|@var{none}>
2588 @cindex arm9tdmi vector_catch
2589 @*Catch arm9 interrupt vectors, can be @option{all} @option{none} or any of the following:
2590 @option{reset} @option{undef} @option{swi} @option{pabt} @option{dabt} @option{reserved}
2591 @option{irq} @option{fiq}.
2593 Can also be used on other arm9 based cores, arm966, arm920t and arm926ejs.
2596 @subsection ARM966E specific commands
2597 @cindex ARM966E specific commands
2600 @item @b{arm966e cp15} <@var{num}> [@var{value}]
2601 @cindex arm966e cp15
2602 @*display/modify cp15 register <@option{num}> [@option{value}].
2605 @subsection ARM920T specific commands
2606 @cindex ARM920T specific commands
2609 @item @b{arm920t cp15} <@var{num}> [@var{value}]
2610 @cindex arm920t cp15
2611 @*display/modify cp15 register <@option{num}> [@option{value}].
2612 @item @b{arm920t cp15i} <@var{num}> [@var{value}] [@var{address}]
2613 @cindex arm920t cp15i
2614 @*display/modify cp15 (interpreted access) <@option{opcode}> [@option{value}] [@option{address}]
2615 @item @b{arm920t cache_info}
2616 @cindex arm920t cache_info
2617 @*Print information about the caches found. This allows you to see if your target
2618 is a ARM920T (2x16kByte cache) or ARM922T (2x8kByte cache).
2619 @item @b{arm920t md<bhw>_phys} <@var{addr}> [@var{count}]
2620 @cindex arm920t md<bhw>_phys
2621 @*Display memory at physical address addr.
2622 @item @b{arm920t mw<bhw>_phys} <@var{addr}> <@var{value}>
2623 @cindex arm920t mw<bhw>_phys
2624 @*Write memory at physical address addr.
2625 @item @b{arm920t read_cache} <@var{filename}>
2626 @cindex arm920t read_cache
2627 @*Dump the content of ICache and DCache to a file.
2628 @item @b{arm920t read_mmu} <@var{filename}>
2629 @cindex arm920t read_mmu
2630 @*Dump the content of the ITLB and DTLB to a file.
2631 @item @b{arm920t virt2phys} <@var{va}>
2632 @cindex arm920t virt2phys
2633 @*Translate a virtual address to a physical address.
2636 @subsection ARM926EJS specific commands
2637 @cindex ARM926EJS specific commands
2640 @item @b{arm926ejs cp15} <@var{num}> [@var{value}]
2641 @cindex arm926ejs cp15
2642 @*display/modify cp15 register <@option{num}> [@option{value}].
2643 @item @b{arm926ejs cache_info}
2644 @cindex arm926ejs cache_info
2645 @*Print information about the caches found.
2646 @item @b{arm926ejs md<bhw>_phys} <@var{addr}> [@var{count}]
2647 @cindex arm926ejs md<bhw>_phys
2648 @*Display memory at physical address addr.
2649 @item @b{arm926ejs mw<bhw>_phys} <@var{addr}> <@var{value}>
2650 @cindex arm926ejs mw<bhw>_phys
2651 @*Write memory at physical address addr.
2652 @item @b{arm926ejs virt2phys} <@var{va}>
2653 @cindex arm926ejs virt2phys
2654 @*Translate a virtual address to a physical address.
2657 @subsection CORTEX_M3 specific commands
2658 @cindex CORTEX_M3 specific commands
2661 @item @b{cortex_m3 maskisr} <@var{on}|@var{off}>
2662 @cindex cortex_m3 maskisr
2663 @*Enable masking (disabling) interrupts during target step/resume.
2667 @section Debug commands
2668 @cindex Debug commands
2669 The following commands give direct access to the core, and are most likely
2670 only useful while debugging OpenOCD.
2672 @item @b{arm7_9 write_xpsr} <@var{32-bit value}> <@option{0=cpsr}, @option{1=spsr}>
2673 @cindex arm7_9 write_xpsr
2674 @*Immediately write either the current program status register (CPSR) or the saved
2675 program status register (SPSR), without changing the register cache (as displayed
2676 by the @option{reg} and @option{armv4_5 reg} commands).
2677 @item @b{arm7_9 write_xpsr_im8} <@var{8-bit value}> <@var{rotate 4-bit}>
2678 <@var{0=cpsr},@var{1=spsr}>
2679 @cindex arm7_9 write_xpsr_im8
2680 @*Write the 8-bit value rotated right by 2*rotate bits, using an immediate write
2681 operation (similar to @option{write_xpsr}).
2682 @item @b{arm7_9 write_core_reg} <@var{num}> <@var{mode}> <@var{value}>
2683 @cindex arm7_9 write_core_reg
2684 @*Write a core register, without changing the register cache (as displayed by the
2685 @option{reg} and @option{armv4_5 reg} commands). The <@var{mode}> argument takes the
2686 encoding of the [M4:M0] bits of the PSR.
2689 @section Target Requests
2690 @cindex Target Requests
2691 OpenOCD can handle certain target requests, currently debugmsg are only supported for arm7_9 and cortex_m3.
2692 See libdcc in the contrib dir for more details.
2694 @item @b{target_request debugmsgs} <@var{enable}|@var{disable}>
2695 @cindex target_request debugmsgs
2696 @*Enable/disable target debugmsgs requests. debugmsgs enable messages to be sent to the debugger while the target is running.
2700 @chapter JTAG Commands
2701 @cindex JTAG commands
2702 Generally most people will not use the bulk of these commands. They
2703 are mostly used by the OpenOCD developers or those who need to
2704 directly manipulate the JTAG taps.
2706 In general these commands control JTAG taps at a very low level. For
2707 example if you need to control a JTAG Route Controller (ie: the
2708 OMAP3530 on the Beagle Board has one) you might use these commands in
2709 a script or an event procedure.
2712 @item @b{scan_chain}
2714 @*Print current scan chain configuration.
2715 @item @b{jtag_reset} <@var{trst}> <@var{srst}>
2717 @*Toggle reset lines.
2718 @item @b{endstate} <@var{tap_state}>
2720 @*Finish JTAG operations in <@var{tap_state}>.
2721 @item @b{runtest} <@var{num_cycles}>
2723 @*Move to Run-Test/Idle, and execute <@var{num_cycles}>
2724 @item @b{statemove} [@var{tap_state}]
2726 @*Move to current endstate or [@var{tap_state}]
2727 @item @b{irscan} <@var{device}> <@var{instr}> [@var{dev2}] [@var{instr2}] ...
2729 @*Execute IR scan <@var{device}> <@var{instr}> [@var{dev2}] [@var{instr2}] ...
2730 @item @b{drscan} <@var{device}> [@var{dev2}] [@var{var2}] ...
2732 @*Execute DR scan <@var{device}> [@var{dev2}] [@var{var2}] ...
2733 @item @b{verify_ircapture} <@option{enable}|@option{disable}>
2734 @cindex verify_ircapture
2735 @*Verify value captured during Capture-IR. Default is enabled.
2736 @item @b{var} <@var{name}> [@var{num_fields}|@var{del}] [@var{size1}] ...
2738 @*Allocate, display or delete variable <@var{name}> [@var{num_fields}|@var{del}] [@var{size1}] ...
2739 @item @b{field} <@var{var}> <@var{field}> [@var{value}|@var{flip}]
2741 Display/modify variable field <@var{var}> <@var{field}> [@var{value}|@var{flip}].
2748 If OpenOCD runs on an embedded host(as ZY1000 does), then tftp can
2749 be used to access files on PCs(either developer PC or some other PC).
2751 The way this works on the ZY1000 is to prefix a filename by
2752 "/tftp/ip/" and append the tftp path on the tftp
2753 server(tftpd). E.g. "load_image /tftp/10.0.0.96/c:\temp\abc.elf" will
2754 load c:\temp\abc.elf from the developer pc (10.0.0.96) into memory as
2755 if the file was hosted on the embedded host.
2757 In order to achieve decent performance, you must choose a tftp server
2758 that supports a packet size bigger than the default packet size(512 bytes). There
2759 are numerous tftp servers out there(free and commercial) and you will have to do
2760 a bit of googling to find something that fits your requirements.
2762 @node Sample Scripts
2763 @chapter Sample Scripts
2766 This page shows how to use the target library.
2768 The configuration script can be divided in the following section:
2770 @item daemon configuration
2772 @item jtag scan chain
2773 @item target configuration
2774 @item flash configuration
2777 Detailed information about each section can be found at OpenOCD configuration.
2779 @section AT91R40008 example
2780 @cindex AT91R40008 example
2781 To start OpenOCD with a target script for the AT91R40008 CPU and reset
2782 the CPU upon startup of the OpenOCD daemon.
2784 openocd -f interface/parport.cfg -f target/at91r40008.cfg -c init -c reset
2788 @node GDB and OpenOCD
2789 @chapter GDB and OpenOCD
2790 @cindex GDB and OpenOCD
2791 OpenOCD complies with the remote gdbserver protocol, and as such can be used
2792 to debug remote targets.
2794 @section Connecting to gdb
2795 @cindex Connecting to gdb
2796 Use GDB 6.7 or newer with OpenOCD if you run into trouble. For
2797 instance 6.3 has a known bug where it produces bogus memory access
2798 errors, which has since been fixed: look up 1836 in
2799 @url{http://sourceware.org/cgi-bin/gnatsweb.pl?database=gdb}
2802 A connection is typically started as follows:
2804 target remote localhost:3333
2806 This would cause gdb to connect to the gdbserver on the local pc using port 3333.
2808 To see a list of available OpenOCD commands type @option{monitor help} on the
2811 OpenOCD supports the gdb @option{qSupported} packet, this enables information
2812 to be sent by the gdb server (openocd) to gdb. Typical information includes
2813 packet size and device memory map.
2815 Previous versions of OpenOCD required the following gdb options to increase
2816 the packet size and speed up gdb communication.
2818 set remote memory-write-packet-size 1024
2819 set remote memory-write-packet-size fixed
2820 set remote memory-read-packet-size 1024
2821 set remote memory-read-packet-size fixed
2823 This is now handled in the @option{qSupported} PacketSize.
2825 @section Programming using gdb
2826 @cindex Programming using gdb
2828 By default the target memory map is sent to gdb, this can be disabled by
2829 the following OpenOCD config option:
2831 gdb_memory_map disable
2833 For this to function correctly a valid flash config must also be configured
2834 in OpenOCD. For faster performance you should also configure a valid
2837 Informing gdb of the memory map of the target will enable gdb to protect any
2838 flash area of the target and use hardware breakpoints by default. This means
2839 that the OpenOCD option @option{gdb_breakpoint_override} is not required when
2840 using a memory map. @xref{gdb_breakpoint_override}.
2842 To view the configured memory map in gdb, use the gdb command @option{info mem}
2843 All other unasigned addresses within gdb are treated as RAM.
2845 GDB 6.8 and higher set any memory area not in the memory map as inaccessible,
2846 this can be changed to the old behaviour by using the following gdb command.
2848 set mem inaccessible-by-default off
2851 If @option{gdb_flash_program enable} is also used, gdb will be able to
2852 program any flash memory using the vFlash interface.
2854 gdb will look at the target memory map when a load command is given, if any
2855 areas to be programmed lie within the target flash area the vFlash packets
2858 If the target needs configuring before gdb programming, an event
2859 script can be executed.
2861 $_TARGETNAME configure -event EVENTNAME BODY
2864 To verify any flash programming the gdb command @option{compare-sections}
2867 @node TCL scripting API
2868 @chapter TCL scripting API
2869 @cindex TCL scripting API
2872 The commands are stateless. E.g. the telnet command line has a concept
2873 of currently active target, the Tcl API proc's take this sort of state
2874 information as an argument to each proc.
2876 There are three main types of return values: single value, name value
2877 pair list and lists.
2879 Name value pair. The proc 'foo' below returns a name/value pair
2885 > set foo(you) Oyvind
2886 > set foo(mouse) Micky
2887 > set foo(duck) Donald
2895 me Duane you Oyvind mouse Micky duck Donald
2897 Thus, to get the names of the associative array is easy:
2899 foreach { name value } [set foo] {
2900 puts "Name: $name, Value: $value"
2904 Lists returned must be relatively small. Otherwise a range
2905 should be passed in to the proc in question.
2907 Low level commands are prefixed with "openocd_", e.g. openocd_flash_banks
2908 is the low level API upon which "flash banks" is implemented.
2911 @item @b{ocd_mem2array} <@var{varname}> <@var{width}> <@var{addr}> <@var{nelems}>
2913 Read memory and return as a TCL array for script processing
2914 @item @b{ocd_array2mem} <@var{varname}> <@var{width}> <@var{addr}> <@var{nelems}>
2916 Convert a TCL array to memory locations and write the values
2917 @item @b{ocd_flash_banks} <@var{driver}> <@var{base}> <@var{size}> <@var{chip_width}> <@var{bus_width}> <@var{target}> [@option{driver options} ...]
2919 Return information about the flash banks
2922 OpenOCD commands can consist of two words, e.g. "flash banks". The
2923 startup.tcl "unknown" proc will translate this into a tcl proc
2924 called "flash_banks".
2928 @chapter Deprecated/Removed Commands
2929 @cindex Deprecated/Removed Commands
2930 Certain OpenOCD commands have been deprecated/removed during the various revisions.
2933 @item @b{arm7_9 fast_writes}
2934 @cindex arm7_9 fast_writes
2935 @*use @option{arm7_9 fast_memory_access} command with same args. @xref{arm7_9 fast_memory_access}.
2936 @item @b{arm7_9 force_hw_bkpts}
2937 @cindex arm7_9 force_hw_bkpts
2938 @*Use @option{gdb_breakpoint_override} instead. Note that GDB will use hardware breakpoints
2939 for flash if the gdb memory map has been set up(default when flash is declared in
2940 target configuration). @xref{gdb_breakpoint_override}.
2941 @item @b{arm7_9 sw_bkpts}
2942 @cindex arm7_9 sw_bkpts
2943 @*On by default. See also @option{gdb_breakpoint_override}. @xref{gdb_breakpoint_override}.
2944 @item @b{daemon_startup}
2945 @cindex daemon_startup
2946 @*this config option has been removed, simply adding @option{init} and @option{reset halt} to
2947 the end of your config script will give the same behaviour as using @option{daemon_startup reset}
2948 and @option{target cortex_m3 little reset_halt 0}.
2949 @item @b{dump_binary}
2951 @*use @option{dump_image} command with same args. @xref{dump_image}.
2952 @item @b{flash erase}
2954 @*use @option{flash erase_sector} command with same args. @xref{flash erase_sector}.
2955 @item @b{flash write}
2957 @*use @option{flash write_bank} command with same args. @xref{flash write_bank}.
2958 @item @b{flash write_binary}
2959 @cindex flash write_binary
2960 @*use @option{flash write_bank} command with same args. @xref{flash write_bank}.
2961 @item @b{flash auto_erase}
2962 @cindex flash auto_erase
2963 @*use @option{flash write_image} command passing @option{erase} as the first parameter. @xref{flash write_image}.
2964 @item @b{load_binary}
2966 @*use @option{load_image} command with same args. @xref{load_image}.
2967 @item @b{run_and_halt_time}
2968 @cindex run_and_halt_time
2969 @*This command has been removed for simpler reset behaviour, it can be simulated with the
2976 @item @b{target} <@var{type}> <@var{endian}> <@var{jtag-position}>
2978 @*use the create subcommand of @option{target}.
2979 @item @b{target_script} <@var{target#}> <@var{eventname}> <@var{scriptname}>
2980 @cindex target_script
2981 @*use <@var{target_name}> configure -event <@var{eventname}> "script <@var{scriptname}>"
2982 @item @b{working_area}
2983 @cindex working_area
2984 @*use the @option{configure} subcommand of @option{target} to set the work-area-virt, work-area-phy, work-area-size, and work-area-backup properties of the target.
2991 @item @b{RTCK, also known as: Adaptive Clocking - What is it?}
2993 @cindex adaptive clocking
2996 In digital circuit design it is often refered to as ``clock
2997 syncronization'' the JTAG interface uses one clock (TCK or TCLK)
2998 operating at some speed, your target is operating at another. The two
2999 clocks are not syncronized, they are ``asynchronous''
3001 In order for the two to work together they must syncronize. Otherwise
3002 the two systems will get out of sync with each other and nothing will
3003 work. There are 2 basic options. @b{1.} use a special circuit or
3004 @b{2.} one clock must be some multile slower the the other.
3006 @b{Does this really matter?} For some chips and some situations, this
3007 is a non-issue (ie: A 500mhz ARM926) but for others - for example some
3008 ATMEL SAM7 and SAM9 chips start operation from reset at 32khz -
3009 program/enable the oscillators and eventually the main clock. It is in
3010 those critical times you must slow the jtag clock to sometimes 1 to
3013 Imagine debugging that 500mhz arm926 hand held battery powered device
3014 that ``deep sleeps'' at 32khz between every keystroke. It can be
3017 @b{Solution #1 - A special circuit}
3019 In order to make use of this your jtag dongle must support the RTCK
3020 feature. Not all dongles support this - keep reading!
3022 The RTCK signal often found in some ARM chips is used to help with
3023 this problem. ARM has a good description of the problem described at
3024 this link: @url{http://www.arm.com/support/faqdev/4170.html} [checked
3025 28/nov/2008]. Link title: ``How does the jtag synchronisation logic
3026 work? / how does adaptive clocking working?''.
3028 The nice thing about adaptive clocking is that ``battery powered hand
3029 held device example'' - the adaptiveness works perfectly all the
3030 time. One can set a break point or halt the system in the deep power
3031 down code, slow step out until the system speeds up.
3033 @b{Solution #2 - Always works - but is slower}
3035 Often this is a perfectly acceptable solution.
3037 In the most simple terms: Often the JTAG clock must be 1/10 to 1/12 of
3038 the target clock speed. But what is that ``magic division'' it varies
3039 depending upon the chips on your board. @b{ARM Rule of thumb} Most ARM
3040 based systems require an 8:1 division. @b{Xilinx Rule of thumb} is
3041 1/12 the clock speed.
3043 Note: Many FTDI2232C based JTAG dongles are limited to 6mhz.
3045 You can still debug the 'lower power' situations - you just need to
3046 manually adjust the clock speed at every step. While painful and
3047 teadious, it is not always practical.
3049 It is however easy to ``code your way around it'' - ie: Cheat a little
3050 have a special debug mode in your application that does a ``high power
3051 sleep''. If you are careful - 98% of your problems can be debugged
3054 To set the JTAG frequency use the command:
3062 @item @b{Win32 Pathnames} Why does not backslashes in paths under Windows doesn't work?
3064 OpenOCD uses Tcl and a backslash is an escape char. Use @{ and @}
3065 around Windows filenames.
3078 @item @b{Missing: cygwin1.dll} OpenOCD complains about a missing cygwin1.dll.
3080 Make sure you have Cygwin installed, or at least a version of OpenOCD that
3081 claims to come with all the necessary dlls. When using Cygwin, try launching
3082 OpenOCD from the Cygwin shell.
3084 @item @b{Breakpoint Issue} I'm trying to set a breakpoint using GDB (or a frontend like Insight or
3085 Eclipse), but OpenOCD complains that "Info: arm7_9_common.c:213
3086 arm7_9_add_breakpoint(): sw breakpoint requested, but software breakpoints not enabled".
3088 GDB issues software breakpoints when a normal breakpoint is requested, or to implement
3089 source-line single-stepping. On ARMv4T systems, like ARM7TDMI, ARM720t or ARM920t,
3090 software breakpoints consume one of the two available hardware breakpoints.
3092 @item @b{LPC2000 Flash} When erasing or writing LPC2000 on-chip flash, the operation fails sometimes
3093 and works sometimes fine.
3095 Make sure the core frequency specified in the @option{flash lpc2000} line matches the
3096 clock at the time you're programming the flash. If you've specified the crystal's
3097 frequency, make sure the PLL is disabled, if you've specified the full core speed
3098 (e.g. 60MHz), make sure the PLL is enabled.
3100 @item @b{Amontec Chameleon} When debugging using an Amontec Chameleon in its JTAG Accelerator configuration,
3101 I keep getting "Error: amt_jtagaccel.c:184 amt_wait_scan_busy(): amt_jtagaccel timed
3102 out while waiting for end of scan, rtck was disabled".
3104 Make sure your PC's parallel port operates in EPP mode. You might have to try several
3105 settings in your PC BIOS (ECP, EPP, and different versions of those).
3107 @item @b{Data Aborts} When debugging with OpenOCD and GDB (plain GDB, Insight, or Eclipse),
3108 I get lots of "Error: arm7_9_common.c:1771 arm7_9_read_memory():
3109 memory read caused data abort".
3111 The errors are non-fatal, and are the result of GDB trying to trace stack frames
3112 beyond the last valid frame. It might be possible to prevent this by setting up
3113 a proper "initial" stack frame, if you happen to know what exactly has to
3114 be done, feel free to add this here.
3116 @b{Simple:} In your startup code - push 8 registers of ZEROs onto the
3117 stack before calling main(). What GDB is doing is ``climbing'' the run
3118 time stack by reading various values on the stack using the standard
3119 call frame for the target. GDB keeps going - until one of 2 things
3120 happen @b{#1} an invalid frame is found, or @b{#2} some huge number of
3121 stackframes have been processed. By pushing ZEROs on the stack, GDB
3124 @b{Debugging Interrupt Service Routines} - In your ISR before you call
3125 your C code, do the same, artifically push some zeros on to the stack,
3126 remember to pop them off when the ISR is done.
3128 @b{Also note:} If you have a multi-threaded operating system, they
3129 often do not @b{in the intrest of saving memory} waste these few
3133 @item @b{JTAG Reset Config} I get the following message in the OpenOCD console (or log file):
3134 "Warning: arm7_9_common.c:679 arm7_9_assert_reset(): srst resets test logic, too".
3136 This warning doesn't indicate any serious problem, as long as you don't want to
3137 debug your core right out of reset. Your .cfg file specified @option{jtag_reset
3138 trst_and_srst srst_pulls_trst} to tell OpenOCD that either your board,
3139 your debugger or your target uC (e.g. LPC2000) can't assert the two reset signals
3140 independently. With this setup, it's not possible to halt the core right out of
3141 reset, everything else should work fine.
3143 @item @b{USB Power} When using OpenOCD in conjunction with Amontec JTAGkey and the Yagarto
3144 Toolchain (Eclipse, arm-elf-gcc, arm-elf-gdb), the debugging seems to be
3145 unstable. When single-stepping over large blocks of code, GDB and OpenOCD
3146 quit with an error message. Is there a stability issue with OpenOCD?
3148 No, this is not a stability issue concerning OpenOCD. Most users have solved
3149 this issue by simply using a self-powered USB hub, which they connect their
3150 Amontec JTAGkey to. Apparently, some computers do not provide a USB power
3151 supply stable enough for the Amontec JTAGkey to be operated.
3153 @b{Laptops running on battery have this problem too...}
3155 @item @b{USB Power} When using the Amontec JTAGkey, sometimes OpenOCD crashes with the
3156 following error messages: "Error: ft2232.c:201 ft2232_read(): FT_Read returned:
3157 4" and "Error: ft2232.c:365 ft2232_send_and_recv(): couldn't read from FT2232".
3158 What does that mean and what might be the reason for this?
3160 First of all, the reason might be the USB power supply. Try using a self-powered
3161 hub instead of a direct connection to your computer. Secondly, the error code 4
3162 corresponds to an FT_IO_ERROR, which means that the driver for the FTDI USB
3163 chip ran into some sort of error - this points us to a USB problem.
3165 @item @b{GDB Disconnects} When using the Amontec JTAGkey, sometimes OpenOCD crashes with the following
3166 error message: "Error: gdb_server.c:101 gdb_get_char(): read: 10054".
3167 What does that mean and what might be the reason for this?
3169 Error code 10054 corresponds to WSAECONNRESET, which means that the debugger (GDB)
3170 has closed the connection to OpenOCD. This might be a GDB issue.
3172 @item @b{LPC2000 Flash} In the configuration file in the section where flash device configurations
3173 are described, there is a parameter for specifying the clock frequency
3174 for LPC2000 internal flash devices (e.g. @option{flash bank lpc2000
3175 0x0 0x40000 0 0 0 lpc2000_v1 14746 calc_checksum}), which must be
3176 specified in kilohertz. However, I do have a quartz crystal of a
3177 frequency that contains fractions of kilohertz (e.g. 14,745,600 Hz,
3178 i.e. 14,745.600 kHz). Is it possible to specify real numbers for the
3181 No. The clock frequency specified here must be given as an integral number.
3182 However, this clock frequency is used by the In-Application-Programming (IAP)
3183 routines of the LPC2000 family only, which seems to be very tolerant concerning
3184 the given clock frequency, so a slight difference between the specified clock
3185 frequency and the actual clock frequency will not cause any trouble.
3187 @item @b{Command Order} Do I have to keep a specific order for the commands in the configuration file?
3189 Well, yes and no. Commands can be given in arbitrary order, yet the
3190 devices listed for the JTAG scan chain must be given in the right
3191 order (jtag newdevice), with the device closest to the TDO-Pin being
3192 listed first. In general, whenever objects of the same type exist
3193 which require an index number, then these objects must be given in the
3194 right order (jtag newtap, targets and flash banks - a target
3195 references a jtag newtap and a flash bank references a target).
3197 You can use the ``scan_chain'' command to verify and display the tap order.
3199 @item @b{JTAG Tap Order} JTAG Tap Order - Command Order
3201 Many newer devices have multiple JTAG taps. For example: ST
3202 Microsystems STM32 chips have two taps, a ``boundary scan tap'' and
3203 ``cortexM3'' tap. Example: The STM32 reference manual, Document ID:
3204 RM0008, Section 26.5, Figure 259, page 651/681, the ``TDI'' pin is
3205 connected to the Boundary Scan Tap, which then connects to the
3206 CortexM3 Tap, which then connects to the TDO pin.
3208 Thus, the proper order for the STM32 chip is: (1) The CortexM3, then
3209 (2) The Boundary Scan Tap. If your board includes an additional JTAG
3210 chip in the scan chain (for example a Xilinx CPLD or FPGA) you could
3211 place it before or after the stm32 chip in the chain. For example:
3214 @item OpenOCD_TDI(output) -> STM32 TDI Pin (BS Input)
3215 @item STM32 BS TDO (output) -> STM32 CortexM3 TDI (input)
3216 @item STM32 CortexM3 TDO (output) -> SM32 TDO Pin
3217 @item STM32 TDO Pin (output) -> Xilinx TDI Pin (input)
3218 @item Xilinx TDO Pin -> OpenOCD TDO (input)
3221 The ``jtag device'' commands would thus be in the order shown below. Note
3224 @item jtag newtap Xilinx tap -irlen ...
3225 @item jtag newtap stm32 cpu -irlen ...
3226 @item jtag newtap stm32 bs -irlen ...
3227 @item # Create the debug target and say where it is
3228 @item target create stm32.cpu -chain-position stm32.cpu ...
3232 @item @b{SYSCOMP} Sometimes my debugging session terminates with an error. When I look into the
3233 log file, I can see these error messages: Error: arm7_9_common.c:561
3234 arm7_9_execute_sys_speed(): timeout waiting for SYSCOMP
3240 @node TCL Crash Course
3241 @chapter TCL Crash Course
3244 Not everyone knows TCL - this is not intended to be a replacement for
3245 learning TCL, the intent of this chapter is to give you some idea of
3246 how the TCL Scripts work.
3248 This chapter is written with two audiences in mind. (1) OpenOCD users
3249 who need to understand a bit more of how JIM-Tcl works so they can do
3250 something useful, and (2) those that want to add a new command to
3253 @section TCL Rule #1
3254 There is a famous joke, it goes like this:
3256 @item Rule #1: The wife is aways correct
3257 @item Rule #2: If you think otherwise, See Rule #1
3260 The TCL equal is this:
3263 @item Rule #1: Everything is a string
3264 @item Rule #2: If you think otherwise, See Rule #1
3267 As in the famous joke, the consiquences of Rule #1 are profound. Once
3268 you understand Rule #1, you will understand TCL.
3270 @section TCL Rule #1b
3271 There is a second pair of rules.
3273 @item Rule #1: Control flow does not exist. Only commands
3274 @* For example: the classic FOR loop or IF statement is not a control
3275 flow item, they are commands, there is no such thing as control flow
3277 @item Rule #2: If you think otherwise, See Rule #1
3278 @* Actually what happens is this: There are commands that by
3279 convention, act like control flow key words in other languages. One of
3280 those commands is the word ``for'', another command is ``if''.
3283 @section Per Rule #1 - All Results are strings
3284 Every TCL command results in a string. The word ``result'' is used
3285 deliberatly. No result is just an empty string. Remember: @i{Rule #1 -
3286 Everything is a string}
3288 @section TCL Quoting Operators
3289 In life of a TCL script, there are two important periods of time, the
3290 difference is subtle.
3293 @item Evaluation Time
3296 The two key items here are how ``quoted things'' work in TCL. TCL has
3297 three primary quoting constructs, the [square-brackets] the
3298 @{curly-braces@} and ``double-quotes''
3300 By now you should know $VARIABLES always start with a $DOLLAR
3301 sign. BTW, to set a variable, you actually use the command ``set'', as
3302 in ``set VARNAME VALUE'' much like the ancient BASIC langauge ``let x
3303 = 1'' statement, but without the equal sign.
3306 @item @b{[square-brackets]}
3307 @* @b{[square-brackets]} are command subsitution. It operates much
3308 like Unix Shell `back-ticks`. The result of a [square-bracket]
3309 operation is exactly 1 string. @i{Remember Rule #1 - Everything is a
3310 string}. These two statments are roughly identical.
3314 echo "The Date is: $X"
3317 puts "The Date is: $X"
3319 @item @b{``double-quoted-things''}
3320 @* @b{``double-quoted-things''} are just simply quoted
3321 text. $VARIABLES and [square-brackets] are expanded in place - the
3322 result however is exactly 1 string. @i{Remember Rule #1 - Everything
3326 puts "It is now \"[date]\", $x is in 1 hour"
3328 @item @b{@{Curly-Braces@}}
3329 @*@b{@{Curly-Braces@}} are magic: $VARIABLES and [square-brackets] are
3330 parsed, but are NOT expanded or executed. @{Curly-Braces@} are like
3331 'single-quote' operators in BASH shell scripts, with the added
3332 feature: @{curly-braces@} nest, single quotes can not. @{@{@{this is
3333 nested 3 times@}@}@} NOTE: [date] is perhaps a bad example, as of
3334 28/nov/2008, Jim/OpenOCD does not have a date command.
3337 @section Consiquences of Rule 1/2/3/4
3339 The consiquences of Rule 1 is profound.
3341 @subsection Tokenizing & Execution.
3343 Of course, whitespace, blank lines and #comment lines are handled in
3346 As a script is parsed, each (multi) line in the script file is
3347 tokenized and according to the quoting rules. After tokenizing, that
3348 line is immedatly executed.
3350 Multi line statements end with one or more ``still-open''
3351 @{curly-braces@} which - eventually - a few lines later closes.
3353 @subsection Command Execution
3355 Remember earlier: There is no such thing as ``control flow''
3356 statements in TCL. Instead there are COMMANDS that simpily act like
3357 control flow operators.
3359 Commands are executed like this:
3362 @item Parse the next line into (argc) and (argv[]).
3363 @item Look up (argv[0]) in a table and call its function.
3364 @item Repeat until End Of File.
3367 It sort of works like this:
3370 ReadAndParse( &argc, &argv );
3372 cmdPtr = LookupCommand( argv[0] );
3374 (*cmdPtr->Execute)( argc, argv );
3378 When the command ``proc'' is parsed (which creates a procedure
3379 function) it gets 3 parameters on the command line. @b{1} the name of
3380 the proc (function), @b{2} the list of parameters, and @b{3} the body
3381 of the function. Not the choice of words: LIST and BODY. The PROC
3382 command stores these items in a table somewhere so it can be found by
3385 @subsection The FOR Command
3387 The most interesting command to look at is the FOR command. In TCL,
3388 the FOR command is normally implimented in C. Remember, FOR is a
3389 command just like any other command.
3391 When the ascii text containing the FOR command is parsed, the parser
3392 produces 5 parameter strings, @i{(If in doubt: Refer to Rule #1)} they
3396 @item The ascii text 'for'
3397 @item The start text
3398 @item The test expression
3403 Sort of reminds you of ``main( int argc, char **argv )'' does it not?
3404 Remember @i{Rule #1 - Everything is a string.} The key point is this:
3405 Often many of those parameters are in @{curly-braces@} - thus the
3406 variables inside are not expanded or replaced until later.
3408 Remember that every TCL command looks like the classic ``main( argc,
3409 argv )'' function in C. In JimTCL - they actually look like this:
3413 MyCommand( Jim_Interp *interp,
3415 Jim_Obj * const *argvs );
3418 Real TCL is nearly identical. Although the newer versions have
3419 introduced a byte-code parser and intepreter, but at the core, it
3420 still operates in the same basic way.
3422 @subsection FOR Command Implimentation
3424 To understand TCL it is perhaps most helpful to see the FOR
3425 command. Remember, it is a COMMAND not a control flow structure.
3427 In TCL there are two underying C helper functions.
3429 Remember Rule #1 - You are a string.
3431 The @b{first} helper parses and executes commands found in an ascii
3432 string. Commands can be seperated by semi-colons, or newlines. While
3433 parsing, variables are expanded per the quoting rules
3435 The @b{second} helper evaluates an ascii string as a numerical
3436 expression and returns a value.
3438 Here is an example of how the @b{FOR} command could be
3439 implimented. The pseudo code below does not show error handling.
3441 void Execute_AsciiString( void *interp, const char *string );
3443 int Evaluate_AsciiExpression( void *interp, const char *string );
3446 MyForCommand( void *interp,
3451 SetResult( interp, "WRONG number of parameters");
3455 // argv[0] = the ascii string just like C
3457 // Execute the start statement.
3458 Execute_AsciiString( interp, argv[1] );
3462 i = Evaluate_AsciiExpression(interp, argv[2]);
3467 Execute_AsciiString( interp, argv[3] );
3469 // Execute the LOOP part
3470 Execute_AsciiString( interp, argv[4] );
3474 SetResult( interp, "" );
3479 Every other command IF, WHILE, FORMAT, PUTS, EXPR, everything works
3480 in the same basic way.
3482 @section OpenOCD TCL Usage
3484 @subsection source and find commands
3485 @b{Where:} In many configuration files
3486 @* Example: @b{ source [find FILENAME] }
3487 @*Remember the parsing rules
3489 @item The FIND command is in square brackets.
3490 @* The FIND command is executed with the parameter FILENAME. It should
3491 find the full path to the named file. The RESULT is a string, which is
3492 subsituted on the orginal command line.
3493 @item The command source is executed with the resulting filename.
3494 @* SOURCE reads a file and executes as a script.
3496 @subsection format command
3497 @b{Where:} Generally occurs in numerous places.
3498 @* TCL no command like @b{printf()}, intead it has @b{format}, which is really more like
3504 puts [format "The answer: %d" [expr $x * $y]]
3507 @item The SET command creates 2 variables, X and Y.
3508 @item The double [nested] EXPR command performs math
3509 @* The EXPR command produces numerical result as a string.
3511 @item The format command is executed, producing a single string
3512 @* Refer to Rule #1.
3513 @item The PUTS command outputs the text.
3515 @subsection Body Or Inlined Text
3516 @b{Where:} Various TARGET scripts.
3519 proc someproc @{@} @{
3520 ... multiple lines of stuff ...
3522 $_TARGETNAME configure -event FOO someproc
3523 #2 Good - no variables
3524 $_TARGETNAME confgure -event foo "this ; that;"
3525 #3 Good Curly Braces
3526 $_TARGETNAME configure -event FOO @{
3529 #4 DANGER DANGER DANGER
3530 $_TARGETNAME configure -event foo "puts \"Time: [date]\""
3533 @item The $_TARGETNAME is an OpenOCD variable convention.
3534 @*@b{$_TARGETNAME} represents the last target created, the value changes
3535 each time a new target is created. Remember the parsing rules. When
3536 the ascii text is parsed, the @b{$_TARGETNAME} becomes a simple string,
3537 the name of the target which happens to be a TARGET (object)
3539 @item The 2nd parameter to the @option{-event} parameter is a TCBODY
3540 @*There are 4 examples:
3542 @item The TCLBODY is a simple string that happens to be a proc name
3543 @item The TCLBODY is several simple commands semi-colon seperated
3544 @item The TCLBODY is a multi-line @{curly-brace@} quoted string
3545 @item The TCLBODY is a string with variables that get expanded.
3548 In the end, when the target event FOO occurs the TCLBODY is
3549 evaluated. Method @b{#1} and @b{#2} are functionally identical. For
3550 Method @b{#3} and @b{#4} it is more interesting. What is the TCLBODY?
3552 Remember the parsing rules. In case #3, @{curly-braces@} mean the
3553 $VARS and [square-brackets] are expanded later, when the EVENT occurs,
3554 and the text is evaluated. In case #4, they are replaced before the
3555 ``Target Object Command'' is executed. This occurs at the same time
3556 $_TARGETNAME is replaced. In case #4 the date will never
3557 change. @{BTW: [date] is perhaps a bad example, as of 28/nov/2008,
3558 Jim/OpenOCD does not have a date command@}
3560 @subsection Global Variables
3561 @b{Where:} You might discover this when writing your own procs @* In
3562 simple terms: Inside a PROC, if you need to access a global variable
3563 you must say so. Also see ``upvar''. Example:
3565 proc myproc @{ @} @{
3566 set y 0 #Local variable Y
3567 global x #Global variable X
3568 puts [format "X=%d, Y=%d" $x $y]
3571 @section Other Tcl Hacks
3572 @b{Dynamic Variable Creation}
3574 # Dynamically create a bunch of variables.
3575 for @{ set x 0 @} @{ $x < 32 @} @{ set x [expr $x + 1]@} @{
3577 set vn [format "BIT%d" $x]
3581 set $vn [expr (1 << $x)]
3584 @b{Dynamic Proc/Command Creation}
3586 # One "X" function - 5 uart functions.
3587 foreach who @{A B C D E@}
3588 proc [format "show_uart%c" $who] @{ @} "show_UARTx $who"
3592 @node Target library
3593 @chapter Target library
3594 @cindex Target library
3596 OpenOCD comes with a target configuration script library. These scripts can be
3597 used as-is or serve as a starting point.
3599 The target library is published together with the openocd executable and
3600 the path to the target library is in the OpenOCD script search path.
3601 Similarly there are example scripts for configuring the JTAG interface.
3603 The command line below uses the example parport configuration scripts
3604 that ship with OpenOCD, then configures the str710.cfg target and
3605 finally issues the init and reset command. The communication speed
3606 is set to 10kHz for reset and 8MHz for post reset.
3610 openocd -f interface/parport.cfg -f target/str710.cfg -c "init" -c "reset"
3614 To list the target scripts available:
3617 $ ls /usr/local/lib/openocd/target
3619 arm7_fast.cfg lm3s6965.cfg pxa255.cfg stm32.cfg xba_revA3.cfg
3620 at91eb40a.cfg lpc2148.cfg pxa255_sst.cfg str710.cfg zy1000.cfg
3621 at91r40008.cfg lpc2294.cfg sam7s256.cfg str912.cfg
3622 at91sam9260.cfg nslu2.cfg sam7x256.cfg wi-9c.cfg
3630 @comment DO NOT use the plain word ``Index'', reason: CYGWIN filename
3631 @comment case issue with ``Index.html'' and ``index.html''
3632 @comment Occurs when creating ``--html --no-split'' output
3633 @comment This fix is based on: http://sourceware.org/ml/binutils/2006-05/msg00215.html
3634 @unnumbered OpenOCD Index