1 \input texinfo @c -*-texinfo-*-
3 @setfilename openocd.info
4 @settitle OpenOCD User's Guide
5 @dircategory Development
7 * OpenOCD: (openocd). OpenOCD User's Guide
16 This User's Guide documents
17 release @value{VERSION},
18 dated @value{UPDATED},
19 of the Open On-Chip Debugger (OpenOCD).
22 @item Copyright @copyright{} 2008 The OpenOCD Project
23 @item Copyright @copyright{} 2007-2008 Spencer Oliver @email{spen@@spen-soft.co.uk}
24 @item Copyright @copyright{} 2008 Oyvind Harboe @email{oyvind.harboe@@zylin.com}
25 @item Copyright @copyright{} 2008 Duane Ellis @email{openocd@@duaneellis.com}
26 @item Copyright @copyright{} 2009 David Brownell
30 Permission is granted to copy, distribute and/or modify this document
31 under the terms of the GNU Free Documentation License, Version 1.2 or
32 any later version published by the Free Software Foundation; with no
33 Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
34 Texts. A copy of the license is included in the section entitled ``GNU
35 Free Documentation License''.
40 @titlefont{@emph{Open On-Chip Debugger:}}
42 @title OpenOCD User's Guide
43 @subtitle for release @value{VERSION}
44 @subtitle @value{UPDATED}
47 @vskip 0pt plus 1filll
56 @top OpenOCD User's Guide
62 * About:: About OpenOCD
63 * Developers:: OpenOCD Developers
64 * JTAG Hardware Dongles:: JTAG Hardware Dongles
65 * About JIM-Tcl:: About JIM-Tcl
66 * Running:: Running OpenOCD
67 * OpenOCD Project Setup:: OpenOCD Project Setup
68 * Config File Guidelines:: Config File Guidelines
69 * Translating Configuration Files:: Translating Configuration Files
70 * Daemon Configuration:: Daemon Configuration
71 * Interface - Dongle Configuration:: Interface - Dongle Configuration
72 * Reset Configuration:: Reset Configuration
73 * TAP Declaration:: TAP Declaration
74 * CPU Configuration:: CPU Configuration
75 * Flash Commands:: Flash Commands
76 * NAND Flash Commands:: NAND Flash Commands
77 * PLD/FPGA Commands:: PLD/FPGA Commands
78 * General Commands:: General Commands
79 * Architecture and Core Commands:: Architecture and Core Commands
80 * JTAG Commands:: JTAG Commands
81 * Boundary Scan Commands:: Boundary Scan Commands
83 * GDB and OpenOCD:: Using GDB and OpenOCD
84 * Tcl Scripting API:: Tcl Scripting API
85 * Upgrading:: Deprecated/Removed Commands
86 * FAQ:: Frequently Asked Questions
87 * Tcl Crash Course:: Tcl Crash Course
88 * License:: GNU Free Documentation License
90 @comment DO NOT use the plain word ``Index'', reason: CYGWIN filename
91 @comment case issue with ``Index.html'' and ``index.html''
92 @comment Occurs when creating ``--html --no-split'' output
93 @comment This fix is based on: http://sourceware.org/ml/binutils/2006-05/msg00215.html
94 * OpenOCD Concept Index:: Concept Index
95 * Command and Driver Index:: Command and Driver Index
102 OpenOCD was created by Dominic Rath as part of a diploma thesis written at the
103 University of Applied Sciences Augsburg (@uref{http://www.fh-augsburg.de}).
104 Since that time, the project has grown into an active open-source project,
105 supported by a diverse community of software and hardware developers from
108 @section What is OpenOCD?
112 The Open On-Chip Debugger (OpenOCD) aims to provide debugging,
113 in-system programming and boundary-scan testing for embedded target
116 @b{JTAG:} OpenOCD uses a ``hardware interface dongle'' to communicate
117 with the JTAG (IEEE 1149.1) compliant TAPs on your target board.
118 A @dfn{TAP} is a ``Test Access Port'', a module which processes
119 special instructions and data. TAPs are daisy-chained within and
120 between chips and boards.
122 @b{Dongles:} OpenOCD currently supports many types of hardware dongles: USB
123 based, parallel port based, and other standalone boxes that run
124 OpenOCD internally. @xref{JTAG Hardware Dongles}.
126 @b{GDB Debug:} It allows ARM7 (ARM7TDMI and ARM720t), ARM9 (ARM920T,
127 ARM922T, ARM926EJ--S, ARM966E--S), XScale (PXA25x, IXP42x) and
128 Cortex-M3 (Stellaris LM3 and ST STM32) based cores to be
129 debugged via the GDB protocol.
131 @b{Flash Programing:} Flash writing is supported for external CFI
132 compatible NOR flashes (Intel and AMD/Spansion command set) and several
133 internal flashes (LPC1700, LPC2000, AT91SAM7, AT91SAM3U, STR7x, STR9x, LM3, and
134 STM32x). Preliminary support for various NAND flash controllers
135 (LPC3180, Orion, S3C24xx, more) controller is included.
137 @section OpenOCD Web Site
139 The OpenOCD web site provides the latest public news from the community:
141 @uref{http://openocd.berlios.de/web/}
143 @section Latest User's Guide:
145 The user's guide you are now reading may not be the latest one
146 available. A version for more recent code may be available.
147 Its HTML form is published irregularly at:
149 @uref{http://openocd.berlios.de/doc/html/index.html}
151 PDF form is likewise published at:
153 @uref{http://openocd.berlios.de/doc/pdf/openocd.pdf}
155 @section OpenOCD User's Forum
157 There is an OpenOCD forum (phpBB) hosted by SparkFun:
159 @uref{http://forum.sparkfun.com/viewforum.php?f=18}
163 @chapter OpenOCD Developer Resources
166 If you are interested in improving the state of OpenOCD's debugging and
167 testing support, new contributions will be welcome. Motivated developers
168 can produce new target, flash or interface drivers, improve the
169 documentation, as well as more conventional bug fixes and enhancements.
171 The resources in this chapter are available for developers wishing to explore
172 or expand the OpenOCD source code.
174 @section OpenOCD GIT Repository
176 During the 0.3.x release cycle, OpenOCD switched from Subversion to
177 a GIT repository hosted at SourceForge. The repository URL is:
179 @uref{git://openocd.git.sourceforge.net/gitroot/openocd/openocd}
181 You may prefer to use a mirror and the HTTP protocol:
183 @uref{http://repo.or.cz/r/openocd.git}
185 With standard GIT tools, use @command{git clone} to initialize
186 a local repository, and @command{git pull} to update it.
187 There are also gitweb pages letting you browse the repository
188 with a web browser, or download arbitrary snapshots without
189 needing a GIT client:
191 @uref{http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd}
193 @uref{http://repo.or.cz/w/openocd.git}
195 The @file{README} file contains the instructions for building the project
196 from the repository or a snapshot.
198 Developers that want to contribute patches to the OpenOCD system are
199 @b{strongly} encouraged to work against mainline.
200 Patches created against older versions may require additional
201 work from their submitter in order to be updated for newer releases.
203 @section Doxygen Developer Manual
205 During the 0.2.x release cycle, the OpenOCD project began
206 providing a Doxygen reference manual. This document contains more
207 technical information about the software internals, development
208 processes, and similar documentation:
210 @uref{http://openocd.berlios.de/doc/doxygen/index.html}
212 This document is a work-in-progress, but contributions would be welcome
213 to fill in the gaps. All of the source files are provided in-tree,
214 listed in the Doxyfile configuration in the top of the source tree.
216 @section OpenOCD Developer Mailing List
218 The OpenOCD Developer Mailing List provides the primary means of
219 communication between developers:
221 @uref{https://lists.berlios.de/mailman/listinfo/openocd-development}
223 Discuss and submit patches to this list.
224 The @file{PATCHES} file contains basic information about how
228 @node JTAG Hardware Dongles
229 @chapter JTAG Hardware Dongles
238 Defined: @b{dongle}: A small device that plugins into a computer and serves as
239 an adapter .... [snip]
241 In the OpenOCD case, this generally refers to @b{a small adapater} one
242 attaches to your computer via USB or the Parallel Printer Port. The
243 execption being the Zylin ZY1000 which is a small box you attach via
244 an ethernet cable. The Zylin ZY1000 has the advantage that it does not
245 require any drivers to be installed on the developer PC. It also has
246 a built in web interface. It supports RTCK/RCLK or adaptive clocking
247 and has a built in relay to power cycle targets remotely.
250 @section Choosing a Dongle
252 There are several things you should keep in mind when choosing a dongle.
255 @item @b{Voltage} What voltage is your target - 1.8, 2.8, 3.3, or 5V?
256 Does your dongle support it? You might need a level converter.
257 @item @b{Pinout} What pinout does your target board use?
258 Does your dongle support it? You may be able to use jumper
259 wires, or an "octopus" connector, to convert pinouts.
260 @item @b{Connection} Does your computer have the USB, printer, or
261 Ethernet port needed?
262 @item @b{RTCK} Do you require RTCK? Also known as ``adaptive clocking''
265 @section Stand alone Systems
267 @b{ZY1000} See: @url{http://www.zylin.com/zy1000.html} Technically, not a
268 dongle, but a standalone box. The ZY1000 has the advantage that it does
269 not require any drivers installed on the developer PC. It also has
270 a built in web interface. It supports RTCK/RCLK or adaptive clocking
271 and has a built in relay to power cycle targets remotely.
273 @section USB FT2232 Based
275 There are many USB JTAG dongles on the market, many of them are based
276 on a chip from ``Future Technology Devices International'' (FTDI)
277 known as the FTDI FT2232; this is a USB full speed (12 Mbps) chip.
278 See: @url{http://www.ftdichip.com} for more information.
279 In summer 2009, USB high speed (480 Mbps) versions of these FTDI
280 chips are starting to become available in JTAG adapters.
284 @* Link @url{http://www.hs-augsburg.de/~hhoegl/proj/usbjtag/usbjtag.html}
286 @* See: @url{http://www.amontec.com/jtagkey.shtml}
288 @* See: @url{http://www.amontec.com/jtagkey2.shtml}
290 @* See: @url{http://www.oocdlink.com} By Joern Kaipf
292 @* See: @url{http://www.signalyzer.com}
293 @item @b{evb_lm3s811}
294 @* See: @url{http://www.luminarymicro.com} - The Stellaris LM3S811 eval board has an FTD2232C chip built in.
295 @item @b{luminary_icdi}
296 @* See: @url{http://www.luminarymicro.com} - Luminary In-Circuit Debug Interface (ICDI) Board, included in the Stellaris LM3S9B90 and LM3S9B92 Evaluation Kits.
297 @item @b{olimex-jtag}
298 @* See: @url{http://www.olimex.com}
300 @* See: @url{http://www.tincantools.com}
301 @item @b{turtelizer2}
303 @uref{http://www.ethernut.de/en/hardware/turtelizer/index.html, Turtelizer 2}, or
304 @url{http://www.ethernut.de}
306 @* Link: @url{http://www.hitex.com/index.php?id=383}
308 @* Link @url{http://www.hitex.com/stm32-stick}
309 @item @b{axm0432_jtag}
310 @* Axiom AXM-0432 Link @url{http://www.axman.com}
312 @* Link @url{http://www.hitex.com/index.php?id=cortino}
315 @section USB JLINK based
316 There are several OEM versions of the Segger @b{JLINK} adapter. It is
317 an example of a micro controller based JTAG adapter, it uses an
318 AT91SAM764 internally.
321 @item @b{ATMEL SAMICE} Only works with ATMEL chips!
322 @* Link: @url{http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3892}
323 @item @b{SEGGER JLINK}
324 @* Link: @url{http://www.segger.com/jlink.html}
326 @* Link: @url{http://www.iar.com/website1/1.0.1.0/369/1/index.php}
329 @section USB RLINK based
330 Raisonance has an adapter called @b{RLink}. It exists in a stripped-down form on the STM32 Primer, permanently attached to the JTAG lines. It also exists on the STM32 Primer2, but that is wired for SWD and not JTAG, thus not supported.
333 @item @b{Raisonance RLink}
334 @* Link: @url{http://www.raisonance.com/products/RLink.php}
335 @item @b{STM32 Primer}
336 @* Link: @url{http://www.stm32circle.com/resources/stm32primer.php}
337 @item @b{STM32 Primer2}
338 @* Link: @url{http://www.stm32circle.com/resources/stm32primer2.php}
344 @* Link: @url{http://www.embedded-projects.net/usbprog} - which uses an Atmel MEGA32 and a UBN9604
346 @item @b{USB - Presto}
347 @* Link: @url{http://tools.asix.net/prg_presto.htm}
349 @item @b{Versaloon-Link}
350 @* Link: @url{http://www.simonqian.com/en/Versaloon}
352 @item @b{ARM-JTAG-EW}
353 @* Link: @url{http://www.olimex.com/dev/arm-jtag-ew.html}
356 @section IBM PC Parallel Printer Port Based
358 The two well known ``JTAG Parallel Ports'' cables are the Xilnx DLC5
359 and the MacGraigor Wiggler. There are many clones and variations of
362 Note that parallel ports are becoming much less common, so if you
363 have the choice you should probably avoid these adapters in favor
368 @item @b{Wiggler} - There are many clones of this.
369 @* Link: @url{http://www.macraigor.com/wiggler.htm}
371 @item @b{DLC5} - From XILINX - There are many clones of this
372 @* Link: Search the web for: ``XILINX DLC5'' - it is no longer
373 produced, PDF schematics are easily found and it is easy to make.
375 @item @b{Amontec - JTAG Accelerator}
376 @* Link: @url{http://www.amontec.com/jtag_accelerator.shtml}
379 @* Link: @url{http://www.gateworks.com/products/avila_accessories/gw16042.php}
382 @*@uref{http://www.ccac.rwth-aachen.de/@/~michaels/@/index.php/hardware/@/armjtag,
383 Improved parallel-port wiggler-style JTAG adapter}
385 @item @b{Wiggler_ntrst_inverted}
386 @* Yet another variation - See the source code, src/jtag/parport.c
388 @item @b{old_amt_wiggler}
389 @* Unknown - probably not on the market today
392 @* Link: Most likely @url{http://www.olimex.com/dev/arm-jtag.html} [another wiggler clone]
395 @* Link: @url{http://www.amontec.com/chameleon.shtml}
401 @* ispDownload from Lattice Semiconductor
402 @url{http://www.latticesemi.com/lit/docs/@/devtools/dlcable.pdf}
405 @* From ST Microsystems;
406 @uref{http://www.st.com/stonline/@/products/literature/um/7889.pdf,
407 FlashLINK JTAG programing cable for PSD and uPSD}
415 @* An EP93xx based Linux machine using the GPIO pins directly.
418 @* Like the EP93xx - but an ATMEL AT91RM9200 based solution using the GPIO pins on the chip.
423 @chapter About JIM-Tcl
427 OpenOCD includes a small ``Tcl Interpreter'' known as JIM-Tcl.
428 This programming language provides a simple and extensible
431 All commands presented in this Guide are extensions to JIM-Tcl.
432 You can use them as simple commands, without needing to learn
433 much of anything about Tcl.
434 Alternatively, can write Tcl programs with them.
436 You can learn more about JIM at its website, @url{http://jim.berlios.de}.
439 @item @b{JIM vs. Tcl}
440 @* JIM-TCL is a stripped down version of the well known Tcl language,
441 which can be found here: @url{http://www.tcl.tk}. JIM-Tcl has far
442 fewer features. JIM-Tcl is a single .C file and a single .H file and
443 implements the basic Tcl command set. In contrast: Tcl 8.6 is a
444 4.2 MB .zip file containing 1540 files.
446 @item @b{Missing Features}
447 @* Our practice has been: Add/clone the real Tcl feature if/when
448 needed. We welcome JIM Tcl improvements, not bloat.
451 @* OpenOCD configuration scripts are JIM Tcl Scripts. OpenOCD's
452 command interpreter today is a mixture of (newer)
453 JIM-Tcl commands, and (older) the orginal command interpreter.
456 @* At the OpenOCD telnet command line (or via the GDB mon command) one
457 can type a Tcl for() loop, set variables, etc.
458 Some of the commands documented in this guide are implemented
459 as Tcl scripts, from a @file{startup.tcl} file internal to the server.
461 @item @b{Historical Note}
462 @* JIM-Tcl was introduced to OpenOCD in spring 2008.
464 @item @b{Need a crash course in Tcl?}
465 @*@xref{Tcl Crash Course}.
470 @cindex command line options
472 @cindex directory search
474 The @option{--help} option shows:
478 --help | -h display this help
479 --version | -v display OpenOCD version
480 --file | -f use configuration file <name>
481 --search | -s dir to search for config files and scripts
482 --debug | -d set debug level <0-3>
483 --log_output | -l redirect log output to file <name>
484 --command | -c run <command>
485 --pipe | -p use pipes when talking to gdb
488 By default OpenOCD reads the file configuration file @file{openocd.cfg}
489 in the current directory. To specify a different (or multiple)
490 configuration file, you can use the ``-f'' option. For example:
493 openocd -f config1.cfg -f config2.cfg -f config3.cfg
496 OpenOCD starts by processing the configuration commands provided
497 on the command line or in @file{openocd.cfg}.
498 @xref{Configuration Stage}.
499 At the end of the configuration stage it verifies the JTAG scan
500 chain defined using those commands; your configuration should
501 ensure that this always succeeds.
502 Normally, OpenOCD then starts running as a daemon.
503 Alternatively, commands may be used to terminate the configuration
504 stage early, perform work (such as updating some flash memory),
505 and then shut down without acting as a daemon.
507 Once OpenOCD starts running as a daemon, it waits for connections from
508 clients (Telnet, GDB, Other) and processes the commands issued through
511 If you are having problems, you can enable internal debug messages via
514 Also it is possible to interleave JIM-Tcl commands w/config scripts using the
515 @option{-c} command line switch.
517 To enable debug output (when reporting problems or working on OpenOCD
518 itself), use the @option{-d} command line switch. This sets the
519 @option{debug_level} to "3", outputting the most information,
520 including debug messages. The default setting is "2", outputting only
521 informational messages, warnings and errors. You can also change this
522 setting from within a telnet or gdb session using @command{debug_level
523 <n>} (@pxref{debug_level}).
525 You can redirect all output from the daemon to a file using the
526 @option{-l <logfile>} switch.
528 Search paths for config/script files can be added to OpenOCD by using
529 the @option{-s <search>} switch. The current directory and the OpenOCD
530 target library is in the search path by default.
532 For details on the @option{-p} option. @xref{Connecting to GDB}.
534 Note! OpenOCD will launch the GDB & telnet server even if it can not
535 establish a connection with the target. In general, it is possible for
536 the JTAG controller to be unresponsive until the target is set up
537 correctly via e.g. GDB monitor commands in a GDB init script.
539 @node OpenOCD Project Setup
540 @chapter OpenOCD Project Setup
542 To use OpenOCD with your development projects, you need to do more than
543 just connecting the JTAG adapter hardware (dongle) to your development board
544 and then starting the OpenOCD server.
545 You also need to configure that server so that it knows
546 about that adapter and board, and helps your work.
548 @section Hooking up the JTAG Adapter
550 Today's most common case is a dongle with a JTAG cable on one side
551 (such as a ribbon cable with a 10-pin or 20-pin IDC connector)
552 and a USB cable on the other.
553 Instead of USB, some cables use Ethernet;
554 older ones may use a PC parallel port, or even a serial port.
557 @item @emph{Start with power to your target board turned off},
558 and nothing connected to your JTAG adapter.
559 If you're particularly paranoid, unplug power to the board.
560 It's important to have the ground signal properly set up,
561 unless you are using a JTAG adapter which provides
562 galvanic isolation between the target board and the
565 @item @emph{Be sure it's the right kind of JTAG connector.}
566 If your dongle has a 20-pin ARM connector, you need some kind
567 of adapter (or octopus, see below) to hook it up to
568 boards using 14-pin or 10-pin connectors ... or to 20-pin
569 connectors which don't use ARM's pinout.
571 In the same vein, make sure the voltage levels are compatible.
572 Not all JTAG adapters have the level shifters needed to work
573 with 1.2 Volt boards.
575 @item @emph{Be certain the cable is properly oriented} or you might
576 damage your board. In most cases there are only two possible
577 ways to connect the cable.
578 Connect the JTAG cable from your adapter to the board.
579 Be sure it's firmly connected.
581 In the best case, the connector is keyed to physically
582 prevent you from inserting it wrong.
583 This is most often done using a slot on the board's male connector
584 housing, which must match a key on the JTAG cable's female connector.
585 If there's no housing, then you must look carefully and
586 make sure pin 1 on the cable hooks up to pin 1 on the board.
587 Ribbon cables are frequently all grey except for a wire on one
588 edge, which is red. The red wire is pin 1.
590 Sometimes dongles provide cables where one end is an ``octopus'' of
591 color coded single-wire connectors, instead of a connector block.
592 These are great when converting from one JTAG pinout to another,
593 but are tedious to set up.
594 Use these with connector pinout diagrams to help you match up the
595 adapter signals to the right board pins.
597 @item @emph{Connect the adapter's other end} once the JTAG cable is connected.
598 A USB, parallel, or serial port connector will go to the host which
599 you are using to run OpenOCD.
600 For Ethernet, consult the documentation and your network administrator.
602 For USB based JTAG adapters you have an easy sanity check at this point:
603 does the host operating system see the JTAG adapter?
605 @item @emph{Connect the adapter's power supply, if needed.}
606 This step is primarily for non-USB adapters,
607 but sometimes USB adapters need extra power.
609 @item @emph{Power up the target board.}
610 Unless you just let the magic smoke escape,
611 you're now ready to set up the OpenOCD server
612 so you can use JTAG to work with that board.
616 Talk with the OpenOCD server using
617 telnet (@code{telnet localhost 4444} on many systems) or GDB.
618 @xref{GDB and OpenOCD}.
620 @section Project Directory
622 There are many ways you can configure OpenOCD and start it up.
624 A simple way to organize them all involves keeping a
625 single directory for your work with a given board.
626 When you start OpenOCD from that directory,
627 it searches there first for configuration files, scripts,
628 and for code you upload to the target board.
629 It is also the natural place to write files,
630 such as log files and data you download from the board.
632 @section Configuration Basics
634 There are two basic ways of configuring OpenOCD, and
635 a variety of ways you can mix them.
636 Think of the difference as just being how you start the server:
639 @item Many @option{-f file} or @option{-c command} options on the command line
640 @item No options, but a @dfn{user config file}
641 in the current directory named @file{openocd.cfg}
644 Here is an example @file{openocd.cfg} file for a setup
645 using a Signalyzer FT2232-based JTAG adapter to talk to
646 a board with an Atmel AT91SAM7X256 microcontroller:
649 source [find interface/signalyzer.cfg]
651 # GDB can also flash my flash!
652 gdb_memory_map enable
653 gdb_flash_program enable
655 source [find target/sam7x256.cfg]
658 Here is the command line equivalent of that configuration:
661 openocd -f interface/signalyzer.cfg \
662 -c "gdb_memory_map enable" \
663 -c "gdb_flash_program enable" \
664 -f target/sam7x256.cfg
667 You could wrap such long command lines in shell scripts,
668 each supporting a different development task.
669 One might re-flash the board with a specific firmware version.
670 Another might set up a particular debugging or run-time environment.
673 At this writing (October 2009) the command line method has
674 problems with how it treats variables.
675 For example, after @option{-c "set VAR value"}, or doing the
676 same in a script, the variable @var{VAR} will have no value
677 that can be tested in a later script.
680 Here we will focus on the simpler solution: one user config
681 file, including basic configuration plus any TCL procedures
682 to simplify your work.
684 @section User Config Files
685 @cindex config file, user
686 @cindex user config file
687 @cindex config file, overview
689 A user configuration file ties together all the parts of a project
691 One of the following will match your situation best:
694 @item Ideally almost everything comes from configuration files
695 provided by someone else.
696 For example, OpenOCD distributes a @file{scripts} directory
697 (probably in @file{/usr/share/openocd/scripts} on Linux).
698 Board and tool vendors can provide these too, as can individual
699 user sites; the @option{-s} command line option lets you say
700 where to find these files. (@xref{Running}.)
701 The AT91SAM7X256 example above works this way.
703 Three main types of non-user configuration file each have their
704 own subdirectory in the @file{scripts} directory:
707 @item @b{interface} -- one for each kind of JTAG adapter/dongle
708 @item @b{board} -- one for each different board
709 @item @b{target} -- the chips which integrate CPUs and other JTAG TAPs
712 Best case: include just two files, and they handle everything else.
713 The first is an interface config file.
714 The second is board-specific, and it sets up the JTAG TAPs and
715 their GDB targets (by deferring to some @file{target.cfg} file),
716 declares all flash memory, and leaves you nothing to do except
720 source [find interface/olimex-jtag-tiny.cfg]
721 source [find board/csb337.cfg]
724 Boards with a single microcontroller often won't need more
725 than the target config file, as in the AT91SAM7X256 example.
726 That's because there is no external memory (flash, DDR RAM), and
727 the board differences are encapsulated by application code.
729 @item You can often reuse some standard config files but
730 need to write a few new ones, probably a @file{board.cfg} file.
731 You will be using commands described later in this User's Guide,
732 and working with the guidelines in the next chapter.
734 For example, there may be configuration files for your JTAG adapter
735 and target chip, but you need a new board-specific config file
736 giving access to your particular flash chips.
737 Or you might need to write another target chip configuration file
738 for a new chip built around the Cortex M3 core.
741 When you write new configuration files, please submit
742 them for inclusion in the next OpenOCD release.
743 For example, a @file{board/newboard.cfg} file will help the
744 next users of that board, and a @file{target/newcpu.cfg}
745 will help support users of any board using that chip.
749 You may may need to write some C code.
750 It may be as simple as a supporting a new ft2232 or parport
751 based dongle; a bit more involved, like a NAND or NOR flash
752 controller driver; or a big piece of work like supporting
753 a new chip architecture.
756 Reuse the existing config files when you can.
757 Look first in the @file{scripts/boards} area, then @file{scripts/targets}.
758 You may find a board configuration that's a good example to follow.
760 When you write config files, separate the reusable parts
761 (things every user of that interface, chip, or board needs)
762 from ones specific to your environment and debugging approach.
766 For example, a @code{gdb-attach} event handler that invokes
767 the @command{reset init} command will interfere with debugging
768 early boot code, which performs some of the same actions
769 that the @code{reset-init} event handler does.
772 Likewise, the @command{arm9tdmi vector_catch} command (or
774 its siblings @command{xscale vector_catch}
775 and @command{cortex_m3 vector_catch}) can be a timesaver
776 during some debug sessions, but don't make everyone use that either.
777 Keep those kinds of debugging aids in your user config file,
778 along with messaging and tracing setup.
779 (@xref{Software Debug Messages and Tracing}.)
782 You might need to override some defaults.
783 For example, you might need to move, shrink, or back up the target's
784 work area if your application needs much SRAM.
787 TCP/IP port configuration is another example of something which
788 is environment-specific, and should only appear in
789 a user config file. @xref{TCP/IP Ports}.
792 @section Project-Specific Utilities
794 A few project-specific utility
795 routines may well speed up your work.
796 Write them, and keep them in your project's user config file.
798 For example, if you are making a boot loader work on a
799 board, it's nice to be able to debug the ``after it's
800 loaded to RAM'' parts separately from the finicky early
801 code which sets up the DDR RAM controller and clocks.
802 A script like this one, or a more GDB-aware sibling,
806 proc ramboot @{ @} @{
807 # Reset, running the target's "reset-init" scripts
808 # to initialize clocks and the DDR RAM controller.
809 # Leave the CPU halted.
812 # Load CONFIG_SKIP_LOWLEVEL_INIT version into DDR RAM.
813 load_image u-boot.bin 0x20000000
820 Then once that code is working you will need to make it
821 boot from NOR flash; a different utility would help.
822 Alternatively, some developers write to flash using GDB.
823 (You might use a similar script if you're working with a flash
824 based microcontroller application instead of a boot loader.)
827 proc newboot @{ @} @{
828 # Reset, leaving the CPU halted. The "reset-init" event
829 # proc gives faster access to the CPU and to NOR flash;
830 # "reset halt" would be slower.
833 # Write standard version of U-Boot into the first two
834 # sectors of NOR flash ... the standard version should
835 # do the same lowlevel init as "reset-init".
836 flash protect 0 0 1 off
837 flash erase_sector 0 0 1
838 flash write_bank 0 u-boot.bin 0x0
839 flash protect 0 0 1 on
841 # Reboot from scratch using that new boot loader.
846 You may need more complicated utility procedures when booting
848 That often involves an extra bootloader stage,
849 running from on-chip SRAM to perform DDR RAM setup so it can load
850 the main bootloader code (which won't fit into that SRAM).
852 Other helper scripts might be used to write production system images,
853 involving considerably more than just a three stage bootloader.
855 @section Target Software Changes
857 Sometimes you may want to make some small changes to the software
858 you're developing, to help make JTAG debugging work better.
859 For example, in C or assembly language code you might
860 use @code{#ifdef JTAG_DEBUG} (or its converse) around code
861 handling issues like:
865 @item @b{ARM Wait-For-Interrupt}...
866 Many ARM chips synchronize the JTAG clock using the core clock.
867 Low power states which stop that core clock thus prevent JTAG access.
868 Idle loops in tasking environments often enter those low power states
869 via the @code{WFI} instruction (or its coprocessor equivalent, before ARMv7).
871 You may want to @emph{disable that instruction} in source code,
872 or otherwise prevent using that state,
873 to ensure you can get JTAG access at any time.
874 For example, the OpenOCD @command{halt} command may not
875 work for an idle processor otherwise.
877 @item @b{Delay after reset}...
878 Not all chips have good support for debugger access
879 right after reset; many LPC2xxx chips have issues here.
880 Similarly, applications that reconfigure pins used for
881 JTAG access as they start will also block debugger access.
883 To work with boards like this, @emph{enable a short delay loop}
884 the first thing after reset, before "real" startup activities.
885 For example, one second's delay is usually more than enough
886 time for a JTAG debugger to attach, so that
887 early code execution can be debugged
888 or firmware can be replaced.
890 @item @b{Debug Communications Channel (DCC)}...
891 Some processors include mechanisms to send messages over JTAG.
892 Many ARM cores support these, as do some cores from other vendors.
893 (OpenOCD may be able to use this DCC internally, speeding up some
894 operations like writing to memory.)
896 Your application may want to deliver various debugging messages
897 over JTAG, by @emph{linking with a small library of code}
898 provided with OpenOCD and using the utilities there to send
899 various kinds of message.
900 @xref{Software Debug Messages and Tracing}.
904 @node Config File Guidelines
905 @chapter Config File Guidelines
907 This chapter is aimed at any user who needs to write a config file,
908 including developers and integrators of OpenOCD and any user who
909 needs to get a new board working smoothly.
910 It provides guidelines for creating those files.
912 You should find the following directories under @t{$(INSTALLDIR)/scripts},
913 with files including the ones listed here.
914 Use them as-is where you can; or as models for new files.
916 @item @file{interface} ...
917 think JTAG Dongle. Files that configure JTAG adapters go here.
920 arm-jtag-ew.cfg hitex_str9-comstick.cfg oocdlink.cfg
921 arm-usb-ocd.cfg icebear.cfg openocd-usb.cfg
922 at91rm9200.cfg jlink.cfg parport.cfg
923 axm0432.cfg jtagkey2.cfg parport_dlc5.cfg
924 calao-usb-a9260-c01.cfg jtagkey.cfg rlink.cfg
925 calao-usb-a9260-c02.cfg jtagkey-tiny.cfg sheevaplug.cfg
926 calao-usb-a9260.cfg luminary.cfg signalyzer.cfg
927 chameleon.cfg luminary-icdi.cfg stm32-stick.cfg
928 cortino.cfg luminary-lm3s811.cfg turtelizer2.cfg
929 dummy.cfg olimex-arm-usb-ocd.cfg usbprog.cfg
930 flyswatter.cfg olimex-jtag-tiny.cfg vsllink.cfg
933 @item @file{board} ...
934 think Circuit Board, PWA, PCB, they go by many names. Board files
935 contain initialization items that are specific to a board.
936 They reuse target configuration files, since the same
937 microprocessor chips are used on many boards,
938 but support for external parts varies widely. For
939 example, the SDRAM initialization sequence for the board, or the type
940 of external flash and what address it uses. Any initialization
941 sequence to enable that external flash or SDRAM should be found in the
942 board file. Boards may also contain multiple targets: two CPUs; or
946 arm_evaluator7t.cfg keil_mcb1700.cfg
947 at91rm9200-dk.cfg keil_mcb2140.cfg
948 at91sam9g20-ek.cfg linksys_nslu2.cfg
949 atmel_at91sam7s-ek.cfg logicpd_imx27.cfg
950 atmel_at91sam9260-ek.cfg mini2440.cfg
951 atmel_sam3u_ek.cfg olimex_LPC2378STK.cfg
952 crossbow_tech_imote2.cfg olimex_lpc_h2148.cfg
953 csb337.cfg olimex_sam7_ex256.cfg
954 csb732.cfg olimex_sam9_l9260.cfg
955 digi_connectcore_wi-9c.cfg olimex_stm32_h103.cfg
956 dm355evm.cfg omap2420_h4.cfg
957 dm365evm.cfg osk5912.cfg
958 dm6446evm.cfg pic-p32mx.cfg
959 eir.cfg propox_mmnet1001.cfg
960 ek-lm3s1968.cfg pxa255_sst.cfg
961 ek-lm3s3748.cfg sheevaplug.cfg
962 ek-lm3s811.cfg stm3210e_eval.cfg
963 ek-lm3s9b9x.cfg stm32f10x_128k_eval.cfg
964 hammer.cfg str910-eval.cfg
965 hitex_lpc2929.cfg telo.cfg
966 hitex_stm32-performancestick.cfg ti_beagleboard.cfg
967 hitex_str9-comstick.cfg topas910.cfg
968 iar_str912_sk.cfg topasa900.cfg
969 imx27ads.cfg unknown_at91sam9260.cfg
970 imx27lnst.cfg x300t.cfg
971 imx31pdk.cfg zy1000.cfg
974 @item @file{target} ...
975 think chip. The ``target'' directory represents the JTAG TAPs
977 which OpenOCD should control, not a board. Two common types of targets
978 are ARM chips and FPGA or CPLD chips.
979 When a chip has multiple TAPs (maybe it has both ARM and DSP cores),
980 the target config file defines all of them.
983 aduc702x.cfg imx27.cfg pxa255.cfg
984 ar71xx.cfg imx31.cfg pxa270.cfg
985 at91eb40a.cfg imx35.cfg readme.txt
986 at91r40008.cfg is5114.cfg sam7se512.cfg
987 at91rm9200.cfg ixp42x.cfg sam7x256.cfg
988 at91sam3u1c.cfg lm3s1968.cfg samsung_s3c2410.cfg
989 at91sam3u1e.cfg lm3s3748.cfg samsung_s3c2440.cfg
990 at91sam3u2c.cfg lm3s6965.cfg samsung_s3c2450.cfg
991 at91sam3u2e.cfg lm3s811.cfg samsung_s3c4510.cfg
992 at91sam3u4c.cfg lm3s9b9x.cfg samsung_s3c6410.cfg
993 at91sam3u4e.cfg lpc1768.cfg sharp_lh79532.cfg
994 at91sam3uXX.cfg lpc2103.cfg smdk6410.cfg
995 at91sam7sx.cfg lpc2124.cfg smp8634.cfg
996 at91sam9260.cfg lpc2129.cfg stm32.cfg
997 c100.cfg lpc2148.cfg str710.cfg
998 c100config.tcl lpc2294.cfg str730.cfg
999 c100helper.tcl lpc2378.cfg str750.cfg
1000 c100regs.tcl lpc2478.cfg str912.cfg
1001 cs351x.cfg lpc2900.cfg telo.cfg
1002 davinci.cfg mega128.cfg ti_dm355.cfg
1003 dragonite.cfg netx500.cfg ti_dm365.cfg
1004 epc9301.cfg omap2420.cfg ti_dm6446.cfg
1005 feroceon.cfg omap3530.cfg tmpa900.cfg
1006 icepick.cfg omap5912.cfg tmpa910.cfg
1007 imx21.cfg pic32mx.cfg xba_revA3.cfg
1010 @item @emph{more} ... browse for other library files which may be useful.
1011 For example, there are various generic and CPU-specific utilities.
1014 The @file{openocd.cfg} user config
1015 file may override features in any of the above files by
1016 setting variables before sourcing the target file, or by adding
1017 commands specific to their situation.
1019 @section Interface Config Files
1021 The user config file
1022 should be able to source one of these files with a command like this:
1025 source [find interface/FOOBAR.cfg]
1028 A preconfigured interface file should exist for every interface in use
1029 today, that said, perhaps some interfaces have only been used by the
1030 sole developer who created it.
1032 A separate chapter gives information about how to set these up.
1033 @xref{Interface - Dongle Configuration}.
1034 Read the OpenOCD source code if you have a new kind of hardware interface
1035 and need to provide a driver for it.
1037 @section Board Config Files
1038 @cindex config file, board
1039 @cindex board config file
1041 The user config file
1042 should be able to source one of these files with a command like this:
1045 source [find board/FOOBAR.cfg]
1048 The point of a board config file is to package everything
1049 about a given board that user config files need to know.
1050 In summary the board files should contain (if present)
1053 @item One or more @command{source [target/...cfg]} statements
1054 @item NOR flash configuration (@pxref{NOR Configuration})
1055 @item NAND flash configuration (@pxref{NAND Configuration})
1056 @item Target @code{reset} handlers for SDRAM and I/O configuration
1057 @item JTAG adapter reset configuration (@pxref{Reset Configuration})
1058 @item All things that are not ``inside a chip''
1061 Generic things inside target chips belong in target config files,
1062 not board config files. So for example a @code{reset-init} event
1063 handler should know board-specific oscillator and PLL parameters,
1064 which it passes to target-specific utility code.
1066 The most complex task of a board config file is creating such a
1067 @code{reset-init} event handler.
1068 Define those handlers last, after you verify the rest of the board
1069 configuration works.
1071 @subsection Communication Between Config files
1073 In addition to target-specific utility code, another way that
1074 board and target config files communicate is by following a
1075 convention on how to use certain variables.
1077 The full Tcl/Tk language supports ``namespaces'', but JIM-Tcl does not.
1078 Thus the rule we follow in OpenOCD is this: Variables that begin with
1079 a leading underscore are temporary in nature, and can be modified and
1080 used at will within a target configuration file.
1082 Complex board config files can do the things like this,
1083 for a board with three chips:
1086 # Chip #1: PXA270 for network side, big endian
1087 set CHIPNAME network
1089 source [find target/pxa270.cfg]
1090 # on return: _TARGETNAME = network.cpu
1091 # other commands can refer to the "network.cpu" target.
1092 $_TARGETNAME configure .... events for this CPU..
1094 # Chip #2: PXA270 for video side, little endian
1097 source [find target/pxa270.cfg]
1098 # on return: _TARGETNAME = video.cpu
1099 # other commands can refer to the "video.cpu" target.
1100 $_TARGETNAME configure .... events for this CPU..
1102 # Chip #3: Xilinx FPGA for glue logic
1105 source [find target/spartan3.cfg]
1108 That example is oversimplified because it doesn't show any flash memory,
1109 or the @code{reset-init} event handlers to initialize external DRAM
1110 or (assuming it needs it) load a configuration into the FPGA.
1111 Such features are usually needed for low-level work with many boards,
1112 where ``low level'' implies that the board initialization software may
1113 not be working. (That's a common reason to need JTAG tools. Another
1114 is to enable working with microcontroller-based systems, which often
1115 have no debugging support except a JTAG connector.)
1117 Target config files may also export utility functions to board and user
1118 config files. Such functions should use name prefixes, to help avoid
1121 Board files could also accept input variables from user config files.
1122 For example, there might be a @code{J4_JUMPER} setting used to identify
1123 what kind of flash memory a development board is using, or how to set
1124 up other clocks and peripherals.
1126 @subsection Variable Naming Convention
1127 @cindex variable names
1129 Most boards have only one instance of a chip.
1130 However, it should be easy to create a board with more than
1131 one such chip (as shown above).
1132 Accordingly, we encourage these conventions for naming
1133 variables associated with different @file{target.cfg} files,
1134 to promote consistency and
1135 so that board files can override target defaults.
1137 Inputs to target config files include:
1140 @item @code{CHIPNAME} ...
1141 This gives a name to the overall chip, and is used as part of
1142 tap identifier dotted names.
1143 While the default is normally provided by the chip manufacturer,
1144 board files may need to distinguish between instances of a chip.
1145 @item @code{ENDIAN} ...
1146 By default @option{little} - although chips may hard-wire @option{big}.
1147 Chips that can't change endianness don't need to use this variable.
1148 @item @code{CPUTAPID} ...
1149 When OpenOCD examines the JTAG chain, it can be told verify the
1150 chips against the JTAG IDCODE register.
1151 The target file will hold one or more defaults, but sometimes the
1152 chip in a board will use a different ID (perhaps a newer revision).
1155 Outputs from target config files include:
1158 @item @code{_TARGETNAME} ...
1159 By convention, this variable is created by the target configuration
1160 script. The board configuration file may make use of this variable to
1161 configure things like a ``reset init'' script, or other things
1162 specific to that board and that target.
1163 If the chip has 2 targets, the names are @code{_TARGETNAME0},
1164 @code{_TARGETNAME1}, ... etc.
1167 @subsection The reset-init Event Handler
1168 @cindex event, reset-init
1169 @cindex reset-init handler
1171 Board config files run in the OpenOCD configuration stage;
1172 they can't use TAPs or targets, since they haven't been
1174 This means you can't write memory or access chip registers;
1175 you can't even verify that a flash chip is present.
1176 That's done later in event handlers, of which the target @code{reset-init}
1177 handler is one of the most important.
1179 Except on microcontrollers, the basic job of @code{reset-init} event
1180 handlers is setting up flash and DRAM, as normally handled by boot loaders.
1181 Microcontrollers rarely use boot loaders; they run right out of their
1182 on-chip flash and SRAM memory. But they may want to use one of these
1183 handlers too, if just for developer convenience.
1186 Because this is so very board-specific, and chip-specific, no examples
1188 Instead, look at the board config files distributed with OpenOCD.
1189 If you have a boot loader, its source code may also be useful.
1192 Some of this code could probably be shared between different boards.
1193 For example, setting up a DRAM controller often doesn't differ by
1194 much except the bus width (16 bits or 32?) and memory timings, so a
1195 reusable TCL procedure loaded by the @file{target.cfg} file might take
1196 those as parameters.
1197 Similarly with oscillator, PLL, and clock setup;
1198 and disabling the watchdog.
1199 Structure the code cleanly, and provide comments to help
1200 the next developer doing such work.
1201 (@emph{You might be that next person} trying to reuse init code!)
1203 The last thing normally done in a @code{reset-init} handler is probing
1204 whatever flash memory was configured. For most chips that needs to be
1205 done while the associated target is halted, either because JTAG memory
1206 access uses the CPU or to prevent conflicting CPU access.
1208 @subsection JTAG Clock Rate
1210 Before your @code{reset-init} handler has set up
1211 the PLLs and clocking, you may need to run with
1212 a low JTAG clock rate.
1214 Then you'd increase that rate after your handler has
1215 made it possible to use the faster JTAG clock.
1216 When the initial low speed is board-specific, for example
1217 because it depends on a board-specific oscillator speed, then
1218 you should probably set it up in the board config file;
1219 if it's target-specific, it belongs in the target config file.
1221 For most ARM-based processors the fastest JTAG clock@footnote{A FAQ
1222 @uref{http://www.arm.com/support/faqdev/4170.html} gives details.}
1223 is one sixth of the CPU clock; or one eighth for ARM11 cores.
1224 Consult chip documentation to determine the peak JTAG clock rate,
1225 which might be less than that.
1228 On most ARMs, JTAG clock detection is coupled to the core clock, so
1229 software using a @option{wait for interrupt} operation blocks JTAG access.
1230 Adaptive clocking provides a partial workaround, but a more complete
1231 solution just avoids using that instruction with JTAG debuggers.
1234 If the board supports adaptive clocking, use the @command{jtag_rclk}
1235 command, in case your board is used with JTAG adapter which
1236 also supports it. Otherwise use @command{jtag_khz}.
1237 Set the slow rate at the beginning of the reset sequence,
1238 and the faster rate as soon as the clocks are at full speed.
1240 @section Target Config Files
1241 @cindex config file, target
1242 @cindex target config file
1244 Board config files communicate with target config files using
1245 naming conventions as described above, and may source one or
1246 more target config files like this:
1249 source [find target/FOOBAR.cfg]
1252 The point of a target config file is to package everything
1253 about a given chip that board config files need to know.
1254 In summary the target files should contain
1258 @item Add TAPs to the scan chain
1259 @item Add CPU targets (includes GDB support)
1260 @item CPU/Chip/CPU-Core specific features
1264 As a rule of thumb, a target file sets up only one chip.
1265 For a microcontroller, that will often include a single TAP,
1266 which is a CPU needing a GDB target, and its on-chip flash.
1268 More complex chips may include multiple TAPs, and the target
1269 config file may need to define them all before OpenOCD
1270 can talk to the chip.
1271 For example, some phone chips have JTAG scan chains that include
1272 an ARM core for operating system use, a DSP,
1273 another ARM core embedded in an image processing engine,
1274 and other processing engines.
1276 @subsection Default Value Boiler Plate Code
1278 All target configuration files should start with code like this,
1279 letting board config files express environment-specific
1280 differences in how things should be set up.
1283 # Boards may override chip names, perhaps based on role,
1284 # but the default should match what the vendor uses
1285 if @{ [info exists CHIPNAME] @} @{
1286 set _CHIPNAME $CHIPNAME
1288 set _CHIPNAME sam7x256
1291 # ONLY use ENDIAN with targets that can change it.
1292 if @{ [info exists ENDIAN] @} @{
1298 # TAP identifiers may change as chips mature, for example with
1299 # new revision fields (the "3" here). Pick a good default; you
1300 # can pass several such identifiers to the "jtag newtap" command.
1301 if @{ [info exists CPUTAPID ] @} @{
1302 set _CPUTAPID $CPUTAPID
1304 set _CPUTAPID 0x3f0f0f0f
1307 @c but 0x3f0f0f0f is for an str73x part ...
1309 @emph{Remember:} Board config files may include multiple target
1310 config files, or the same target file multiple times
1311 (changing at least @code{CHIPNAME}).
1313 Likewise, the target configuration file should define
1314 @code{_TARGETNAME} (or @code{_TARGETNAME0} etc) and
1315 use it later on when defining debug targets:
1318 set _TARGETNAME $_CHIPNAME.cpu
1319 target create $_TARGETNAME arm7tdmi -chain-position $_TARGETNAME
1322 @subsection Adding TAPs to the Scan Chain
1323 After the ``defaults'' are set up,
1324 add the TAPs on each chip to the JTAG scan chain.
1325 @xref{TAP Declaration}, and the naming convention
1328 In the simplest case the chip has only one TAP,
1329 probably for a CPU or FPGA.
1330 The config file for the Atmel AT91SAM7X256
1331 looks (in part) like this:
1334 jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf \
1335 -expected-id $_CPUTAPID
1338 A board with two such at91sam7 chips would be able
1339 to source such a config file twice, with different
1340 values for @code{CHIPNAME}, so
1341 it adds a different TAP each time.
1343 If there are nonzero @option{-expected-id} values,
1344 OpenOCD attempts to verify the actual tap id against those values.
1345 It will issue error messages if there is mismatch, which
1346 can help to pinpoint problems in OpenOCD configurations.
1349 JTAG tap: sam7x256.cpu tap/device found: 0x3f0f0f0f
1350 (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
1351 ERROR: Tap: sam7x256.cpu - Expected id: 0x12345678, Got: 0x3f0f0f0f
1352 ERROR: expected: mfg: 0x33c, part: 0x2345, ver: 0x1
1353 ERROR: got: mfg: 0x787, part: 0xf0f0, ver: 0x3
1356 There are more complex examples too, with chips that have
1357 multiple TAPs. Ones worth looking at include:
1360 @item @file{target/omap3530.cfg} -- with disabled ARM and DSP,
1361 plus a JRC to enable them
1362 @item @file{target/str912.cfg} -- with flash, CPU, and boundary scan
1363 @item @file{target/ti_dm355.cfg} -- with ETM, ARM, and JRC (this JRC
1364 is not currently used)
1367 @subsection Add CPU targets
1369 After adding a TAP for a CPU, you should set it up so that
1370 GDB and other commands can use it.
1371 @xref{CPU Configuration}.
1372 For the at91sam7 example above, the command can look like this;
1373 note that @code{$_ENDIAN} is not needed, since OpenOCD defaults
1374 to little endian, and this chip doesn't support changing that.
1377 set _TARGETNAME $_CHIPNAME.cpu
1378 target create $_TARGETNAME arm7tdmi -chain-position $_TARGETNAME
1381 Work areas are small RAM areas associated with CPU targets.
1382 They are used by OpenOCD to speed up downloads,
1383 and to download small snippets of code to program flash chips.
1384 If the chip includes a form of ``on-chip-ram'' - and many do - define
1385 a work area if you can.
1386 Again using the at91sam7 as an example, this can look like:
1389 $_TARGETNAME configure -work-area-phys 0x00200000 \
1390 -work-area-size 0x4000 -work-area-backup 0
1393 @subsection Chip Reset Setup
1395 As a rule, you should put the @command{reset_config} command
1396 into the board file. Most things you think you know about a
1397 chip can be tweaked by the board.
1399 Some chips have specific ways the TRST and SRST signals are
1400 managed. In the unusual case that these are @emph{chip specific}
1401 and can never be changed by board wiring, they could go here.
1403 Some chips need special attention during reset handling if
1404 they're going to be used with JTAG.
1405 An example might be needing to send some commands right
1406 after the target's TAP has been reset, providing a
1407 @code{reset-deassert-post} event handler that writes a chip
1408 register to report that JTAG debugging is being done.
1410 JTAG clocking constraints often change during reset, and in
1411 some cases target config files (rather than board config files)
1412 are the right places to handle some of those issues.
1413 For example, immediately after reset most chips run using a
1414 slower clock than they will use later.
1415 That means that after reset (and potentially, as OpenOCD
1416 first starts up) they must use a slower JTAG clock rate
1417 than they will use later.
1420 @quotation Important
1421 When you are debugging code that runs right after chip
1422 reset, getting these issues right is critical.
1423 In particular, if you see intermittent failures when
1424 OpenOCD verifies the scan chain after reset,
1425 look at how you are setting up JTAG clocking.
1428 @subsection ARM Core Specific Hacks
1430 If the chip has a DCC, enable it. If the chip is an ARM9 with some
1431 special high speed download features - enable it.
1433 If present, the MMU, the MPU and the CACHE should be disabled.
1435 Some ARM cores are equipped with trace support, which permits
1436 examination of the instruction and data bus activity. Trace
1437 activity is controlled through an ``Embedded Trace Module'' (ETM)
1438 on one of the core's scan chains. The ETM emits voluminous data
1439 through a ``trace port''. (@xref{ARM Hardware Tracing}.)
1440 If you are using an external trace port,
1441 configure it in your board config file.
1442 If you are using an on-chip ``Embedded Trace Buffer'' (ETB),
1443 configure it in your target config file.
1446 etm config $_TARGETNAME 16 normal full etb
1447 etb config $_TARGETNAME $_CHIPNAME.etb
1450 @subsection Internal Flash Configuration
1452 This applies @b{ONLY TO MICROCONTROLLERS} that have flash built in.
1454 @b{Never ever} in the ``target configuration file'' define any type of
1455 flash that is external to the chip. (For example a BOOT flash on
1456 Chip Select 0.) Such flash information goes in a board file - not
1457 the TARGET (chip) file.
1461 @item at91sam7x256 - has 256K flash YES enable it.
1462 @item str912 - has flash internal YES enable it.
1463 @item imx27 - uses boot flash on CS0 - it goes in the board file.
1464 @item pxa270 - again - CS0 flash - it goes in the board file.
1467 @node Translating Configuration Files
1468 @chapter Translating Configuration Files
1470 If you have a configuration file for another hardware debugger(Abatron,
1471 BDI2000, BDI3000, Lauterbach, Segger, MacRaigor, etc.), translating
1472 it into OpenOCD syntax is often quite straightforward. The most tricky
1473 part of creating a configuration script is oftentimes the reset init
1474 sequence where e.g. PLLs, DRAM and the like is set up.
1476 One trick that you can use when translating is to write small
1477 Tcl proc's to translate the syntax into OpenOCD syntax. This
1478 can avoid manual translation errors and make it easier to
1479 convert other scripts later on.
1481 Example of transforming quirky arguments to a simple search and
1485 # rewrite commands of the form below to arm11 mcr...
1487 # Lauterbach syntax(?)
1489 # Data.Set c15:0x042f %long 0x40000015
1491 # OpenOCD syntax when using procedure below.
1493 # setc15 0x01 0x00050078
1496 proc setc15 @{regs value@} @{
1499 echo [format "set p15 0x%04x, 0x%08x" $regs $value]
1501 arm11 mcr $TARGETNAME 15 [expr ($regs>>12)&0x7] [expr ($regs>>0)&0xf] [expr ($regs>>4)&0xf] [expr ($regs>>8)&0x7] $value
1507 @node Daemon Configuration
1508 @chapter Daemon Configuration
1509 @cindex initialization
1510 The commands here are commonly found in the openocd.cfg file and are
1511 used to specify what TCP/IP ports are used, and how GDB should be
1514 @anchor{Configuration Stage}
1515 @section Configuration Stage
1516 @cindex configuration stage
1517 @cindex config command
1519 When the OpenOCD server process starts up, it enters a
1520 @emph{configuration stage} which is the only time that
1521 certain commands, @emph{configuration commands}, may be issued.
1522 In this manual, the definition of a configuration command is
1523 presented as a @emph{Config Command}, not as a @emph{Command}
1524 which may be issued interactively.
1526 Those configuration commands include declaration of TAPs,
1528 the interface used for JTAG communication,
1529 and other basic setup.
1530 The server must leave the configuration stage before it
1531 may access or activate TAPs.
1532 After it leaves this stage, configuration commands may no
1535 The first thing OpenOCD does after leaving the configuration
1536 stage is to verify that it can talk to the scan chain
1537 (list of TAPs) which has been configured.
1538 It will warn if it doesn't find TAPs it expects to find,
1539 or finds TAPs that aren't supposed to be there.
1540 You should see no errors at this point.
1541 If you see errors, resolve them by correcting the
1542 commands you used to configure the server.
1543 Common errors include using an initial JTAG speed that's too
1544 fast, and not providing the right IDCODE values for the TAPs
1547 @deffn {Config Command} init
1548 This command terminates the configuration stage and
1549 enters the normal command mode. This can be useful to add commands to
1550 the startup scripts and commands such as resetting the target,
1551 programming flash, etc. To reset the CPU upon startup, add "init" and
1552 "reset" at the end of the config script or at the end of the OpenOCD
1553 command line using the @option{-c} command line switch.
1555 If this command does not appear in any startup/configuration file
1556 OpenOCD executes the command for you after processing all
1557 configuration files and/or command line options.
1559 @b{NOTE:} This command normally occurs at or near the end of your
1560 openocd.cfg file to force OpenOCD to ``initialize'' and make the
1561 targets ready. For example: If your openocd.cfg file needs to
1562 read/write memory on your target, @command{init} must occur before
1563 the memory read/write commands. This includes @command{nand probe}.
1566 @anchor{TCP/IP Ports}
1567 @section TCP/IP Ports
1572 The OpenOCD server accepts remote commands in several syntaxes.
1573 Each syntax uses a different TCP/IP port, which you may specify
1574 only during configuration (before those ports are opened).
1576 For reasons including security, you may wish to prevent remote
1577 access using one or more of these ports.
1578 In such cases, just specify the relevant port number as zero.
1579 If you disable all access through TCP/IP, you will need to
1580 use the command line @option{-pipe} option.
1582 @deffn {Command} gdb_port (number)
1584 Specify or query the first port used for incoming GDB connections.
1585 The GDB port for the
1586 first target will be gdb_port, the second target will listen on gdb_port + 1, and so on.
1587 When not specified during the configuration stage,
1588 the port @var{number} defaults to 3333.
1589 When specified as zero, this port is not activated.
1592 @deffn {Command} tcl_port (number)
1593 Specify or query the port used for a simplified RPC
1594 connection that can be used by clients to issue TCL commands and get the
1595 output from the Tcl engine.
1596 Intended as a machine interface.
1597 When not specified during the configuration stage,
1598 the port @var{number} defaults to 6666.
1599 When specified as zero, this port is not activated.
1602 @deffn {Command} telnet_port (number)
1603 Specify or query the
1604 port on which to listen for incoming telnet connections.
1605 This port is intended for interaction with one human through TCL commands.
1606 When not specified during the configuration stage,
1607 the port @var{number} defaults to 4444.
1608 When specified as zero, this port is not activated.
1611 @anchor{GDB Configuration}
1612 @section GDB Configuration
1614 @cindex GDB configuration
1615 You can reconfigure some GDB behaviors if needed.
1616 The ones listed here are static and global.
1617 @xref{Target Configuration}, about configuring individual targets.
1618 @xref{Target Events}, about configuring target-specific event handling.
1620 @anchor{gdb_breakpoint_override}
1621 @deffn {Command} gdb_breakpoint_override [@option{hard}|@option{soft}|@option{disable}]
1622 Force breakpoint type for gdb @command{break} commands.
1623 This option supports GDB GUIs which don't
1624 distinguish hard versus soft breakpoints, if the default OpenOCD and
1625 GDB behaviour is not sufficient. GDB normally uses hardware
1626 breakpoints if the memory map has been set up for flash regions.
1629 @deffn {Config Command} gdb_detach (@option{resume}|@option{reset}|@option{halt}|@option{nothing})
1630 Configures what OpenOCD will do when GDB detaches from the daemon.
1631 Default behaviour is @option{resume}.
1634 @anchor{gdb_flash_program}
1635 @deffn {Config Command} gdb_flash_program (@option{enable}|@option{disable})
1636 Set to @option{enable} to cause OpenOCD to program the flash memory when a
1637 vFlash packet is received.
1638 The default behaviour is @option{enable}.
1641 @deffn {Config Command} gdb_memory_map (@option{enable}|@option{disable})
1642 Set to @option{enable} to cause OpenOCD to send the memory configuration to GDB when
1643 requested. GDB will then know when to set hardware breakpoints, and program flash
1644 using the GDB load command. @command{gdb_flash_program enable} must also be enabled
1645 for flash programming to work.
1646 Default behaviour is @option{enable}.
1647 @xref{gdb_flash_program}.
1650 @deffn {Config Command} gdb_report_data_abort (@option{enable}|@option{disable})
1651 Specifies whether data aborts cause an error to be reported
1652 by GDB memory read packets.
1653 The default behaviour is @option{disable};
1654 use @option{enable} see these errors reported.
1657 @anchor{Event Polling}
1658 @section Event Polling
1660 Hardware debuggers are parts of asynchronous systems,
1661 where significant events can happen at any time.
1662 The OpenOCD server needs to detect some of these events,
1663 so it can report them to through TCL command line
1666 Examples of such events include:
1669 @item One of the targets can stop running ... maybe it triggers
1670 a code breakpoint or data watchpoint, or halts itself.
1671 @item Messages may be sent over ``debug message'' channels ... many
1672 targets support such messages sent over JTAG,
1673 for receipt by the person debugging or tools.
1674 @item Loss of power ... some adapters can detect these events.
1675 @item Resets not issued through JTAG ... such reset sources
1676 can include button presses or other system hardware, sometimes
1677 including the target itself (perhaps through a watchdog).
1678 @item Debug instrumentation sometimes supports event triggering
1679 such as ``trace buffer full'' (so it can quickly be emptied)
1680 or other signals (to correlate with code behavior).
1683 None of those events are signaled through standard JTAG signals.
1684 However, most conventions for JTAG connectors include voltage
1685 level and system reset (SRST) signal detection.
1686 Some connectors also include instrumentation signals, which
1687 can imply events when those signals are inputs.
1689 In general, OpenOCD needs to periodically check for those events,
1690 either by looking at the status of signals on the JTAG connector
1691 or by sending synchronous ``tell me your status'' JTAG requests
1692 to the various active targets.
1693 There is a command to manage and monitor that polling,
1694 which is normally done in the background.
1696 @deffn Command poll [@option{on}|@option{off}]
1697 Poll the current target for its current state.
1698 (Also, @pxref{target curstate}.)
1699 If that target is in debug mode, architecture
1700 specific information about the current state is printed.
1701 An optional parameter
1702 allows background polling to be enabled and disabled.
1704 You could use this from the TCL command shell, or
1705 from GDB using @command{monitor poll} command.
1708 background polling: on
1709 target state: halted
1710 target halted in ARM state due to debug-request, \
1711 current mode: Supervisor
1712 cpsr: 0x800000d3 pc: 0x11081bfc
1713 MMU: disabled, D-Cache: disabled, I-Cache: enabled
1718 @node Interface - Dongle Configuration
1719 @chapter Interface - Dongle Configuration
1720 @cindex config file, interface
1721 @cindex interface config file
1723 JTAG Adapters/Interfaces/Dongles are normally configured
1724 through commands in an interface configuration
1725 file which is sourced by your @file{openocd.cfg} file, or
1726 through a command line @option{-f interface/....cfg} option.
1729 source [find interface/olimex-jtag-tiny.cfg]
1733 OpenOCD what type of JTAG adapter you have, and how to talk to it.
1734 A few cases are so simple that you only need to say what driver to use:
1741 Most adapters need a bit more configuration than that.
1744 @section Interface Configuration
1746 The interface command tells OpenOCD what type of JTAG dongle you are
1747 using. Depending on the type of dongle, you may need to have one or
1748 more additional commands.
1750 @deffn {Config Command} {interface} name
1751 Use the interface driver @var{name} to connect to the
1755 @deffn Command {interface_list}
1756 List the interface drivers that have been built into
1757 the running copy of OpenOCD.
1760 @deffn Command {jtag interface}
1761 Returns the name of the interface driver being used.
1764 @section Interface Drivers
1766 Each of the interface drivers listed here must be explicitly
1767 enabled when OpenOCD is configured, in order to be made
1768 available at run time.
1770 @deffn {Interface Driver} {amt_jtagaccel}
1771 Amontec Chameleon in its JTAG Accelerator configuration,
1772 connected to a PC's EPP mode parallel port.
1773 This defines some driver-specific commands:
1775 @deffn {Config Command} {parport_port} number
1776 Specifies either the address of the I/O port (default: 0x378 for LPT1) or
1777 the number of the @file{/dev/parport} device.
1780 @deffn {Config Command} rtck [@option{enable}|@option{disable}]
1781 Displays status of RTCK option.
1782 Optionally sets that option first.
1786 @deffn {Interface Driver} {arm-jtag-ew}
1787 Olimex ARM-JTAG-EW USB adapter
1788 This has one driver-specific command:
1790 @deffn Command {armjtagew_info}
1795 @deffn {Interface Driver} {at91rm9200}
1796 Supports bitbanged JTAG from the local system,
1797 presuming that system is an Atmel AT91rm9200
1798 and a specific set of GPIOs is used.
1799 @c command: at91rm9200_device NAME
1800 @c chooses among list of bit configs ... only one option
1803 @deffn {Interface Driver} {dummy}
1804 A dummy software-only driver for debugging.
1807 @deffn {Interface Driver} {ep93xx}
1808 Cirrus Logic EP93xx based single-board computer bit-banging (in development)
1811 @deffn {Interface Driver} {ft2232}
1812 FTDI FT2232 (USB) based devices over one of the userspace libraries.
1813 These interfaces have several commands, used to configure the driver
1814 before initializing the JTAG scan chain:
1816 @deffn {Config Command} {ft2232_device_desc} description
1817 Provides the USB device description (the @emph{iProduct string})
1818 of the FTDI FT2232 device. If not
1819 specified, the FTDI default value is used. This setting is only valid
1820 if compiled with FTD2XX support.
1823 @deffn {Config Command} {ft2232_serial} serial-number
1824 Specifies the @var{serial-number} of the FTDI FT2232 device to use,
1825 in case the vendor provides unique IDs and more than one FT2232 device
1826 is connected to the host.
1827 If not specified, serial numbers are not considered.
1828 (Note that USB serial numbers can be arbitrary Unicode strings,
1829 and are not restricted to containing only decimal digits.)
1832 @deffn {Config Command} {ft2232_layout} name
1833 Each vendor's FT2232 device can use different GPIO signals
1834 to control output-enables, reset signals, and LEDs.
1835 Currently valid layout @var{name} values include:
1837 @item @b{axm0432_jtag} Axiom AXM-0432
1838 @item @b{comstick} Hitex STR9 comstick
1839 @item @b{cortino} Hitex Cortino JTAG interface
1840 @item @b{evb_lm3s811} Luminary Micro EVB_LM3S811 as a JTAG interface,
1841 either for the local Cortex-M3 (SRST only)
1842 or in a passthrough mode (neither SRST nor TRST)
1843 @item @b{luminary_icdi} Luminary In-Circuit Debug Interface (ICDI) Board
1844 @item @b{flyswatter} Tin Can Tools Flyswatter
1845 @item @b{icebear} ICEbear JTAG adapter from Section 5
1846 @item @b{jtagkey} Amontec JTAGkey and JTAGkey-Tiny (and compatibles)
1847 @item @b{jtagkey2} Amontec JTAGkey2 (and compatibles)
1848 @item @b{m5960} American Microsystems M5960
1849 @item @b{olimex-jtag} Olimex ARM-USB-OCD and ARM-USB-Tiny
1850 @item @b{oocdlink} OOCDLink
1851 @c oocdlink ~= jtagkey_prototype_v1
1852 @item @b{sheevaplug} Marvell Sheevaplug development kit
1853 @item @b{signalyzer} Xverve Signalyzer
1854 @item @b{stm32stick} Hitex STM32 Performance Stick
1855 @item @b{turtelizer2} egnite Software turtelizer2
1856 @item @b{usbjtag} "USBJTAG-1" layout described in the OpenOCD diploma thesis
1860 @deffn {Config Command} {ft2232_vid_pid} [vid pid]+
1861 The vendor ID and product ID of the FTDI FT2232 device. If not specified, the FTDI
1862 default values are used.
1863 Currently, up to eight [@var{vid}, @var{pid}] pairs may be given, e.g.
1865 ft2232_vid_pid 0x0403 0xcff8 0x15ba 0x0003
1869 @deffn {Config Command} {ft2232_latency} ms
1870 On some systems using FT2232 based JTAG interfaces the FT_Read function call in
1871 ft2232_read() fails to return the expected number of bytes. This can be caused by
1872 USB communication delays and has proved hard to reproduce and debug. Setting the
1873 FT2232 latency timer to a larger value increases delays for short USB packets but it
1874 also reduces the risk of timeouts before receiving the expected number of bytes.
1875 The OpenOCD default value is 2 and for some systems a value of 10 has proved useful.
1878 For example, the interface config file for a
1879 Turtelizer JTAG Adapter looks something like this:
1883 ft2232_device_desc "Turtelizer JTAG/RS232 Adapter"
1884 ft2232_layout turtelizer2
1885 ft2232_vid_pid 0x0403 0xbdc8
1889 @deffn {Interface Driver} {gw16012}
1890 Gateworks GW16012 JTAG programmer.
1891 This has one driver-specific command:
1893 @deffn {Config Command} {parport_port} number
1894 Specifies either the address of the I/O port (default: 0x378 for LPT1) or
1895 the number of the @file{/dev/parport} device.
1899 @deffn {Interface Driver} {jlink}
1900 Segger jlink USB adapter
1901 @c command: jlink_info
1903 @c command: jlink_hw_jtag (2|3)
1904 @c sets version 2 or 3
1907 @deffn {Interface Driver} {parport}
1908 Supports PC parallel port bit-banging cables:
1909 Wigglers, PLD download cable, and more.
1910 These interfaces have several commands, used to configure the driver
1911 before initializing the JTAG scan chain:
1913 @deffn {Config Command} {parport_cable} name
1914 The layout of the parallel port cable used to connect to the target.
1915 Currently valid cable @var{name} values include:
1918 @item @b{altium} Altium Universal JTAG cable.
1919 @item @b{arm-jtag} Same as original wiggler except SRST and
1920 TRST connections reversed and TRST is also inverted.
1921 @item @b{chameleon} The Amontec Chameleon's CPLD when operated
1922 in configuration mode. This is only used to
1923 program the Chameleon itself, not a connected target.
1924 @item @b{dlc5} The Xilinx Parallel cable III.
1925 @item @b{flashlink} The ST Parallel cable.
1926 @item @b{lattice} Lattice ispDOWNLOAD Cable
1927 @item @b{old_amt_wiggler} The Wiggler configuration that comes with
1929 Amontec's Chameleon Programmer. The new version available from
1930 the website uses the original Wiggler layout ('@var{wiggler}')
1931 @item @b{triton} The parallel port adapter found on the
1932 ``Karo Triton 1 Development Board''.
1933 This is also the layout used by the HollyGates design
1934 (see @uref{http://www.lartmaker.nl/projects/jtag/}).
1935 @item @b{wiggler} The original Wiggler layout, also supported by
1936 several clones, such as the Olimex ARM-JTAG
1937 @item @b{wiggler2} Same as original wiggler except an led is fitted on D5.
1938 @item @b{wiggler_ntrst_inverted} Same as original wiggler except TRST is inverted.
1942 @deffn {Config Command} {parport_port} number
1943 Either the address of the I/O port (default: 0x378 for LPT1) or the number of
1944 the @file{/dev/parport} device
1946 When using PPDEV to access the parallel port, use the number of the parallel port:
1947 @option{parport_port 0} (the default). If @option{parport_port 0x378} is specified
1948 you may encounter a problem.
1951 @deffn {Config Command} {parport_write_on_exit} (on|off)
1952 This will configure the parallel driver to write a known
1953 cable-specific value to the parallel interface on exiting OpenOCD
1956 For example, the interface configuration file for a
1957 classic ``Wiggler'' cable might look something like this:
1962 parport_cable wiggler
1966 @deffn {Interface Driver} {presto}
1967 ASIX PRESTO USB JTAG programmer.
1968 @c command: presto_serial str
1969 @c sets serial number
1972 @deffn {Interface Driver} {rlink}
1973 Raisonance RLink USB adapter
1976 @deffn {Interface Driver} {usbprog}
1977 usbprog is a freely programmable USB adapter.
1980 @deffn {Interface Driver} {vsllink}
1981 vsllink is part of Versaloon which is a versatile USB programmer.
1984 This defines quite a few driver-specific commands,
1985 which are not currently documented here.
1989 @deffn {Interface Driver} {ZY1000}
1990 This is the Zylin ZY1000 JTAG debugger.
1993 This defines some driver-specific commands,
1994 which are not currently documented here.
1997 @deffn Command power [@option{on}|@option{off}]
1998 Turn power switch to target on/off.
1999 No arguments: print status.
2006 JTAG clock setup is part of system setup.
2007 It @emph{does not belong with interface setup} since any interface
2008 only knows a few of the constraints for the JTAG clock speed.
2009 Sometimes the JTAG speed is
2010 changed during the target initialization process: (1) slow at
2011 reset, (2) program the CPU clocks, (3) run fast.
2012 Both the "slow" and "fast" clock rates are functions of the
2013 oscillators used, the chip, the board design, and sometimes
2014 power management software that may be active.
2016 The speed used during reset, and the scan chain verification which
2017 follows reset, can be adjusted using a @code{reset-start}
2018 target event handler.
2019 It can then be reconfigured to a faster speed by a
2020 @code{reset-init} target event handler after it reprograms those
2021 CPU clocks, or manually (if something else, such as a boot loader,
2022 sets up those clocks).
2023 @xref{Target Events}.
2024 When the initial low JTAG speed is a chip characteristic, perhaps
2025 because of a required oscillator speed, provide such a handler
2026 in the target config file.
2027 When that speed is a function of a board-specific characteristic
2028 such as which speed oscillator is used, it belongs in the board
2029 config file instead.
2030 In both cases it's safest to also set the initial JTAG clock rate
2031 to that same slow speed, so that OpenOCD never starts up using a
2032 clock speed that's faster than the scan chain can support.
2036 $_TARGET.cpu configure -event reset-start @{ jtag_rclk 3000 @}
2039 If your system supports adaptive clocking (RTCK), configuring
2040 JTAG to use that is probably the most robust approach.
2041 However, it introduces delays to synchronize clocks; so it
2042 may not be the fastest solution.
2044 @b{NOTE:} Script writers should consider using @command{jtag_rclk}
2045 instead of @command{jtag_khz}.
2047 @deffn {Command} jtag_khz max_speed_kHz
2048 A non-zero speed is in KHZ. Hence: 3000 is 3mhz.
2049 JTAG interfaces usually support a limited number of
2050 speeds. The speed actually used won't be faster
2051 than the speed specified.
2053 Chip data sheets generally include a top JTAG clock rate.
2054 The actual rate is often a function of a CPU core clock,
2055 and is normally less than that peak rate.
2056 For example, most ARM cores accept at most one sixth of the CPU clock.
2058 Speed 0 (khz) selects RTCK method.
2060 If your system uses RTCK, you won't need to change the
2061 JTAG clocking after setup.
2062 Not all interfaces, boards, or targets support ``rtck''.
2063 If the interface device can not
2064 support it, an error is returned when you try to use RTCK.
2067 @defun jtag_rclk fallback_speed_kHz
2068 @cindex adaptive clocking
2070 This Tcl proc (defined in @file{startup.tcl}) attempts to enable RTCK/RCLK.
2071 If that fails (maybe the interface, board, or target doesn't
2072 support it), falls back to the specified frequency.
2074 # Fall back to 3mhz if RTCK is not supported
2079 @node Reset Configuration
2080 @chapter Reset Configuration
2081 @cindex Reset Configuration
2083 Every system configuration may require a different reset
2084 configuration. This can also be quite confusing.
2085 Resets also interact with @var{reset-init} event handlers,
2086 which do things like setting up clocks and DRAM, and
2087 JTAG clock rates. (@xref{JTAG Speed}.)
2088 They can also interact with JTAG routers.
2089 Please see the various board files for examples.
2092 To maintainers and integrators:
2093 Reset configuration touches several things at once.
2094 Normally the board configuration file
2095 should define it and assume that the JTAG adapter supports
2096 everything that's wired up to the board's JTAG connector.
2098 However, the target configuration file could also make note
2099 of something the silicon vendor has done inside the chip,
2100 which will be true for most (or all) boards using that chip.
2101 And when the JTAG adapter doesn't support everything, the
2102 user configuration file will need to override parts of
2103 the reset configuration provided by other files.
2106 @section Types of Reset
2108 There are many kinds of reset possible through JTAG, but
2109 they may not all work with a given board and adapter.
2110 That's part of why reset configuration can be error prone.
2114 @emph{System Reset} ... the @emph{SRST} hardware signal
2115 resets all chips connected to the JTAG adapter, such as processors,
2116 power management chips, and I/O controllers. Normally resets triggered
2117 with this signal behave exactly like pressing a RESET button.
2119 @emph{JTAG TAP Reset} ... the @emph{TRST} hardware signal resets
2120 just the TAP controllers connected to the JTAG adapter.
2121 Such resets should not be visible to the rest of the system; resetting a
2122 device's the TAP controller just puts that controller into a known state.
2124 @emph{Emulation Reset} ... many devices can be reset through JTAG
2125 commands. These resets are often distinguishable from system
2126 resets, either explicitly (a "reset reason" register says so)
2127 or implicitly (not all parts of the chip get reset).
2129 @emph{Other Resets} ... system-on-chip devices often support
2130 several other types of reset.
2131 You may need to arrange that a watchdog timer stops
2132 while debugging, preventing a watchdog reset.
2133 There may be individual module resets.
2136 In the best case, OpenOCD can hold SRST, then reset
2137 the TAPs via TRST and send commands through JTAG to halt the
2138 CPU at the reset vector before the 1st instruction is executed.
2139 Then when it finally releases the SRST signal, the system is
2140 halted under debugger control before any code has executed.
2141 This is the behavior required to support the @command{reset halt}
2142 and @command{reset init} commands; after @command{reset init} a
2143 board-specific script might do things like setting up DRAM.
2144 (@xref{Reset Command}.)
2146 @anchor{SRST and TRST Issues}
2147 @section SRST and TRST Issues
2149 Because SRST and TRST are hardware signals, they can have a
2150 variety of system-specific constraints. Some of the most
2155 @item @emph{Signal not available} ... Some boards don't wire
2156 SRST or TRST to the JTAG connector. Some JTAG adapters don't
2157 support such signals even if they are wired up.
2158 Use the @command{reset_config} @var{signals} options to say
2159 when either of those signals is not connected.
2160 When SRST is not available, your code might not be able to rely
2161 on controllers having been fully reset during code startup.
2162 Missing TRST is not a problem, since JTAG level resets can
2163 be triggered using with TMS signaling.
2165 @item @emph{Signals shorted} ... Sometimes a chip, board, or
2166 adapter will connect SRST to TRST, instead of keeping them separate.
2167 Use the @command{reset_config} @var{combination} options to say
2168 when those signals aren't properly independent.
2170 @item @emph{Timing} ... Reset circuitry like a resistor/capacitor
2171 delay circuit, reset supervisor, or on-chip features can extend
2172 the effect of a JTAG adapter's reset for some time after the adapter
2173 stops issuing the reset. For example, there may be chip or board
2174 requirements that all reset pulses last for at least a
2175 certain amount of time; and reset buttons commonly have
2176 hardware debouncing.
2177 Use the @command{jtag_nsrst_delay} and @command{jtag_ntrst_delay}
2178 commands to say when extra delays are needed.
2180 @item @emph{Drive type} ... Reset lines often have a pullup
2181 resistor, letting the JTAG interface treat them as open-drain
2182 signals. But that's not a requirement, so the adapter may need
2183 to use push/pull output drivers.
2184 Also, with weak pullups it may be advisable to drive
2185 signals to both levels (push/pull) to minimize rise times.
2186 Use the @command{reset_config} @var{trst_type} and
2187 @var{srst_type} parameters to say how to drive reset signals.
2189 @item @emph{Special initialization} ... Targets sometimes need
2190 special JTAG initialization sequences to handle chip-specific
2191 issues (not limited to errata).
2192 For example, certain JTAG commands might need to be issued while
2193 the system as a whole is in a reset state (SRST active)
2194 but the JTAG scan chain is usable (TRST inactive).
2195 (@xref{JTAG Commands}, where the @command{jtag_reset}
2196 command is presented.)
2199 There can also be other issues.
2200 Some devices don't fully conform to the JTAG specifications.
2201 Trivial system-specific differences are common, such as
2202 SRST and TRST using slightly different names.
2203 There are also vendors who distribute key JTAG documentation for
2204 their chips only to developers who have signed a Non-Disclosure
2207 Sometimes there are chip-specific extensions like a requirement to use
2208 the normally-optional TRST signal (precluding use of JTAG adapters which
2209 don't pass TRST through), or needing extra steps to complete a TAP reset.
2211 In short, SRST and especially TRST handling may be very finicky,
2212 needing to cope with both architecture and board specific constraints.
2214 @section Commands for Handling Resets
2216 @deffn {Command} jtag_nsrst_delay milliseconds
2217 How long (in milliseconds) OpenOCD should wait after deasserting
2218 nSRST (active-low system reset) before starting new JTAG operations.
2219 When a board has a reset button connected to SRST line it will
2220 probably have hardware debouncing, implying you should use this.
2223 @deffn {Command} jtag_ntrst_delay milliseconds
2224 How long (in milliseconds) OpenOCD should wait after deasserting
2225 nTRST (active-low JTAG TAP reset) before starting new JTAG operations.
2228 @deffn {Command} reset_config mode_flag ...
2229 This command displays or modifies the reset configuration
2230 of your combination of JTAG board and target in target
2231 configuration scripts.
2233 Information earlier in this section describes the kind of problems
2234 the command is intended to address (@pxref{SRST and TRST Issues}).
2235 As a rule this command belongs only in board config files,
2236 describing issues like @emph{board doesn't connect TRST};
2237 or in user config files, addressing limitations derived
2238 from a particular combination of interface and board.
2239 (An unlikely example would be using a TRST-only adapter
2240 with a board that only wires up SRST.)
2242 The @var{mode_flag} options can be specified in any order, but only one
2243 of each type -- @var{signals}, @var{combination},
2246 and @var{srst_type} -- may be specified at a time.
2247 If you don't provide a new value for a given type, its previous
2248 value (perhaps the default) is unchanged.
2249 For example, this means that you don't need to say anything at all about
2250 TRST just to declare that if the JTAG adapter should want to drive SRST,
2251 it must explicitly be driven high (@option{srst_push_pull}).
2255 @var{signals} can specify which of the reset signals are connected.
2256 For example, If the JTAG interface provides SRST, but the board doesn't
2257 connect that signal properly, then OpenOCD can't use it.
2258 Possible values are @option{none} (the default), @option{trst_only},
2259 @option{srst_only} and @option{trst_and_srst}.
2262 If your board provides SRST and/or TRST through the JTAG connector,
2263 you must declare that or else those signals will not be used.
2267 The @var{combination} is an optional value specifying broken reset
2268 signal implementations.
2269 The default behaviour if no option given is @option{separate},
2270 indicating everything behaves normally.
2271 @option{srst_pulls_trst} states that the
2272 test logic is reset together with the reset of the system (e.g. Philips
2273 LPC2000, "broken" board layout), @option{trst_pulls_srst} says that
2274 the system is reset together with the test logic (only hypothetical, I
2275 haven't seen hardware with such a bug, and can be worked around).
2276 @option{combined} implies both @option{srst_pulls_trst} and
2277 @option{trst_pulls_srst}.
2280 The @var{gates} tokens control flags that describe some cases where
2281 JTAG may be unvailable during reset.
2282 @option{srst_gates_jtag} (default)
2283 indicates that asserting SRST gates the
2284 JTAG clock. This means that no communication can happen on JTAG
2285 while SRST is asserted.
2286 Its converse is @option{srst_nogate}, indicating that JTAG commands
2287 can safely be issued while SRST is active.
2290 The optional @var{trst_type} and @var{srst_type} parameters allow the
2291 driver mode of each reset line to be specified. These values only affect
2292 JTAG interfaces with support for different driver modes, like the Amontec
2293 JTAGkey and JTAG Accelerator. Also, they are necessarily ignored if the
2294 relevant signal (TRST or SRST) is not connected.
2298 Possible @var{trst_type} driver modes for the test reset signal (TRST)
2299 are the default @option{trst_push_pull}, and @option{trst_open_drain}.
2300 Most boards connect this signal to a pulldown, so the JTAG TAPs
2301 never leave reset unless they are hooked up to a JTAG adapter.
2304 Possible @var{srst_type} driver modes for the system reset signal (SRST)
2305 are the default @option{srst_open_drain}, and @option{srst_push_pull}.
2306 Most boards connect this signal to a pullup, and allow the
2307 signal to be pulled low by various events including system
2308 powerup and pressing a reset button.
2313 @node TAP Declaration
2314 @chapter TAP Declaration
2315 @cindex TAP declaration
2316 @cindex TAP configuration
2318 @emph{Test Access Ports} (TAPs) are the core of JTAG.
2319 TAPs serve many roles, including:
2322 @item @b{Debug Target} A CPU TAP can be used as a GDB debug target
2323 @item @b{Flash Programing} Some chips program the flash directly via JTAG.
2324 Others do it indirectly, making a CPU do it.
2325 @item @b{Program Download} Using the same CPU support GDB uses,
2326 you can initialize a DRAM controller, download code to DRAM, and then
2327 start running that code.
2328 @item @b{Boundary Scan} Most chips support boundary scan, which
2329 helps test for board assembly problems like solder bridges
2330 and missing connections
2333 OpenOCD must know about the active TAPs on your board(s).
2334 Setting up the TAPs is the core task of your configuration files.
2335 Once those TAPs are set up, you can pass their names to code
2336 which sets up CPUs and exports them as GDB targets,
2337 probes flash memory, performs low-level JTAG operations, and more.
2339 @section Scan Chains
2342 TAPs are part of a hardware @dfn{scan chain},
2343 which is daisy chain of TAPs.
2344 They also need to be added to
2345 OpenOCD's software mirror of that hardware list,
2346 giving each member a name and associating other data with it.
2347 Simple scan chains, with a single TAP, are common in
2348 systems with a single microcontroller or microprocessor.
2349 More complex chips may have several TAPs internally.
2350 Very complex scan chains might have a dozen or more TAPs:
2351 several in one chip, more in the next, and connecting
2352 to other boards with their own chips and TAPs.
2354 You can display the list with the @command{scan_chain} command.
2355 (Don't confuse this with the list displayed by the @command{targets}
2356 command, presented in the next chapter.
2357 That only displays TAPs for CPUs which are configured as
2359 Here's what the scan chain might look like for a chip more than one TAP:
2362 TapName Enabled IdCode Expected IrLen IrCap IrMask Instr
2363 -- ------------------ ------- ---------- ---------- ----- ----- ------ -----
2364 0 omap5912.dsp Y 0x03df1d81 0x03df1d81 38 0 0 0x...
2365 1 omap5912.arm Y 0x0692602f 0x0692602f 4 0x1 0 0xc
2366 2 omap5912.unknown Y 0x00000000 0x00000000 8 0 0 0xff
2369 Unfortunately those TAPs can't always be autoconfigured,
2370 because not all devices provide good support for that.
2371 JTAG doesn't require supporting IDCODE instructions, and
2372 chips with JTAG routers may not link TAPs into the chain
2373 until they are told to do so.
2375 The configuration mechanism currently supported by OpenOCD
2376 requires explicit configuration of all TAP devices using
2377 @command{jtag newtap} commands, as detailed later in this chapter.
2378 A command like this would declare one tap and name it @code{chip1.cpu}:
2381 jtag newtap chip1 cpu -irlen 7 -ircapture 0x01 -irmask 0x55
2384 Each target configuration file lists the TAPs provided
2386 Board configuration files combine all the targets on a board,
2388 Note that @emph{the order in which TAPs are declared is very important.}
2389 It must match the order in the JTAG scan chain, both inside
2390 a single chip and between them.
2391 @xref{FAQ TAP Order}.
2393 For example, the ST Microsystems STR912 chip has
2394 three separate TAPs@footnote{See the ST
2395 document titled: @emph{STR91xFAxxx, Section 3.15 Jtag Interface, Page:
2396 28/102, Figure 3: JTAG chaining inside the STR91xFA}.
2397 @url{http://eu.st.com/stonline/products/literature/ds/13495.pdf}}.
2398 To configure those taps, @file{target/str912.cfg}
2399 includes commands something like this:
2402 jtag newtap str912 flash ... params ...
2403 jtag newtap str912 cpu ... params ...
2404 jtag newtap str912 bs ... params ...
2407 Actual config files use a variable instead of literals like
2408 @option{str912}, to support more than one chip of each type.
2409 @xref{Config File Guidelines}.
2411 @deffn Command {jtag names}
2412 Returns the names of all current TAPs in the scan chain.
2413 Use @command{jtag cget} or @command{jtag tapisenabled}
2414 to examine attributes and state of each TAP.
2416 foreach t [jtag names] @{
2417 puts [format "TAP: %s\n" $t]
2422 @deffn Command {scan_chain}
2423 Displays the TAPs in the scan chain configuration,
2425 The set of TAPs listed by this command is fixed by
2426 exiting the OpenOCD configuration stage,
2427 but systems with a JTAG router can
2428 enable or disable TAPs dynamically.
2429 In addition to the enable/disable status, the contents of
2430 each TAP's instruction register can also change.
2433 @c FIXME! "jtag cget" should be able to return all TAP
2434 @c attributes, like "$target_name cget" does for targets.
2436 @c Probably want "jtag eventlist", and a "tap-reset" event
2437 @c (on entry to RESET state).
2442 When TAP objects are declared with @command{jtag newtap},
2443 a @dfn{dotted.name} is created for the TAP, combining the
2444 name of a module (usually a chip) and a label for the TAP.
2445 For example: @code{xilinx.tap}, @code{str912.flash},
2446 @code{omap3530.jrc}, @code{dm6446.dsp}, or @code{stm32.cpu}.
2447 Many other commands use that dotted.name to manipulate or
2448 refer to the TAP. For example, CPU configuration uses the
2449 name, as does declaration of NAND or NOR flash banks.
2451 The components of a dotted name should follow ``C'' symbol
2452 name rules: start with an alphabetic character, then numbers
2453 and underscores are OK; while others (including dots!) are not.
2456 In older code, JTAG TAPs were numbered from 0..N.
2457 This feature is still present.
2458 However its use is highly discouraged, and
2459 should not be relied on; it will be removed by mid-2010.
2460 Update all of your scripts to use TAP names rather than numbers,
2461 by paying attention to the runtime warnings they trigger.
2462 Using TAP numbers in target configuration scripts prevents
2463 reusing those scripts on boards with multiple targets.
2466 @section TAP Declaration Commands
2468 @c shouldn't this be(come) a {Config Command}?
2469 @anchor{jtag newtap}
2470 @deffn Command {jtag newtap} chipname tapname configparams...
2471 Declares a new TAP with the dotted name @var{chipname}.@var{tapname},
2472 and configured according to the various @var{configparams}.
2474 The @var{chipname} is a symbolic name for the chip.
2475 Conventionally target config files use @code{$_CHIPNAME},
2476 defaulting to the model name given by the chip vendor but
2479 @cindex TAP naming convention
2480 The @var{tapname} reflects the role of that TAP,
2481 and should follow this convention:
2484 @item @code{bs} -- For boundary scan if this is a seperate TAP;
2485 @item @code{cpu} -- The main CPU of the chip, alternatively
2486 @code{arm} and @code{dsp} on chips with both ARM and DSP CPUs,
2487 @code{arm1} and @code{arm2} on chips two ARMs, and so forth;
2488 @item @code{etb} -- For an embedded trace buffer (example: an ARM ETB11);
2489 @item @code{flash} -- If the chip has a flash TAP, like the str912;
2490 @item @code{jrc} -- For JTAG route controller (example: the ICEpick modules
2491 on many Texas Instruments chips, like the OMAP3530 on Beagleboards);
2492 @item @code{tap} -- Should be used only FPGA or CPLD like devices
2494 @item @code{unknownN} -- If you have no idea what the TAP is for (N is a number);
2495 @item @emph{when in doubt} -- Use the chip maker's name in their data sheet.
2496 For example, the Freescale IMX31 has a SDMA (Smart DMA) with
2497 a JTAG TAP; that TAP should be named @code{sdma}.
2500 Every TAP requires at least the following @var{configparams}:
2503 @item @code{-irlen} @var{NUMBER}
2504 @*The length in bits of the
2505 instruction register, such as 4 or 5 bits.
2508 A TAP may also provide optional @var{configparams}:
2511 @item @code{-disable} (or @code{-enable})
2512 @*Use the @code{-disable} parameter to flag a TAP which is not
2513 linked in to the scan chain after a reset using either TRST
2514 or the JTAG state machine's @sc{reset} state.
2515 You may use @code{-enable} to highlight the default state
2516 (the TAP is linked in).
2517 @xref{Enabling and Disabling TAPs}.
2518 @item @code{-expected-id} @var{number}
2519 @*A non-zero @var{number} represents a 32-bit IDCODE
2520 which you expect to find when the scan chain is examined.
2521 These codes are not required by all JTAG devices.
2522 @emph{Repeat the option} as many times as required if more than one
2523 ID code could appear (for example, multiple versions).
2524 Specify @var{number} as zero to suppress warnings about IDCODE
2525 values that were found but not included in the list.
2526 @item @code{-ircapture} @var{NUMBER}
2527 @*The bit pattern loaded by the TAP into the JTAG shift register
2528 on entry to the @sc{ircapture} state, such as 0x01.
2529 JTAG requires the two LSBs of this value to be 01.
2530 By default, @code{-ircapture} and @code{-irmask} are set
2531 up to verify that two-bit value; but you may provide
2532 additional bits, if you know them.
2533 @item @code{-irmask} @var{NUMBER}
2534 @*A mask used with @code{-ircapture}
2535 to verify that instruction scans work correctly.
2536 Such scans are not used by OpenOCD except to verify that
2537 there seems to be no problems with JTAG scan chain operations.
2541 @section Other TAP commands
2543 @c @deffn Command {jtag arp_init-reset}
2544 @c ... more or less "toggle TRST ... and SRST too, what the heck"
2546 @deffn Command {jtag cget} dotted.name @option{-event} name
2547 @deffnx Command {jtag configure} dotted.name @option{-event} name string
2548 At this writing this TAP attribute
2549 mechanism is used only for event handling.
2550 (It is not a direct analogue of the @code{cget}/@code{configure}
2551 mechanism for debugger targets.)
2552 See the next section for information about the available events.
2554 The @code{configure} subcommand assigns an event handler,
2555 a TCL string which is evaluated when the event is triggered.
2556 The @code{cget} subcommand returns that handler.
2564 OpenOCD includes two event mechanisms.
2565 The one presented here applies to all JTAG TAPs.
2566 The other applies to debugger targets,
2567 which are associated with certain TAPs.
2569 The TAP events currently defined are:
2572 @item @b{post-reset}
2573 @* The TAP has just completed a JTAG reset.
2574 The tap may still be in the JTAG @sc{reset} state.
2575 Handlers for these events might perform initialization sequences
2576 such as issuing TCK cycles, TMS sequences to ensure
2577 exit from the ARM SWD mode, and more.
2579 Because the scan chain has not yet been verified, handlers for these events
2580 @emph{should not issue commands which scan the JTAG IR or DR registers}
2581 of any particular target.
2582 @b{NOTE:} As this is written (September 2009), nothing prevents such access.
2584 @* The scan chain has been reset and verified.
2585 This handler may enable TAPs as needed.
2586 @item @b{tap-disable}
2587 @* The TAP needs to be disabled. This handler should
2588 implement @command{jtag tapdisable}
2589 by issuing the relevant JTAG commands.
2590 @item @b{tap-enable}
2591 @* The TAP needs to be enabled. This handler should
2592 implement @command{jtag tapenable}
2593 by issuing the relevant JTAG commands.
2596 If you need some action after each JTAG reset, which isn't actually
2597 specific to any TAP (since you can't yet trust the scan chain's
2598 contents to be accurate), you might:
2601 jtag configure CHIP.jrc -event post-reset @{
2602 echo "JTAG Reset done"
2603 ... non-scan jtag operations to be done after reset
2608 @anchor{Enabling and Disabling TAPs}
2609 @section Enabling and Disabling TAPs
2610 @cindex JTAG Route Controller
2613 In some systems, a @dfn{JTAG Route Controller} (JRC)
2614 is used to enable and/or disable specific JTAG TAPs.
2615 Many ARM based chips from Texas Instruments include
2616 an ``ICEpick'' module, which is a JRC.
2617 Such chips include DaVinci and OMAP3 processors.
2619 A given TAP may not be visible until the JRC has been
2620 told to link it into the scan chain; and if the JRC
2621 has been told to unlink that TAP, it will no longer
2623 Such routers address problems that JTAG ``bypass mode''
2627 @item The scan chain can only go as fast as its slowest TAP.
2628 @item Having many TAPs slows instruction scans, since all
2629 TAPs receive new instructions.
2630 @item TAPs in the scan chain must be powered up, which wastes
2631 power and prevents debugging some power management mechanisms.
2634 The IEEE 1149.1 JTAG standard has no concept of a ``disabled'' tap,
2635 as implied by the existence of JTAG routers.
2636 However, the upcoming IEEE 1149.7 framework (layered on top of JTAG)
2637 does include a kind of JTAG router functionality.
2639 @c (a) currently the event handlers don't seem to be able to
2640 @c fail in a way that could lead to no-change-of-state.
2642 In OpenOCD, tap enabling/disabling is invoked by the Tcl commands
2643 shown below, and is implemented using TAP event handlers.
2644 So for example, when defining a TAP for a CPU connected to
2645 a JTAG router, your @file{target.cfg} file
2646 should define TAP event handlers using
2647 code that looks something like this:
2650 jtag configure CHIP.cpu -event tap-enable @{
2651 ... jtag operations using CHIP.jrc
2653 jtag configure CHIP.cpu -event tap-disable @{
2654 ... jtag operations using CHIP.jrc
2658 Then you might want that CPU's TAP enabled almost all the time:
2661 jtag configure $CHIP.jrc -event setup "jtag tapenable $CHIP.cpu"
2664 Note how that particular setup event handler declaration
2665 uses quotes to evaluate @code{$CHIP} when the event is configured.
2666 Using brackets @{ @} would cause it to be evaluated later,
2667 at runtime, when it might have a different value.
2669 @deffn Command {jtag tapdisable} dotted.name
2670 If necessary, disables the tap
2671 by sending it a @option{tap-disable} event.
2672 Returns the string "1" if the tap
2673 specified by @var{dotted.name} is enabled,
2674 and "0" if it is disabled.
2677 @deffn Command {jtag tapenable} dotted.name
2678 If necessary, enables the tap
2679 by sending it a @option{tap-enable} event.
2680 Returns the string "1" if the tap
2681 specified by @var{dotted.name} is enabled,
2682 and "0" if it is disabled.
2685 @deffn Command {jtag tapisenabled} dotted.name
2686 Returns the string "1" if the tap
2687 specified by @var{dotted.name} is enabled,
2688 and "0" if it is disabled.
2691 Humans will find the @command{scan_chain} command more helpful
2692 for querying the state of the JTAG taps.
2696 @node CPU Configuration
2697 @chapter CPU Configuration
2700 This chapter discusses how to set up GDB debug targets for CPUs.
2701 You can also access these targets without GDB
2702 (@pxref{Architecture and Core Commands},
2703 and @ref{Target State handling}) and
2704 through various kinds of NAND and NOR flash commands.
2705 If you have multiple CPUs you can have multiple such targets.
2707 We'll start by looking at how to examine the targets you have,
2708 then look at how to add one more target and how to configure it.
2710 @section Target List
2711 @cindex target, current
2712 @cindex target, list
2714 All targets that have been set up are part of a list,
2715 where each member has a name.
2716 That name should normally be the same as the TAP name.
2717 You can display the list with the @command{targets}
2719 This display often has only one CPU; here's what it might
2720 look like with more than one:
2722 TargetName Type Endian TapName State
2723 -- ------------------ ---------- ------ ------------------ ------------
2724 0* at91rm9200.cpu arm920t little at91rm9200.cpu running
2725 1 MyTarget cortex_m3 little mychip.foo tap-disabled
2728 One member of that list is the @dfn{current target}, which
2729 is implicitly referenced by many commands.
2730 It's the one marked with a @code{*} near the target name.
2731 In particular, memory addresses often refer to the address
2732 space seen by that current target.
2733 Commands like @command{mdw} (memory display words)
2734 and @command{flash erase_address} (erase NOR flash blocks)
2735 are examples; and there are many more.
2737 Several commands let you examine the list of targets:
2739 @deffn Command {target count}
2740 @emph{Note: target numbers are deprecated; don't use them.
2741 They will be removed shortly after August 2010, including this command.
2742 Iterate target using @command{target names}, not by counting.}
2744 Returns the number of targets, @math{N}.
2745 The highest numbered target is @math{N - 1}.
2747 set c [target count]
2748 for @{ set x 0 @} @{ $x < $c @} @{ incr x @} @{
2749 # Assuming you have created this function
2750 print_target_details $x
2755 @deffn Command {target current}
2756 Returns the name of the current target.
2759 @deffn Command {target names}
2760 Lists the names of all current targets in the list.
2762 foreach t [target names] @{
2763 puts [format "Target: %s\n" $t]
2768 @deffn Command {target number} number
2769 @emph{Note: target numbers are deprecated; don't use them.
2770 They will be removed shortly after August 2010, including this command.}
2772 The list of targets is numbered starting at zero.
2773 This command returns the name of the target at index @var{number}.
2775 set thename [target number $x]
2776 puts [format "Target %d is: %s\n" $x $thename]
2780 @c yep, "target list" would have been better.
2781 @c plus maybe "target setdefault".
2783 @deffn Command targets [name]
2784 @emph{Note: the name of this command is plural. Other target
2785 command names are singular.}
2787 With no parameter, this command displays a table of all known
2788 targets in a user friendly form.
2790 With a parameter, this command sets the current target to
2791 the given target with the given @var{name}; this is
2792 only relevant on boards which have more than one target.
2795 @section Target CPU Types and Variants
2800 Each target has a @dfn{CPU type}, as shown in the output of
2801 the @command{targets} command. You need to specify that type
2802 when calling @command{target create}.
2803 The CPU type indicates more than just the instruction set.
2804 It also indicates how that instruction set is implemented,
2805 what kind of debug support it integrates,
2806 whether it has an MMU (and if so, what kind),
2807 what core-specific commands may be available
2808 (@pxref{Architecture and Core Commands}),
2811 For some CPU types, OpenOCD also defines @dfn{variants} which
2812 indicate differences that affect their handling.
2813 For example, a particular implementation bug might need to be
2814 worked around in some chip versions.
2816 It's easy to see what target types are supported,
2817 since there's a command to list them.
2818 However, there is currently no way to list what target variants
2819 are supported (other than by reading the OpenOCD source code).
2821 @anchor{target types}
2822 @deffn Command {target types}
2823 Lists all supported target types.
2824 At this writing, the supported CPU types and variants are:
2827 @item @code{arm11} -- this is a generation of ARMv6 cores
2828 @item @code{arm720t} -- this is an ARMv4 core
2829 @item @code{arm7tdmi} -- this is an ARMv4 core
2830 @item @code{arm920t} -- this is an ARMv5 core
2831 @item @code{arm926ejs} -- this is an ARMv5 core
2832 @item @code{arm966e} -- this is an ARMv5 core
2833 @item @code{arm9tdmi} -- this is an ARMv4 core
2834 @item @code{avr} -- implements Atmel's 8-bit AVR instruction set.
2835 (Support for this is preliminary and incomplete.)
2836 @item @code{cortex_a8} -- this is an ARMv7 core
2837 @item @code{cortex_m3} -- this is an ARMv7 core, supporting only the
2838 compact Thumb2 instruction set. It supports one variant:
2840 @item @code{lm3s} ... Use this when debugging older Stellaris LM3S targets.
2841 This will cause OpenOCD to use a software reset rather than asserting
2842 SRST, to avoid a issue with clearing the debug registers.
2843 This is fixed in Fury Rev B, DustDevil Rev B, Tempest; these revisions will
2844 be detected and the normal reset behaviour used.
2846 @item @code{fa526} -- resembles arm920 (w/o Thumb)
2847 @item @code{feroceon} -- resembles arm926
2848 @item @code{mips_m4k} -- a MIPS core. This supports one variant:
2850 @item @code{ejtag_srst} ... Use this when debugging targets that do not
2851 provide a functional SRST line on the EJTAG connector. This causes
2852 OpenOCD to instead use an EJTAG software reset command to reset the
2854 You still need to enable @option{srst} on the @command{reset_config}
2855 command to enable OpenOCD hardware reset functionality.
2857 @item @code{xscale} -- this is actually an architecture,
2858 not a CPU type. It is based on the ARMv5 architecture.
2859 There are several variants defined:
2861 @item @code{ixp42x}, @code{ixp45x}, @code{ixp46x},
2862 @code{pxa27x} ... instruction register length is 7 bits
2863 @item @code{pxa250}, @code{pxa255},
2864 @code{pxa26x} ... instruction register length is 5 bits
2869 To avoid being confused by the variety of ARM based cores, remember
2870 this key point: @emph{ARM is a technology licencing company}.
2871 (See: @url{http://www.arm.com}.)
2872 The CPU name used by OpenOCD will reflect the CPU design that was
2873 licenced, not a vendor brand which incorporates that design.
2874 Name prefixes like arm7, arm9, arm11, and cortex
2875 reflect design generations;
2876 while names like ARMv4, ARMv5, ARMv6, and ARMv7
2877 reflect an architecture version implemented by a CPU design.
2879 @anchor{Target Configuration}
2880 @section Target Configuration
2882 Before creating a ``target'', you must have added its TAP to the scan chain.
2883 When you've added that TAP, you will have a @code{dotted.name}
2884 which is used to set up the CPU support.
2885 The chip-specific configuration file will normally configure its CPU(s)
2886 right after it adds all of the chip's TAPs to the scan chain.
2888 Although you can set up a target in one step, it's often clearer if you
2889 use shorter commands and do it in two steps: create it, then configure
2891 All operations on the target after it's created will use a new
2892 command, created as part of target creation.
2894 The two main things to configure after target creation are
2895 a work area, which usually has target-specific defaults even
2896 if the board setup code overrides them later;
2897 and event handlers (@pxref{Target Events}), which tend
2898 to be much more board-specific.
2899 The key steps you use might look something like this
2902 target create MyTarget cortex_m3 -chain-position mychip.cpu
2903 $MyTarget configure -work-area-phys 0x08000 -work-area-size 8096
2904 $MyTarget configure -event reset-deassert-pre @{ jtag_rclk 5 @}
2905 $MyTarget configure -event reset-init @{ myboard_reinit @}
2908 You should specify a working area if you can; typically it uses some
2910 Such a working area can speed up many things, including bulk
2911 writes to target memory;
2912 flash operations like checking to see if memory needs to be erased;
2913 GDB memory checksumming;
2917 On more complex chips, the work area can become
2918 inaccessible when application code
2919 (such as an operating system)
2920 enables or disables the MMU.
2921 For example, the particular MMU context used to acess the virtual
2922 address will probably matter ... and that context might not have
2923 easy access to other addresses needed.
2924 At this writing, OpenOCD doesn't have much MMU intelligence.
2927 It's often very useful to define a @code{reset-init} event handler.
2928 For systems that are normally used with a boot loader,
2929 common tasks include updating clocks and initializing memory
2931 That may be needed to let you write the boot loader into flash,
2932 in order to ``de-brick'' your board; or to load programs into
2933 external DDR memory without having run the boot loader.
2935 @deffn Command {target create} target_name type configparams...
2936 This command creates a GDB debug target that refers to a specific JTAG tap.
2937 It enters that target into a list, and creates a new
2938 command (@command{@var{target_name}}) which is used for various
2939 purposes including additional configuration.
2942 @item @var{target_name} ... is the name of the debug target.
2943 By convention this should be the same as the @emph{dotted.name}
2944 of the TAP associated with this target, which must be specified here
2945 using the @code{-chain-position @var{dotted.name}} configparam.
2947 This name is also used to create the target object command,
2948 referred to here as @command{$target_name},
2949 and in other places the target needs to be identified.
2950 @item @var{type} ... specifies the target type. @xref{target types}.
2951 @item @var{configparams} ... all parameters accepted by
2952 @command{$target_name configure} are permitted.
2953 If the target is big-endian, set it here with @code{-endian big}.
2954 If the variant matters, set it here with @code{-variant}.
2956 You @emph{must} set the @code{-chain-position @var{dotted.name}} here.
2960 @deffn Command {$target_name configure} configparams...
2961 The options accepted by this command may also be
2962 specified as parameters to @command{target create}.
2963 Their values can later be queried one at a time by
2964 using the @command{$target_name cget} command.
2966 @emph{Warning:} changing some of these after setup is dangerous.
2967 For example, moving a target from one TAP to another;
2968 and changing its endianness or variant.
2972 @item @code{-chain-position} @var{dotted.name} -- names the TAP
2973 used to access this target.
2975 @item @code{-endian} (@option{big}|@option{little}) -- specifies
2976 whether the CPU uses big or little endian conventions
2978 @item @code{-event} @var{event_name} @var{event_body} --
2979 @xref{Target Events}.
2980 Note that this updates a list of named event handlers.
2981 Calling this twice with two different event names assigns
2982 two different handlers, but calling it twice with the
2983 same event name assigns only one handler.
2985 @item @code{-variant} @var{name} -- specifies a variant of the target,
2986 which OpenOCD needs to know about.
2988 @item @code{-work-area-backup} (@option{0}|@option{1}) -- says
2989 whether the work area gets backed up; by default,
2990 @emph{it is not backed up.}
2991 When possible, use a working_area that doesn't need to be backed up,
2992 since performing a backup slows down operations.
2993 For example, the beginning of an SRAM block is likely to
2994 be used by most build systems, but the end is often unused.
2996 @item @code{-work-area-size} @var{size} -- specify/set the work area
2998 @item @code{-work-area-phys} @var{address} -- set the work area
2999 base @var{address} to be used when no MMU is active.
3001 @item @code{-work-area-virt} @var{address} -- set the work area
3002 base @var{address} to be used when an MMU is active.
3007 @section Other $target_name Commands
3008 @cindex object command
3010 The Tcl/Tk language has the concept of object commands,
3011 and OpenOCD adopts that same model for targets.
3013 A good Tk example is a on screen button.
3014 Once a button is created a button
3015 has a name (a path in Tk terms) and that name is useable as a first
3016 class command. For example in Tk, one can create a button and later
3017 configure it like this:
3021 button .foobar -background red -command @{ foo @}
3023 .foobar configure -foreground blue
3025 set x [.foobar cget -background]
3027 puts [format "The button is %s" $x]
3030 In OpenOCD's terms, the ``target'' is an object just like a Tcl/Tk
3031 button, and its object commands are invoked the same way.
3034 str912.cpu mww 0x1234 0x42
3035 omap3530.cpu mww 0x5555 123
3038 The commands supported by OpenOCD target objects are:
3040 @deffn Command {$target_name arp_examine}
3041 @deffnx Command {$target_name arp_halt}
3042 @deffnx Command {$target_name arp_poll}
3043 @deffnx Command {$target_name arp_reset}
3044 @deffnx Command {$target_name arp_waitstate}
3045 Internal OpenOCD scripts (most notably @file{startup.tcl})
3046 use these to deal with specific reset cases.
3047 They are not otherwise documented here.
3050 @deffn Command {$target_name array2mem} arrayname width address count
3051 @deffnx Command {$target_name mem2array} arrayname width address count
3052 These provide an efficient script-oriented interface to memory.
3053 The @code{array2mem} primitive writes bytes, halfwords, or words;
3054 while @code{mem2array} reads them.
3055 In both cases, the TCL side uses an array, and
3056 the target side uses raw memory.
3058 The efficiency comes from enabling the use of
3059 bulk JTAG data transfer operations.
3060 The script orientation comes from working with data
3061 values that are packaged for use by TCL scripts;
3062 @command{mdw} type primitives only print data they retrieve,
3063 and neither store nor return those values.
3066 @item @var{arrayname} ... is the name of an array variable
3067 @item @var{width} ... is 8/16/32 - indicating the memory access size
3068 @item @var{address} ... is the target memory address
3069 @item @var{count} ... is the number of elements to process
3073 @deffn Command {$target_name cget} queryparm
3074 Each configuration parameter accepted by
3075 @command{$target_name configure}
3076 can be individually queried, to return its current value.
3077 The @var{queryparm} is a parameter name
3078 accepted by that command, such as @code{-work-area-phys}.
3079 There are a few special cases:
3082 @item @code{-event} @var{event_name} -- returns the handler for the
3083 event named @var{event_name}.
3084 This is a special case because setting a handler requires
3086 @item @code{-type} -- returns the target type.
3087 This is a special case because this is set using
3088 @command{target create} and can't be changed
3089 using @command{$target_name configure}.
3092 For example, if you wanted to summarize information about
3093 all the targets you might use something like this:
3096 foreach name [target names] @{
3097 set y [$name cget -endian]
3098 set z [$name cget -type]
3099 puts [format "Chip %d is %s, Endian: %s, type: %s" \
3105 @anchor{target curstate}
3106 @deffn Command {$target_name curstate}
3107 Displays the current target state:
3108 @code{debug-running},
3111 @code{running}, or @code{unknown}.
3112 (Also, @pxref{Event Polling}.)
3115 @deffn Command {$target_name eventlist}
3116 Displays a table listing all event handlers
3117 currently associated with this target.
3118 @xref{Target Events}.
3121 @deffn Command {$target_name invoke-event} event_name
3122 Invokes the handler for the event named @var{event_name}.
3123 (This is primarily intended for use by OpenOCD framework
3124 code, for example by the reset code in @file{startup.tcl}.)
3127 @deffn Command {$target_name mdw} addr [count]
3128 @deffnx Command {$target_name mdh} addr [count]
3129 @deffnx Command {$target_name mdb} addr [count]
3130 Display contents of address @var{addr}, as
3131 32-bit words (@command{mdw}), 16-bit halfwords (@command{mdh}),
3132 or 8-bit bytes (@command{mdb}).
3133 If @var{count} is specified, displays that many units.
3134 (If you want to manipulate the data instead of displaying it,
3135 see the @code{mem2array} primitives.)
3138 @deffn Command {$target_name mww} addr word
3139 @deffnx Command {$target_name mwh} addr halfword
3140 @deffnx Command {$target_name mwb} addr byte
3141 Writes the specified @var{word} (32 bits),
3142 @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
3143 at the specified address @var{addr}.
3146 @anchor{Target Events}
3147 @section Target Events
3148 @cindex target events
3150 At various times, certain things can happen, or you want them to happen.
3153 @item What should happen when GDB connects? Should your target reset?
3154 @item When GDB tries to flash the target, do you need to enable the flash via a special command?
3155 @item During reset, do you need to write to certain memory locations
3156 to set up system clocks or
3157 to reconfigure the SDRAM?
3160 All of the above items can be addressed by target event handlers.
3161 These are set up by @command{$target_name configure -event} or
3162 @command{target create ... -event}.
3164 The programmer's model matches the @code{-command} option used in Tcl/Tk
3165 buttons and events. The two examples below act the same, but one creates
3166 and invokes a small procedure while the other inlines it.
3169 proc my_attach_proc @{ @} @{
3173 mychip.cpu configure -event gdb-attach my_attach_proc
3174 mychip.cpu configure -event gdb-attach @{
3180 The following target events are defined:
3183 @item @b{debug-halted}
3184 @* The target has halted for debug reasons (i.e.: breakpoint)
3185 @item @b{debug-resumed}
3186 @* The target has resumed (i.e.: gdb said run)
3187 @item @b{early-halted}
3188 @* Occurs early in the halt process
3190 @item @b{examine-end}
3191 @* Currently not used (goal: when JTAG examine completes)
3192 @item @b{examine-start}
3193 @* Currently not used (goal: when JTAG examine starts)
3195 @item @b{gdb-attach}
3196 @* When GDB connects
3197 @item @b{gdb-detach}
3198 @* When GDB disconnects
3200 @* When the target has halted and GDB is not doing anything (see early halt)
3201 @item @b{gdb-flash-erase-start}
3202 @* Before the GDB flash process tries to erase the flash
3203 @item @b{gdb-flash-erase-end}
3204 @* After the GDB flash process has finished erasing the flash
3205 @item @b{gdb-flash-write-start}
3206 @* Before GDB writes to the flash
3207 @item @b{gdb-flash-write-end}
3208 @* After GDB writes to the flash
3210 @* Before the target steps, gdb is trying to start/resume the target
3212 @* The target has halted
3214 @item @b{old-gdb_program_config}
3215 @* DO NOT USE THIS: Used internally
3216 @item @b{old-pre_resume}
3217 @* DO NOT USE THIS: Used internally
3219 @item @b{reset-assert-pre}
3220 @* Issued as part of @command{reset} processing
3221 after SRST and/or TRST were activated and deactivated,
3222 but before SRST alone is re-asserted on the tap.
3223 @item @b{reset-assert-post}
3224 @* Issued as part of @command{reset} processing
3225 when SRST is asserted on the tap.
3226 @item @b{reset-deassert-pre}
3227 @* Issued as part of @command{reset} processing
3228 when SRST is about to be released on the tap.
3229 @item @b{reset-deassert-post}
3230 @* Issued as part of @command{reset} processing
3231 when SRST has been released on the tap.
3233 @* Issued as the final step in @command{reset} processing.
3235 @item @b{reset-halt-post}
3236 @* Currently not used
3237 @item @b{reset-halt-pre}
3238 @* Currently not used
3240 @item @b{reset-init}
3241 @* Used by @b{reset init} command for board-specific initialization.
3242 This event fires after @emph{reset-deassert-post}.
3244 This is where you would configure PLLs and clocking, set up DRAM so
3245 you can download programs that don't fit in on-chip SRAM, set up pin
3246 multiplexing, and so on.
3247 (You may be able to switch to a fast JTAG clock rate here, after
3248 the target clocks are fully set up.)
3249 @item @b{reset-start}
3250 @* Issued as part of @command{reset} processing
3251 before either SRST or TRST are activated.
3253 This is the most robust place to switch to a low JTAG clock rate, if
3254 SRST disables PLLs needed to use a fast clock.
3256 @item @b{reset-wait-pos}
3257 @* Currently not used
3258 @item @b{reset-wait-pre}
3259 @* Currently not used
3261 @item @b{resume-start}
3262 @* Before any target is resumed
3263 @item @b{resume-end}
3264 @* After all targets have resumed
3268 @* Target has resumed
3272 @node Flash Commands
3273 @chapter Flash Commands
3275 OpenOCD has different commands for NOR and NAND flash;
3276 the ``flash'' command works with NOR flash, while
3277 the ``nand'' command works with NAND flash.
3278 This partially reflects different hardware technologies:
3279 NOR flash usually supports direct CPU instruction and data bus access,
3280 while data from a NAND flash must be copied to memory before it can be
3281 used. (SPI flash must also be copied to memory before use.)
3282 However, the documentation also uses ``flash'' as a generic term;
3283 for example, ``Put flash configuration in board-specific files''.
3287 @item Configure via the command @command{flash bank}
3288 @* Do this in a board-specific configuration file,
3289 passing parameters as needed by the driver.
3290 @item Operate on the flash via @command{flash subcommand}
3291 @* Often commands to manipulate the flash are typed by a human, or run
3292 via a script in some automated way. Common tasks include writing a
3293 boot loader, operating system, or other data.
3295 @* Flashing via GDB requires the flash be configured via ``flash
3296 bank'', and the GDB flash features be enabled.
3297 @xref{GDB Configuration}.
3300 Many CPUs have the ablity to ``boot'' from the first flash bank.
3301 This means that misprogramming that bank can ``brick'' a system,
3302 so that it can't boot.
3303 JTAG tools, like OpenOCD, are often then used to ``de-brick'' the
3304 board by (re)installing working boot firmware.
3306 @anchor{NOR Configuration}
3307 @section Flash Configuration Commands
3308 @cindex flash configuration
3310 @deffn {Config Command} {flash bank} driver base size chip_width bus_width target [driver_options]
3311 Configures a flash bank which provides persistent storage
3312 for addresses from @math{base} to @math{base + size - 1}.
3313 These banks will often be visible to GDB through the target's memory map.
3314 In some cases, configuring a flash bank will activate extra commands;
3315 see the driver-specific documentation.
3318 @item @var{driver} ... identifies the controller driver
3319 associated with the flash bank being declared.
3320 This is usually @code{cfi} for external flash, or else
3321 the name of a microcontroller with embedded flash memory.
3322 @xref{Flash Driver List}.
3323 @item @var{base} ... Base address of the flash chip.
3324 @item @var{size} ... Size of the chip, in bytes.
3325 For some drivers, this value is detected from the hardware.
3326 @item @var{chip_width} ... Width of the flash chip, in bytes;
3327 ignored for most microcontroller drivers.
3328 @item @var{bus_width} ... Width of the data bus used to access the
3329 chip, in bytes; ignored for most microcontroller drivers.
3330 @item @var{target} ... Names the target used to issue
3331 commands to the flash controller.
3332 @comment Actually, it's currently a controller-specific parameter...
3333 @item @var{driver_options} ... drivers may support, or require,
3334 additional parameters. See the driver-specific documentation
3335 for more information.
3338 This command is not available after OpenOCD initialization has completed.
3339 Use it in board specific configuration files, not interactively.
3343 @comment the REAL name for this command is "ocd_flash_banks"
3344 @comment less confusing would be: "flash list" (like "nand list")
3345 @deffn Command {flash banks}
3346 Prints a one-line summary of each device declared
3347 using @command{flash bank}, numbered from zero.
3348 Note that this is the @emph{plural} form;
3349 the @emph{singular} form is a very different command.
3352 @deffn Command {flash probe} num
3353 Identify the flash, or validate the parameters of the configured flash. Operation
3354 depends on the flash type.
3355 The @var{num} parameter is a value shown by @command{flash banks}.
3356 Most flash commands will implicitly @emph{autoprobe} the bank;
3357 flash drivers can distinguish between probing and autoprobing,
3358 but most don't bother.
3361 @section Erasing, Reading, Writing to Flash
3362 @cindex flash erasing
3363 @cindex flash reading
3364 @cindex flash writing
3365 @cindex flash programming
3367 One feature distinguishing NOR flash from NAND or serial flash technologies
3368 is that for read access, it acts exactly like any other addressible memory.
3369 This means you can use normal memory read commands like @command{mdw} or
3370 @command{dump_image} with it, with no special @command{flash} subcommands.
3371 @xref{Memory access}, and @ref{Image access}.
3373 Write access works differently. Flash memory normally needs to be erased
3374 before it's written. Erasing a sector turns all of its bits to ones, and
3375 writing can turn ones into zeroes. This is why there are special commands
3376 for interactive erasing and writing, and why GDB needs to know which parts
3377 of the address space hold NOR flash memory.
3380 Most of these erase and write commands leverage the fact that NOR flash
3381 chips consume target address space. They implicitly refer to the current
3382 JTAG target, and map from an address in that target's address space
3383 back to a flash bank.
3384 @comment In May 2009, those mappings may fail if any bank associated
3385 @comment with that target doesn't succesfuly autoprobe ... bug worth fixing?
3386 A few commands use abstract addressing based on bank and sector numbers,
3387 and don't depend on searching the current target and its address space.
3388 Avoid confusing the two command models.
3391 Some flash chips implement software protection against accidental writes,
3392 since such buggy writes could in some cases ``brick'' a system.
3393 For such systems, erasing and writing may require sector protection to be
3395 Examples include CFI flash such as ``Intel Advanced Bootblock flash'',
3396 and AT91SAM7 on-chip flash.
3397 @xref{flash protect}.
3399 @anchor{flash erase_sector}
3400 @deffn Command {flash erase_sector} num first last
3401 Erase sectors in bank @var{num}, starting at sector @var{first}
3402 up to and including @var{last}.
3403 Sector numbering starts at 0.
3404 Providing a @var{last} sector of @option{last}
3405 specifies "to the end of the flash bank".
3406 The @var{num} parameter is a value shown by @command{flash banks}.
3409 @deffn Command {flash erase_address} address length
3410 Erase sectors starting at @var{address} for @var{length} bytes.
3411 The flash bank to use is inferred from the @var{address}, and
3412 the specified length must stay within that bank.
3413 As a special case, when @var{length} is zero and @var{address} is
3414 the start of the bank, the whole flash is erased.
3417 @deffn Command {flash fillw} address word length
3418 @deffnx Command {flash fillh} address halfword length
3419 @deffnx Command {flash fillb} address byte length
3420 Fills flash memory with the specified @var{word} (32 bits),
3421 @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
3422 starting at @var{address} and continuing
3423 for @var{length} units (word/halfword/byte).
3424 No erasure is done before writing; when needed, that must be done
3425 before issuing this command.
3426 Writes are done in blocks of up to 1024 bytes, and each write is
3427 verified by reading back the data and comparing it to what was written.
3428 The flash bank to use is inferred from the @var{address} of
3429 each block, and the specified length must stay within that bank.
3431 @comment no current checks for errors if fill blocks touch multiple banks!
3433 @anchor{flash write_bank}
3434 @deffn Command {flash write_bank} num filename offset
3435 Write the binary @file{filename} to flash bank @var{num},
3436 starting at @var{offset} bytes from the beginning of the bank.
3437 The @var{num} parameter is a value shown by @command{flash banks}.
3440 @anchor{flash write_image}
3441 @deffn Command {flash write_image} [erase] filename [offset] [type]
3442 Write the image @file{filename} to the current target's flash bank(s).
3443 A relocation @var{offset} may be specified, in which case it is added
3444 to the base address for each section in the image.
3445 The file [@var{type}] can be specified
3446 explicitly as @option{bin} (binary), @option{ihex} (Intel hex),
3447 @option{elf} (ELF file), @option{s19} (Motorola s19).
3448 @option{mem}, or @option{builder}.
3449 The relevant flash sectors will be erased prior to programming
3450 if the @option{erase} parameter is given.
3451 The flash bank to use is inferred from the @var{address} of
3455 @section Other Flash commands
3456 @cindex flash protection
3458 @deffn Command {flash erase_check} num
3459 Check erase state of sectors in flash bank @var{num},
3460 and display that status.
3461 The @var{num} parameter is a value shown by @command{flash banks}.
3462 This is the only operation that
3463 updates the erase state information displayed by @option{flash info}. That means you have
3464 to issue a @command{flash erase_check} command after erasing or programming the device
3465 to get updated information.
3466 (Code execution may have invalidated any state records kept by OpenOCD.)
3469 @deffn Command {flash info} num
3470 Print info about flash bank @var{num}
3471 The @var{num} parameter is a value shown by @command{flash banks}.
3472 The information includes per-sector protect status.
3475 @anchor{flash protect}
3476 @deffn Command {flash protect} num first last (@option{on}|@option{off})
3477 Enable (@option{on}) or disable (@option{off}) protection of flash sectors
3478 in flash bank @var{num}, starting at sector @var{first}
3479 and continuing up to and including @var{last}.
3480 Providing a @var{last} sector of @option{last}
3481 specifies "to the end of the flash bank".
3482 The @var{num} parameter is a value shown by @command{flash banks}.
3485 @deffn Command {flash protect_check} num
3486 Check protection state of sectors in flash bank @var{num}.
3487 The @var{num} parameter is a value shown by @command{flash banks}.
3488 @comment @option{flash erase_sector} using the same syntax.
3491 @anchor{Flash Driver List}
3492 @section Flash Drivers, Options, and Commands
3493 As noted above, the @command{flash bank} command requires a driver name,
3494 and allows driver-specific options and behaviors.
3495 Some drivers also activate driver-specific commands.
3497 @subsection External Flash
3499 @deffn {Flash Driver} cfi
3500 @cindex Common Flash Interface
3502 The ``Common Flash Interface'' (CFI) is the main standard for
3503 external NOR flash chips, each of which connects to a
3504 specific external chip select on the CPU.
3505 Frequently the first such chip is used to boot the system.
3506 Your board's @code{reset-init} handler might need to
3507 configure additional chip selects using other commands (like: @command{mww} to
3508 configure a bus and its timings) , or
3509 perhaps configure a GPIO pin that controls the ``write protect'' pin
3511 The CFI driver can use a target-specific working area to significantly
3514 The CFI driver can accept the following optional parameters, in any order:
3517 @item @var{jedec_probe} ... is used to detect certain non-CFI flash ROMs,
3518 like AM29LV010 and similar types.
3519 @item @var{x16_as_x8} ... when a 16-bit flash is hooked up to an 8-bit bus.
3522 To configure two adjacent banks of 16 MBytes each, both sixteen bits (two bytes)
3523 wide on a sixteen bit bus:
3526 flash bank cfi 0x00000000 0x01000000 2 2 $_TARGETNAME
3527 flash bank cfi 0x01000000 0x01000000 2 2 $_TARGETNAME
3529 @c "cfi part_id" disabled
3532 @subsection Internal Flash (Microcontrollers)
3534 @deffn {Flash Driver} aduc702x
3535 The ADUC702x analog microcontrollers from Analog Devices
3536 include internal flash and use ARM7TDMI cores.
3537 The aduc702x flash driver works with models ADUC7019 through ADUC7028.
3538 The setup command only requires the @var{target} argument
3539 since all devices in this family have the same memory layout.
3542 flash bank aduc702x 0 0 0 0 $_TARGETNAME
3546 @deffn {Flash Driver} at91sam3
3548 All members of the AT91SAM3 microcontroller family from
3549 Atmel include internal flash and use ARM's Cortex-M3 core. The driver
3550 currently (6/22/09) recognizes the AT91SAM3U[1/2/4][C/E] chips. Note
3551 that the driver was orginaly developed and tested using the
3552 AT91SAM3U4E, using a SAM3U-EK eval board. Support for other chips in
3553 the family was cribbed from the data sheet. @emph{Note to future
3554 readers/updaters: Please remove this worrysome comment after other
3555 chips are confirmed.}
3557 The AT91SAM3U4[E/C] (256K) chips have two flash banks; most other chips
3558 have one flash bank. In all cases the flash banks are at
3559 the following fixed locations:
3562 # Flash bank 0 - all chips
3563 flash bank at91sam3 0x00080000 0 1 1 $_TARGETNAME
3564 # Flash bank 1 - only 256K chips
3565 flash bank at91sam3 0x00100000 0 1 1 $_TARGETNAME
3568 Internally, the AT91SAM3 flash memory is organized as follows.
3569 Unlike the AT91SAM7 chips, these are not used as parameters
3570 to the @command{flash bank} command:
3573 @item @emph{N-Banks:} 256K chips have 2 banks, others have 1 bank.
3574 @item @emph{Bank Size:} 128K/64K Per flash bank
3575 @item @emph{Sectors:} 16 or 8 per bank
3576 @item @emph{SectorSize:} 8K Per Sector
3577 @item @emph{PageSize:} 256 bytes per page. Note that OpenOCD operates on 'sector' sizes, not page sizes.
3580 The AT91SAM3 driver adds some additional commands:
3582 @deffn Command {at91sam3 gpnvm}
3583 @deffnx Command {at91sam3 gpnvm clear} number
3584 @deffnx Command {at91sam3 gpnvm set} number
3585 @deffnx Command {at91sam3 gpnvm show} [@option{all}|number]
3586 With no parameters, @command{show} or @command{show all},
3587 shows the status of all GPNVM bits.
3588 With @command{show} @var{number}, displays that bit.
3590 With @command{set} @var{number} or @command{clear} @var{number},
3591 modifies that GPNVM bit.
3594 @deffn Command {at91sam3 info}
3595 This command attempts to display information about the AT91SAM3
3596 chip. @emph{First} it read the @code{CHIPID_CIDR} [address 0x400e0740, see
3597 Section 28.2.1, page 505 of the AT91SAM3U 29/may/2009 datasheet,
3598 document id: doc6430A] and decodes the values. @emph{Second} it reads the
3599 various clock configuration registers and attempts to display how it
3600 believes the chip is configured. By default, the SLOWCLK is assumed to
3601 be 32768 Hz, see the command @command{at91sam3 slowclk}.
3604 @deffn Command {at91sam3 slowclk} [value]
3605 This command shows/sets the slow clock frequency used in the
3606 @command{at91sam3 info} command calculations above.
3610 @deffn {Flash Driver} at91sam7
3611 All members of the AT91SAM7 microcontroller family from Atmel include
3612 internal flash and use ARM7TDMI cores. The driver automatically
3613 recognizes a number of these chips using the chip identification
3614 register, and autoconfigures itself.
3617 flash bank at91sam7 0 0 0 0 $_TARGETNAME
3620 For chips which are not recognized by the controller driver, you must
3621 provide additional parameters in the following order:
3624 @item @var{chip_model} ... label used with @command{flash info}
3626 @item @var{sectors_per_bank}
3627 @item @var{pages_per_sector}
3628 @item @var{pages_size}
3629 @item @var{num_nvm_bits}
3630 @item @var{freq_khz} ... required if an external clock is provided,
3631 optional (but recommended) when the oscillator frequency is known
3634 It is recommended that you provide zeroes for all of those values
3635 except the clock frequency, so that everything except that frequency
3636 will be autoconfigured.
3637 Knowing the frequency helps ensure correct timings for flash access.
3639 The flash controller handles erases automatically on a page (128/256 byte)
3640 basis, so explicit erase commands are not necessary for flash programming.
3641 However, there is an ``EraseAll`` command that can erase an entire flash
3642 plane (of up to 256KB), and it will be used automatically when you issue
3643 @command{flash erase_sector} or @command{flash erase_address} commands.
3645 @deffn Command {at91sam7 gpnvm} bitnum (@option{set}|@option{clear})
3646 Set or clear a ``General Purpose Non-Volatle Memory'' (GPNVM)
3647 bit for the processor. Each processor has a number of such bits,
3648 used for controlling features such as brownout detection (so they
3649 are not truly general purpose).
3651 This assumes that the first flash bank (number 0) is associated with
3652 the appropriate at91sam7 target.
3657 @deffn {Flash Driver} avr
3658 The AVR 8-bit microcontrollers from Atmel integrate flash memory.
3659 @emph{The current implementation is incomplete.}
3660 @comment - defines mass_erase ... pointless given flash_erase_address
3663 @deffn {Flash Driver} ecosflash
3664 @emph{No idea what this is...}
3665 The @var{ecosflash} driver defines one mandatory parameter,
3666 the name of a modules of target code which is downloaded
3670 @deffn {Flash Driver} lpc2000
3671 Most members of the LPC1700 and LPC2000 microcontroller families from NXP
3672 include internal flash and use Cortex-M3 (LPC1700) or ARM7TDMI (LPC2000) cores.
3675 There are LPC2000 devices which are not supported by the @var{lpc2000}
3677 The LPC2888 is supported by the @var{lpc288x} driver.
3678 The LPC29xx family is supported by the @var{lpc2900} driver.
3681 The @var{lpc2000} driver defines two mandatory and one optional parameters,
3682 which must appear in the following order:
3685 @item @var{variant} ... required, may be
3686 @var{lpc2000_v1} (older LPC21xx and LPC22xx)
3687 @var{lpc2000_v2} (LPC213x, LPC214x, LPC210[123], LPC23xx and LPC24xx)
3688 or @var{lpc1700} (LPC175x and LPC176x)
3689 @item @var{clock_kHz} ... the frequency, in kiloHertz,
3690 at which the core is running
3691 @item @var{calc_checksum} ... optional (but you probably want to provide this!),
3692 telling the driver to calculate a valid checksum for the exception vector table.
3695 LPC flashes don't require the chip and bus width to be specified.
3698 flash bank lpc2000 0x0 0x7d000 0 0 $_TARGETNAME \
3699 lpc2000_v2 14765 calc_checksum
3702 @deffn {Command} {lpc2000 part_id} bank
3703 Displays the four byte part identifier associated with
3704 the specified flash @var{bank}.
3708 @deffn {Flash Driver} lpc288x
3709 The LPC2888 microcontroller from NXP needs slightly different flash
3710 support from its lpc2000 siblings.
3711 The @var{lpc288x} driver defines one mandatory parameter,
3712 the programming clock rate in Hz.
3713 LPC flashes don't require the chip and bus width to be specified.
3716 flash bank lpc288x 0 0 0 0 $_TARGETNAME 12000000
3720 @deffn {Flash Driver} lpc2900
3721 This driver supports the LPC29xx ARM968E based microcontroller family
3724 The predefined parameters @var{base}, @var{size}, @var{chip_width} and
3725 @var{bus_width} of the @code{flash bank} command are ignored. Flash size and
3726 sector layout are auto-configured by the driver.
3727 The driver has one additional mandatory parameter: The CPU clock rate
3728 (in kHz) at the time the flash operations will take place. Most of the time this
3729 will not be the crystal frequency, but a higher PLL frequency. The
3730 @code{reset-init} event handler in the board script is usually the place where
3733 The driver rejects flashless devices (currently the LPC2930).
3735 The EEPROM in LPC2900 devices is not mapped directly into the address space.
3736 It must be handled much more like NAND flash memory, and will therefore be
3737 handled by a separate @code{lpc2900_eeprom} driver (not yet available).
3739 Sector protection in terms of the LPC2900 is handled transparently. Every time a
3740 sector needs to be erased or programmed, it is automatically unprotected.
3741 What is shown as protection status in the @code{flash info} command, is
3742 actually the LPC2900 @emph{sector security}. This is a mechanism to prevent a
3743 sector from ever being erased or programmed again. As this is an irreversible
3744 mechanism, it is handled by a special command (@code{lpc2900 secure_sector}),
3745 and not by the standard @code{flash protect} command.
3747 Example for a 125 MHz clock frequency:
3749 flash bank lpc2900 0 0 0 0 $_TARGETNAME 125000
3752 Some @code{lpc2900}-specific commands are defined. In the following command list,
3753 the @var{bank} parameter is the bank number as obtained by the
3754 @code{flash banks} command.
3756 @deffn Command {lpc2900 signature} bank
3757 Calculates a 128-bit hash value, the @emph{signature}, from the whole flash
3758 content. This is a hardware feature of the flash block, hence the calculation is
3759 very fast. You may use this to verify the content of a programmed device against
3764 signature: 0x5f40cdc8:0xc64e592e:0x10490f89:0x32a0f317
3768 @deffn Command {lpc2900 read_custom} bank filename
3769 Reads the 912 bytes of customer information from the flash index sector, and
3770 saves it to a file in binary format.
3773 lpc2900 read_custom 0 /path_to/customer_info.bin
3777 The index sector of the flash is a @emph{write-only} sector. It cannot be
3778 erased! In order to guard against unintentional write access, all following
3779 commands need to be preceeded by a successful call to the @code{password}
3782 @deffn Command {lpc2900 password} bank password
3783 You need to use this command right before each of the following commands:
3784 @code{lpc2900 write_custom}, @code{lpc2900 secure_sector},
3785 @code{lpc2900 secure_jtag}.
3787 The password string is fixed to "I_know_what_I_am_doing".
3790 lpc2900 password 0 I_know_what_I_am_doing
3791 Potentially dangerous operation allowed in next command!
3795 @deffn Command {lpc2900 write_custom} bank filename type
3796 Writes the content of the file into the customer info space of the flash index
3797 sector. The filetype can be specified with the @var{type} field. Possible values
3798 for @var{type} are: @var{bin} (binary), @var{ihex} (Intel hex format),
3799 @var{elf} (ELF binary) or @var{s19} (Motorola S-records). The file must
3800 contain a single section, and the contained data length must be exactly
3802 @quotation Attention
3803 This cannot be reverted! Be careful!
3807 lpc2900 write_custom 0 /path_to/customer_info.bin bin
3811 @deffn Command {lpc2900 secure_sector} bank first last
3812 Secures the sector range from @var{first} to @var{last} (including) against
3813 further program and erase operations. The sector security will be effective
3814 after the next power cycle.
3815 @quotation Attention
3816 This cannot be reverted! Be careful!
3818 Secured sectors appear as @emph{protected} in the @code{flash info} command.
3821 lpc2900 secure_sector 0 1 1
3823 #0 : lpc2900 at 0x20000000, size 0x000c0000, (...)
3824 # 0: 0x00000000 (0x2000 8kB) not protected
3825 # 1: 0x00002000 (0x2000 8kB) protected
3826 # 2: 0x00004000 (0x2000 8kB) not protected
3830 @deffn Command {lpc2900 secure_jtag} bank
3831 Irreversibly disable the JTAG port. The new JTAG security setting will be
3832 effective after the next power cycle.
3833 @quotation Attention
3834 This cannot be reverted! Be careful!
3838 lpc2900 secure_jtag 0
3843 @deffn {Flash Driver} ocl
3844 @emph{No idea what this is, other than using some arm7/arm9 core.}
3847 flash bank ocl 0 0 0 0 $_TARGETNAME
3851 @deffn {Flash Driver} pic32mx
3852 The PIC32MX microcontrollers are based on the MIPS 4K cores,
3853 and integrate flash memory.
3854 @emph{The current implementation is incomplete.}
3857 flash bank pix32mx 0 0 0 0 $_TARGETNAME
3860 @comment numerous *disabled* commands are defined:
3861 @comment - chip_erase ... pointless given flash_erase_address
3862 @comment - lock, unlock ... pointless given protect on/off (yes?)
3863 @comment - pgm_word ... shouldn't bank be deduced from address??
3864 Some pic32mx-specific commands are defined:
3865 @deffn Command {pic32mx pgm_word} address value bank
3866 Programs the specified 32-bit @var{value} at the given @var{address}
3867 in the specified chip @var{bank}.
3871 @deffn {Flash Driver} stellaris
3872 All members of the Stellaris LM3Sxxx microcontroller family from
3874 include internal flash and use ARM Cortex M3 cores.
3875 The driver automatically recognizes a number of these chips using
3876 the chip identification register, and autoconfigures itself.
3877 @footnote{Currently there is a @command{stellaris mass_erase} command.
3878 That seems pointless since the same effect can be had using the
3879 standard @command{flash erase_address} command.}
3882 flash bank stellaris 0 0 0 0 $_TARGETNAME
3886 @deffn {Flash Driver} stm32x
3887 All members of the STM32 microcontroller family from ST Microelectronics
3888 include internal flash and use ARM Cortex M3 cores.
3889 The driver automatically recognizes a number of these chips using
3890 the chip identification register, and autoconfigures itself.
3893 flash bank stm32x 0 0 0 0 $_TARGETNAME
3896 Some stm32x-specific commands
3897 @footnote{Currently there is a @command{stm32x mass_erase} command.
3898 That seems pointless since the same effect can be had using the
3899 standard @command{flash erase_address} command.}
3902 @deffn Command {stm32x lock} num
3903 Locks the entire stm32 device.
3904 The @var{num} parameter is a value shown by @command{flash banks}.
3907 @deffn Command {stm32x unlock} num
3908 Unlocks the entire stm32 device.
3909 The @var{num} parameter is a value shown by @command{flash banks}.
3912 @deffn Command {stm32x options_read} num
3913 Read and display the stm32 option bytes written by
3914 the @command{stm32x options_write} command.
3915 The @var{num} parameter is a value shown by @command{flash banks}.
3918 @deffn Command {stm32x options_write} num (@option{SWWDG}|@option{HWWDG}) (@option{RSTSTNDBY}|@option{NORSTSTNDBY}) (@option{RSTSTOP}|@option{NORSTSTOP})
3919 Writes the stm32 option byte with the specified values.
3920 The @var{num} parameter is a value shown by @command{flash banks}.
3924 @deffn {Flash Driver} str7x
3925 All members of the STR7 microcontroller family from ST Microelectronics
3926 include internal flash and use ARM7TDMI cores.
3927 The @var{str7x} driver defines one mandatory parameter, @var{variant},
3928 which is either @code{STR71x}, @code{STR73x} or @code{STR75x}.
3931 flash bank str7x 0x40000000 0x00040000 0 0 $_TARGETNAME STR71x
3934 @deffn Command {str7x disable_jtag} bank
3935 Activate the Debug/Readout protection mechanism
3936 for the specified flash bank.
3940 @deffn {Flash Driver} str9x
3941 Most members of the STR9 microcontroller family from ST Microelectronics
3942 include internal flash and use ARM966E cores.
3943 The str9 needs the flash controller to be configured using
3944 the @command{str9x flash_config} command prior to Flash programming.
3947 flash bank str9x 0x40000000 0x00040000 0 0 $_TARGETNAME
3948 str9x flash_config 0 4 2 0 0x80000
3951 @deffn Command {str9x flash_config} num bbsr nbbsr bbadr nbbadr
3952 Configures the str9 flash controller.
3953 The @var{num} parameter is a value shown by @command{flash banks}.
3956 @item @var{bbsr} - Boot Bank Size register
3957 @item @var{nbbsr} - Non Boot Bank Size register
3958 @item @var{bbadr} - Boot Bank Start Address register
3959 @item @var{nbbadr} - Boot Bank Start Address register
3965 @deffn {Flash Driver} tms470
3966 Most members of the TMS470 microcontroller family from Texas Instruments
3967 include internal flash and use ARM7TDMI cores.
3968 This driver doesn't require the chip and bus width to be specified.
3970 Some tms470-specific commands are defined:
3972 @deffn Command {tms470 flash_keyset} key0 key1 key2 key3
3973 Saves programming keys in a register, to enable flash erase and write commands.
3976 @deffn Command {tms470 osc_mhz} clock_mhz
3977 Reports the clock speed, which is used to calculate timings.
3980 @deffn Command {tms470 plldis} (0|1)
3981 Disables (@var{1}) or enables (@var{0}) use of the PLL to speed up
3986 @subsection str9xpec driver
3989 Here is some background info to help
3990 you better understand how this driver works. OpenOCD has two flash drivers for
3994 Standard driver @option{str9x} programmed via the str9 core. Normally used for
3995 flash programming as it is faster than the @option{str9xpec} driver.
3997 Direct programming @option{str9xpec} using the flash controller. This is an
3998 ISC compilant (IEEE 1532) tap connected in series with the str9 core. The str9
3999 core does not need to be running to program using this flash driver. Typical use
4000 for this driver is locking/unlocking the target and programming the option bytes.
4003 Before we run any commands using the @option{str9xpec} driver we must first disable
4004 the str9 core. This example assumes the @option{str9xpec} driver has been
4005 configured for flash bank 0.
4007 # assert srst, we do not want core running
4008 # while accessing str9xpec flash driver
4010 # turn off target polling
4013 str9xpec enable_turbo 0
4015 str9xpec options_read 0
4016 # re-enable str9 core
4017 str9xpec disable_turbo 0
4021 The above example will read the str9 option bytes.
4022 When performing a unlock remember that you will not be able to halt the str9 - it
4023 has been locked. Halting the core is not required for the @option{str9xpec} driver
4024 as mentioned above, just issue the commands above manually or from a telnet prompt.
4026 @deffn {Flash Driver} str9xpec
4027 Only use this driver for locking/unlocking the device or configuring the option bytes.
4028 Use the standard str9 driver for programming.
4029 Before using the flash commands the turbo mode must be enabled using the
4030 @command{str9xpec enable_turbo} command.
4032 Several str9xpec-specific commands are defined:
4034 @deffn Command {str9xpec disable_turbo} num
4035 Restore the str9 into JTAG chain.
4038 @deffn Command {str9xpec enable_turbo} num
4039 Enable turbo mode, will simply remove the str9 from the chain and talk
4040 directly to the embedded flash controller.
4043 @deffn Command {str9xpec lock} num
4044 Lock str9 device. The str9 will only respond to an unlock command that will
4048 @deffn Command {str9xpec part_id} num
4049 Prints the part identifier for bank @var{num}.
4052 @deffn Command {str9xpec options_cmap} num (@option{bank0}|@option{bank1})
4053 Configure str9 boot bank.
4056 @deffn Command {str9xpec options_lvdsel} num (@option{vdd}|@option{vdd_vddq})
4057 Configure str9 lvd source.
4060 @deffn Command {str9xpec options_lvdthd} num (@option{2.4v}|@option{2.7v})
4061 Configure str9 lvd threshold.
4064 @deffn Command {str9xpec options_lvdwarn} bank (@option{vdd}|@option{vdd_vddq})
4065 Configure str9 lvd reset warning source.
4068 @deffn Command {str9xpec options_read} num
4069 Read str9 option bytes.
4072 @deffn Command {str9xpec options_write} num
4073 Write str9 option bytes.
4076 @deffn Command {str9xpec unlock} num
4085 @subsection mFlash Configuration
4086 @cindex mFlash Configuration
4088 @deffn {Config Command} {mflash bank} soc base RST_pin target
4089 Configures a mflash for @var{soc} host bank at
4091 The pin number format depends on the host GPIO naming convention.
4092 Currently, the mflash driver supports s3c2440 and pxa270.
4094 Example for s3c2440 mflash where @var{RST pin} is GPIO B1:
4097 mflash bank s3c2440 0x10000000 1b 0
4100 Example for pxa270 mflash where @var{RST pin} is GPIO 43:
4103 mflash bank pxa270 0x08000000 43 0
4107 @subsection mFlash commands
4108 @cindex mFlash commands
4110 @deffn Command {mflash config pll} frequency
4111 Configure mflash PLL.
4112 The @var{frequency} is the mflash input frequency, in Hz.
4113 Issuing this command will erase mflash's whole internal nand and write new pll.
4114 After this command, mflash needs power-on-reset for normal operation.
4115 If pll was newly configured, storage and boot(optional) info also need to be update.
4118 @deffn Command {mflash config boot}
4119 Configure bootable option.
4120 If bootable option is set, mflash offer the first 8 sectors
4124 @deffn Command {mflash config storage}
4125 Configure storage information.
4126 For the normal storage operation, this information must be
4130 @deffn Command {mflash dump} num filename offset size
4131 Dump @var{size} bytes, starting at @var{offset} bytes from the
4132 beginning of the bank @var{num}, to the file named @var{filename}.
4135 @deffn Command {mflash probe}
4139 @deffn Command {mflash write} num filename offset
4140 Write the binary file @var{filename} to mflash bank @var{num}, starting at
4141 @var{offset} bytes from the beginning of the bank.
4144 @node NAND Flash Commands
4145 @chapter NAND Flash Commands
4148 Compared to NOR or SPI flash, NAND devices are inexpensive
4149 and high density. Today's NAND chips, and multi-chip modules,
4150 commonly hold multiple GigaBytes of data.
4152 NAND chips consist of a number of ``erase blocks'' of a given
4153 size (such as 128 KBytes), each of which is divided into a
4154 number of pages (of perhaps 512 or 2048 bytes each). Each
4155 page of a NAND flash has an ``out of band'' (OOB) area to hold
4156 Error Correcting Code (ECC) and other metadata, usually 16 bytes
4157 of OOB for every 512 bytes of page data.
4159 One key characteristic of NAND flash is that its error rate
4160 is higher than that of NOR flash. In normal operation, that
4161 ECC is used to correct and detect errors. However, NAND
4162 blocks can also wear out and become unusable; those blocks
4163 are then marked "bad". NAND chips are even shipped from the
4164 manufacturer with a few bad blocks. The highest density chips
4165 use a technology (MLC) that wears out more quickly, so ECC
4166 support is increasingly important as a way to detect blocks
4167 that have begun to fail, and help to preserve data integrity
4168 with techniques such as wear leveling.
4170 Software is used to manage the ECC. Some controllers don't
4171 support ECC directly; in those cases, software ECC is used.
4172 Other controllers speed up the ECC calculations with hardware.
4173 Single-bit error correction hardware is routine. Controllers
4174 geared for newer MLC chips may correct 4 or more errors for
4175 every 512 bytes of data.
4177 You will need to make sure that any data you write using
4178 OpenOCD includes the apppropriate kind of ECC. For example,
4179 that may mean passing the @code{oob_softecc} flag when
4180 writing NAND data, or ensuring that the correct hardware
4183 The basic steps for using NAND devices include:
4185 @item Declare via the command @command{nand device}
4186 @* Do this in a board-specific configuration file,
4187 passing parameters as needed by the controller.
4188 @item Configure each device using @command{nand probe}.
4189 @* Do this only after the associated target is set up,
4190 such as in its reset-init script or in procures defined
4191 to access that device.
4192 @item Operate on the flash via @command{nand subcommand}
4193 @* Often commands to manipulate the flash are typed by a human, or run
4194 via a script in some automated way. Common task include writing a
4195 boot loader, operating system, or other data needed to initialize or
4199 @b{NOTE:} At the time this text was written, the largest NAND
4200 flash fully supported by OpenOCD is 2 GiBytes (16 GiBits).
4201 This is because the variables used to hold offsets and lengths
4202 are only 32 bits wide.
4203 (Larger chips may work in some cases, unless an offset or length
4204 is larger than 0xffffffff, the largest 32-bit unsigned integer.)
4205 Some larger devices will work, since they are actually multi-chip
4206 modules with two smaller chips and individual chipselect lines.
4208 @anchor{NAND Configuration}
4209 @section NAND Configuration Commands
4210 @cindex NAND configuration
4212 NAND chips must be declared in configuration scripts,
4213 plus some additional configuration that's done after
4214 OpenOCD has initialized.
4216 @deffn {Config Command} {nand device} controller target [configparams...]
4217 Declares a NAND device, which can be read and written to
4218 after it has been configured through @command{nand probe}.
4219 In OpenOCD, devices are single chips; this is unlike some
4220 operating systems, which may manage multiple chips as if
4221 they were a single (larger) device.
4222 In some cases, configuring a device will activate extra
4223 commands; see the controller-specific documentation.
4225 @b{NOTE:} This command is not available after OpenOCD
4226 initialization has completed. Use it in board specific
4227 configuration files, not interactively.
4230 @item @var{controller} ... identifies the controller driver
4231 associated with the NAND device being declared.
4232 @xref{NAND Driver List}.
4233 @item @var{target} ... names the target used when issuing
4234 commands to the NAND controller.
4235 @comment Actually, it's currently a controller-specific parameter...
4236 @item @var{configparams} ... controllers may support, or require,
4237 additional parameters. See the controller-specific documentation
4238 for more information.
4242 @deffn Command {nand list}
4243 Prints a summary of each device declared
4244 using @command{nand device}, numbered from zero.
4245 Note that un-probed devices show no details.
4248 #0: NAND 1GiB 3,3V 8-bit (Micron) pagesize: 2048, buswidth: 8,
4249 blocksize: 131072, blocks: 8192
4250 #1: NAND 1GiB 3,3V 8-bit (Micron) pagesize: 2048, buswidth: 8,
4251 blocksize: 131072, blocks: 8192
4256 @deffn Command {nand probe} num
4257 Probes the specified device to determine key characteristics
4258 like its page and block sizes, and how many blocks it has.
4259 The @var{num} parameter is the value shown by @command{nand list}.
4260 You must (successfully) probe a device before you can use
4261 it with most other NAND commands.
4264 @section Erasing, Reading, Writing to NAND Flash
4266 @deffn Command {nand dump} num filename offset length [oob_option]
4267 @cindex NAND reading
4268 Reads binary data from the NAND device and writes it to the file,
4269 starting at the specified offset.
4270 The @var{num} parameter is the value shown by @command{nand list}.
4272 Use a complete path name for @var{filename}, so you don't depend
4273 on the directory used to start the OpenOCD server.
4275 The @var{offset} and @var{length} must be exact multiples of the
4276 device's page size. They describe a data region; the OOB data
4277 associated with each such page may also be accessed.
4279 @b{NOTE:} At the time this text was written, no error correction
4280 was done on the data that's read, unless raw access was disabled
4281 and the underlying NAND controller driver had a @code{read_page}
4282 method which handled that error correction.
4284 By default, only page data is saved to the specified file.
4285 Use an @var{oob_option} parameter to save OOB data:
4287 @item no oob_* parameter
4288 @*Output file holds only page data; OOB is discarded.
4289 @item @code{oob_raw}
4290 @*Output file interleaves page data and OOB data;
4291 the file will be longer than "length" by the size of the
4292 spare areas associated with each data page.
4293 Note that this kind of "raw" access is different from
4294 what's implied by @command{nand raw_access}, which just
4295 controls whether a hardware-aware access method is used.
4296 @item @code{oob_only}
4297 @*Output file has only raw OOB data, and will
4298 be smaller than "length" since it will contain only the
4299 spare areas associated with each data page.
4303 @deffn Command {nand erase} num [offset length]
4304 @cindex NAND erasing
4305 @cindex NAND programming
4306 Erases blocks on the specified NAND device, starting at the
4307 specified @var{offset} and continuing for @var{length} bytes.
4308 Both of those values must be exact multiples of the device's
4309 block size, and the region they specify must fit entirely in the chip.
4310 If those parameters are not specified,
4311 the whole NAND chip will be erased.
4312 The @var{num} parameter is the value shown by @command{nand list}.
4314 @b{NOTE:} This command will try to erase bad blocks, when told
4315 to do so, which will probably invalidate the manufacturer's bad
4317 For the remainder of the current server session, @command{nand info}
4318 will still report that the block ``is'' bad.
4321 @deffn Command {nand write} num filename offset [option...]
4322 @cindex NAND writing
4323 @cindex NAND programming
4324 Writes binary data from the file into the specified NAND device,
4325 starting at the specified offset. Those pages should already
4326 have been erased; you can't change zero bits to one bits.
4327 The @var{num} parameter is the value shown by @command{nand list}.
4329 Use a complete path name for @var{filename}, so you don't depend
4330 on the directory used to start the OpenOCD server.
4332 The @var{offset} must be an exact multiple of the device's page size.
4333 All data in the file will be written, assuming it doesn't run
4334 past the end of the device.
4335 Only full pages are written, and any extra space in the last
4336 page will be filled with 0xff bytes. (That includes OOB data,
4337 if that's being written.)
4339 @b{NOTE:} At the time this text was written, bad blocks are
4340 ignored. That is, this routine will not skip bad blocks,
4341 but will instead try to write them. This can cause problems.
4343 Provide at most one @var{option} parameter. With some
4344 NAND drivers, the meanings of these parameters may change
4345 if @command{nand raw_access} was used to disable hardware ECC.
4347 @item no oob_* parameter
4348 @*File has only page data, which is written.
4349 If raw acccess is in use, the OOB area will not be written.
4350 Otherwise, if the underlying NAND controller driver has
4351 a @code{write_page} routine, that routine may write the OOB
4352 with hardware-computed ECC data.
4353 @item @code{oob_only}
4354 @*File has only raw OOB data, which is written to the OOB area.
4355 Each page's data area stays untouched. @i{This can be a dangerous
4356 option}, since it can invalidate the ECC data.
4357 You may need to force raw access to use this mode.
4358 @item @code{oob_raw}
4359 @*File interleaves data and OOB data, both of which are written
4360 If raw access is enabled, the data is written first, then the
4362 Otherwise, if the underlying NAND controller driver has
4363 a @code{write_page} routine, that routine may modify the OOB
4364 before it's written, to include hardware-computed ECC data.
4365 @item @code{oob_softecc}
4366 @*File has only page data, which is written.
4367 The OOB area is filled with 0xff, except for a standard 1-bit
4368 software ECC code stored in conventional locations.
4369 You might need to force raw access to use this mode, to prevent
4370 the underlying driver from applying hardware ECC.
4371 @item @code{oob_softecc_kw}
4372 @*File has only page data, which is written.
4373 The OOB area is filled with 0xff, except for a 4-bit software ECC
4374 specific to the boot ROM in Marvell Kirkwood SoCs.
4375 You might need to force raw access to use this mode, to prevent
4376 the underlying driver from applying hardware ECC.
4380 @section Other NAND commands
4381 @cindex NAND other commands
4383 @deffn Command {nand check_bad_blocks} [offset length]
4384 Checks for manufacturer bad block markers on the specified NAND
4385 device. If no parameters are provided, checks the whole
4386 device; otherwise, starts at the specified @var{offset} and
4387 continues for @var{length} bytes.
4388 Both of those values must be exact multiples of the device's
4389 block size, and the region they specify must fit entirely in the chip.
4390 The @var{num} parameter is the value shown by @command{nand list}.
4392 @b{NOTE:} Before using this command you should force raw access
4393 with @command{nand raw_access enable} to ensure that the underlying
4394 driver will not try to apply hardware ECC.
4397 @deffn Command {nand info} num
4398 The @var{num} parameter is the value shown by @command{nand list}.
4399 This prints the one-line summary from "nand list", plus for
4400 devices which have been probed this also prints any known
4401 status for each block.
4404 @deffn Command {nand raw_access} num (@option{enable}|@option{disable})
4405 Sets or clears an flag affecting how page I/O is done.
4406 The @var{num} parameter is the value shown by @command{nand list}.
4408 This flag is cleared (disabled) by default, but changing that
4409 value won't affect all NAND devices. The key factor is whether
4410 the underlying driver provides @code{read_page} or @code{write_page}
4411 methods. If it doesn't provide those methods, the setting of
4412 this flag is irrelevant; all access is effectively ``raw''.
4414 When those methods exist, they are normally used when reading
4415 data (@command{nand dump} or reading bad block markers) or
4416 writing it (@command{nand write}). However, enabling
4417 raw access (setting the flag) prevents use of those methods,
4418 bypassing hardware ECC logic.
4419 @i{This can be a dangerous option}, since writing blocks
4420 with the wrong ECC data can cause them to be marked as bad.
4423 @anchor{NAND Driver List}
4424 @section NAND Drivers, Options, and Commands
4425 As noted above, the @command{nand device} command allows
4426 driver-specific options and behaviors.
4427 Some controllers also activate controller-specific commands.
4429 @deffn {NAND Driver} davinci
4430 This driver handles the NAND controllers found on DaVinci family
4431 chips from Texas Instruments.
4432 It takes three extra parameters:
4433 address of the NAND chip;
4434 hardware ECC mode to use (@option{hwecc1},
4435 @option{hwecc4}, @option{hwecc4_infix});
4436 address of the AEMIF controller on this processor.
4438 nand device davinci dm355.arm 0x02000000 hwecc4 0x01e10000
4440 All DaVinci processors support the single-bit ECC hardware,
4441 and newer ones also support the four-bit ECC hardware.
4442 The @code{write_page} and @code{read_page} methods are used
4443 to implement those ECC modes, unless they are disabled using
4444 the @command{nand raw_access} command.
4447 @deffn {NAND Driver} lpc3180
4448 These controllers require an extra @command{nand device}
4449 parameter: the clock rate used by the controller.
4450 @deffn Command {lpc3180 select} num [mlc|slc]
4451 Configures use of the MLC or SLC controller mode.
4452 MLC implies use of hardware ECC.
4453 The @var{num} parameter is the value shown by @command{nand list}.
4456 At this writing, this driver includes @code{write_page}
4457 and @code{read_page} methods. Using @command{nand raw_access}
4458 to disable those methods will prevent use of hardware ECC
4459 in the MLC controller mode, but won't change SLC behavior.
4461 @comment current lpc3180 code won't issue 5-byte address cycles
4463 @deffn {NAND Driver} orion
4464 These controllers require an extra @command{nand device}
4465 parameter: the address of the controller.
4467 nand device orion 0xd8000000
4469 These controllers don't define any specialized commands.
4470 At this writing, their drivers don't include @code{write_page}
4471 or @code{read_page} methods, so @command{nand raw_access} won't
4472 change any behavior.
4475 @deffn {NAND Driver} s3c2410
4476 @deffnx {NAND Driver} s3c2412
4477 @deffnx {NAND Driver} s3c2440
4478 @deffnx {NAND Driver} s3c2443
4479 These S3C24xx family controllers don't have any special
4480 @command{nand device} options, and don't define any
4481 specialized commands.
4482 At this writing, their drivers don't include @code{write_page}
4483 or @code{read_page} methods, so @command{nand raw_access} won't
4484 change any behavior.
4487 @node PLD/FPGA Commands
4488 @chapter PLD/FPGA Commands
4492 Programmable Logic Devices (PLDs) and the more flexible
4493 Field Programmable Gate Arrays (FPGAs) are both types of programmable hardware.
4494 OpenOCD can support programming them.
4495 Although PLDs are generally restrictive (cells are less functional, and
4496 there are no special purpose cells for memory or computational tasks),
4497 they share the same OpenOCD infrastructure.
4498 Accordingly, both are called PLDs here.
4500 @section PLD/FPGA Configuration and Commands
4502 As it does for JTAG TAPs, debug targets, and flash chips (both NOR and NAND),
4503 OpenOCD maintains a list of PLDs available for use in various commands.
4504 Also, each such PLD requires a driver.
4506 They are referenced by the number shown by the @command{pld devices} command,
4507 and new PLDs are defined by @command{pld device driver_name}.
4509 @deffn {Config Command} {pld device} driver_name tap_name [driver_options]
4510 Defines a new PLD device, supported by driver @var{driver_name},
4511 using the TAP named @var{tap_name}.
4512 The driver may make use of any @var{driver_options} to configure its
4516 @deffn {Command} {pld devices}
4517 Lists the PLDs and their numbers.
4520 @deffn {Command} {pld load} num filename
4521 Loads the file @file{filename} into the PLD identified by @var{num}.
4522 The file format must be inferred by the driver.
4525 @section PLD/FPGA Drivers, Options, and Commands
4527 Drivers may support PLD-specific options to the @command{pld device}
4528 definition command, and may also define commands usable only with
4529 that particular type of PLD.
4531 @deffn {FPGA Driver} virtex2
4532 Virtex-II is a family of FPGAs sold by Xilinx.
4533 It supports the IEEE 1532 standard for In-System Configuration (ISC).
4534 No driver-specific PLD definition options are used,
4535 and one driver-specific command is defined.
4537 @deffn {Command} {virtex2 read_stat} num
4538 Reads and displays the Virtex-II status register (STAT)
4543 @node General Commands
4544 @chapter General Commands
4547 The commands documented in this chapter here are common commands that
4548 you, as a human, may want to type and see the output of. Configuration type
4549 commands are documented elsewhere.
4553 @item @b{Source Of Commands}
4554 @* OpenOCD commands can occur in a configuration script (discussed
4555 elsewhere) or typed manually by a human or supplied programatically,
4556 or via one of several TCP/IP Ports.
4558 @item @b{From the human}
4559 @* A human should interact with the telnet interface (default port: 4444)
4560 or via GDB (default port 3333).
4562 To issue commands from within a GDB session, use the @option{monitor}
4563 command, e.g. use @option{monitor poll} to issue the @option{poll}
4564 command. All output is relayed through the GDB session.
4566 @item @b{Machine Interface}
4567 The Tcl interface's intent is to be a machine interface. The default Tcl
4572 @section Daemon Commands
4574 @deffn {Command} exit
4575 Exits the current telnet session.
4578 @c note EXTREMELY ANNOYING word wrap at column 75
4579 @c even when lines are e.g. 100+ columns ...
4580 @c coded in startup.tcl
4581 @deffn {Command} help [string]
4582 With no parameters, prints help text for all commands.
4583 Otherwise, prints each helptext containing @var{string}.
4584 Not every command provides helptext.
4587 @deffn Command sleep msec [@option{busy}]
4588 Wait for at least @var{msec} milliseconds before resuming.
4589 If @option{busy} is passed, busy-wait instead of sleeping.
4590 (This option is strongly discouraged.)
4591 Useful in connection with script files
4592 (@command{script} command and @command{target_name} configuration).
4595 @deffn Command shutdown
4596 Close the OpenOCD daemon, disconnecting all clients (GDB, telnet, other).
4599 @anchor{debug_level}
4600 @deffn Command debug_level [n]
4601 @cindex message level
4602 Display debug level.
4603 If @var{n} (from 0..3) is provided, then set it to that level.
4604 This affects the kind of messages sent to the server log.
4605 Level 0 is error messages only;
4606 level 1 adds warnings;
4607 level 2 adds informational messages;
4608 and level 3 adds debugging messages.
4609 The default is level 2, but that can be overridden on
4610 the command line along with the location of that log
4611 file (which is normally the server's standard output).
4615 @deffn Command fast (@option{enable}|@option{disable})
4617 Set default behaviour of OpenOCD to be "fast and dangerous".
4619 At this writing, this only affects the defaults for two ARM7/ARM9 parameters:
4620 fast memory access, and DCC downloads. Those parameters may still be
4621 individually overridden.
4623 The target specific "dangerous" optimisation tweaking options may come and go
4624 as more robust and user friendly ways are found to ensure maximum throughput
4625 and robustness with a minimum of configuration.
4627 Typically the "fast enable" is specified first on the command line:
4630 openocd -c "fast enable" -c "interface dummy" -f target/str710.cfg
4634 @deffn Command echo message
4635 Logs a message at "user" priority.
4636 Output @var{message} to stdout.
4638 echo "Downloading kernel -- please wait"
4642 @deffn Command log_output [filename]
4643 Redirect logging to @var{filename};
4644 the initial log output channel is stderr.
4647 @anchor{Target State handling}
4648 @section Target State handling
4651 @cindex target initialization
4653 In this section ``target'' refers to a CPU configured as
4654 shown earlier (@pxref{CPU Configuration}).
4655 These commands, like many, implicitly refer to
4656 a current target which is used to perform the
4657 various operations. The current target may be changed
4658 by using @command{targets} command with the name of the
4659 target which should become current.
4661 @deffn Command reg [(number|name) [value]]
4662 Access a single register by @var{number} or by its @var{name}.
4664 @emph{With no arguments}:
4665 list all available registers for the current target,
4666 showing number, name, size, value, and cache status.
4668 @emph{With number/name}: display that register's value.
4670 @emph{With both number/name and value}: set register's value.
4672 Cores may have surprisingly many registers in their
4673 Debug and trace infrastructure:
4677 (0) r0 (/32): 0x0000D3C2 (dirty: 1, valid: 1)
4678 (1) r1 (/32): 0xFD61F31C (dirty: 0, valid: 1)
4679 (2) r2 (/32): 0x00022551 (dirty: 0, valid: 1)
4681 (164) ETM_CONTEXTID_COMPARATOR_MASK (/32): \
4682 0x00000000 (dirty: 0, valid: 0)
4687 @deffn Command halt [ms]
4688 @deffnx Command wait_halt [ms]
4689 The @command{halt} command first sends a halt request to the target,
4690 which @command{wait_halt} doesn't.
4691 Otherwise these behave the same: wait up to @var{ms} milliseconds,
4692 or 5 seconds if there is no parameter, for the target to halt
4693 (and enter debug mode).
4694 Using 0 as the @var{ms} parameter prevents OpenOCD from waiting.
4697 On ARM cores, software using the @emph{wait for interrupt} operation
4698 often blocks the JTAG access needed by a @command{halt} command.
4699 This is because that operation also puts the core into a low
4700 power mode by gating the core clock;
4701 but the core clock is needed to detect JTAG clock transitions.
4703 One partial workaround uses adaptive clocking: when the core is
4704 interrupted the operation completes, then JTAG clocks are accepted
4705 at least until the interrupt handler completes.
4706 However, this workaround is often unusable since the processor, board,
4707 and JTAG adapter must all support adaptive JTAG clocking.
4708 Also, it can't work until an interrupt is issued.
4710 A more complete workaround is to not use that operation while you
4711 work with a JTAG debugger.
4712 Tasking environments generaly have idle loops where the body is the
4713 @emph{wait for interrupt} operation.
4714 (On older cores, it is a coprocessor action;
4715 newer cores have a @option{wfi} instruction.)
4716 Such loops can just remove that operation, at the cost of higher
4717 power consumption (because the CPU is needlessly clocked).
4722 @deffn Command resume [address]
4723 Resume the target at its current code position,
4724 or the optional @var{address} if it is provided.
4725 OpenOCD will wait 5 seconds for the target to resume.
4728 @deffn Command step [address]
4729 Single-step the target at its current code position,
4730 or the optional @var{address} if it is provided.
4733 @anchor{Reset Command}
4734 @deffn Command reset
4735 @deffnx Command {reset run}
4736 @deffnx Command {reset halt}
4737 @deffnx Command {reset init}
4738 Perform as hard a reset as possible, using SRST if possible.
4739 @emph{All defined targets will be reset, and target
4740 events will fire during the reset sequence.}
4742 The optional parameter specifies what should
4743 happen after the reset.
4744 If there is no parameter, a @command{reset run} is executed.
4745 The other options will not work on all systems.
4746 @xref{Reset Configuration}.
4749 @item @b{run} Let the target run
4750 @item @b{halt} Immediately halt the target
4751 @item @b{init} Immediately halt the target, and execute the reset-init script
4755 @deffn Command soft_reset_halt
4756 Requesting target halt and executing a soft reset. This is often used
4757 when a target cannot be reset and halted. The target, after reset is
4758 released begins to execute code. OpenOCD attempts to stop the CPU and
4759 then sets the program counter back to the reset vector. Unfortunately
4760 the code that was executed may have left the hardware in an unknown
4764 @section I/O Utilities
4766 These commands are available when
4767 OpenOCD is built with @option{--enable-ioutil}.
4768 They are mainly useful on embedded targets,
4770 Hosts with operating systems have complementary tools.
4772 @emph{Note:} there are several more such commands.
4774 @deffn Command append_file filename [string]*
4775 Appends the @var{string} parameters to
4776 the text file @file{filename}.
4777 Each string except the last one is followed by one space.
4778 The last string is followed by a newline.
4781 @deffn Command cat filename
4782 Reads and displays the text file @file{filename}.
4785 @deffn Command cp src_filename dest_filename
4786 Copies contents from the file @file{src_filename}
4787 into @file{dest_filename}.
4791 @emph{No description provided.}
4795 @emph{No description provided.}
4799 @emph{No description provided.}
4802 @deffn Command meminfo
4803 Display available RAM memory on OpenOCD host.
4804 Used in OpenOCD regression testing scripts.
4808 @emph{No description provided.}
4812 @emph{No description provided.}
4815 @deffn Command rm filename
4816 @c "rm" has both normal and Jim-level versions??
4817 Unlinks the file @file{filename}.
4820 @deffn Command trunc filename
4821 Removes all data in the file @file{filename}.
4824 @anchor{Memory access}
4825 @section Memory access commands
4826 @cindex memory access
4828 These commands allow accesses of a specific size to the memory
4829 system. Often these are used to configure the current target in some
4830 special way. For example - one may need to write certain values to the
4831 SDRAM controller to enable SDRAM.
4834 @item Use the @command{targets} (plural) command
4835 to change the current target.
4836 @item In system level scripts these commands are deprecated.
4837 Please use their TARGET object siblings to avoid making assumptions
4838 about what TAP is the current target, or about MMU configuration.
4841 @deffn Command mdw addr [count]
4842 @deffnx Command mdh addr [count]
4843 @deffnx Command mdb addr [count]
4844 Display contents of address @var{addr}, as
4845 32-bit words (@command{mdw}), 16-bit halfwords (@command{mdh}),
4846 or 8-bit bytes (@command{mdb}).
4847 If @var{count} is specified, displays that many units.
4848 (If you want to manipulate the data instead of displaying it,
4849 see the @code{mem2array} primitives.)
4852 @deffn Command mww addr word
4853 @deffnx Command mwh addr halfword
4854 @deffnx Command mwb addr byte
4855 Writes the specified @var{word} (32 bits),
4856 @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
4857 at the specified address @var{addr}.
4861 @anchor{Image access}
4862 @section Image loading commands
4863 @cindex image loading
4864 @cindex image dumping
4867 @deffn Command {dump_image} filename address size
4868 Dump @var{size} bytes of target memory starting at @var{address} to the
4869 binary file named @var{filename}.
4872 @deffn Command {fast_load}
4873 Loads an image stored in memory by @command{fast_load_image} to the
4874 current target. Must be preceeded by fast_load_image.
4877 @deffn Command {fast_load_image} filename address [@option{bin}|@option{ihex}|@option{elf}]
4878 Normally you should be using @command{load_image} or GDB load. However, for
4879 testing purposes or when I/O overhead is significant(OpenOCD running on an embedded
4880 host), storing the image in memory and uploading the image to the target
4881 can be a way to upload e.g. multiple debug sessions when the binary does not change.
4882 Arguments are the same as @command{load_image}, but the image is stored in OpenOCD host
4883 memory, i.e. does not affect target. This approach is also useful when profiling
4884 target programming performance as I/O and target programming can easily be profiled
4889 @deffn Command {load_image} filename address [@option{bin}|@option{ihex}|@option{elf}]
4890 Load image from file @var{filename} to target memory at @var{address}.
4891 The file format may optionally be specified
4892 (@option{bin}, @option{ihex}, or @option{elf})
4895 @deffn Command {test_image} filename [address [@option{bin}|@option{ihex}|@option{elf}]]
4896 Displays image section sizes and addresses
4897 as if @var{filename} were loaded into target memory
4898 starting at @var{address} (defaults to zero).
4899 The file format may optionally be specified
4900 (@option{bin}, @option{ihex}, or @option{elf})
4903 @deffn Command {verify_image} filename address [@option{bin}|@option{ihex}|@option{elf}]
4904 Verify @var{filename} against target memory starting at @var{address}.
4905 The file format may optionally be specified
4906 (@option{bin}, @option{ihex}, or @option{elf})
4907 This will first attempt a comparison using a CRC checksum, if this fails it will try a binary compare.
4911 @section Breakpoint and Watchpoint commands
4915 CPUs often make debug modules accessible through JTAG, with
4916 hardware support for a handful of code breakpoints and data
4918 In addition, CPUs almost always support software breakpoints.
4920 @deffn Command {bp} [address len [@option{hw}]]
4921 With no parameters, lists all active breakpoints.
4922 Else sets a breakpoint on code execution starting
4923 at @var{address} for @var{length} bytes.
4924 This is a software breakpoint, unless @option{hw} is specified
4925 in which case it will be a hardware breakpoint.
4927 (@xref{arm9tdmi vector_catch}, or @pxref{xscale vector_catch},
4928 for similar mechanisms that do not consume hardware breakpoints.)
4931 @deffn Command {rbp} address
4932 Remove the breakpoint at @var{address}.
4935 @deffn Command {rwp} address
4936 Remove data watchpoint on @var{address}
4939 @deffn Command {wp} [address len [(@option{r}|@option{w}|@option{a}) [value [mask]]]]
4940 With no parameters, lists all active watchpoints.
4941 Else sets a data watchpoint on data from @var{address} for @var{length} bytes.
4942 The watch point is an "access" watchpoint unless
4943 the @option{r} or @option{w} parameter is provided,
4944 defining it as respectively a read or write watchpoint.
4945 If a @var{value} is provided, that value is used when determining if
4946 the watchpoint should trigger. The value may be first be masked
4947 using @var{mask} to mark ``don't care'' fields.
4950 @section Misc Commands
4953 @deffn Command {profile} seconds filename
4954 Profiling samples the CPU's program counter as quickly as possible,
4955 which is useful for non-intrusive stochastic profiling.
4956 Saves up to 10000 sampines in @file{filename} using ``gmon.out'' format.
4959 @deffn Command {version}
4960 Displays a string identifying the version of this OpenOCD server.
4963 @deffn Command {virt2phys} virtual_address
4964 Requests the current target to map the specified @var{virtual_address}
4965 to its corresponding physical address, and displays the result.
4968 @node Architecture and Core Commands
4969 @chapter Architecture and Core Commands
4970 @cindex Architecture Specific Commands
4971 @cindex Core Specific Commands
4973 Most CPUs have specialized JTAG operations to support debugging.
4974 OpenOCD packages most such operations in its standard command framework.
4975 Some of those operations don't fit well in that framework, so they are
4976 exposed here as architecture or implementation (core) specific commands.
4978 @anchor{ARM Hardware Tracing}
4979 @section ARM Hardware Tracing
4984 CPUs based on ARM cores may include standard tracing interfaces,
4985 based on an ``Embedded Trace Module'' (ETM) which sends voluminous
4986 address and data bus trace records to a ``Trace Port''.
4990 Development-oriented boards will sometimes provide a high speed
4991 trace connector for collecting that data, when the particular CPU
4992 supports such an interface.
4993 (The standard connector is a 38-pin Mictor, with both JTAG
4994 and trace port support.)
4995 Those trace connectors are supported by higher end JTAG adapters
4996 and some logic analyzer modules; frequently those modules can
4997 buffer several megabytes of trace data.
4998 Configuring an ETM coupled to such an external trace port belongs
4999 in the board-specific configuration file.
5001 If the CPU doesn't provide an external interface, it probably
5002 has an ``Embedded Trace Buffer'' (ETB) on the chip, which is a
5003 dedicated SRAM. 4KBytes is one common ETB size.
5004 Configuring an ETM coupled only to an ETB belongs in the CPU-specific
5005 (target) configuration file, since it works the same on all boards.
5008 ETM support in OpenOCD doesn't seem to be widely used yet.
5011 ETM support may be buggy, and at least some @command{etm config}
5012 parameters should be detected by asking the ETM for them.
5013 It seems like a GDB hookup should be possible,
5014 as well as triggering trace on specific events
5015 (perhaps @emph{handling IRQ 23} or @emph{calls foo()}).
5016 There should be GUI tools to manipulate saved trace data and help
5017 analyse it in conjunction with the source code.
5018 It's unclear how much of a common interface is shared
5019 with the current XScale trace support, or should be
5020 shared with eventual Nexus-style trace module support.
5021 At this writing (September 2009) only ARM7 and ARM9 support
5022 for ETM modules is available. The code should be able to
5023 work with some newer cores; but not all of them support
5024 this original style of JTAG access.
5027 @subsection ETM Configuration
5028 ETM setup is coupled with the trace port driver configuration.
5030 @deffn {Config Command} {etm config} target width mode clocking driver
5031 Declares the ETM associated with @var{target}, and associates it
5032 with a given trace port @var{driver}. @xref{Trace Port Drivers}.
5034 Several of the parameters must reflect the trace port configuration.
5035 The @var{width} must be either 4, 8, or 16.
5036 The @var{mode} must be @option{normal}, @option{multiplexted},
5037 or @option{demultiplexted}.
5038 The @var{clocking} must be @option{half} or @option{full}.
5041 You can see the ETM registers using the @command{reg} command.
5042 Not all possible registers are present in every ETM.
5043 Most of the registers are write-only, and are used to configure
5044 what CPU activities are traced.
5048 @deffn Command {etm info}
5049 Displays information about the current target's ETM.
5052 @deffn Command {etm status}
5053 Displays status of the current target's ETM and trace port driver:
5054 is the ETM idle, or is it collecting data?
5055 Did trace data overflow?
5059 @deffn Command {etm tracemode} [type context_id_bits cycle_accurate branch_output]
5060 Displays what data that ETM will collect.
5061 If arguments are provided, first configures that data.
5062 When the configuration changes, tracing is stopped
5063 and any buffered trace data is invalidated.
5066 @item @var{type} ... describing how data accesses are traced,
5067 when they pass any ViewData filtering that that was set up.
5069 @option{none} (save nothing),
5070 @option{data} (save data),
5071 @option{address} (save addresses),
5072 @option{all} (save data and addresses)
5073 @item @var{context_id_bits} ... 0, 8, 16, or 32
5074 @item @var{cycle_accurate} ... @option{enable} or @option{disable}
5075 cycle-accurate instruction tracing.
5076 Before ETMv3, enabling this causes much extra data to be recorded.
5077 @item @var{branch_output} ... @option{enable} or @option{disable}.
5078 Disable this unless you need to try reconstructing the instruction
5079 trace stream without an image of the code.
5083 @deffn Command {etm trigger_percent} [percent]
5084 This displays, or optionally changes, the trace port driver's
5085 behavior after the ETM's configured @emph{trigger} event fires.
5086 It controls how much more trace data is saved after the (single)
5087 trace trigger becomes active.
5090 @item The default corresponds to @emph{trace around} usage,
5091 recording 50 percent data before the event and the rest
5093 @item The minimum value of @var{percent} is 2 percent,
5094 recording almost exclusively data before the trigger.
5095 Such extreme @emph{trace before} usage can help figure out
5096 what caused that event to happen.
5097 @item The maximum value of @var{percent} is 100 percent,
5098 recording data almost exclusively after the event.
5099 This extreme @emph{trace after} usage might help sort out
5100 how the event caused trouble.
5102 @c REVISIT allow "break" too -- enter debug mode.
5105 @subsection ETM Trace Operation
5107 After setting up the ETM, you can use it to collect data.
5108 That data can be exported to files for later analysis.
5109 It can also be parsed with OpenOCD, for basic sanity checking.
5111 To configure what is being traced, you will need to write
5112 various trace registers using @command{reg ETM_*} commands.
5113 For the definitions of these registers, read ARM publication
5114 @emph{IHI 0014, ``Embedded Trace Macrocell, Architecture Specification''}.
5115 Be aware that most of the relevant registers are write-only,
5116 and that ETM resources are limited. There are only a handful
5117 of address comparators, data comparators, counters, and so on.
5119 Examples of scenarios you might arrange to trace include:
5122 @item Code flow within a function, @emph{excluding} subroutines
5123 it calls. Use address range comparators to enable tracing
5124 for instruction access within that function's body.
5125 @item Code flow within a function, @emph{including} subroutines
5126 it calls. Use the sequencer and address comparators to activate
5127 tracing on an ``entered function'' state, then deactivate it by
5128 exiting that state when the function's exit code is invoked.
5129 @item Code flow starting at the fifth invocation of a function,
5130 combining one of the above models with a counter.
5131 @item CPU data accesses to the registers for a particular device,
5132 using address range comparators and the ViewData logic.
5133 @item Such data accesses only during IRQ handling, combining the above
5134 model with sequencer triggers which on entry and exit to the IRQ handler.
5135 @item @emph{... more}
5138 At this writing, September 2009, there are no Tcl utility
5139 procedures to help set up any common tracing scenarios.
5141 @deffn Command {etm analyze}
5142 Reads trace data into memory, if it wasn't already present.
5143 Decodes and prints the data that was collected.
5146 @deffn Command {etm dump} filename
5147 Stores the captured trace data in @file{filename}.
5150 @deffn Command {etm image} filename [base_address] [type]
5151 Opens an image file.
5154 @deffn Command {etm load} filename
5155 Loads captured trace data from @file{filename}.
5158 @deffn Command {etm start}
5159 Starts trace data collection.
5162 @deffn Command {etm stop}
5163 Stops trace data collection.
5166 @anchor{Trace Port Drivers}
5167 @subsection Trace Port Drivers
5169 To use an ETM trace port it must be associated with a driver.
5171 @deffn {Trace Port Driver} dummy
5172 Use the @option{dummy} driver if you are configuring an ETM that's
5173 not connected to anything (on-chip ETB or off-chip trace connector).
5174 @emph{This driver lets OpenOCD talk to the ETM, but it does not expose
5175 any trace data collection.}
5176 @deffn {Config Command} {etm_dummy config} target
5177 Associates the ETM for @var{target} with a dummy driver.
5181 @deffn {Trace Port Driver} etb
5182 Use the @option{etb} driver if you are configuring an ETM
5183 to use on-chip ETB memory.
5184 @deffn {Config Command} {etb config} target etb_tap
5185 Associates the ETM for @var{target} with the ETB at @var{etb_tap}.
5186 You can see the ETB registers using the @command{reg} command.
5190 @deffn {Trace Port Driver} oocd_trace
5191 This driver isn't available unless OpenOCD was explicitly configured
5192 with the @option{--enable-oocd_trace} option. You probably don't want
5193 to configure it unless you've built the appropriate prototype hardware;
5194 it's @emph{proof-of-concept} software.
5196 Use the @option{oocd_trace} driver if you are configuring an ETM that's
5197 connected to an off-chip trace connector.
5199 @deffn {Config Command} {oocd_trace config} target tty
5200 Associates the ETM for @var{target} with a trace driver which
5201 collects data through the serial port @var{tty}.
5204 @deffn Command {oocd_trace resync}
5205 Re-synchronizes with the capture clock.
5208 @deffn Command {oocd_trace status}
5209 Reports whether the capture clock is locked or not.
5214 @section ARMv4 and ARMv5 Architecture
5218 These commands are specific to ARM architecture v4 and v5,
5219 including all ARM7 or ARM9 systems and Intel XScale.
5220 They are available in addition to other core-specific
5221 commands that may be available.
5223 @deffn Command {armv4_5 core_state} [@option{arm}|@option{thumb}]
5224 Displays the core_state, optionally changing it to process
5225 either @option{arm} or @option{thumb} instructions.
5226 The target may later be resumed in the currently set core_state.
5227 (Processors may also support the Jazelle state, but
5228 that is not currently supported in OpenOCD.)
5231 @deffn Command {armv4_5 disassemble} address [count [@option{thumb}]]
5233 Disassembles @var{count} instructions starting at @var{address}.
5234 If @var{count} is not specified, a single instruction is disassembled.
5235 If @option{thumb} is specified, or the low bit of the address is set,
5236 Thumb (16-bit) instructions are used;
5237 else ARM (32-bit) instructions are used.
5238 (Processors may also support the Jazelle state, but
5239 those instructions are not currently understood by OpenOCD.)
5242 @deffn Command {armv4_5 reg}
5243 Display a table of all banked core registers, fetching the current value from every
5244 core mode if necessary. OpenOCD versions before rev. 60 didn't fetch the current
5248 @subsection ARM7 and ARM9 specific commands
5252 These commands are specific to ARM7 and ARM9 cores, like ARM7TDMI, ARM720T,
5253 ARM9TDMI, ARM920T or ARM926EJ-S.
5254 They are available in addition to the ARMv4/5 commands,
5255 and any other core-specific commands that may be available.
5257 @deffn Command {arm7_9 dbgrq} (@option{enable}|@option{disable})
5258 Control use of the EmbeddedIce DBGRQ signal to force entry into debug mode,
5259 instead of breakpoints. This should be
5260 safe for all but ARM7TDMI--S cores (like Philips LPC).
5261 This feature is enabled by default on most ARM9 cores,
5262 including ARM9TDMI, ARM920T, and ARM926EJ-S.
5265 @deffn Command {arm7_9 dcc_downloads} (@option{enable}|@option{disable})
5267 Control the use of the debug communications channel (DCC) to write larger (>128 byte)
5268 amounts of memory. DCC downloads offer a huge speed increase, but might be
5269 unsafe, especially with targets running at very low speeds. This command was introduced
5270 with OpenOCD rev. 60, and requires a few bytes of working area.
5273 @anchor{arm7_9 fast_memory_access}
5274 @deffn Command {arm7_9 fast_memory_access} (@option{enable}|@option{disable})
5275 Enable or disable memory writes and reads that don't check completion of
5276 the operation. This provides a huge speed increase, especially with USB JTAG
5277 cables (FT2232), but might be unsafe if used with targets running at very low
5278 speeds, like the 32kHz startup clock of an AT91RM9200.
5281 @deffn {Debug Command} {arm7_9 write_core_reg} num mode word
5282 @emph{This is intended for use while debugging OpenOCD; you probably
5285 Writes a 32-bit @var{word} to register @var{num} (from 0 to 16)
5286 as used in the specified @var{mode}
5287 (where e.g. mode 16 is "user" and mode 19 is "supervisor";
5288 the M4..M0 bits of the PSR).
5289 Registers 0..15 are the normal CPU registers such as r0(0), r1(1) ... pc(15).
5290 Register 16 is the mode-specific SPSR,
5291 unless the specified mode is 0xffffffff (32-bit all-ones)
5292 in which case register 16 is the CPSR.
5293 The write goes directly to the CPU, bypassing the register cache.
5296 @deffn {Debug Command} {arm7_9 write_xpsr} word (@option{0}|@option{1})
5297 @emph{This is intended for use while debugging OpenOCD; you probably
5300 If the second parameter is zero, writes @var{word} to the
5301 Current Program Status register (CPSR).
5302 Else writes @var{word} to the current mode's Saved PSR (SPSR).
5303 In both cases, this bypasses the register cache.
5306 @deffn {Debug Command} {arm7_9 write_xpsr_im8} byte rotate (@option{0}|@option{1})
5307 @emph{This is intended for use while debugging OpenOCD; you probably
5310 Writes eight bits to the CPSR or SPSR,
5311 first rotating them by @math{2*rotate} bits,
5312 and bypassing the register cache.
5313 This has lower JTAG overhead than writing the entire CPSR or SPSR
5314 with @command{arm7_9 write_xpsr}.
5317 @subsection ARM720T specific commands
5320 These commands are available to ARM720T based CPUs,
5321 which are implementations of the ARMv4T architecture
5322 based on the ARM7TDMI-S integer core.
5323 They are available in addition to the ARMv4/5 and ARM7/ARM9 commands.
5325 @deffn Command {arm720t cp15} regnum [value]
5326 Display cp15 register @var{regnum};
5327 else if a @var{value} is provided, that value is written to that register.
5330 @deffn Command {arm720t mdw_phys} addr [count]
5331 @deffnx Command {arm720t mdh_phys} addr [count]
5332 @deffnx Command {arm720t mdb_phys} addr [count]
5333 Display contents of physical address @var{addr}, as
5334 32-bit words (@command{mdw_phys}), 16-bit halfwords (@command{mdh_phys}),
5335 or 8-bit bytes (@command{mdb_phys}).
5336 If @var{count} is specified, displays that many units.
5339 @deffn Command {arm720t mww_phys} addr word
5340 @deffnx Command {arm720t mwh_phys} addr halfword
5341 @deffnx Command {arm720t mwb_phys} addr byte
5342 Writes the specified @var{word} (32 bits),
5343 @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
5344 at the specified physical address @var{addr}.
5347 @deffn Command {arm720t virt2phys} va
5348 Translate a virtual address @var{va} to a physical address
5349 and display the result.
5352 @subsection ARM9 specific commands
5355 ARM9-family cores are built around ARM9TDMI or ARM9E (including ARM9EJS)
5357 Such cores include the ARM920T, ARM926EJ-S, and ARM966.
5359 For historical reasons, one command shared by these cores starts
5360 with the @command{arm9tdmi} prefix.
5361 This is true even for ARM9E based processors, which implement the
5362 ARMv5TE architecture instead of ARMv4T.
5364 @c 9-june-2009: tried this on arm920t, it didn't work.
5365 @c no-params always lists nothing caught, and that's how it acts.
5367 @anchor{arm9tdmi vector_catch}
5368 @deffn Command {arm9tdmi vector_catch} [@option{all}|@option{none}|list]
5369 @cindex vector_catch
5370 Vector Catch hardware provides a sort of dedicated breakpoint
5371 for hardware events such as reset, interrupt, and abort.
5372 You can use this to conserve normal breakpoint resources,
5373 so long as you're not concerned with code that branches directly
5374 to those hardware vectors.
5376 This always finishes by listing the current configuration.
5377 If parameters are provided, it first reconfigures the
5378 vector catch hardware to intercept
5379 @option{all} of the hardware vectors,
5380 @option{none} of them,
5381 or a list with one or more of the following:
5382 @option{reset} @option{undef} @option{swi} @option{pabt} @option{dabt} @option{reserved}
5383 @option{irq} @option{fiq}.
5386 @subsection ARM920T specific commands
5389 These commands are available to ARM920T based CPUs,
5390 which are implementations of the ARMv4T architecture
5391 built using the ARM9TDMI integer core.
5392 They are available in addition to the ARMv4/5, ARM7/ARM9,
5393 and ARM9TDMI commands.
5395 @deffn Command {arm920t cache_info}
5396 Print information about the caches found. This allows to see whether your target
5397 is an ARM920T (2x16kByte cache) or ARM922T (2x8kByte cache).
5400 @deffn Command {arm920t cp15} regnum [value]
5401 Display cp15 register @var{regnum};
5402 else if a @var{value} is provided, that value is written to that register.
5405 @deffn Command {arm920t cp15i} opcode [value [address]]
5406 Interpreted access using cp15 @var{opcode}.
5407 If no @var{value} is provided, the result is displayed.
5408 Else if that value is written using the specified @var{address},
5409 or using zero if no other address is not provided.
5412 @deffn Command {arm920t mdw_phys} addr [count]
5413 @deffnx Command {arm920t mdh_phys} addr [count]
5414 @deffnx Command {arm920t mdb_phys} addr [count]
5415 Display contents of physical address @var{addr}, as
5416 32-bit words (@command{mdw_phys}), 16-bit halfwords (@command{mdh_phys}),
5417 or 8-bit bytes (@command{mdb_phys}).
5418 If @var{count} is specified, displays that many units.
5421 @deffn Command {arm920t mww_phys} addr word
5422 @deffnx Command {arm920t mwh_phys} addr halfword
5423 @deffnx Command {arm920t mwb_phys} addr byte
5424 Writes the specified @var{word} (32 bits),
5425 @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
5426 at the specified physical address @var{addr}.
5429 @deffn Command {arm920t read_cache} filename
5430 Dump the content of ICache and DCache to a file named @file{filename}.
5433 @deffn Command {arm920t read_mmu} filename
5434 Dump the content of the ITLB and DTLB to a file named @file{filename}.
5437 @deffn Command {arm920t virt2phys} va
5438 Translate a virtual address @var{va} to a physical address
5439 and display the result.
5442 @subsection ARM926ej-s specific commands
5445 These commands are available to ARM926ej-s based CPUs,
5446 which are implementations of the ARMv5TEJ architecture
5447 based on the ARM9EJ-S integer core.
5448 They are available in addition to the ARMv4/5, ARM7/ARM9,
5449 and ARM9TDMI commands.
5451 The Feroceon cores also support these commands, although
5452 they are not built from ARM926ej-s designs.
5454 @deffn Command {arm926ejs cache_info}
5455 Print information about the caches found.
5458 @deffn Command {arm926ejs cp15} opcode1 opcode2 CRn CRm regnum [value]
5459 Accesses cp15 register @var{regnum} using
5460 @var{opcode1}, @var{opcode2}, @var{CRn}, and @var{CRm}.
5461 If a @var{value} is provided, that value is written to that register.
5462 Else that register is read and displayed.
5465 @deffn Command {arm926ejs mdw_phys} addr [count]
5466 @deffnx Command {arm926ejs mdh_phys} addr [count]
5467 @deffnx Command {arm926ejs mdb_phys} addr [count]
5468 Display contents of physical address @var{addr}, as
5469 32-bit words (@command{mdw_phys}), 16-bit halfwords (@command{mdh_phys}),
5470 or 8-bit bytes (@command{mdb_phys}).
5471 If @var{count} is specified, displays that many units.
5474 @deffn Command {arm926ejs mww_phys} addr word
5475 @deffnx Command {arm926ejs mwh_phys} addr halfword
5476 @deffnx Command {arm926ejs mwb_phys} addr byte
5477 Writes the specified @var{word} (32 bits),
5478 @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
5479 at the specified physical address @var{addr}.
5482 @deffn Command {arm926ejs virt2phys} va
5483 Translate a virtual address @var{va} to a physical address
5484 and display the result.
5487 @subsection ARM966E specific commands
5490 These commands are available to ARM966 based CPUs,
5491 which are implementations of the ARMv5TE architecture.
5492 They are available in addition to the ARMv4/5, ARM7/ARM9,
5493 and ARM9TDMI commands.
5495 @deffn Command {arm966e cp15} regnum [value]
5496 Display cp15 register @var{regnum};
5497 else if a @var{value} is provided, that value is written to that register.
5500 @subsection XScale specific commands
5503 Some notes about the debug implementation on the XScale CPUs:
5505 The XScale CPU provides a special debug-only mini-instruction cache
5506 (mini-IC) in which exception vectors and target-resident debug handler
5507 code are placed by OpenOCD. In order to get access to the CPU, OpenOCD
5508 must point vector 0 (the reset vector) to the entry of the debug
5509 handler. However, this means that the complete first cacheline in the
5510 mini-IC is marked valid, which makes the CPU fetch all exception
5511 handlers from the mini-IC, ignoring the code in RAM.
5513 OpenOCD currently does not sync the mini-IC entries with the RAM
5514 contents (which would fail anyway while the target is running), so
5515 the user must provide appropriate values using the @code{xscale
5516 vector_table} command.
5518 It is recommended to place a pc-relative indirect branch in the vector
5519 table, and put the branch destination somewhere in memory. Doing so
5520 makes sure the code in the vector table stays constant regardless of
5521 code layout in memory:
5524 ldr pc,[pc,#0x100-8]
5525 ldr pc,[pc,#0x100-8]
5526 ldr pc,[pc,#0x100-8]
5527 ldr pc,[pc,#0x100-8]
5528 ldr pc,[pc,#0x100-8]
5529 ldr pc,[pc,#0x100-8]
5530 ldr pc,[pc,#0x100-8]
5531 ldr pc,[pc,#0x100-8]
5533 .long real_reset_vector
5534 .long real_ui_handler
5535 .long real_swi_handler
5537 .long real_data_abort
5538 .long 0 /* unused */
5539 .long real_irq_handler
5540 .long real_fiq_handler
5543 The debug handler must be placed somewhere in the address space using
5544 the @code{xscale debug_handler} command. The allowed locations for the
5545 debug handler are either (0x800 - 0x1fef800) or (0xfe000800 -
5546 0xfffff800). The default value is 0xfe000800.
5549 These commands are available to XScale based CPUs,
5550 which are implementations of the ARMv5TE architecture.
5552 @deffn Command {xscale analyze_trace}
5553 Displays the contents of the trace buffer.
5556 @deffn Command {xscale cache_clean_address} address
5557 Changes the address used when cleaning the data cache.
5560 @deffn Command {xscale cache_info}
5561 Displays information about the CPU caches.
5564 @deffn Command {xscale cp15} regnum [value]
5565 Display cp15 register @var{regnum};
5566 else if a @var{value} is provided, that value is written to that register.
5569 @deffn Command {xscale debug_handler} target address
5570 Changes the address used for the specified target's debug handler.
5573 @deffn Command {xscale dcache} (@option{enable}|@option{disable})
5574 Enables or disable the CPU's data cache.
5577 @deffn Command {xscale dump_trace} filename
5578 Dumps the raw contents of the trace buffer to @file{filename}.
5581 @deffn Command {xscale icache} (@option{enable}|@option{disable})
5582 Enables or disable the CPU's instruction cache.
5585 @deffn Command {xscale mmu} (@option{enable}|@option{disable})
5586 Enables or disable the CPU's memory management unit.
5589 @deffn Command {xscale trace_buffer} (@option{enable}|@option{disable}) [@option{fill} [n] | @option{wrap}]
5590 Enables or disables the trace buffer,
5591 and controls how it is emptied.
5594 @deffn Command {xscale trace_image} filename [offset [type]]
5595 Opens a trace image from @file{filename}, optionally rebasing
5596 its segment addresses by @var{offset}.
5597 The image @var{type} may be one of
5598 @option{bin} (binary), @option{ihex} (Intel hex),
5599 @option{elf} (ELF file), @option{s19} (Motorola s19),
5600 @option{mem}, or @option{builder}.
5603 @anchor{xscale vector_catch}
5604 @deffn Command {xscale vector_catch} [mask]
5605 @cindex vector_catch
5606 Display a bitmask showing the hardware vectors to catch.
5607 If the optional parameter is provided, first set the bitmask to that value.
5609 The mask bits correspond with bit 16..23 in the DCSR:
5612 0x02 Trap Undefined Instructions
5613 0x04 Trap Software Interrupt
5614 0x08 Trap Prefetch Abort
5615 0x10 Trap Data Abort
5622 @anchor{xscale vector_table}
5623 @deffn Command {xscale vector_table} [<low|high> <index> <value>]
5624 @cindex vector_table
5626 Set an entry in the mini-IC vector table. There are two tables: one for
5627 low vectors (at 0x00000000), and one for high vectors (0xFFFF0000), each
5628 holding the 8 exception vectors. @var{index} can be 1-7, because vector 0
5629 points to the debug handler entry and can not be overwritten.
5630 @var{value} holds the 32-bit opcode that is placed in the mini-IC.
5632 Without arguments, the current settings are displayed.
5636 @section ARMv6 Architecture
5639 @subsection ARM11 specific commands
5642 @deffn Command {arm11 mcr} pX opc1 CRn CRm opc2 value
5643 Write @var{value} to a coprocessor @var{pX} register
5644 passing parameters @var{CRn},
5645 @var{CRm}, opcodes @var{opc1} and @var{opc2},
5646 and the MCR instruction.
5647 (The difference beween this and the MCR2 instruction is
5648 one bit in the encoding, effecively a fifth parameter.)
5651 @deffn Command {arm11 memwrite burst} [value]
5652 Displays the value of the memwrite burst-enable flag,
5653 which is enabled by default.
5654 If @var{value} is defined, first assigns that.
5657 @deffn Command {arm11 memwrite error_fatal} [value]
5658 Displays the value of the memwrite error_fatal flag,
5659 which is enabled by default.
5660 If @var{value} is defined, first assigns that.
5663 @deffn Command {arm11 mrc} pX opc1 CRn CRm opc2
5664 Read a coprocessor @var{pX} register passing parameters @var{CRn},
5665 @var{CRm}, opcodes @var{opc1} and @var{opc2},
5666 and the MRC instruction.
5667 (The difference beween this and the MRC2 instruction is
5668 one bit in the encoding, effecively a fifth parameter.)
5669 Displays the result.
5672 @deffn Command {arm11 no_increment} [value]
5673 Displays the value of the flag controlling whether
5674 some read or write operations increment the pointer
5675 (the default behavior) or not (acting like a FIFO).
5676 If @var{value} is defined, first assigns that.
5679 @deffn Command {arm11 step_irq_enable} [value]
5680 Displays the value of the flag controlling whether
5681 IRQs are enabled during single stepping;
5682 they are disabled by default.
5683 If @var{value} is defined, first assigns that.
5686 @deffn Command {arm11 vcr} [value]
5687 @cindex vector_catch
5688 Displays the value of the @emph{Vector Catch Register (VCR)},
5689 coprocessor 14 register 7.
5690 If @var{value} is defined, first assigns that.
5692 Vector Catch hardware provides dedicated breakpoints
5693 for certain hardware events.
5694 The specific bit values are core-specific (as in fact is using
5695 coprocessor 14 register 7 itself) but all current ARM11
5696 cores @emph{except the ARM1176} use the same six bits.
5699 @section ARMv7 Architecture
5702 @subsection ARMv7 Debug Access Port (DAP) specific commands
5703 @cindex Debug Access Port
5705 These commands are specific to ARM architecture v7 Debug Access Port (DAP),
5706 included on cortex-m3 and cortex-a8 systems.
5707 They are available in addition to other core-specific commands that may be available.
5709 @deffn Command {dap info} [num]
5710 Displays dap info for ap @var{num}, defaulting to the currently selected AP.
5713 @deffn Command {dap apsel} [num]
5714 Select AP @var{num}, defaulting to 0.
5717 @deffn Command {dap apid} [num]
5718 Displays id register from AP @var{num},
5719 defaulting to the currently selected AP.
5722 @deffn Command {dap baseaddr} [num]
5723 Displays debug base address from AP @var{num},
5724 defaulting to the currently selected AP.
5727 @deffn Command {dap memaccess} [value]
5728 Displays the number of extra tck for mem-ap memory bus access [0-255].
5729 If @var{value} is defined, first assigns that.
5732 @subsection ARMv7-A specific commands
5735 @deffn Command {armv7a disassemble} address [count [@option{thumb}]]
5737 Disassembles @var{count} instructions starting at @var{address}.
5738 If @var{count} is not specified, a single instruction is disassembled.
5739 If @option{thumb} is specified, or the low bit of the address is set,
5740 Thumb2 (mixed 16/32-bit) instructions are used;
5741 else ARM (32-bit) instructions are used.
5742 With a handful of exceptions, ThumbEE instructions are the same as Thumb2;
5743 ThumbEE disassembly currently has no explicit support.
5744 (Processors may also support the Jazelle state, but
5745 those instructions are not currently understood by OpenOCD.)
5749 @subsection Cortex-M3 specific commands
5752 @deffn Command {cortex_m3 disassemble} address [count]
5754 Disassembles @var{count} Thumb2 instructions starting at @var{address}.
5755 If @var{count} is not specified, a single instruction is disassembled.
5758 @deffn Command {cortex_m3 maskisr} (@option{on}|@option{off})
5759 Control masking (disabling) interrupts during target step/resume.
5762 @deffn Command {cortex_m3 vector_catch} [@option{all}|@option{none}|list]
5763 @cindex vector_catch
5764 Vector Catch hardware provides dedicated breakpoints
5765 for certain hardware events.
5767 Parameters request interception of
5768 @option{all} of these hardware event vectors,
5769 @option{none} of them,
5770 or one or more of the following:
5771 @option{hard_err} for a HardFault exception;
5772 @option{mm_err} for a MemManage exception;
5773 @option{bus_err} for a BusFault exception;
5776 @option{chk_err}, or
5777 @option{nocp_err} for various UsageFault exceptions; or
5779 If NVIC setup code does not enable them,
5780 MemManage, BusFault, and UsageFault exceptions
5781 are mapped to HardFault.
5782 UsageFault checks for
5783 divide-by-zero and unaligned access
5784 must also be explicitly enabled.
5786 This finishes by listing the current vector catch configuration.
5789 @anchor{Software Debug Messages and Tracing}
5790 @section Software Debug Messages and Tracing
5791 @cindex Linux-ARM DCC support
5795 OpenOCD can process certain requests from target software. Currently
5796 @command{target_request debugmsgs}
5797 is supported only for @option{arm7_9} and @option{cortex_m3} cores.
5798 These messages are received as part of target polling, so
5799 you need to have @command{poll on} active to receive them.
5800 They are intrusive in that they will affect program execution
5801 times. If that is a problem, @pxref{ARM Hardware Tracing}.
5803 See @file{libdcc} in the contrib dir for more details.
5804 In addition to sending strings, characters, and
5805 arrays of various size integers from the target,
5806 @file{libdcc} also exports a software trace point mechanism.
5807 The target being debugged may
5808 issue trace messages which include a 24-bit @dfn{trace point} number.
5809 Trace point support includes two distinct mechanisms,
5810 each supported by a command:
5813 @item @emph{History} ... A circular buffer of trace points
5814 can be set up, and then displayed at any time.
5815 This tracks where code has been, which can be invaluable in
5816 finding out how some fault was triggered.
5818 The buffer may overflow, since it collects records continuously.
5819 It may be useful to use some of the 24 bits to represent a
5820 particular event, and other bits to hold data.
5822 @item @emph{Counting} ... An array of counters can be set up,
5823 and then displayed at any time.
5824 This can help establish code coverage and identify hot spots.
5826 The array of counters is directly indexed by the trace point
5827 number, so trace points with higher numbers are not counted.
5830 Linux-ARM kernels have a ``Kernel low-level debugging
5831 via EmbeddedICE DCC channel'' option (CONFIG_DEBUG_ICEDCC,
5832 depends on CONFIG_DEBUG_LL) which uses this mechanism to
5833 deliver messages before a serial console can be activated.
5834 This is not the same format used by @file{libdcc}.
5835 Other software, such as the U-Boot boot loader, sometimes
5836 does the same thing.
5838 @deffn Command {target_request debugmsgs} [@option{enable}|@option{disable}|@option{charmsg}]
5839 Displays current handling of target DCC message requests.
5840 These messages may be sent to the debugger while the target is running.
5841 The optional @option{enable} and @option{charmsg} parameters
5842 both enable the messages, while @option{disable} disables them.
5844 With @option{charmsg} the DCC words each contain one character,
5845 as used by Linux with CONFIG_DEBUG_ICEDCC;
5846 otherwise the libdcc format is used.
5849 @deffn Command {trace history} [@option{clear}|count]
5850 With no parameter, displays all the trace points that have triggered
5851 in the order they triggered.
5852 With the parameter @option{clear}, erases all current trace history records.
5853 With a @var{count} parameter, allocates space for that many
5857 @deffn Command {trace point} [@option{clear}|identifier]
5858 With no parameter, displays all trace point identifiers and how many times
5859 they have been triggered.
5860 With the parameter @option{clear}, erases all current trace point counters.
5861 With a numeric @var{identifier} parameter, creates a new a trace point counter
5862 and associates it with that identifier.
5864 @emph{Important:} The identifier and the trace point number
5865 are not related except by this command.
5866 These trace point numbers always start at zero (from server startup,
5867 or after @command{trace point clear}) and count up from there.
5872 @chapter JTAG Commands
5873 @cindex JTAG Commands
5874 Most general purpose JTAG commands have been presented earlier.
5875 (@xref{JTAG Speed}, @ref{Reset Configuration}, and @ref{TAP Declaration}.)
5876 Lower level JTAG commands, as presented here,
5877 may be needed to work with targets which require special
5878 attention during operations such as reset or initialization.
5880 To use these commands you will need to understand some
5881 of the basics of JTAG, including:
5884 @item A JTAG scan chain consists of a sequence of individual TAP
5885 devices such as a CPUs.
5886 @item Control operations involve moving each TAP through the same
5887 standard state machine (in parallel)
5888 using their shared TMS and clock signals.
5889 @item Data transfer involves shifting data through the chain of
5890 instruction or data registers of each TAP, writing new register values
5891 while the reading previous ones.
5892 @item Data register sizes are a function of the instruction active in
5893 a given TAP, while instruction register sizes are fixed for each TAP.
5894 All TAPs support a BYPASS instruction with a single bit data register.
5895 @item The way OpenOCD differentiates between TAP devices is by
5896 shifting different instructions into (and out of) their instruction
5900 @section Low Level JTAG Commands
5902 These commands are used by developers who need to access
5903 JTAG instruction or data registers, possibly controlling
5904 the order of TAP state transitions.
5905 If you're not debugging OpenOCD internals, or bringing up a
5906 new JTAG adapter or a new type of TAP device (like a CPU or
5907 JTAG router), you probably won't need to use these commands.
5909 @deffn Command {drscan} tap [numbits value]+ [@option{-endstate} tap_state]
5910 Loads the data register of @var{tap} with a series of bit fields
5911 that specify the entire register.
5912 Each field is @var{numbits} bits long with
5913 a numeric @var{value} (hexadecimal encouraged).
5914 The return value holds the original value of each
5917 For example, a 38 bit number might be specified as one
5918 field of 32 bits then one of 6 bits.
5919 @emph{For portability, never pass fields which are more
5920 than 32 bits long. Many OpenOCD implementations do not
5921 support 64-bit (or larger) integer values.}
5923 All TAPs other than @var{tap} must be in BYPASS mode.
5924 The single bit in their data registers does not matter.
5926 When @var{tap_state} is specified, the JTAG state machine is left
5928 For example @sc{drpause} might be specified, so that more
5929 instructions can be issued before re-entering the @sc{run/idle} state.
5930 If the end state is not specified, the @sc{run/idle} state is entered.
5933 OpenOCD does not record information about data register lengths,
5934 so @emph{it is important that you get the bit field lengths right}.
5935 Remember that different JTAG instructions refer to different
5936 data registers, which may have different lengths.
5937 Moreover, those lengths may not be fixed;
5938 the SCAN_N instruction can change the length of
5939 the register accessed by the INTEST instruction
5940 (by connecting a different scan chain).
5944 @deffn Command {flush_count}
5945 Returns the number of times the JTAG queue has been flushed.
5946 This may be used for performance tuning.
5948 For example, flushing a queue over USB involves a
5949 minimum latency, often several milliseconds, which does
5950 not change with the amount of data which is written.
5951 You may be able to identify performance problems by finding
5952 tasks which waste bandwidth by flushing small transfers too often,
5953 instead of batching them into larger operations.
5956 @deffn Command {irscan} [tap instruction]+ [@option{-endstate} tap_state]
5957 For each @var{tap} listed, loads the instruction register
5958 with its associated numeric @var{instruction}.
5959 (The number of bits in that instruction may be displayed
5960 using the @command{scan_chain} command.)
5961 For other TAPs, a BYPASS instruction is loaded.
5963 When @var{tap_state} is specified, the JTAG state machine is left
5965 For example @sc{irpause} might be specified, so the data register
5966 can be loaded before re-entering the @sc{run/idle} state.
5967 If the end state is not specified, the @sc{run/idle} state is entered.
5970 OpenOCD currently supports only a single field for instruction
5971 register values, unlike data register values.
5972 For TAPs where the instruction register length is more than 32 bits,
5973 portable scripts currently must issue only BYPASS instructions.
5977 @deffn Command {jtag_reset} trst srst
5978 Set values of reset signals.
5979 The @var{trst} and @var{srst} parameter values may be
5980 @option{0}, indicating that reset is inactive (pulled or driven high),
5981 or @option{1}, indicating it is active (pulled or driven low).
5982 The @command{reset_config} command should already have been used
5983 to configure how the board and JTAG adapter treat these two
5984 signals, and to say if either signal is even present.
5985 @xref{Reset Configuration}.
5988 @deffn Command {runtest} @var{num_cycles}
5989 Move to the @sc{run/idle} state, and execute at least
5990 @var{num_cycles} of the JTAG clock (TCK).
5991 Instructions often need some time
5992 to execute before they take effect.
5995 @c tms_sequence (short|long)
5996 @c ... temporary, debug-only, probably gone before 0.2 ships
5998 @deffn Command {verify_ircapture} (@option{enable}|@option{disable})
5999 Verify values captured during @sc{ircapture} and returned
6000 during IR scans. Default is enabled, but this can be
6001 overridden by @command{verify_jtag}.
6004 @deffn Command {verify_jtag} (@option{enable}|@option{disable})
6005 Enables verification of DR and IR scans, to help detect
6006 programming errors. For IR scans, @command{verify_ircapture}
6007 must also be enabled.
6011 @section TAP state names
6012 @cindex TAP state names
6014 The @var{tap_state} names used by OpenOCD in the @command{drscan},
6015 and @command{irscan} commands are:
6018 @item @b{RESET} ... should act as if TRST were active
6019 @item @b{RUN/IDLE} ... don't assume this always means IDLE
6022 @item @b{DRSHIFT} ... TDI/TDO shifting through the data register
6024 @item @b{DRPAUSE} ... data register ready for update or more shifting
6029 @item @b{IRSHIFT} ... TDI/TDO shifting through the instruction register
6031 @item @b{IRPAUSE} ... instruction register ready for update or more shifting
6036 Note that only six of those states are fully ``stable'' in the
6037 face of TMS fixed (low except for @sc{reset})
6038 and a free-running JTAG clock. For all the
6039 others, the next TCK transition changes to a new state.
6042 @item From @sc{drshift} and @sc{irshift}, clock transitions will
6043 produce side effects by changing register contents. The values
6044 to be latched in upcoming @sc{drupdate} or @sc{irupdate} states
6045 may not be as expected.
6046 @item @sc{run/idle}, @sc{drpause}, and @sc{irpause} are reasonable
6047 choices after @command{drscan} or @command{irscan} commands,
6048 since they are free of JTAG side effects.
6049 However, @sc{run/idle} may have side effects that appear at other
6050 levels, such as advancing the ARM9E-S instruction pipeline.
6051 Consult the documentation for the TAP(s) you are working with.
6054 @node Boundary Scan Commands
6055 @chapter Boundary Scan Commands
6057 One of the original purposes of JTAG was to support
6058 boundary scan based hardware testing.
6059 Although its primary focus is to support On-Chip Debugging,
6060 OpenOCD also includes some boundary scan commands.
6062 @section SVF: Serial Vector Format
6063 @cindex Serial Vector Format
6066 The Serial Vector Format, better known as @dfn{SVF}, is a
6067 way to represent JTAG test patterns in text files.
6068 OpenOCD supports running such test files.
6070 @deffn Command {svf} filename [@option{quiet}]
6071 This issues a JTAG reset (Test-Logic-Reset) and then
6072 runs the SVF script from @file{filename}.
6073 Unless the @option{quiet} option is specified,
6074 each command is logged before it is executed.
6077 @section XSVF: Xilinx Serial Vector Format
6078 @cindex Xilinx Serial Vector Format
6081 The Xilinx Serial Vector Format, better known as @dfn{XSVF}, is a
6082 binary representation of SVF which is optimized for use with
6084 OpenOCD supports running such test files.
6086 @quotation Important
6087 Not all XSVF commands are supported.
6090 @deffn Command {xsvf} (tapname|@option{plain}) filename [@option{virt2}] [@option{quiet}]
6091 This issues a JTAG reset (Test-Logic-Reset) and then
6092 runs the XSVF script from @file{filename}.
6093 When a @var{tapname} is specified, the commands are directed at
6095 When @option{virt2} is specified, the @sc{xruntest} command counts
6096 are interpreted as TCK cycles instead of microseconds.
6097 Unless the @option{quiet} option is specified,
6098 messages are logged for comments and some retries.
6104 If OpenOCD runs on an embedded host(as ZY1000 does), then TFTP can
6105 be used to access files on PCs (either the developer's PC or some other PC).
6107 The way this works on the ZY1000 is to prefix a filename by
6108 "/tftp/ip/" and append the TFTP path on the TFTP
6109 server (tftpd). For example,
6112 load_image /tftp/10.0.0.96/c:\temp\abc.elf
6115 will load c:\temp\abc.elf from the developer pc (10.0.0.96) into memory as
6116 if the file was hosted on the embedded host.
6118 In order to achieve decent performance, you must choose a TFTP server
6119 that supports a packet size bigger than the default packet size (512 bytes). There
6120 are numerous TFTP servers out there (free and commercial) and you will have to do
6121 a bit of googling to find something that fits your requirements.
6123 @node GDB and OpenOCD
6124 @chapter GDB and OpenOCD
6126 OpenOCD complies with the remote gdbserver protocol, and as such can be used
6127 to debug remote targets.
6129 @anchor{Connecting to GDB}
6130 @section Connecting to GDB
6131 @cindex Connecting to GDB
6132 Use GDB 6.7 or newer with OpenOCD if you run into trouble. For
6133 instance GDB 6.3 has a known bug that produces bogus memory access
6134 errors, which has since been fixed: look up 1836 in
6135 @url{http://sourceware.org/cgi-bin/gnatsweb.pl?database=gdb}
6137 OpenOCD can communicate with GDB in two ways:
6141 A socket (TCP/IP) connection is typically started as follows:
6143 target remote localhost:3333
6145 This would cause GDB to connect to the gdbserver on the local pc using port 3333.
6147 A pipe connection is typically started as follows:
6149 target remote | openocd --pipe
6151 This would cause GDB to run OpenOCD and communicate using pipes (stdin/stdout).
6152 Using this method has the advantage of GDB starting/stopping OpenOCD for the debug
6156 To list the available OpenOCD commands type @command{monitor help} on the
6159 OpenOCD supports the gdb @option{qSupported} packet, this enables information
6160 to be sent by the GDB remote server (i.e. OpenOCD) to GDB. Typical information includes
6161 packet size and the device's memory map.
6163 Previous versions of OpenOCD required the following GDB options to increase
6164 the packet size and speed up GDB communication:
6166 set remote memory-write-packet-size 1024
6167 set remote memory-write-packet-size fixed
6168 set remote memory-read-packet-size 1024
6169 set remote memory-read-packet-size fixed
6171 This is now handled in the @option{qSupported} PacketSize and should not be required.
6173 @section Programming using GDB
6174 @cindex Programming using GDB
6176 By default the target memory map is sent to GDB. This can be disabled by
6177 the following OpenOCD configuration option:
6179 gdb_memory_map disable
6181 For this to function correctly a valid flash configuration must also be set
6182 in OpenOCD. For faster performance you should also configure a valid
6185 Informing GDB of the memory map of the target will enable GDB to protect any
6186 flash areas of the target and use hardware breakpoints by default. This means
6187 that the OpenOCD option @command{gdb_breakpoint_override} is not required when
6188 using a memory map. @xref{gdb_breakpoint_override}.
6190 To view the configured memory map in GDB, use the GDB command @option{info mem}
6191 All other unassigned addresses within GDB are treated as RAM.
6193 GDB 6.8 and higher set any memory area not in the memory map as inaccessible.
6194 This can be changed to the old behaviour by using the following GDB command
6196 set mem inaccessible-by-default off
6199 If @command{gdb_flash_program enable} is also used, GDB will be able to
6200 program any flash memory using the vFlash interface.
6202 GDB will look at the target memory map when a load command is given, if any
6203 areas to be programmed lie within the target flash area the vFlash packets
6206 If the target needs configuring before GDB programming, an event
6207 script can be executed:
6209 $_TARGETNAME configure -event EVENTNAME BODY
6212 To verify any flash programming the GDB command @option{compare-sections}
6215 @node Tcl Scripting API
6216 @chapter Tcl Scripting API
6217 @cindex Tcl Scripting API
6221 The commands are stateless. E.g. the telnet command line has a concept
6222 of currently active target, the Tcl API proc's take this sort of state
6223 information as an argument to each proc.
6225 There are three main types of return values: single value, name value
6226 pair list and lists.
6228 Name value pair. The proc 'foo' below returns a name/value pair
6234 > set foo(you) Oyvind
6235 > set foo(mouse) Micky
6236 > set foo(duck) Donald
6244 me Duane you Oyvind mouse Micky duck Donald
6246 Thus, to get the names of the associative array is easy:
6248 foreach { name value } [set foo] {
6249 puts "Name: $name, Value: $value"
6253 Lists returned must be relatively small. Otherwise a range
6254 should be passed in to the proc in question.
6256 @section Internal low-level Commands
6258 By low-level, the intent is a human would not directly use these commands.
6260 Low-level commands are (should be) prefixed with "ocd_", e.g.
6261 @command{ocd_flash_banks}
6262 is the low level API upon which @command{flash banks} is implemented.
6265 @item @b{ocd_mem2array} <@var{varname}> <@var{width}> <@var{addr}> <@var{nelems}>
6267 Read memory and return as a Tcl array for script processing
6268 @item @b{ocd_array2mem} <@var{varname}> <@var{width}> <@var{addr}> <@var{nelems}>
6270 Convert a Tcl array to memory locations and write the values
6271 @item @b{ocd_flash_banks} <@var{driver}> <@var{base}> <@var{size}> <@var{chip_width}> <@var{bus_width}> <@var{target}> [@option{driver options} ...]
6273 Return information about the flash banks
6276 OpenOCD commands can consist of two words, e.g. "flash banks". The
6277 @file{startup.tcl} "unknown" proc will translate this into a Tcl proc
6278 called "flash_banks".
6280 @section OpenOCD specific Global Variables
6284 Real Tcl has ::tcl_platform(), and platform::identify, and many other
6285 variables. JimTCL, as implemented in OpenOCD creates $HostOS which
6286 holds one of the following values:
6289 @item @b{winxx} Built using Microsoft Visual Studio
6290 @item @b{linux} Linux is the underlying operating sytem
6291 @item @b{darwin} Darwin (mac-os) is the underlying operating sytem.
6292 @item @b{cygwin} Running under Cygwin
6293 @item @b{mingw32} Running under MingW32
6294 @item @b{other} Unknown, none of the above.
6297 Note: 'winxx' was choosen because today (March-2009) no distinction is made between Win32 and Win64.
6300 We should add support for a variable like Tcl variable
6301 @code{tcl_platform(platform)}, it should be called
6302 @code{jim_platform} (because it
6303 is jim, not real tcl).
6307 @chapter Deprecated/Removed Commands
6308 @cindex Deprecated/Removed Commands
6309 Certain OpenOCD commands have been deprecated or
6310 removed during the various revisions.
6312 Upgrade your scripts as soon as possible.
6313 These descriptions for old commands may be removed
6314 a year after the command itself was removed.
6315 This means that in January 2010 this chapter may
6316 become much shorter.
6319 @item @b{arm7_9 fast_writes}
6320 @cindex arm7_9 fast_writes
6321 @*Use @command{arm7_9 fast_memory_access} instead.
6322 @xref{arm7_9 fast_memory_access}.
6325 @*An buggy old command that would not really work since background polling would wipe out the global endstate
6326 @item @b{arm7_9 force_hw_bkpts}
6327 @*Use @command{gdb_breakpoint_override} instead. Note that GDB will use hardware breakpoints
6328 for flash if the GDB memory map has been set up(default when flash is declared in
6329 target configuration). @xref{gdb_breakpoint_override}.
6330 @item @b{arm7_9 sw_bkpts}
6331 @*On by default. @xref{gdb_breakpoint_override}.
6332 @item @b{daemon_startup}
6333 @*this config option has been removed, simply adding @option{init} and @option{reset halt} to
6334 the end of your config script will give the same behaviour as using @option{daemon_startup reset}
6335 and @option{target cortex_m3 little reset_halt 0}.
6336 @item @b{dump_binary}
6337 @*use @option{dump_image} command with same args. @xref{dump_image}.
6338 @item @b{flash erase}
6339 @*use @option{flash erase_sector} command with same args. @xref{flash erase_sector}.
6340 @item @b{flash write}
6341 @*use @option{flash write_bank} command with same args. @xref{flash write_bank}.
6342 @item @b{flash write_binary}
6343 @*use @option{flash write_bank} command with same args. @xref{flash write_bank}.
6344 @item @b{flash auto_erase}
6345 @*use @option{flash write_image} command passing @option{erase} as the first parameter. @xref{flash write_image}.
6347 @item @b{jtag_device}
6348 @*use the @command{jtag newtap} command, converting from positional syntax
6349 to named prefixes, and naming the TAP.
6351 Note that if you try to use the old command, a message will tell you the
6352 right new command to use; and that the fourth parameter in the old syntax
6353 was never actually used.
6355 OLD: jtag_device 8 0x01 0xe3 0xfe
6356 NEW: jtag newtap CHIPNAME TAPNAME \
6357 -irlen 8 -ircapture 0x01 -irmask 0xe3
6360 @item @b{jtag_speed} value
6361 @*@xref{JTAG Speed}.
6362 Usually, a value of zero means maximum
6363 speed. The actual effect of this option depends on the JTAG interface used.
6365 @item wiggler: maximum speed / @var{number}
6366 @item ft2232: 6MHz / (@var{number}+1)
6367 @item amt jtagaccel: 8 / 2**@var{number}
6368 @item jlink: maximum speed in kHz (0-12000), 0 will use RTCK
6369 @item rlink: 24MHz / @var{number}, but only for certain values of @var{number}
6370 @comment end speed list.
6373 @item @b{load_binary}
6374 @*use @option{load_image} command with same args. @xref{load_image}.
6375 @item @b{run_and_halt_time}
6376 @*This command has been removed for simpler reset behaviour, it can be simulated with the
6383 @item @b{target} <@var{type}> <@var{endian}> <@var{jtag-position}>
6384 @*use the create subcommand of @option{target}.
6385 @item @b{target_script} <@var{target#}> <@var{eventname}> <@var{scriptname}>
6386 @*use <@var{target_name}> configure -event <@var{eventname}> "script <@var{scriptname}>"
6387 @item @b{working_area}
6388 @*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.
6396 @item @b{RTCK, also known as: Adaptive Clocking - What is it?}
6398 @cindex adaptive clocking
6401 In digital circuit design it is often refered to as ``clock
6402 synchronisation'' the JTAG interface uses one clock (TCK or TCLK)
6403 operating at some speed, your target is operating at another. The two
6404 clocks are not synchronised, they are ``asynchronous''
6406 In order for the two to work together they must be synchronised. Otherwise
6407 the two systems will get out of sync with each other and nothing will
6408 work. There are 2 basic options:
6411 Use a special circuit.
6413 One clock must be some multiple slower than the other.
6416 @b{Does this really matter?} For some chips and some situations, this
6417 is a non-issue (i.e.: A 500MHz ARM926) but for others - for example some
6418 Atmel SAM7 and SAM9 chips start operation from reset at 32kHz -
6419 program/enable the oscillators and eventually the main clock. It is in
6420 those critical times you must slow the JTAG clock to sometimes 1 to
6423 Imagine debugging a 500MHz ARM926 hand held battery powered device
6424 that ``deep sleeps'' at 32kHz between every keystroke. It can be
6427 @b{Solution #1 - A special circuit}
6429 In order to make use of this, your JTAG dongle must support the RTCK
6430 feature. Not all dongles support this - keep reading!
6432 The RTCK signal often found in some ARM chips is used to help with
6433 this problem. ARM has a good description of the problem described at
6434 this link: @url{http://www.arm.com/support/faqdev/4170.html} [checked
6435 28/nov/2008]. Link title: ``How does the JTAG synchronisation logic
6436 work? / how does adaptive clocking work?''.
6438 The nice thing about adaptive clocking is that ``battery powered hand
6439 held device example'' - the adaptiveness works perfectly all the
6440 time. One can set a break point or halt the system in the deep power
6441 down code, slow step out until the system speeds up.
6443 Note that adaptive clocking may also need to work at the board level,
6444 when a board-level scan chain has multiple chips.
6445 Parallel clock voting schemes are good way to implement this,
6446 both within and between chips, and can easily be implemented
6448 It's not difficult to have logic fan a module's input TCK signal out
6449 to each TAP in the scan chain, and then wait until each TAP's RTCK comes
6450 back with the right polarity before changing the output RTCK signal.
6451 Texas Instruments makes some clock voting logic available
6452 for free (with no support) in VHDL form; see
6453 @url{http://tiexpressdsp.com/index.php/Adaptive_Clocking}
6455 @b{Solution #2 - Always works - but may be slower}
6457 Often this is a perfectly acceptable solution.
6459 In most simple terms: Often the JTAG clock must be 1/10 to 1/12 of
6460 the target clock speed. But what that ``magic division'' is varies
6461 depending on the chips on your board.
6462 @b{ARM rule of thumb} Most ARM based systems require an 6:1 division;
6463 ARM11 cores use an 8:1 division.
6464 @b{Xilinx rule of thumb} is 1/12 the clock speed.
6466 Note: Many FTDI2232C based JTAG dongles are limited to 6MHz.
6468 You can still debug the 'low power' situations - you just need to
6469 manually adjust the clock speed at every step. While painful and
6470 tedious, it is not always practical.
6472 It is however easy to ``code your way around it'' - i.e.: Cheat a little,
6473 have a special debug mode in your application that does a ``high power
6474 sleep''. If you are careful - 98% of your problems can be debugged
6477 Note that on ARM you may need to avoid using the @emph{wait for interrupt}
6478 operation in your idle loops even if you don't otherwise change the CPU
6480 That operation gates the CPU clock, and thus the JTAG clock; which
6481 prevents JTAG access. One consequence is not being able to @command{halt}
6482 cores which are executing that @emph{wait for interrupt} operation.
6484 To set the JTAG frequency use the command:
6492 @item @b{Win32 Pathnames} Why don't backslashes work in Windows paths?
6494 OpenOCD uses Tcl and a backslash is an escape char. Use @{ and @}
6495 around Windows filenames.
6508 @item @b{Missing: cygwin1.dll} OpenOCD complains about a missing cygwin1.dll.
6510 Make sure you have Cygwin installed, or at least a version of OpenOCD that
6511 claims to come with all the necessary DLLs. When using Cygwin, try launching
6512 OpenOCD from the Cygwin shell.
6514 @item @b{Breakpoint Issue} I'm trying to set a breakpoint using GDB (or a frontend like Insight or
6515 Eclipse), but OpenOCD complains that "Info: arm7_9_common.c:213
6516 arm7_9_add_breakpoint(): sw breakpoint requested, but software breakpoints not enabled".
6518 GDB issues software breakpoints when a normal breakpoint is requested, or to implement
6519 source-line single-stepping. On ARMv4T systems, like ARM7TDMI, ARM720T or ARM920T,
6520 software breakpoints consume one of the two available hardware breakpoints.
6522 @item @b{LPC2000 Flash} When erasing or writing LPC2000 on-chip flash, the operation fails at random.
6524 Make sure the core frequency specified in the @option{flash lpc2000} line matches the
6525 clock at the time you're programming the flash. If you've specified the crystal's
6526 frequency, make sure the PLL is disabled. If you've specified the full core speed
6527 (e.g. 60MHz), make sure the PLL is enabled.
6529 @item @b{Amontec Chameleon} When debugging using an Amontec Chameleon in its JTAG Accelerator configuration,
6530 I keep getting "Error: amt_jtagaccel.c:184 amt_wait_scan_busy(): amt_jtagaccel timed
6531 out while waiting for end of scan, rtck was disabled".
6533 Make sure your PC's parallel port operates in EPP mode. You might have to try several
6534 settings in your PC BIOS (ECP, EPP, and different versions of those).
6536 @item @b{Data Aborts} When debugging with OpenOCD and GDB (plain GDB, Insight, or Eclipse),
6537 I get lots of "Error: arm7_9_common.c:1771 arm7_9_read_memory():
6538 memory read caused data abort".
6540 The errors are non-fatal, and are the result of GDB trying to trace stack frames
6541 beyond the last valid frame. It might be possible to prevent this by setting up
6542 a proper "initial" stack frame, if you happen to know what exactly has to
6543 be done, feel free to add this here.
6545 @b{Simple:} In your startup code - push 8 registers of zeros onto the
6546 stack before calling main(). What GDB is doing is ``climbing'' the run
6547 time stack by reading various values on the stack using the standard
6548 call frame for the target. GDB keeps going - until one of 2 things
6549 happen @b{#1} an invalid frame is found, or @b{#2} some huge number of
6550 stackframes have been processed. By pushing zeros on the stack, GDB
6553 @b{Debugging Interrupt Service Routines} - In your ISR before you call
6554 your C code, do the same - artifically push some zeros onto the stack,
6555 remember to pop them off when the ISR is done.
6557 @b{Also note:} If you have a multi-threaded operating system, they
6558 often do not @b{in the intrest of saving memory} waste these few
6562 @item @b{JTAG Reset Config} I get the following message in the OpenOCD console (or log file):
6563 "Warning: arm7_9_common.c:679 arm7_9_assert_reset(): srst resets test logic, too".
6565 This warning doesn't indicate any serious problem, as long as you don't want to
6566 debug your core right out of reset. Your .cfg file specified @option{jtag_reset
6567 trst_and_srst srst_pulls_trst} to tell OpenOCD that either your board,
6568 your debugger or your target uC (e.g. LPC2000) can't assert the two reset signals
6569 independently. With this setup, it's not possible to halt the core right out of
6570 reset, everything else should work fine.
6572 @item @b{USB Power} When using OpenOCD in conjunction with Amontec JTAGkey and the Yagarto
6573 toolchain (Eclipse, arm-elf-gcc, arm-elf-gdb), the debugging seems to be
6574 unstable. When single-stepping over large blocks of code, GDB and OpenOCD
6575 quit with an error message. Is there a stability issue with OpenOCD?
6577 No, this is not a stability issue concerning OpenOCD. Most users have solved
6578 this issue by simply using a self-powered USB hub, which they connect their
6579 Amontec JTAGkey to. Apparently, some computers do not provide a USB power
6580 supply stable enough for the Amontec JTAGkey to be operated.
6582 @b{Laptops running on battery have this problem too...}
6584 @item @b{USB Power} When using the Amontec JTAGkey, sometimes OpenOCD crashes with the
6585 following error messages: "Error: ft2232.c:201 ft2232_read(): FT_Read returned:
6586 4" and "Error: ft2232.c:365 ft2232_send_and_recv(): couldn't read from FT2232".
6587 What does that mean and what might be the reason for this?
6589 First of all, the reason might be the USB power supply. Try using a self-powered
6590 hub instead of a direct connection to your computer. Secondly, the error code 4
6591 corresponds to an FT_IO_ERROR, which means that the driver for the FTDI USB
6592 chip ran into some sort of error - this points us to a USB problem.
6594 @item @b{GDB Disconnects} When using the Amontec JTAGkey, sometimes OpenOCD crashes with the following
6595 error message: "Error: gdb_server.c:101 gdb_get_char(): read: 10054".
6596 What does that mean and what might be the reason for this?
6598 Error code 10054 corresponds to WSAECONNRESET, which means that the debugger (GDB)
6599 has closed the connection to OpenOCD. This might be a GDB issue.
6601 @item @b{LPC2000 Flash} In the configuration file in the section where flash device configurations
6602 are described, there is a parameter for specifying the clock frequency
6603 for LPC2000 internal flash devices (e.g. @option{flash bank lpc2000
6604 0x0 0x40000 0 0 0 lpc2000_v1 14746 calc_checksum}), which must be
6605 specified in kilohertz. However, I do have a quartz crystal of a
6606 frequency that contains fractions of kilohertz (e.g. 14,745,600 Hz,
6607 i.e. 14,745.600 kHz). Is it possible to specify real numbers for the
6610 No. The clock frequency specified here must be given as an integral number.
6611 However, this clock frequency is used by the In-Application-Programming (IAP)
6612 routines of the LPC2000 family only, which seems to be very tolerant concerning
6613 the given clock frequency, so a slight difference between the specified clock
6614 frequency and the actual clock frequency will not cause any trouble.
6616 @item @b{Command Order} Do I have to keep a specific order for the commands in the configuration file?
6618 Well, yes and no. Commands can be given in arbitrary order, yet the
6619 devices listed for the JTAG scan chain must be given in the right
6620 order (jtag newdevice), with the device closest to the TDO-Pin being
6621 listed first. In general, whenever objects of the same type exist
6622 which require an index number, then these objects must be given in the
6623 right order (jtag newtap, targets and flash banks - a target
6624 references a jtag newtap and a flash bank references a target).
6626 You can use the ``scan_chain'' command to verify and display the tap order.
6628 Also, some commands can't execute until after @command{init} has been
6629 processed. Such commands include @command{nand probe} and everything
6630 else that needs to write to controller registers, perhaps for setting
6631 up DRAM and loading it with code.
6633 @anchor{FAQ TAP Order}
6634 @item @b{JTAG TAP Order} Do I have to declare the TAPS in some
6637 Yes; whenever you have more than one, you must declare them in
6638 the same order used by the hardware.
6640 Many newer devices have multiple JTAG TAPs. For example: ST
6641 Microsystems STM32 chips have two TAPs, a ``boundary scan TAP'' and
6642 ``Cortex-M3'' TAP. Example: The STM32 reference manual, Document ID:
6643 RM0008, Section 26.5, Figure 259, page 651/681, the ``TDI'' pin is
6644 connected to the boundary scan TAP, which then connects to the
6645 Cortex-M3 TAP, which then connects to the TDO pin.
6647 Thus, the proper order for the STM32 chip is: (1) The Cortex-M3, then
6648 (2) The boundary scan TAP. If your board includes an additional JTAG
6649 chip in the scan chain (for example a Xilinx CPLD or FPGA) you could
6650 place it before or after the STM32 chip in the chain. For example:
6653 @item OpenOCD_TDI(output) -> STM32 TDI Pin (BS Input)
6654 @item STM32 BS TDO (output) -> STM32 Cortex-M3 TDI (input)
6655 @item STM32 Cortex-M3 TDO (output) -> SM32 TDO Pin
6656 @item STM32 TDO Pin (output) -> Xilinx TDI Pin (input)
6657 @item Xilinx TDO Pin -> OpenOCD TDO (input)
6660 The ``jtag device'' commands would thus be in the order shown below. Note:
6663 @item jtag newtap Xilinx tap -irlen ...
6664 @item jtag newtap stm32 cpu -irlen ...
6665 @item jtag newtap stm32 bs -irlen ...
6666 @item # Create the debug target and say where it is
6667 @item target create stm32.cpu -chain-position stm32.cpu ...
6671 @item @b{SYSCOMP} Sometimes my debugging session terminates with an error. When I look into the
6672 log file, I can see these error messages: Error: arm7_9_common.c:561
6673 arm7_9_execute_sys_speed(): timeout waiting for SYSCOMP
6679 @node Tcl Crash Course
6680 @chapter Tcl Crash Course
6683 Not everyone knows Tcl - this is not intended to be a replacement for
6684 learning Tcl, the intent of this chapter is to give you some idea of
6685 how the Tcl scripts work.
6687 This chapter is written with two audiences in mind. (1) OpenOCD users
6688 who need to understand a bit more of how JIM-Tcl works so they can do
6689 something useful, and (2) those that want to add a new command to
6692 @section Tcl Rule #1
6693 There is a famous joke, it goes like this:
6695 @item Rule #1: The wife is always correct
6696 @item Rule #2: If you think otherwise, See Rule #1
6699 The Tcl equal is this:
6702 @item Rule #1: Everything is a string
6703 @item Rule #2: If you think otherwise, See Rule #1
6706 As in the famous joke, the consequences of Rule #1 are profound. Once
6707 you understand Rule #1, you will understand Tcl.
6709 @section Tcl Rule #1b
6710 There is a second pair of rules.
6712 @item Rule #1: Control flow does not exist. Only commands
6713 @* For example: the classic FOR loop or IF statement is not a control
6714 flow item, they are commands, there is no such thing as control flow
6716 @item Rule #2: If you think otherwise, See Rule #1
6717 @* Actually what happens is this: There are commands that by
6718 convention, act like control flow key words in other languages. One of
6719 those commands is the word ``for'', another command is ``if''.
6722 @section Per Rule #1 - All Results are strings
6723 Every Tcl command results in a string. The word ``result'' is used
6724 deliberatly. No result is just an empty string. Remember: @i{Rule #1 -
6725 Everything is a string}
6727 @section Tcl Quoting Operators
6728 In life of a Tcl script, there are two important periods of time, the
6729 difference is subtle.
6732 @item Evaluation Time
6735 The two key items here are how ``quoted things'' work in Tcl. Tcl has
6736 three primary quoting constructs, the [square-brackets] the
6737 @{curly-braces@} and ``double-quotes''
6739 By now you should know $VARIABLES always start with a $DOLLAR
6740 sign. BTW: To set a variable, you actually use the command ``set'', as
6741 in ``set VARNAME VALUE'' much like the ancient BASIC langauge ``let x
6742 = 1'' statement, but without the equal sign.
6745 @item @b{[square-brackets]}
6746 @* @b{[square-brackets]} are command substitutions. It operates much
6747 like Unix Shell `back-ticks`. The result of a [square-bracket]
6748 operation is exactly 1 string. @i{Remember Rule #1 - Everything is a
6749 string}. These two statements are roughly identical:
6753 echo "The Date is: $X"
6756 puts "The Date is: $X"
6758 @item @b{``double-quoted-things''}
6759 @* @b{``double-quoted-things''} are just simply quoted
6760 text. $VARIABLES and [square-brackets] are expanded in place - the
6761 result however is exactly 1 string. @i{Remember Rule #1 - Everything
6765 puts "It is now \"[date]\", $x is in 1 hour"
6767 @item @b{@{Curly-Braces@}}
6768 @*@b{@{Curly-Braces@}} are magic: $VARIABLES and [square-brackets] are
6769 parsed, but are NOT expanded or executed. @{Curly-Braces@} are like
6770 'single-quote' operators in BASH shell scripts, with the added
6771 feature: @{curly-braces@} can be nested, single quotes can not. @{@{@{this is
6772 nested 3 times@}@}@} NOTE: [date] is a bad example;
6773 at this writing, Jim/OpenOCD does not have a date command.
6776 @section Consequences of Rule 1/2/3/4
6778 The consequences of Rule 1 are profound.
6780 @subsection Tokenisation & Execution.
6782 Of course, whitespace, blank lines and #comment lines are handled in
6785 As a script is parsed, each (multi) line in the script file is
6786 tokenised and according to the quoting rules. After tokenisation, that
6787 line is immedatly executed.
6789 Multi line statements end with one or more ``still-open''
6790 @{curly-braces@} which - eventually - closes a few lines later.
6792 @subsection Command Execution
6794 Remember earlier: There are no ``control flow''
6795 statements in Tcl. Instead there are COMMANDS that simply act like
6796 control flow operators.
6798 Commands are executed like this:
6801 @item Parse the next line into (argc) and (argv[]).
6802 @item Look up (argv[0]) in a table and call its function.
6803 @item Repeat until End Of File.
6806 It sort of works like this:
6809 ReadAndParse( &argc, &argv );
6811 cmdPtr = LookupCommand( argv[0] );
6813 (*cmdPtr->Execute)( argc, argv );
6817 When the command ``proc'' is parsed (which creates a procedure
6818 function) it gets 3 parameters on the command line. @b{1} the name of
6819 the proc (function), @b{2} the list of parameters, and @b{3} the body
6820 of the function. Not the choice of words: LIST and BODY. The PROC
6821 command stores these items in a table somewhere so it can be found by
6824 @subsection The FOR command
6826 The most interesting command to look at is the FOR command. In Tcl,
6827 the FOR command is normally implemented in C. Remember, FOR is a
6828 command just like any other command.
6830 When the ascii text containing the FOR command is parsed, the parser
6831 produces 5 parameter strings, @i{(If in doubt: Refer to Rule #1)} they
6835 @item The ascii text 'for'
6836 @item The start text
6837 @item The test expression
6842 Sort of reminds you of ``main( int argc, char **argv )'' does it not?
6843 Remember @i{Rule #1 - Everything is a string.} The key point is this:
6844 Often many of those parameters are in @{curly-braces@} - thus the
6845 variables inside are not expanded or replaced until later.
6847 Remember that every Tcl command looks like the classic ``main( argc,
6848 argv )'' function in C. In JimTCL - they actually look like this:
6852 MyCommand( Jim_Interp *interp,
6854 Jim_Obj * const *argvs );
6857 Real Tcl is nearly identical. Although the newer versions have
6858 introduced a byte-code parser and intepreter, but at the core, it
6859 still operates in the same basic way.
6861 @subsection FOR command implementation
6863 To understand Tcl it is perhaps most helpful to see the FOR
6864 command. Remember, it is a COMMAND not a control flow structure.
6866 In Tcl there are two underlying C helper functions.
6868 Remember Rule #1 - You are a string.
6870 The @b{first} helper parses and executes commands found in an ascii
6871 string. Commands can be seperated by semicolons, or newlines. While
6872 parsing, variables are expanded via the quoting rules.
6874 The @b{second} helper evaluates an ascii string as a numerical
6875 expression and returns a value.
6877 Here is an example of how the @b{FOR} command could be
6878 implemented. The pseudo code below does not show error handling.
6880 void Execute_AsciiString( void *interp, const char *string );
6882 int Evaluate_AsciiExpression( void *interp, const char *string );
6885 MyForCommand( void *interp,
6890 SetResult( interp, "WRONG number of parameters");
6894 // argv[0] = the ascii string just like C
6896 // Execute the start statement.
6897 Execute_AsciiString( interp, argv[1] );
6901 i = Evaluate_AsciiExpression(interp, argv[2]);
6906 Execute_AsciiString( interp, argv[3] );
6908 // Execute the LOOP part
6909 Execute_AsciiString( interp, argv[4] );
6913 SetResult( interp, "" );
6918 Every other command IF, WHILE, FORMAT, PUTS, EXPR, everything works
6919 in the same basic way.
6921 @section OpenOCD Tcl Usage
6923 @subsection source and find commands
6924 @b{Where:} In many configuration files
6925 @* Example: @b{ source [find FILENAME] }
6926 @*Remember the parsing rules
6928 @item The FIND command is in square brackets.
6929 @* The FIND command is executed with the parameter FILENAME. It should
6930 find the full path to the named file. The RESULT is a string, which is
6931 substituted on the orginal command line.
6932 @item The command source is executed with the resulting filename.
6933 @* SOURCE reads a file and executes as a script.
6935 @subsection format command
6936 @b{Where:} Generally occurs in numerous places.
6937 @* Tcl has no command like @b{printf()}, instead it has @b{format}, which is really more like
6943 puts [format "The answer: %d" [expr $x * $y]]
6946 @item The SET command creates 2 variables, X and Y.
6947 @item The double [nested] EXPR command performs math
6948 @* The EXPR command produces numerical result as a string.
6950 @item The format command is executed, producing a single string
6951 @* Refer to Rule #1.
6952 @item The PUTS command outputs the text.
6954 @subsection Body or Inlined Text
6955 @b{Where:} Various TARGET scripts.
6958 proc someproc @{@} @{
6959 ... multiple lines of stuff ...
6961 $_TARGETNAME configure -event FOO someproc
6962 #2 Good - no variables
6963 $_TARGETNAME confgure -event foo "this ; that;"
6964 #3 Good Curly Braces
6965 $_TARGETNAME configure -event FOO @{
6968 #4 DANGER DANGER DANGER
6969 $_TARGETNAME configure -event foo "puts \"Time: [date]\""
6972 @item The $_TARGETNAME is an OpenOCD variable convention.
6973 @*@b{$_TARGETNAME} represents the last target created, the value changes
6974 each time a new target is created. Remember the parsing rules. When
6975 the ascii text is parsed, the @b{$_TARGETNAME} becomes a simple string,
6976 the name of the target which happens to be a TARGET (object)
6978 @item The 2nd parameter to the @option{-event} parameter is a TCBODY
6979 @*There are 4 examples:
6981 @item The TCLBODY is a simple string that happens to be a proc name
6982 @item The TCLBODY is several simple commands seperated by semicolons
6983 @item The TCLBODY is a multi-line @{curly-brace@} quoted string
6984 @item The TCLBODY is a string with variables that get expanded.
6987 In the end, when the target event FOO occurs the TCLBODY is
6988 evaluated. Method @b{#1} and @b{#2} are functionally identical. For
6989 Method @b{#3} and @b{#4} it is more interesting. What is the TCLBODY?
6991 Remember the parsing rules. In case #3, @{curly-braces@} mean the
6992 $VARS and [square-brackets] are expanded later, when the EVENT occurs,
6993 and the text is evaluated. In case #4, they are replaced before the
6994 ``Target Object Command'' is executed. This occurs at the same time
6995 $_TARGETNAME is replaced. In case #4 the date will never
6996 change. @{BTW: [date] is a bad example; at this writing,
6997 Jim/OpenOCD does not have a date command@}
6999 @subsection Global Variables
7000 @b{Where:} You might discover this when writing your own procs @* In
7001 simple terms: Inside a PROC, if you need to access a global variable
7002 you must say so. See also ``upvar''. Example:
7004 proc myproc @{ @} @{
7005 set y 0 #Local variable Y
7006 global x #Global variable X
7007 puts [format "X=%d, Y=%d" $x $y]
7010 @section Other Tcl Hacks
7011 @b{Dynamic variable creation}
7013 # Dynamically create a bunch of variables.
7014 for @{ set x 0 @} @{ $x < 32 @} @{ set x [expr $x + 1]@} @{
7016 set vn [format "BIT%d" $x]
7020 set $vn [expr (1 << $x)]
7023 @b{Dynamic proc/command creation}
7025 # One "X" function - 5 uart functions.
7026 foreach who @{A B C D E@}
7027 proc [format "show_uart%c" $who] @{ @} "show_UARTx $who"
7033 @node OpenOCD Concept Index
7034 @comment DO NOT use the plain word ``Index'', reason: CYGWIN filename
7035 @comment case issue with ``Index.html'' and ``index.html''
7036 @comment Occurs when creating ``--html --no-split'' output
7037 @comment This fix is based on: http://sourceware.org/ml/binutils/2006-05/msg00215.html
7038 @unnumbered OpenOCD Concept Index
7042 @node Command and Driver Index
7043 @unnumbered Command and Driver Index