You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

6743 lines
243 KiB

  1. \input texinfo @c -*-texinfo-*-
  2. @c %**start of header
  3. @setfilename openocd.info
  4. @settitle OpenOCD User's Guide
  5. @dircategory Development
  6. @direntry
  7. * OpenOCD: (openocd). OpenOCD User's Guide
  8. @end direntry
  9. @paragraphindent 0
  10. @c %**end of header
  11. @include version.texi
  12. @copying
  13. This User's Guide documents
  14. release @value{VERSION},
  15. dated @value{UPDATED},
  16. of the Open On-Chip Debugger (OpenOCD).
  17. @itemize @bullet
  18. @item Copyright @copyright{} 2008 The OpenOCD Project
  19. @item Copyright @copyright{} 2007-2008 Spencer Oliver @email{spen@@spen-soft.co.uk}
  20. @item Copyright @copyright{} 2008 Oyvind Harboe @email{oyvind.harboe@@zylin.com}
  21. @item Copyright @copyright{} 2008 Duane Ellis @email{openocd@@duaneellis.com}
  22. @item Copyright @copyright{} 2009 David Brownell
  23. @end itemize
  24. @quotation
  25. Permission is granted to copy, distribute and/or modify this document
  26. under the terms of the GNU Free Documentation License, Version 1.2 or
  27. any later version published by the Free Software Foundation; with no
  28. Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
  29. Texts. A copy of the license is included in the section entitled ``GNU
  30. Free Documentation License''.
  31. @end quotation
  32. @end copying
  33. @titlepage
  34. @titlefont{@emph{Open On-Chip Debugger:}}
  35. @sp 1
  36. @title OpenOCD User's Guide
  37. @subtitle for release @value{VERSION}
  38. @subtitle @value{UPDATED}
  39. @page
  40. @vskip 0pt plus 1filll
  41. @insertcopying
  42. @end titlepage
  43. @summarycontents
  44. @contents
  45. @ifnottex
  46. @node Top
  47. @top OpenOCD User's Guide
  48. @insertcopying
  49. @end ifnottex
  50. @menu
  51. * About:: About OpenOCD
  52. * Developers:: OpenOCD Developers
  53. * JTAG Hardware Dongles:: JTAG Hardware Dongles
  54. * About JIM-Tcl:: About JIM-Tcl
  55. * Running:: Running OpenOCD
  56. * OpenOCD Project Setup:: OpenOCD Project Setup
  57. * Config File Guidelines:: Config File Guidelines
  58. * Daemon Configuration:: Daemon Configuration
  59. * Interface - Dongle Configuration:: Interface - Dongle Configuration
  60. * Reset Configuration:: Reset Configuration
  61. * TAP Declaration:: TAP Declaration
  62. * CPU Configuration:: CPU Configuration
  63. * Flash Commands:: Flash Commands
  64. * NAND Flash Commands:: NAND Flash Commands
  65. * PLD/FPGA Commands:: PLD/FPGA Commands
  66. * General Commands:: General Commands
  67. * Architecture and Core Commands:: Architecture and Core Commands
  68. * JTAG Commands:: JTAG Commands
  69. * Boundary Scan Commands:: Boundary Scan Commands
  70. * TFTP:: TFTP
  71. * GDB and OpenOCD:: Using GDB and OpenOCD
  72. * Tcl Scripting API:: Tcl Scripting API
  73. * Upgrading:: Deprecated/Removed Commands
  74. * Target Library:: Target Library
  75. * FAQ:: Frequently Asked Questions
  76. * Tcl Crash Course:: Tcl Crash Course
  77. * License:: GNU Free Documentation License
  78. @comment DO NOT use the plain word ``Index'', reason: CYGWIN filename
  79. @comment case issue with ``Index.html'' and ``index.html''
  80. @comment Occurs when creating ``--html --no-split'' output
  81. @comment This fix is based on: http://sourceware.org/ml/binutils/2006-05/msg00215.html
  82. * OpenOCD Concept Index:: Concept Index
  83. * Command and Driver Index:: Command and Driver Index
  84. @end menu
  85. @node About
  86. @unnumbered About
  87. @cindex about
  88. OpenOCD was created by Dominic Rath as part of a diploma thesis written at the
  89. University of Applied Sciences Augsburg (@uref{http://www.fh-augsburg.de}).
  90. Since that time, the project has grown into an active open-source project,
  91. supported by a diverse community of software and hardware developers from
  92. around the world.
  93. @section What is OpenOCD?
  94. @cindex TAP
  95. @cindex JTAG
  96. The Open On-Chip Debugger (OpenOCD) aims to provide debugging,
  97. in-system programming and boundary-scan testing for embedded target
  98. devices.
  99. @b{JTAG:} OpenOCD uses a ``hardware interface dongle'' to communicate
  100. with the JTAG (IEEE 1149.1) compliant TAPs on your target board.
  101. A @dfn{TAP} is a ``Test Access Port'', a module which processes
  102. special instructions and data. TAPs are daisy-chained within and
  103. between chips and boards.
  104. @b{Dongles:} OpenOCD currently supports many types of hardware dongles: USB
  105. based, parallel port based, and other standalone boxes that run
  106. OpenOCD internally. @xref{JTAG Hardware Dongles}.
  107. @b{GDB Debug:} It allows ARM7 (ARM7TDMI and ARM720t), ARM9 (ARM920T,
  108. ARM922T, ARM926EJ--S, ARM966E--S), XScale (PXA25x, IXP42x) and
  109. Cortex-M3 (Stellaris LM3 and ST STM32) based cores to be
  110. debugged via the GDB protocol.
  111. @b{Flash Programing:} Flash writing is supported for external CFI
  112. compatible NOR flashes (Intel and AMD/Spansion command set) and several
  113. internal flashes (LPC1700, LPC2000, AT91SAM7, AT91SAM3U, STR7x, STR9x, LM3, and
  114. STM32x). Preliminary support for various NAND flash controllers
  115. (LPC3180, Orion, S3C24xx, more) controller is included.
  116. @section OpenOCD Web Site
  117. The OpenOCD web site provides the latest public news from the community:
  118. @uref{http://openocd.berlios.de/web/}
  119. @section Latest User's Guide:
  120. The user's guide you are now reading may not be the latest one
  121. available. A version for more recent code may be available.
  122. Its HTML form is published irregularly at:
  123. @uref{http://openocd.berlios.de/doc/html/index.html}
  124. PDF form is likewise published at:
  125. @uref{http://openocd.berlios.de/doc/pdf/openocd.pdf}
  126. @section OpenOCD User's Forum
  127. There is an OpenOCD forum (phpBB) hosted by SparkFun:
  128. @uref{http://forum.sparkfun.com/viewforum.php?f=18}
  129. @node Developers
  130. @chapter OpenOCD Developer Resources
  131. @cindex developers
  132. If you are interested in improving the state of OpenOCD's debugging and
  133. testing support, new contributions will be welcome. Motivated developers
  134. can produce new target, flash or interface drivers, improve the
  135. documentation, as well as more conventional bug fixes and enhancements.
  136. The resources in this chapter are available for developers wishing to explore
  137. or expand the OpenOCD source code.
  138. @section OpenOCD Subversion Repository
  139. You can download the current SVN version with an SVN client of your
  140. choice from the following repositories:
  141. @uref{svn://svn.berlios.de/openocd/trunk}
  142. or
  143. @uref{http://svn.berlios.de/svnroot/repos/openocd/trunk}
  144. Using the SVN command line client, you can use the following command to
  145. fetch the latest version (make sure there is no (non-svn) directory
  146. called "openocd" in the current directory):
  147. svn checkout svn://svn.berlios.de/openocd/trunk openocd
  148. If you prefer GIT based tools, the @command{git-svn} package works too:
  149. git svn clone -s svn://svn.berlios.de/openocd
  150. The ``README'' file contains the instructions for building the project
  151. from the repository.
  152. Developers that want to contribute patches to the OpenOCD system are
  153. @b{strongly} encouraged to base their work off of the most recent trunk
  154. revision. Patches created against older versions may require additional
  155. work from their submitter in order to be updated for newer releases.
  156. @section Doxygen Developer Manual
  157. During the development of the 0.2.0 release, the OpenOCD project began
  158. providing a Doxygen reference manual. This document contains more
  159. technical information about the software internals, development
  160. processes, and similar documentation:
  161. @uref{http://openocd.berlios.de/doc/doxygen/index.html}
  162. This document is a work-in-progress, but contributions would be welcome
  163. to fill in the gaps. All of the source files are provided in-tree,
  164. listed in the Doxyfile configuration in the top of the repository trunk.
  165. @section OpenOCD Developer Mailing List
  166. The OpenOCD Developer Mailing List provides the primary means of
  167. communication between developers:
  168. @uref{https://lists.berlios.de/mailman/listinfo/openocd-development}
  169. All drivers developers are enouraged to also subscribe to the list of
  170. SVN commits to keep pace with the ongoing changes:
  171. @uref{https://lists.berlios.de/mailman/listinfo/openocd-svn}
  172. @node JTAG Hardware Dongles
  173. @chapter JTAG Hardware Dongles
  174. @cindex dongles
  175. @cindex FTDI
  176. @cindex wiggler
  177. @cindex zy1000
  178. @cindex printer port
  179. @cindex USB Adapter
  180. @cindex RTCK
  181. Defined: @b{dongle}: A small device that plugins into a computer and serves as
  182. an adapter .... [snip]
  183. In the OpenOCD case, this generally refers to @b{a small adapater} one
  184. attaches to your computer via USB or the Parallel Printer Port. The
  185. execption being the Zylin ZY1000 which is a small box you attach via
  186. an ethernet cable. The Zylin ZY1000 has the advantage that it does not
  187. require any drivers to be installed on the developer PC. It also has
  188. a built in web interface. It supports RTCK/RCLK or adaptive clocking
  189. and has a built in relay to power cycle targets remotely.
  190. @section Choosing a Dongle
  191. There are several things you should keep in mind when choosing a dongle.
  192. @enumerate
  193. @item @b{Voltage} What voltage is your target - 1.8, 2.8, 3.3, or 5V?
  194. Does your dongle support it? You might need a level converter.
  195. @item @b{Pinout} What pinout does your target board use?
  196. Does your dongle support it? You may be able to use jumper
  197. wires, or an "octopus" connector, to convert pinouts.
  198. @item @b{Connection} Does your computer have the USB, printer, or
  199. Ethernet port needed?
  200. @item @b{RTCK} Do you require RTCK? Also known as ``adaptive clocking''
  201. @end enumerate
  202. @section Stand alone Systems
  203. @b{ZY1000} See: @url{http://www.zylin.com/zy1000.html} Technically, not a
  204. dongle, but a standalone box. The ZY1000 has the advantage that it does
  205. not require any drivers installed on the developer PC. It also has
  206. a built in web interface. It supports RTCK/RCLK or adaptive clocking
  207. and has a built in relay to power cycle targets remotely.
  208. @section USB FT2232 Based
  209. There are many USB JTAG dongles on the market, many of them are based
  210. on a chip from ``Future Technology Devices International'' (FTDI)
  211. known as the FTDI FT2232; this is a USB full speed (12 Mbps) chip.
  212. See: @url{http://www.ftdichip.com} for more information.
  213. In summer 2009, USB high speed (480 Mbps) versions of these FTDI
  214. chips are starting to become available in JTAG adapters.
  215. @itemize @bullet
  216. @item @b{usbjtag}
  217. @* Link @url{http://www.hs-augsburg.de/~hhoegl/proj/usbjtag/usbjtag.html}
  218. @item @b{jtagkey}
  219. @* See: @url{http://www.amontec.com/jtagkey.shtml}
  220. @item @b{jtagkey2}
  221. @* See: @url{http://www.amontec.com/jtagkey2.shtml}
  222. @item @b{oocdlink}
  223. @* See: @url{http://www.oocdlink.com} By Joern Kaipf
  224. @item @b{signalyzer}
  225. @* See: @url{http://www.signalyzer.com}
  226. @item @b{evb_lm3s811}
  227. @* See: @url{http://www.luminarymicro.com} - The Stellaris LM3S811 eval board has an FTD2232C chip built in.
  228. @item @b{luminary_icdi}
  229. @* See: @url{http://www.luminarymicro.com} - Luminary In-Circuit Debug Interface (ICDI) Board, included in the Stellaris LM3S9B90 and LM3S9B92 Evaluation Kits.
  230. @item @b{olimex-jtag}
  231. @* See: @url{http://www.olimex.com}
  232. @item @b{flyswatter}
  233. @* See: @url{http://www.tincantools.com}
  234. @item @b{turtelizer2}
  235. @* See:
  236. @uref{http://www.ethernut.de/en/hardware/turtelizer/index.html, Turtelizer 2}, or
  237. @url{http://www.ethernut.de}
  238. @item @b{comstick}
  239. @* Link: @url{http://www.hitex.com/index.php?id=383}
  240. @item @b{stm32stick}
  241. @* Link @url{http://www.hitex.com/stm32-stick}
  242. @item @b{axm0432_jtag}
  243. @* Axiom AXM-0432 Link @url{http://www.axman.com}
  244. @item @b{cortino}
  245. @* Link @url{http://www.hitex.com/index.php?id=cortino}
  246. @end itemize
  247. @section USB JLINK based
  248. There are several OEM versions of the Segger @b{JLINK} adapter. It is
  249. an example of a micro controller based JTAG adapter, it uses an
  250. AT91SAM764 internally.
  251. @itemize @bullet
  252. @item @b{ATMEL SAMICE} Only works with ATMEL chips!
  253. @* Link: @url{http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3892}
  254. @item @b{SEGGER JLINK}
  255. @* Link: @url{http://www.segger.com/jlink.html}
  256. @item @b{IAR J-Link}
  257. @* Link: @url{http://www.iar.com/website1/1.0.1.0/369/1/index.php}
  258. @end itemize
  259. @section USB RLINK based
  260. 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.
  261. @itemize @bullet
  262. @item @b{Raisonance RLink}
  263. @* Link: @url{http://www.raisonance.com/products/RLink.php}
  264. @item @b{STM32 Primer}
  265. @* Link: @url{http://www.stm32circle.com/resources/stm32primer.php}
  266. @item @b{STM32 Primer2}
  267. @* Link: @url{http://www.stm32circle.com/resources/stm32primer2.php}
  268. @end itemize
  269. @section USB Other
  270. @itemize @bullet
  271. @item @b{USBprog}
  272. @* Link: @url{http://www.embedded-projects.net/usbprog} - which uses an Atmel MEGA32 and a UBN9604
  273. @item @b{USB - Presto}
  274. @* Link: @url{http://tools.asix.net/prg_presto.htm}
  275. @item @b{Versaloon-Link}
  276. @* Link: @url{http://www.simonqian.com/en/Versaloon}
  277. @item @b{ARM-JTAG-EW}
  278. @* Link: @url{http://www.olimex.com/dev/arm-jtag-ew.html}
  279. @end itemize
  280. @section IBM PC Parallel Printer Port Based
  281. The two well known ``JTAG Parallel Ports'' cables are the Xilnx DLC5
  282. and the MacGraigor Wiggler. There are many clones and variations of
  283. these on the market.
  284. Note that parallel ports are becoming much less common, so if you
  285. have the choice you should probably avoid these adapters in favor
  286. of USB-based ones.
  287. @itemize @bullet
  288. @item @b{Wiggler} - There are many clones of this.
  289. @* Link: @url{http://www.macraigor.com/wiggler.htm}
  290. @item @b{DLC5} - From XILINX - There are many clones of this
  291. @* Link: Search the web for: ``XILINX DLC5'' - it is no longer
  292. produced, PDF schematics are easily found and it is easy to make.
  293. @item @b{Amontec - JTAG Accelerator}
  294. @* Link: @url{http://www.amontec.com/jtag_accelerator.shtml}
  295. @item @b{GW16402}
  296. @* Link: @url{http://www.gateworks.com/products/avila_accessories/gw16042.php}
  297. @item @b{Wiggler2}
  298. @*@uref{http://www.ccac.rwth-aachen.de/@/~michaels/@/index.php/hardware/@/armjtag,
  299. Improved parallel-port wiggler-style JTAG adapter}
  300. @item @b{Wiggler_ntrst_inverted}
  301. @* Yet another variation - See the source code, src/jtag/parport.c
  302. @item @b{old_amt_wiggler}
  303. @* Unknown - probably not on the market today
  304. @item @b{arm-jtag}
  305. @* Link: Most likely @url{http://www.olimex.com/dev/arm-jtag.html} [another wiggler clone]
  306. @item @b{chameleon}
  307. @* Link: @url{http://www.amontec.com/chameleon.shtml}
  308. @item @b{Triton}
  309. @* Unknown.
  310. @item @b{Lattice}
  311. @* ispDownload from Lattice Semiconductor
  312. @url{http://www.latticesemi.com/lit/docs/@/devtools/dlcable.pdf}
  313. @item @b{flashlink}
  314. @* From ST Microsystems;
  315. @uref{http://www.st.com/stonline/@/products/literature/um/7889.pdf,
  316. FlashLINK JTAG programing cable for PSD and uPSD}
  317. @end itemize
  318. @section Other...
  319. @itemize @bullet
  320. @item @b{ep93xx}
  321. @* An EP93xx based Linux machine using the GPIO pins directly.
  322. @item @b{at91rm9200}
  323. @* Like the EP93xx - but an ATMEL AT91RM9200 based solution using the GPIO pins on the chip.
  324. @end itemize
  325. @node About JIM-Tcl
  326. @chapter About JIM-Tcl
  327. @cindex JIM Tcl
  328. @cindex tcl
  329. OpenOCD includes a small ``Tcl Interpreter'' known as JIM-Tcl.
  330. This programming language provides a simple and extensible
  331. command interpreter.
  332. All commands presented in this Guide are extensions to JIM-Tcl.
  333. You can use them as simple commands, without needing to learn
  334. much of anything about Tcl.
  335. Alternatively, can write Tcl programs with them.
  336. You can learn more about JIM at its website, @url{http://jim.berlios.de}.
  337. @itemize @bullet
  338. @item @b{JIM vs. Tcl}
  339. @* JIM-TCL is a stripped down version of the well known Tcl language,
  340. which can be found here: @url{http://www.tcl.tk}. JIM-Tcl has far
  341. fewer features. JIM-Tcl is a single .C file and a single .H file and
  342. implements the basic Tcl command set. In contrast: Tcl 8.6 is a
  343. 4.2 MB .zip file containing 1540 files.
  344. @item @b{Missing Features}
  345. @* Our practice has been: Add/clone the real Tcl feature if/when
  346. needed. We welcome JIM Tcl improvements, not bloat.
  347. @item @b{Scripts}
  348. @* OpenOCD configuration scripts are JIM Tcl Scripts. OpenOCD's
  349. command interpreter today is a mixture of (newer)
  350. JIM-Tcl commands, and (older) the orginal command interpreter.
  351. @item @b{Commands}
  352. @* At the OpenOCD telnet command line (or via the GDB mon command) one
  353. can type a Tcl for() loop, set variables, etc.
  354. Some of the commands documented in this guide are implemented
  355. as Tcl scripts, from a @file{startup.tcl} file internal to the server.
  356. @item @b{Historical Note}
  357. @* JIM-Tcl was introduced to OpenOCD in spring 2008.
  358. @item @b{Need a crash course in Tcl?}
  359. @*@xref{Tcl Crash Course}.
  360. @end itemize
  361. @node Running
  362. @chapter Running
  363. @cindex command line options
  364. @cindex logfile
  365. @cindex directory search
  366. The @option{--help} option shows:
  367. @verbatim
  368. bash$ openocd --help
  369. --help | -h display this help
  370. --version | -v display OpenOCD version
  371. --file | -f use configuration file <name>
  372. --search | -s dir to search for config files and scripts
  373. --debug | -d set debug level <0-3>
  374. --log_output | -l redirect log output to file <name>
  375. --command | -c run <command>
  376. --pipe | -p use pipes when talking to gdb
  377. @end verbatim
  378. By default OpenOCD reads the file configuration file @file{openocd.cfg}
  379. in the current directory. To specify a different (or multiple)
  380. configuration file, you can use the ``-f'' option. For example:
  381. @example
  382. openocd -f config1.cfg -f config2.cfg -f config3.cfg
  383. @end example
  384. OpenOCD starts by processing the configuration commands provided
  385. on the command line or in @file{openocd.cfg}.
  386. @xref{Configuration Stage}.
  387. At the end of the configuration stage it verifies the JTAG scan
  388. chain defined using those commands; your configuration should
  389. ensure that this always succeeds.
  390. Normally, OpenOCD then starts running as a daemon.
  391. Alternatively, commands may be used to terminate the configuration
  392. stage early, perform work (such as updating some flash memory),
  393. and then shut down without acting as a daemon.
  394. Once OpenOCD starts running as a daemon, it waits for connections from
  395. clients (Telnet, GDB, Other) and processes the commands issued through
  396. those channels.
  397. If you are having problems, you can enable internal debug messages via
  398. the ``-d'' option.
  399. Also it is possible to interleave JIM-Tcl commands w/config scripts using the
  400. @option{-c} command line switch.
  401. To enable debug output (when reporting problems or working on OpenOCD
  402. itself), use the @option{-d} command line switch. This sets the
  403. @option{debug_level} to "3", outputting the most information,
  404. including debug messages. The default setting is "2", outputting only
  405. informational messages, warnings and errors. You can also change this
  406. setting from within a telnet or gdb session using @command{debug_level
  407. <n>} (@pxref{debug_level}).
  408. You can redirect all output from the daemon to a file using the
  409. @option{-l <logfile>} switch.
  410. Search paths for config/script files can be added to OpenOCD by using
  411. the @option{-s <search>} switch. The current directory and the OpenOCD
  412. target library is in the search path by default.
  413. For details on the @option{-p} option. @xref{Connecting to GDB}.
  414. Note! OpenOCD will launch the GDB & telnet server even if it can not
  415. establish a connection with the target. In general, it is possible for
  416. the JTAG controller to be unresponsive until the target is set up
  417. correctly via e.g. GDB monitor commands in a GDB init script.
  418. @node OpenOCD Project Setup
  419. @chapter OpenOCD Project Setup
  420. To use OpenOCD with your development projects, you need to do more than
  421. just connecting the JTAG adapter hardware (dongle) to your development board
  422. and then starting the OpenOCD server.
  423. You also need to configure that server so that it knows
  424. about that adapter and board, and helps your work.
  425. @section Hooking up the JTAG Adapter
  426. Today's most common case is a dongle with a JTAG cable on one side
  427. (such as a ribbon cable with a 10-pin or 20-pin IDC connector)
  428. and a USB cable on the other.
  429. Instead of USB, some cables use Ethernet;
  430. older ones may use a PC parallel port, or even a serial port.
  431. @enumerate
  432. @item @emph{Start with power to your target board turned off},
  433. and nothing connected to your JTAG adapter.
  434. If you're particularly paranoid, unplug power to the board.
  435. It's important to have the ground signal properly set up,
  436. unless you are using a JTAG adapter which provides
  437. galvanic isolation between the target board and the
  438. debugging host.
  439. @item @emph{Be sure it's the right kind of JTAG connector.}
  440. If your dongle has a 20-pin ARM connector, you need some kind
  441. of adapter (or octopus, see below) to hook it up to
  442. boards using 14-pin or 10-pin connectors ... or to 20-pin
  443. connectors which don't use ARM's pinout.
  444. In the same vein, make sure the voltage levels are compatible.
  445. Not all JTAG adapters have the level shifters needed to work
  446. with 1.2 Volt boards.
  447. @item @emph{Be certain the cable is properly oriented} or you might
  448. damage your board. In most cases there are only two possible
  449. ways to connect the cable.
  450. Connect the JTAG cable from your adapter to the board.
  451. Be sure it's firmly connected.
  452. In the best case, the connector is keyed to physically
  453. prevent you from inserting it wrong.
  454. This is most often done using a slot on the board's male connector
  455. housing, which must match a key on the JTAG cable's female connector.
  456. If there's no housing, then you must look carefully and
  457. make sure pin 1 on the cable hooks up to pin 1 on the board.
  458. Ribbon cables are frequently all grey except for a wire on one
  459. edge, which is red. The red wire is pin 1.
  460. Sometimes dongles provide cables where one end is an ``octopus'' of
  461. color coded single-wire connectors, instead of a connector block.
  462. These are great when converting from one JTAG pinout to another,
  463. but are tedious to set up.
  464. Use these with connector pinout diagrams to help you match up the
  465. adapter signals to the right board pins.
  466. @item @emph{Connect the adapter's other end} once the JTAG cable is connected.
  467. A USB, parallel, or serial port connector will go to the host which
  468. you are using to run OpenOCD.
  469. For Ethernet, consult the documentation and your network administrator.
  470. For USB based JTAG adapters you have an easy sanity check at this point:
  471. does the host operating system see the JTAG adapter?
  472. @item @emph{Connect the adapter's power supply, if needed.}
  473. This step is primarily for non-USB adapters,
  474. but sometimes USB adapters need extra power.
  475. @item @emph{Power up the target board.}
  476. Unless you just let the magic smoke escape,
  477. you're now ready to set up the OpenOCD server
  478. so you can use JTAG to work with that board.
  479. @end enumerate
  480. Talk with the OpenOCD server using
  481. telnet (@code{telnet localhost 4444} on many systems) or GDB.
  482. @xref{GDB and OpenOCD}.
  483. @section Project Directory
  484. There are many ways you can configure OpenOCD and start it up.
  485. A simple way to organize them all involves keeping a
  486. single directory for your work with a given board.
  487. When you start OpenOCD from that directory,
  488. it searches there first for configuration files, scripts,
  489. and for code you upload to the target board.
  490. It is also the natural place to write files,
  491. such as log files and data you download from the board.
  492. @section Configuration Basics
  493. There are two basic ways of configuring OpenOCD, and
  494. a variety of ways you can mix them.
  495. Think of the difference as just being how you start the server:
  496. @itemize
  497. @item Many @option{-f file} or @option{-c command} options on the command line
  498. @item No options, but a @dfn{user config file}
  499. in the current directory named @file{openocd.cfg}
  500. @end itemize
  501. Here is an example @file{openocd.cfg} file for a setup
  502. using a Signalyzer FT2232-based JTAG adapter to talk to
  503. a board with an Atmel AT91SAM7X256 microcontroller:
  504. @example
  505. source [find interface/signalyzer.cfg]
  506. # GDB can also flash my flash!
  507. gdb_memory_map enable
  508. gdb_flash_program enable
  509. source [find target/sam7x256.cfg]
  510. @end example
  511. Here is the command line equivalent of that configuration:
  512. @example
  513. openocd -f interface/signalyzer.cfg \
  514. -c "gdb_memory_map enable" \
  515. -c "gdb_flash_program enable" \
  516. -f target/sam7x256.cfg
  517. @end example
  518. You could wrap such long command lines in shell scripts,
  519. each supporting a different development task.
  520. One might re-flash the board with a specific firmware version.
  521. Another might set up a particular debugging or run-time environment.
  522. Here we will focus on the simpler solution: one user config
  523. file, including basic configuration plus any TCL procedures
  524. to simplify your work.
  525. @section User Config Files
  526. @cindex config file, user
  527. @cindex user config file
  528. @cindex config file, overview
  529. A user configuration file ties together all the parts of a project
  530. in one place.
  531. One of the following will match your situation best:
  532. @itemize
  533. @item Ideally almost everything comes from configuration files
  534. provided by someone else.
  535. For example, OpenOCD distributes a @file{scripts} directory
  536. (probably in @file{/usr/share/openocd/scripts} on Linux).
  537. Board and tool vendors can provide these too, as can individual
  538. user sites; the @option{-s} command line option lets you say
  539. where to find these files. (@xref{Running}.)
  540. The AT91SAM7X256 example above works this way.
  541. Three main types of non-user configuration file each have their
  542. own subdirectory in the @file{scripts} directory:
  543. @enumerate
  544. @item @b{interface} -- one for each kind of JTAG adapter/dongle
  545. @item @b{board} -- one for each different board
  546. @item @b{target} -- the chips which integrate CPUs and other JTAG TAPs
  547. @end enumerate
  548. Best case: include just two files, and they handle everything else.
  549. The first is an interface config file.
  550. The second is board-specific, and it sets up the JTAG TAPs and
  551. their GDB targets (by deferring to some @file{target.cfg} file),
  552. declares all flash memory, and leaves you nothing to do except
  553. meet your deadline:
  554. @example
  555. source [find interface/olimex-jtag-tiny.cfg]
  556. source [find board/csb337.cfg]
  557. @end example
  558. Boards with a single microcontroller often won't need more
  559. than the target config file, as in the AT91SAM7X256 example.
  560. That's because there is no external memory (flash, DDR RAM), and
  561. the board differences are encapsulated by application code.
  562. @item You can often reuse some standard config files but
  563. need to write a few new ones, probably a @file{board.cfg} file.
  564. You will be using commands described later in this User's Guide,
  565. and working with the guidelines in the next chapter.
  566. For example, there may be configuration files for your JTAG adapter
  567. and target chip, but you need a new board-specific config file
  568. giving access to your particular flash chips.
  569. Or you might need to write another target chip configuration file
  570. for a new chip built around the Cortex M3 core.
  571. @quotation Note
  572. When you write new configuration files, please submit
  573. them for inclusion in the next OpenOCD release.
  574. For example, a @file{board/newboard.cfg} file will help the
  575. next users of that board, and a @file{target/newcpu.cfg}
  576. will help support users of any board using that chip.
  577. @end quotation
  578. @item
  579. You may may need to write some C code.
  580. It may be as simple as a supporting a new ft2232 or parport
  581. based dongle; a bit more involved, like a NAND or NOR flash
  582. controller driver; or a big piece of work like supporting
  583. a new chip architecture.
  584. @end itemize
  585. Reuse the existing config files when you can.
  586. Look first in the @file{scripts/boards} area, then @file{scripts/targets}.
  587. You may find a board configuration that's a good example to follow.
  588. When you write config files, separate the reusable parts
  589. (things every user of that interface, chip, or board needs)
  590. from ones specific to your environment and debugging approach.
  591. @itemize
  592. @item
  593. For example, a @code{gdb-attach} event handler that invokes
  594. the @command{reset init} command will interfere with debugging
  595. early boot code, which performs some of the same actions
  596. that the @code{reset-init} event handler does.
  597. @item
  598. Likewise, the @command{arm9tdmi vector_catch} command (or
  599. @cindex vector_catch
  600. its siblings @command{xscale vector_catch}
  601. and @command{cortex_m3 vector_catch}) can be a timesaver
  602. during some debug sessions, but don't make everyone use that either.
  603. Keep those kinds of debugging aids in your user config file,
  604. along with messaging and tracing setup.
  605. (@xref{Software Debug Messages and Tracing}.)
  606. @item
  607. You might need to override some defaults.
  608. For example, you might need to move, shrink, or back up the target's
  609. work area if your application needs much SRAM.
  610. @item
  611. TCP/IP port configuration is another example of something which
  612. is environment-specific, and should only appear in
  613. a user config file. @xref{TCP/IP Ports}.
  614. @end itemize
  615. @section Project-Specific Utilities
  616. A few project-specific utility
  617. routines may well speed up your work.
  618. Write them, and keep them in your project's user config file.
  619. For example, if you are making a boot loader work on a
  620. board, it's nice to be able to debug the ``after it's
  621. loaded to RAM'' parts separately from the finicky early
  622. code which sets up the DDR RAM controller and clocks.
  623. A script like this one, or a more GDB-aware sibling,
  624. may help:
  625. @example
  626. proc ramboot @{ @} @{
  627. # Reset, running the target's "reset-init" scripts
  628. # to initialize clocks and the DDR RAM controller.
  629. # Leave the CPU halted.
  630. reset init
  631. # Load CONFIG_SKIP_LOWLEVEL_INIT version into DDR RAM.
  632. load_image u-boot.bin 0x20000000
  633. # Start running.
  634. resume 0x20000000
  635. @}
  636. @end example
  637. Then once that code is working you will need to make it
  638. boot from NOR flash; a different utility would help.
  639. Alternatively, some developers write to flash using GDB.
  640. (You might use a similar script if you're working with a flash
  641. based microcontroller application instead of a boot loader.)
  642. @example
  643. proc newboot @{ @} @{
  644. # Reset, leaving the CPU halted. The "reset-init" event
  645. # proc gives faster access to the CPU and to NOR flash;
  646. # "reset halt" would be slower.
  647. reset init
  648. # Write standard version of U-Boot into the first two
  649. # sectors of NOR flash ... the standard version should
  650. # do the same lowlevel init as "reset-init".
  651. flash protect 0 0 1 off
  652. flash erase_sector 0 0 1
  653. flash write_bank 0 u-boot.bin 0x0
  654. flash protect 0 0 1 on
  655. # Reboot from scratch using that new boot loader.
  656. reset run
  657. @}
  658. @end example
  659. You may need more complicated utility procedures when booting
  660. from NAND.
  661. That often involves an extra bootloader stage,
  662. running from on-chip SRAM to perform DDR RAM setup so it can load
  663. the main bootloader code (which won't fit into that SRAM).
  664. Other helper scripts might be used to write production system images,
  665. involving considerably more than just a three stage bootloader.
  666. @node Config File Guidelines
  667. @chapter Config File Guidelines
  668. This chapter is aimed at any user who needs to write a config file,
  669. including developers and integrators of OpenOCD and any user who
  670. needs to get a new board working smoothly.
  671. It provides guidelines for creating those files.
  672. You should find the following directories under @t{$(INSTALLDIR)/scripts}:
  673. @itemize @bullet
  674. @item @file{interface} ...
  675. think JTAG Dongle. Files that configure JTAG adapters go here.
  676. @item @file{board} ...
  677. think Circuit Board, PWA, PCB, they go by many names. Board files
  678. contain initialization items that are specific to a board. For
  679. example, the SDRAM initialization sequence for the board, or the type
  680. of external flash and what address it uses. Any initialization
  681. sequence to enable that external flash or SDRAM should be found in the
  682. board file. Boards may also contain multiple targets: two CPUs; or
  683. a CPU and an FPGA or CPLD.
  684. @item @file{target} ...
  685. think chip. The ``target'' directory represents the JTAG TAPs
  686. on a chip
  687. which OpenOCD should control, not a board. Two common types of targets
  688. are ARM chips and FPGA or CPLD chips.
  689. When a chip has multiple TAPs (maybe it has both ARM and DSP cores),
  690. the target config file defines all of them.
  691. @end itemize
  692. The @file{openocd.cfg} user config
  693. file may override features in any of the above files by
  694. setting variables before sourcing the target file, or by adding
  695. commands specific to their situation.
  696. @section Interface Config Files
  697. The user config file
  698. should be able to source one of these files with a command like this:
  699. @example
  700. source [find interface/FOOBAR.cfg]
  701. @end example
  702. A preconfigured interface file should exist for every interface in use
  703. today, that said, perhaps some interfaces have only been used by the
  704. sole developer who created it.
  705. A separate chapter gives information about how to set these up.
  706. @xref{Interface - Dongle Configuration}.
  707. Read the OpenOCD source code if you have a new kind of hardware interface
  708. and need to provide a driver for it.
  709. @section Board Config Files
  710. @cindex config file, board
  711. @cindex board config file
  712. The user config file
  713. should be able to source one of these files with a command like this:
  714. @example
  715. source [find board/FOOBAR.cfg]
  716. @end example
  717. The point of a board config file is to package everything
  718. about a given board that user config files need to know.
  719. In summary the board files should contain (if present)
  720. @enumerate
  721. @item One or more @command{source [target/...cfg]} statements
  722. @item NOR flash configuration (@pxref{NOR Configuration})
  723. @item NAND flash configuration (@pxref{NAND Configuration})
  724. @item Target @code{reset} handlers for SDRAM and I/O configuration
  725. @item JTAG adapter reset configuration (@pxref{Reset Configuration})
  726. @item All things that are not ``inside a chip''
  727. @end enumerate
  728. Generic things inside target chips belong in target config files,
  729. not board config files. So for example a @code{reset-init} event
  730. handler should know board-specific oscillator and PLL parameters,
  731. which it passes to target-specific utility code.
  732. The most complex task of a board config file is creating such a
  733. @code{reset-init} event handler.
  734. Define those handlers last, after you verify the rest of the board
  735. configuration works.
  736. @subsection Communication Between Config files
  737. In addition to target-specific utility code, another way that
  738. board and target config files communicate is by following a
  739. convention on how to use certain variables.
  740. The full Tcl/Tk language supports ``namespaces'', but JIM-Tcl does not.
  741. Thus the rule we follow in OpenOCD is this: Variables that begin with
  742. a leading underscore are temporary in nature, and can be modified and
  743. used at will within a target configuration file.
  744. Complex board config files can do the things like this,
  745. for a board with three chips:
  746. @example
  747. # Chip #1: PXA270 for network side, big endian
  748. set CHIPNAME network
  749. set ENDIAN big
  750. source [find target/pxa270.cfg]
  751. # on return: _TARGETNAME = network.cpu
  752. # other commands can refer to the "network.cpu" target.
  753. $_TARGETNAME configure .... events for this CPU..
  754. # Chip #2: PXA270 for video side, little endian
  755. set CHIPNAME video
  756. set ENDIAN little
  757. source [find target/pxa270.cfg]
  758. # on return: _TARGETNAME = video.cpu
  759. # other commands can refer to the "video.cpu" target.
  760. $_TARGETNAME configure .... events for this CPU..
  761. # Chip #3: Xilinx FPGA for glue logic
  762. set CHIPNAME xilinx
  763. unset ENDIAN
  764. source [find target/spartan3.cfg]
  765. @end example
  766. That example is oversimplified because it doesn't show any flash memory,
  767. or the @code{reset-init} event handlers to initialize external DRAM
  768. or (assuming it needs it) load a configuration into the FPGA.
  769. Such features are usually needed for low-level work with many boards,
  770. where ``low level'' implies that the board initialization software may
  771. not be working. (That's a common reason to need JTAG tools. Another
  772. is to enable working with microcontroller-based systems, which often
  773. have no debugging support except a JTAG connector.)
  774. Target config files may also export utility functions to board and user
  775. config files. Such functions should use name prefixes, to help avoid
  776. naming collisions.
  777. Board files could also accept input variables from user config files.
  778. For example, there might be a @code{J4_JUMPER} setting used to identify
  779. what kind of flash memory a development board is using, or how to set
  780. up other clocks and peripherals.
  781. @subsection Variable Naming Convention
  782. @cindex variable names
  783. Most boards have only one instance of a chip.
  784. However, it should be easy to create a board with more than
  785. one such chip (as shown above).
  786. Accordingly, we encourage these conventions for naming
  787. variables associated with different @file{target.cfg} files,
  788. to promote consistency and
  789. so that board files can override target defaults.
  790. Inputs to target config files include:
  791. @itemize @bullet
  792. @item @code{CHIPNAME} ...
  793. This gives a name to the overall chip, and is used as part of
  794. tap identifier dotted names.
  795. While the default is normally provided by the chip manufacturer,
  796. board files may need to distinguish between instances of a chip.
  797. @item @code{ENDIAN} ...
  798. By default @option{little} - although chips may hard-wire @option{big}.
  799. Chips that can't change endianness don't need to use this variable.
  800. @item @code{CPUTAPID} ...
  801. When OpenOCD examines the JTAG chain, it can be told verify the
  802. chips against the JTAG IDCODE register.
  803. The target file will hold one or more defaults, but sometimes the
  804. chip in a board will use a different ID (perhaps a newer revision).
  805. @end itemize
  806. Outputs from target config files include:
  807. @itemize @bullet
  808. @item @code{_TARGETNAME} ...
  809. By convention, this variable is created by the target configuration
  810. script. The board configuration file may make use of this variable to
  811. configure things like a ``reset init'' script, or other things
  812. specific to that board and that target.
  813. If the chip has 2 targets, the names are @code{_TARGETNAME0},
  814. @code{_TARGETNAME1}, ... etc.
  815. @end itemize
  816. @subsection The reset-init Event Handler
  817. @cindex event, reset-init
  818. @cindex reset-init handler
  819. Board config files run in the OpenOCD configuration stage;
  820. they can't use TAPs or targets, since they haven't been
  821. fully set up yet.
  822. This means you can't write memory or access chip registers;
  823. you can't even verify that a flash chip is present.
  824. That's done later in event handlers, of which the target @code{reset-init}
  825. handler is one of the most important.
  826. Except on microcontrollers, the basic job of @code{reset-init} event
  827. handlers is setting up flash and DRAM, as normally handled by boot loaders.
  828. Microcontrollers rarely use boot loaders; they run right out of their
  829. on-chip flash and SRAM memory. But they may want to use one of these
  830. handlers too, if just for developer convenience.
  831. @quotation Note
  832. Because this is so very board-specific, and chip-specific, no examples
  833. are included here.
  834. Instead, look at the board config files distributed with OpenOCD.
  835. If you have a boot loader, its source code may also be useful.
  836. @end quotation
  837. Some of this code could probably be shared between different boards.
  838. For example, setting up a DRAM controller often doesn't differ by
  839. much except the bus width (16 bits or 32?) and memory timings, so a
  840. reusable TCL procedure loaded by the @file{target.cfg} file might take
  841. those as parameters.
  842. Similarly with oscillator, PLL, and clock setup;
  843. and disabling the watchdog.
  844. Structure the code cleanly, and provide comments to help
  845. the next developer doing such work.
  846. (@emph{You might be that next person} trying to reuse init code!)
  847. The last thing normally done in a @code{reset-init} handler is probing
  848. whatever flash memory was configured. For most chips that needs to be
  849. done while the associated target is halted, either because JTAG memory
  850. access uses the CPU or to prevent conflicting CPU access.
  851. @subsection JTAG Clock Rate
  852. Before your @code{reset-init} handler has set up
  853. the PLLs and clocking, you may need to run with
  854. a low JTAG clock rate.
  855. @xref{JTAG Speed}.
  856. Then you'd increase that rate after your handler has
  857. made it possible to use the faster JTAG clock.
  858. When the initial low speed is board-specific, for example
  859. because it depends on a board-specific oscillator speed, then
  860. you should probably set it up in the board config file;
  861. if it's target-specific, it belongs in the target config file.
  862. For most ARM-based processors the fastest JTAG clock@footnote{A FAQ
  863. @uref{http://www.arm.com/support/faqdev/4170.html} gives details.}
  864. is one sixth of the CPU clock; or one eighth for ARM11 cores.
  865. Consult chip documentation to determine the peak JTAG clock rate,
  866. which might be less than that.
  867. @quotation Warning
  868. On most ARMs, JTAG clock detection is coupled to the core clock, so
  869. software using a @option{wait for interrupt} operation blocks JTAG access.
  870. Adaptive clocking provides a partial workaround, but a more complete
  871. solution just avoids using that instruction with JTAG debuggers.
  872. @end quotation
  873. If the board supports adaptive clocking, use the @command{jtag_rclk}
  874. command, in case your board is used with JTAG adapter which
  875. also supports it. Otherwise use @command{jtag_khz}.
  876. Set the slow rate at the beginning of the reset sequence,
  877. and the faster rate as soon as the clocks are at full speed.
  878. @section Target Config Files
  879. @cindex config file, target
  880. @cindex target config file
  881. Board config files communicate with target config files using
  882. naming conventions as described above, and may source one or
  883. more target config files like this:
  884. @example
  885. source [find target/FOOBAR.cfg]
  886. @end example
  887. The point of a target config file is to package everything
  888. about a given chip that board config files need to know.
  889. In summary the target files should contain
  890. @enumerate
  891. @item Set defaults
  892. @item Add TAPs to the scan chain
  893. @item Add CPU targets (includes GDB support)
  894. @item CPU/Chip/CPU-Core specific features
  895. @item On-Chip flash
  896. @end enumerate
  897. As a rule of thumb, a target file sets up only one chip.
  898. For a microcontroller, that will often include a single TAP,
  899. which is a CPU needing a GDB target, and its on-chip flash.
  900. More complex chips may include multiple TAPs, and the target
  901. config file may need to define them all before OpenOCD
  902. can talk to the chip.
  903. For example, some phone chips have JTAG scan chains that include
  904. an ARM core for operating system use, a DSP,
  905. another ARM core embedded in an image processing engine,
  906. and other processing engines.
  907. @subsection Default Value Boiler Plate Code
  908. All target configuration files should start with code like this,
  909. letting board config files express environment-specific
  910. differences in how things should be set up.
  911. @example
  912. # Boards may override chip names, perhaps based on role,
  913. # but the default should match what the vendor uses
  914. if @{ [info exists CHIPNAME] @} @{
  915. set _CHIPNAME $CHIPNAME
  916. @} else @{
  917. set _CHIPNAME sam7x256
  918. @}
  919. # ONLY use ENDIAN with targets that can change it.
  920. if @{ [info exists ENDIAN] @} @{
  921. set _ENDIAN $ENDIAN
  922. @} else @{
  923. set _ENDIAN little
  924. @}
  925. # TAP identifiers may change as chips mature, for example with
  926. # new revision fields (the "3" here). Pick a good default; you
  927. # can pass several such identifiers to the "jtag newtap" command.
  928. if @{ [info exists CPUTAPID ] @} @{
  929. set _CPUTAPID $CPUTAPID
  930. @} else @{
  931. set _CPUTAPID 0x3f0f0f0f
  932. @}
  933. @end example
  934. @c but 0x3f0f0f0f is for an str73x part ...
  935. @emph{Remember:} Board config files may include multiple target
  936. config files, or the same target file multiple times
  937. (changing at least @code{CHIPNAME}).
  938. Likewise, the target configuration file should define
  939. @code{_TARGETNAME} (or @code{_TARGETNAME0} etc) and
  940. use it later on when defining debug targets:
  941. @example
  942. set _TARGETNAME $_CHIPNAME.cpu
  943. target create $_TARGETNAME arm7tdmi -chain-position $_TARGETNAME
  944. @end example
  945. @subsection Adding TAPs to the Scan Chain
  946. After the ``defaults'' are set up,
  947. add the TAPs on each chip to the JTAG scan chain.
  948. @xref{TAP Declaration}, and the naming convention
  949. for taps.
  950. In the simplest case the chip has only one TAP,
  951. probably for a CPU or FPGA.
  952. The config file for the Atmel AT91SAM7X256
  953. looks (in part) like this:
  954. @example
  955. jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf \
  956. -expected-id $_CPUTAPID
  957. @end example
  958. A board with two such at91sam7 chips would be able
  959. to source such a config file twice, with different
  960. values for @code{CHIPNAME}, so
  961. it adds a different TAP each time.
  962. If there are one or more nonzero @option{-expected-id} values,
  963. OpenOCD attempts to verify the actual tap id against those values.
  964. It will issue error messages if there is mismatch, which
  965. can help to pinpoint problems in OpenOCD configurations.
  966. @example
  967. JTAG tap: sam7x256.cpu tap/device found: 0x3f0f0f0f
  968. (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
  969. ERROR: Tap: sam7x256.cpu - Expected id: 0x12345678, Got: 0x3f0f0f0f
  970. ERROR: expected: mfg: 0x33c, part: 0x2345, ver: 0x1
  971. ERROR: got: mfg: 0x787, part: 0xf0f0, ver: 0x3
  972. @end example
  973. There are more complex examples too, with chips that have
  974. multiple TAPs. Ones worth looking at include:
  975. @itemize
  976. @item @file{target/omap3530.cfg} -- with disabled ARM and DSP,
  977. plus a JRC to enable them
  978. @item @file{target/str912.cfg} -- with flash, CPU, and boundary scan
  979. @item @file{target/ti_dm355.cfg} -- with ETM, ARM, and JRC (this JRC
  980. is not currently used)
  981. @end itemize
  982. @subsection Add CPU targets
  983. After adding a TAP for a CPU, you should set it up so that
  984. GDB and other commands can use it.
  985. @xref{CPU Configuration}.
  986. For the at91sam7 example above, the command can look like this;
  987. note that @code{$_ENDIAN} is not needed, since OpenOCD defaults
  988. to little endian, and this chip doesn't support changing that.
  989. @example
  990. set _TARGETNAME $_CHIPNAME.cpu
  991. target create $_TARGETNAME arm7tdmi -chain-position $_TARGETNAME
  992. @end example
  993. Work areas are small RAM areas associated with CPU targets.
  994. They are used by OpenOCD to speed up downloads,
  995. and to download small snippets of code to program flash chips.
  996. If the chip includes a form of ``on-chip-ram'' - and many do - define
  997. a work area if you can.
  998. Again using the at91sam7 as an example, this can look like:
  999. @example
  1000. $_TARGETNAME configure -work-area-phys 0x00200000 \
  1001. -work-area-size 0x4000 -work-area-backup 0
  1002. @end example
  1003. @subsection Chip Reset Setup
  1004. As a rule, you should put the @command{reset_config} command
  1005. into the board file. Most things you think you know about a
  1006. chip can be tweaked by the board.
  1007. Some chips have specific ways the TRST and SRST signals are
  1008. managed. In the unusual case that these are @emph{chip specific}
  1009. and can never be changed by board wiring, they could go here.
  1010. Some chips need special attention during reset handling if
  1011. they're going to be used with JTAG.
  1012. An example might be needing to send some commands right
  1013. after the target's TAP has been reset, providing a
  1014. @code{reset-deassert-post} event handler that writes a chip
  1015. register to report that JTAG debugging is being done.
  1016. JTAG clocking constraints often change during reset, and in
  1017. some cases target config files (rather than board config files)
  1018. are the right places to handle some of those issues.
  1019. For example, immediately after reset most chips run using a
  1020. slower clock than they will use later.
  1021. That means that after reset (and potentially, as OpenOCD
  1022. first starts up) they must use a slower JTAG clock rate
  1023. than they will use later.
  1024. @xref{JTAG Speed}.
  1025. @quotation Important
  1026. When you are debugging code that runs right after chip
  1027. reset, getting these issues right is critical.
  1028. In particular, if you see intermittent failures when
  1029. OpenOCD verifies the scan chain after reset,
  1030. look at how you are setting up JTAG clocking.
  1031. @end quotation
  1032. @subsection ARM Core Specific Hacks
  1033. If the chip has a DCC, enable it. If the chip is an ARM9 with some
  1034. special high speed download features - enable it.
  1035. If present, the MMU, the MPU and the CACHE should be disabled.
  1036. Some ARM cores are equipped with trace support, which permits
  1037. examination of the instruction and data bus activity. Trace
  1038. activity is controlled through an ``Embedded Trace Module'' (ETM)
  1039. on one of the core's scan chains. The ETM emits voluminous data
  1040. through a ``trace port''. (@xref{ARM Hardware Tracing}.)
  1041. If you are using an external trace port,
  1042. configure it in your board config file.
  1043. If you are using an on-chip ``Embedded Trace Buffer'' (ETB),
  1044. configure it in your target config file.
  1045. @example
  1046. etm config $_TARGETNAME 16 normal full etb
  1047. etb config $_TARGETNAME $_CHIPNAME.etb
  1048. @end example
  1049. @subsection Internal Flash Configuration
  1050. This applies @b{ONLY TO MICROCONTROLLERS} that have flash built in.
  1051. @b{Never ever} in the ``target configuration file'' define any type of
  1052. flash that is external to the chip. (For example a BOOT flash on
  1053. Chip Select 0.) Such flash information goes in a board file - not
  1054. the TARGET (chip) file.
  1055. Examples:
  1056. @itemize @bullet
  1057. @item at91sam7x256 - has 256K flash YES enable it.
  1058. @item str912 - has flash internal YES enable it.
  1059. @item imx27 - uses boot flash on CS0 - it goes in the board file.
  1060. @item pxa270 - again - CS0 flash - it goes in the board file.
  1061. @end itemize
  1062. @node Daemon Configuration
  1063. @chapter Daemon Configuration
  1064. @cindex initialization
  1065. The commands here are commonly found in the openocd.cfg file and are
  1066. used to specify what TCP/IP ports are used, and how GDB should be
  1067. supported.
  1068. @anchor{Configuration Stage}
  1069. @section Configuration Stage
  1070. @cindex configuration stage
  1071. @cindex config command
  1072. When the OpenOCD server process starts up, it enters a
  1073. @emph{configuration stage} which is the only time that
  1074. certain commands, @emph{configuration commands}, may be issued.
  1075. In this manual, the definition of a configuration command is
  1076. presented as a @emph{Config Command}, not as a @emph{Command}
  1077. which may be issued interactively.
  1078. Those configuration commands include declaration of TAPs,
  1079. flash banks,
  1080. the interface used for JTAG communication,
  1081. and other basic setup.
  1082. The server must leave the configuration stage before it
  1083. may access or activate TAPs.
  1084. After it leaves this stage, configuration commands may no
  1085. longer be issued.
  1086. The first thing OpenOCD does after leaving the configuration
  1087. stage is to verify that it can talk to the scan chain
  1088. (list of TAPs) which has been configured.
  1089. It will warn if it doesn't find TAPs it expects to find,
  1090. or finds TAPs that aren't supposed to be there.
  1091. You should see no errors at this point.
  1092. If you see errors, resolve them by correcting the
  1093. commands you used to configure the server.
  1094. Common errors include using an initial JTAG speed that's too
  1095. fast, and not providing the right IDCODE values for the TAPs
  1096. on the scan chain.
  1097. @deffn {Config Command} init
  1098. This command terminates the configuration stage and
  1099. enters the normal command mode. This can be useful to add commands to
  1100. the startup scripts and commands such as resetting the target,
  1101. programming flash, etc. To reset the CPU upon startup, add "init" and
  1102. "reset" at the end of the config script or at the end of the OpenOCD
  1103. command line using the @option{-c} command line switch.
  1104. If this command does not appear in any startup/configuration file
  1105. OpenOCD executes the command for you after processing all
  1106. configuration files and/or command line options.
  1107. @b{NOTE:} This command normally occurs at or near the end of your
  1108. openocd.cfg file to force OpenOCD to ``initialize'' and make the
  1109. targets ready. For example: If your openocd.cfg file needs to
  1110. read/write memory on your target, @command{init} must occur before
  1111. the memory read/write commands. This includes @command{nand probe}.
  1112. @end deffn
  1113. @anchor{TCP/IP Ports}
  1114. @section TCP/IP Ports
  1115. @cindex TCP port
  1116. @cindex server
  1117. @cindex port
  1118. @cindex security
  1119. The OpenOCD server accepts remote commands in several syntaxes.
  1120. Each syntax uses a different TCP/IP port, which you may specify
  1121. only during configuration (before those ports are opened).
  1122. For reasons including security, you may wish to prevent remote
  1123. access using one or more of these ports.
  1124. In such cases, just specify the relevant port number as zero.
  1125. If you disable all access through TCP/IP, you will need to
  1126. use the command line @option{-pipe} option.
  1127. @deffn {Command} gdb_port (number)
  1128. @cindex GDB server
  1129. Specify or query the first port used for incoming GDB connections.
  1130. The GDB port for the
  1131. first target will be gdb_port, the second target will listen on gdb_port + 1, and so on.
  1132. When not specified during the configuration stage,
  1133. the port @var{number} defaults to 3333.
  1134. When specified as zero, this port is not activated.
  1135. @end deffn
  1136. @deffn {Command} tcl_port (number)
  1137. Specify or query the port used for a simplified RPC
  1138. connection that can be used by clients to issue TCL commands and get the
  1139. output from the Tcl engine.
  1140. Intended as a machine interface.
  1141. When not specified during the configuration stage,
  1142. the port @var{number} defaults to 6666.
  1143. When specified as zero, this port is not activated.
  1144. @end deffn
  1145. @deffn {Command} telnet_port (number)
  1146. Specify or query the
  1147. port on which to listen for incoming telnet connections.
  1148. This port is intended for interaction with one human through TCL commands.
  1149. When not specified during the configuration stage,
  1150. the port @var{number} defaults to 4444.
  1151. When specified as zero, this port is not activated.
  1152. @end deffn
  1153. @anchor{GDB Configuration}
  1154. @section GDB Configuration
  1155. @cindex GDB
  1156. @cindex GDB configuration
  1157. You can reconfigure some GDB behaviors if needed.
  1158. The ones listed here are static and global.
  1159. @xref{Target Configuration}, about configuring individual targets.
  1160. @xref{Target Events}, about configuring target-specific event handling.
  1161. @anchor{gdb_breakpoint_override}
  1162. @deffn {Command} gdb_breakpoint_override [@option{hard}|@option{soft}|@option{disable}]
  1163. Force breakpoint type for gdb @command{break} commands.
  1164. This option supports GDB GUIs which don't
  1165. distinguish hard versus soft breakpoints, if the default OpenOCD and
  1166. GDB behaviour is not sufficient. GDB normally uses hardware
  1167. breakpoints if the memory map has been set up for flash regions.
  1168. @end deffn
  1169. @deffn {Config Command} gdb_detach (@option{resume}|@option{reset}|@option{halt}|@option{nothing})
  1170. Configures what OpenOCD will do when GDB detaches from the daemon.
  1171. Default behaviour is @option{resume}.
  1172. @end deffn
  1173. @anchor{gdb_flash_program}
  1174. @deffn {Config Command} gdb_flash_program (@option{enable}|@option{disable})
  1175. Set to @option{enable} to cause OpenOCD to program the flash memory when a
  1176. vFlash packet is received.
  1177. The default behaviour is @option{enable}.
  1178. @end deffn
  1179. @deffn {Config Command} gdb_memory_map (@option{enable}|@option{disable})
  1180. Set to @option{enable} to cause OpenOCD to send the memory configuration to GDB when
  1181. requested. GDB will then know when to set hardware breakpoints, and program flash
  1182. using the GDB load command. @command{gdb_flash_program enable} must also be enabled
  1183. for flash programming to work.
  1184. Default behaviour is @option{enable}.
  1185. @xref{gdb_flash_program}.
  1186. @end deffn
  1187. @deffn {Config Command} gdb_report_data_abort (@option{enable}|@option{disable})
  1188. Specifies whether data aborts cause an error to be reported
  1189. by GDB memory read packets.
  1190. The default behaviour is @option{disable};
  1191. use @option{enable} see these errors reported.
  1192. @end deffn
  1193. @anchor{Event Polling}
  1194. @section Event Polling
  1195. Hardware debuggers are parts of asynchronous systems,
  1196. where significant events can happen at any time.
  1197. The OpenOCD server needs to detect some of these events,
  1198. so it can report them to through TCL command line
  1199. or to GDB.
  1200. Examples of such events include:
  1201. @itemize
  1202. @item One of the targets can stop running ... maybe it triggers
  1203. a code breakpoint or data watchpoint, or halts itself.
  1204. @item Messages may be sent over ``debug message'' channels ... many
  1205. targets support such messages sent over JTAG,
  1206. for receipt by the person debugging or tools.
  1207. @item Loss of power ... some adapters can detect these events.
  1208. @item Resets not issued through JTAG ... such reset sources
  1209. can include button presses or other system hardware, sometimes
  1210. including the target itself (perhaps through a watchdog).
  1211. @item Debug instrumentation sometimes supports event triggering
  1212. such as ``trace buffer full'' (so it can quickly be emptied)
  1213. or other signals (to correlate with code behavior).
  1214. @end itemize
  1215. None of those events are signaled through standard JTAG signals.
  1216. However, most conventions for JTAG connectors include voltage
  1217. level and system reset (SRST) signal detection.
  1218. Some connectors also include instrumentation signals, which
  1219. can imply events when those signals are inputs.
  1220. In general, OpenOCD needs to periodically check for those events,
  1221. either by looking at the status of signals on the JTAG connector
  1222. or by sending synchronous ``tell me your status'' JTAG requests
  1223. to the various active targets.
  1224. There is a command to manage and monitor that polling,
  1225. which is normally done in the background.
  1226. @deffn Command poll [@option{on}|@option{off}]
  1227. Poll the current target for its current state.
  1228. (Also, @pxref{target curstate}.)
  1229. If that target is in debug mode, architecture
  1230. specific information about the current state is printed.
  1231. An optional parameter
  1232. allows background polling to be enabled and disabled.
  1233. You could use this from the TCL command shell, or
  1234. from GDB using @command{monitor poll} command.
  1235. @example
  1236. > poll
  1237. background polling: on
  1238. target state: halted
  1239. target halted in ARM state due to debug-request, \
  1240. current mode: Supervisor
  1241. cpsr: 0x800000d3 pc: 0x11081bfc
  1242. MMU: disabled, D-Cache: disabled, I-Cache: enabled
  1243. >
  1244. @end example
  1245. @end deffn
  1246. @node Interface - Dongle Configuration
  1247. @chapter Interface - Dongle Configuration
  1248. @cindex config file, interface
  1249. @cindex interface config file
  1250. JTAG Adapters/Interfaces/Dongles are normally configured
  1251. through commands in an interface configuration
  1252. file which is sourced by your @file{openocd.cfg} file, or
  1253. through a command line @option{-f interface/....cfg} option.
  1254. @example
  1255. source [find interface/olimex-jtag-tiny.cfg]
  1256. @end example
  1257. These commands tell
  1258. OpenOCD what type of JTAG adapter you have, and how to talk to it.
  1259. A few cases are so simple that you only need to say what driver to use:
  1260. @example
  1261. # jlink interface
  1262. interface jlink
  1263. @end example
  1264. Most adapters need a bit more configuration than that.
  1265. @section Interface Configuration
  1266. The interface command tells OpenOCD what type of JTAG dongle you are
  1267. using. Depending on the type of dongle, you may need to have one or
  1268. more additional commands.
  1269. @deffn {Config Command} {interface} name
  1270. Use the interface driver @var{name} to connect to the
  1271. target.
  1272. @end deffn
  1273. @deffn Command {interface_list}
  1274. List the interface drivers that have been built into
  1275. the running copy of OpenOCD.
  1276. @end deffn
  1277. @deffn Command {jtag interface}
  1278. Returns the name of the interface driver being used.
  1279. @end deffn
  1280. @section Interface Drivers
  1281. Each of the interface drivers listed here must be explicitly
  1282. enabled when OpenOCD is configured, in order to be made
  1283. available at run time.
  1284. @deffn {Interface Driver} {amt_jtagaccel}
  1285. Amontec Chameleon in its JTAG Accelerator configuration,
  1286. connected to a PC's EPP mode parallel port.
  1287. This defines some driver-specific commands:
  1288. @deffn {Config Command} {parport_port} number
  1289. Specifies either the address of the I/O port (default: 0x378 for LPT1) or
  1290. the number of the @file{/dev/parport} device.
  1291. @end deffn
  1292. @deffn {Config Command} rtck [@option{enable}|@option{disable}]
  1293. Displays status of RTCK option.
  1294. Optionally sets that option first.
  1295. @end deffn
  1296. @end deffn
  1297. @deffn {Interface Driver} {arm-jtag-ew}
  1298. Olimex ARM-JTAG-EW USB adapter
  1299. This has one driver-specific command:
  1300. @deffn Command {armjtagew_info}
  1301. Logs some status
  1302. @end deffn
  1303. @end deffn
  1304. @deffn {Interface Driver} {at91rm9200}
  1305. Supports bitbanged JTAG from the local system,
  1306. presuming that system is an Atmel AT91rm9200
  1307. and a specific set of GPIOs is used.
  1308. @c command: at91rm9200_device NAME
  1309. @c chooses among list of bit configs ... only one option
  1310. @end deffn
  1311. @deffn {Interface Driver} {dummy}
  1312. A dummy software-only driver for debugging.
  1313. @end deffn
  1314. @deffn {Interface Driver} {ep93xx}
  1315. Cirrus Logic EP93xx based single-board computer bit-banging (in development)
  1316. @end deffn
  1317. @deffn {Interface Driver} {ft2232}
  1318. FTDI FT2232 (USB) based devices over one of the userspace libraries.
  1319. These interfaces have several commands, used to configure the driver
  1320. before initializing the JTAG scan chain:
  1321. @deffn {Config Command} {ft2232_device_desc} description
  1322. Provides the USB device description (the @emph{iProduct string})
  1323. of the FTDI FT2232 device. If not
  1324. specified, the FTDI default value is used. This setting is only valid
  1325. if compiled with FTD2XX support.
  1326. @end deffn
  1327. @deffn {Config Command} {ft2232_serial} serial-number
  1328. Specifies the @var{serial-number} of the FTDI FT2232 device to use,
  1329. in case the vendor provides unique IDs and more than one FT2232 device
  1330. is connected to the host.
  1331. If not specified, serial numbers are not considered.
  1332. (Note that USB serial numbers can be arbitrary Unicode strings,
  1333. and are not restricted to containing only decimal digits.)
  1334. @end deffn
  1335. @deffn {Config Command} {ft2232_layout} name
  1336. Each vendor's FT2232 device can use different GPIO signals
  1337. to control output-enables, reset signals, and LEDs.
  1338. Currently valid layout @var{name} values include:
  1339. @itemize @minus
  1340. @item @b{axm0432_jtag} Axiom AXM-0432
  1341. @item @b{comstick} Hitex STR9 comstick
  1342. @item @b{cortino} Hitex Cortino JTAG interface
  1343. @item @b{evb_lm3s811} Luminary Micro EVB_LM3S811 as a JTAG interface,
  1344. either for the local Cortex-M3 (SRST only)
  1345. or in a passthrough mode (neither SRST nor TRST)
  1346. @item @b{luminary_icdi} Luminary In-Circuit Debug Interface (ICDI) Board
  1347. @item @b{flyswatter} Tin Can Tools Flyswatter
  1348. @item @b{icebear} ICEbear JTAG adapter from Section 5
  1349. @item @b{jtagkey} Amontec JTAGkey and JTAGkey-Tiny (and compatibles)
  1350. @item @b{jtagkey2} Amontec JTAGkey2 (and compatibles)
  1351. @item @b{m5960} American Microsystems M5960
  1352. @item @b{olimex-jtag} Olimex ARM-USB-OCD and ARM-USB-Tiny
  1353. @item @b{oocdlink} OOCDLink
  1354. @c oocdlink ~= jtagkey_prototype_v1
  1355. @item @b{sheevaplug} Marvell Sheevaplug development kit
  1356. @item @b{signalyzer} Xverve Signalyzer
  1357. @item @b{stm32stick} Hitex STM32 Performance Stick
  1358. @item @b{turtelizer2} egnite Software turtelizer2
  1359. @item @b{usbjtag} "USBJTAG-1" layout described in the OpenOCD diploma thesis
  1360. @end itemize
  1361. @end deffn
  1362. @deffn {Config Command} {ft2232_vid_pid} [vid pid]+
  1363. The vendor ID and product ID of the FTDI FT2232 device. If not specified, the FTDI
  1364. default values are used.
  1365. Currently, up to eight [@var{vid}, @var{pid}] pairs may be given, e.g.
  1366. @example
  1367. ft2232_vid_pid 0x0403 0xcff8 0x15ba 0x0003
  1368. @end example
  1369. @end deffn
  1370. @deffn {Config Command} {ft2232_latency} ms
  1371. On some systems using FT2232 based JTAG interfaces the FT_Read function call in
  1372. ft2232_read() fails to return the expected number of bytes. This can be caused by
  1373. USB communication delays and has proved hard to reproduce and debug. Setting the
  1374. FT2232 latency timer to a larger value increases delays for short USB packets but it
  1375. also reduces the risk of timeouts before receiving the expected number of bytes.
  1376. The OpenOCD default value is 2 and for some systems a value of 10 has proved useful.
  1377. @end deffn
  1378. For example, the interface config file for a
  1379. Turtelizer JTAG Adapter looks something like this:
  1380. @example
  1381. interface ft2232
  1382. ft2232_device_desc "Turtelizer JTAG/RS232 Adapter"
  1383. ft2232_layout turtelizer2
  1384. ft2232_vid_pid 0x0403 0xbdc8
  1385. @end example
  1386. @end deffn
  1387. @deffn {Interface Driver} {gw16012}
  1388. Gateworks GW16012 JTAG programmer.
  1389. This has one driver-specific command:
  1390. @deffn {Config Command} {parport_port} number
  1391. Specifies either the address of the I/O port (default: 0x378 for LPT1) or
  1392. the number of the @file{/dev/parport} device.
  1393. @end deffn
  1394. @end deffn
  1395. @deffn {Interface Driver} {jlink}
  1396. Segger jlink USB adapter
  1397. @c command: jlink_info
  1398. @c dumps status
  1399. @c command: jlink_hw_jtag (2|3)
  1400. @c sets version 2 or 3
  1401. @end deffn
  1402. @deffn {Interface Driver} {parport}
  1403. Supports PC parallel port bit-banging cables:
  1404. Wigglers, PLD download cable, and more.
  1405. These interfaces have several commands, used to configure the driver
  1406. before initializing the JTAG scan chain:
  1407. @deffn {Config Command} {parport_cable} name
  1408. The layout of the parallel port cable used to connect to the target.
  1409. Currently valid cable @var{name} values include:
  1410. @itemize @minus
  1411. @item @b{altium} Altium Universal JTAG cable.
  1412. @item @b{arm-jtag} Same as original wiggler except SRST and
  1413. TRST connections reversed and TRST is also inverted.
  1414. @item @b{chameleon} The Amontec Chameleon's CPLD when operated
  1415. in configuration mode. This is only used to
  1416. program the Chameleon itself, not a connected target.
  1417. @item @b{dlc5} The Xilinx Parallel cable III.
  1418. @item @b{flashlink} The ST Parallel cable.
  1419. @item @b{lattice} Lattice ispDOWNLOAD Cable
  1420. @item @b{old_amt_wiggler} The Wiggler configuration that comes with
  1421. some versions of
  1422. Amontec's Chameleon Programmer. The new version available from
  1423. the website uses the original Wiggler layout ('@var{wiggler}')
  1424. @item @b{triton} The parallel port adapter found on the
  1425. ``Karo Triton 1 Development Board''.
  1426. This is also the layout used by the HollyGates design
  1427. (see @uref{http://www.lartmaker.nl/projects/jtag/}).
  1428. @item @b{wiggler} The original Wiggler layout, also supported by
  1429. several clones, such as the Olimex ARM-JTAG
  1430. @item @b{wiggler2} Same as original wiggler except an led is fitted on D5.
  1431. @item @b{wiggler_ntrst_inverted} Same as original wiggler except TRST is inverted.
  1432. @end itemize
  1433. @end deffn
  1434. @deffn {Config Command} {parport_port} number
  1435. Either the address of the I/O port (default: 0x378 for LPT1) or the number of
  1436. the @file{/dev/parport} device
  1437. When using PPDEV to access the parallel port, use the number of the parallel port:
  1438. @option{parport_port 0} (the default). If @option{parport_port 0x378} is specified
  1439. you may encounter a problem.
  1440. @end deffn
  1441. @deffn {Config Command} {parport_write_on_exit} (on|off)
  1442. This will configure the parallel driver to write a known
  1443. cable-specific value to the parallel interface on exiting OpenOCD
  1444. @end deffn
  1445. For example, the interface configuration file for a
  1446. classic ``Wiggler'' cable might look something like this:
  1447. @example
  1448. interface parport
  1449. parport_port 0xc8b8
  1450. parport_cable wiggler
  1451. @end example
  1452. @end deffn
  1453. @deffn {Interface Driver} {presto}
  1454. ASIX PRESTO USB JTAG programmer.
  1455. @c command: presto_serial str
  1456. @c sets serial number
  1457. @end deffn
  1458. @deffn {Interface Driver} {rlink}
  1459. Raisonance RLink USB adapter
  1460. @end deffn
  1461. @deffn {Interface Driver} {usbprog}
  1462. usbprog is a freely programmable USB adapter.
  1463. @end deffn
  1464. @deffn {Interface Driver} {vsllink}
  1465. vsllink is part of Versaloon which is a versatile USB programmer.
  1466. @quotation Note
  1467. This defines quite a few driver-specific commands,
  1468. which are not currently documented here.
  1469. @end quotation
  1470. @end deffn
  1471. @deffn {Interface Driver} {ZY1000}
  1472. This is the Zylin ZY1000 JTAG debugger.
  1473. @quotation Note
  1474. This defines some driver-specific commands,
  1475. which are not currently documented here.
  1476. @end quotation
  1477. @deffn Command power [@option{on}|@option{off}]
  1478. Turn power switch to target on/off.
  1479. No arguments: print status.
  1480. @end deffn
  1481. @end deffn
  1482. @anchor{JTAG Speed}
  1483. @section JTAG Speed
  1484. JTAG clock setup is part of system setup.
  1485. It @emph{does not belong with interface setup} since any interface
  1486. only knows a few of the constraints for the JTAG clock speed.
  1487. Sometimes the JTAG speed is
  1488. changed during the target initialization process: (1) slow at
  1489. reset, (2) program the CPU clocks, (3) run fast.
  1490. Both the "slow" and "fast" clock rates are functions of the
  1491. oscillators used, the chip, the board design, and sometimes
  1492. power management software that may be active.
  1493. The speed used during reset, and the scan chain verification which
  1494. follows reset, can be adjusted using a @code{reset-start}
  1495. target event handler.
  1496. It can then be reconfigured to a faster speed by a
  1497. @code{reset-init} target event handler after it reprograms those
  1498. CPU clocks, or manually (if something else, such as a boot loader,
  1499. sets up those clocks).
  1500. @xref{Target Events}.
  1501. When the initial low JTAG speed is a chip characteristic, perhaps
  1502. because of a required oscillator speed, provide such a handler
  1503. in the target config file.
  1504. When that speed is a function of a board-specific characteristic
  1505. such as which speed oscillator is used, it belongs in the board
  1506. config file instead.
  1507. In both cases it's safest to also set the initial JTAG clock rate
  1508. to that same slow speed, so that OpenOCD never starts up using a
  1509. clock speed that's faster than the scan chain can support.
  1510. @example
  1511. jtag_rclk 3000
  1512. $_TARGET.cpu configure -event reset-start @{ jtag_rclk 3000 @}
  1513. @end example
  1514. If your system supports adaptive clocking (RTCK), configuring
  1515. JTAG to use that is probably the most robust approach.
  1516. However, it introduces delays to synchronize clocks; so it
  1517. may not be the fastest solution.
  1518. @b{NOTE:} Script writers should consider using @command{jtag_rclk}
  1519. instead of @command{jtag_khz}.
  1520. @deffn {Command} jtag_khz max_speed_kHz
  1521. A non-zero speed is in KHZ. Hence: 3000 is 3mhz.
  1522. JTAG interfaces usually support a limited number of
  1523. speeds. The speed actually used won't be faster
  1524. than the speed specified.
  1525. Chip data sheets generally include a top JTAG clock rate.
  1526. The actual rate is often a function of a CPU core clock,
  1527. and is normally less than that peak rate.
  1528. For example, most ARM cores accept at most one sixth of the CPU clock.
  1529. Speed 0 (khz) selects RTCK method.
  1530. @xref{FAQ RTCK}.
  1531. If your system uses RTCK, you won't need to change the
  1532. JTAG clocking after setup.
  1533. Not all interfaces, boards, or targets support ``rtck''.
  1534. If the interface device can not
  1535. support it, an error is returned when you try to use RTCK.
  1536. @end deffn
  1537. @defun jtag_rclk fallback_speed_kHz
  1538. @cindex adaptive clocking
  1539. @cindex RTCK
  1540. This Tcl proc (defined in @file{startup.tcl}) attempts to enable RTCK/RCLK.
  1541. If that fails (maybe the interface, board, or target doesn't
  1542. support it), falls back to the specified frequency.
  1543. @example
  1544. # Fall back to 3mhz if RTCK is not supported
  1545. jtag_rclk 3000
  1546. @end example
  1547. @end defun
  1548. @node Reset Configuration
  1549. @chapter Reset Configuration
  1550. @cindex Reset Configuration
  1551. Every system configuration may require a different reset
  1552. configuration. This can also be quite confusing.
  1553. Resets also interact with @var{reset-init} event handlers,
  1554. which do things like setting up clocks and DRAM, and
  1555. JTAG clock rates. (@xref{JTAG Speed}.)
  1556. They can also interact with JTAG routers.
  1557. Please see the various board files for examples.
  1558. @quotation Note
  1559. To maintainers and integrators:
  1560. Reset configuration touches several things at once.
  1561. Normally the board configuration file
  1562. should define it and assume that the JTAG adapter supports
  1563. everything that's wired up to the board's JTAG connector.
  1564. However, the target configuration file could also make note
  1565. of something the silicon vendor has done inside the chip,
  1566. which will be true for most (or all) boards using that chip.
  1567. And when the JTAG adapter doesn't support everything, the
  1568. user configuration file will need to override parts of
  1569. the reset configuration provided by other files.
  1570. @end quotation
  1571. @section Types of Reset
  1572. There are many kinds of reset possible through JTAG, but
  1573. they may not all work with a given board and adapter.
  1574. That's part of why reset configuration can be error prone.
  1575. @itemize @bullet
  1576. @item
  1577. @emph{System Reset} ... the @emph{SRST} hardware signal
  1578. resets all chips connected to the JTAG adapter, such as processors,
  1579. power management chips, and I/O controllers. Normally resets triggered
  1580. with this signal behave exactly like pressing a RESET button.
  1581. @item
  1582. @emph{JTAG TAP Reset} ... the @emph{TRST} hardware signal resets
  1583. just the TAP controllers connected to the JTAG adapter.
  1584. Such resets should not be visible to the rest of the system; resetting a
  1585. device's the TAP controller just puts that controller into a known state.
  1586. @item
  1587. @emph{Emulation Reset} ... many devices can be reset through JTAG
  1588. commands. These resets are often distinguishable from system
  1589. resets, either explicitly (a "reset reason" register says so)
  1590. or implicitly (not all parts of the chip get reset).
  1591. @item
  1592. @emph{Other Resets} ... system-on-chip devices often support
  1593. several other types of reset.
  1594. You may need to arrange that a watchdog timer stops
  1595. while debugging, preventing a watchdog reset.
  1596. There may be individual module resets.
  1597. @end itemize
  1598. In the best case, OpenOCD can hold SRST, then reset
  1599. the TAPs via TRST and send commands through JTAG to halt the
  1600. CPU at the reset vector before the 1st instruction is executed.
  1601. Then when it finally releases the SRST signal, the system is
  1602. halted under debugger control before any code has executed.
  1603. This is the behavior required to support the @command{reset halt}
  1604. and @command{reset init} commands; after @command{reset init} a
  1605. board-specific script might do things like setting up DRAM.
  1606. (@xref{Reset Command}.)
  1607. @anchor{SRST and TRST Issues}
  1608. @section SRST and TRST Issues
  1609. Because SRST and TRST are hardware signals, they can have a
  1610. variety of system-specific constraints. Some of the most
  1611. common issues are:
  1612. @itemize @bullet
  1613. @item @emph{Signal not available} ... Some boards don't wire
  1614. SRST or TRST to the JTAG connector. Some JTAG adapters don't
  1615. support such signals even if they are wired up.
  1616. Use the @command{reset_config} @var{signals} options to say
  1617. when either of those signals is not connected.
  1618. When SRST is not available, your code might not be able to rely
  1619. on controllers having been fully reset during code startup.
  1620. Missing TRST is not a problem, since JTAG level resets can
  1621. be triggered using with TMS signaling.
  1622. @item @emph{Signals shorted} ... Sometimes a chip, board, or
  1623. adapter will connect SRST to TRST, instead of keeping them separate.
  1624. Use the @command{reset_config} @var{combination} options to say
  1625. when those signals aren't properly independent.
  1626. @item @emph{Timing} ... Reset circuitry like a resistor/capacitor
  1627. delay circuit, reset supervisor, or on-chip features can extend
  1628. the effect of a JTAG adapter's reset for some time after the adapter
  1629. stops issuing the reset. For example, there may be chip or board
  1630. requirements that all reset pulses last for at least a
  1631. certain amount of time; and reset buttons commonly have
  1632. hardware debouncing.
  1633. Use the @command{jtag_nsrst_delay} and @command{jtag_ntrst_delay}
  1634. commands to say when extra delays are needed.
  1635. @item @emph{Drive type} ... Reset lines often have a pullup
  1636. resistor, letting the JTAG interface treat them as open-drain
  1637. signals. But that's not a requirement, so the adapter may need
  1638. to use push/pull output drivers.
  1639. Also, with weak pullups it may be advisable to drive
  1640. signals to both levels (push/pull) to minimize rise times.
  1641. Use the @command{reset_config} @var{trst_type} and
  1642. @var{srst_type} parameters to say how to drive reset signals.
  1643. @item @emph{Special initialization} ... Targets sometimes need
  1644. special JTAG initialization sequences to handle chip-specific
  1645. issues (not limited to errata).
  1646. For example, certain JTAG commands might need to be issued while
  1647. the system as a whole is in a reset state (SRST active)
  1648. but the JTAG scan chain is usable (TRST inactive).
  1649. (@xref{JTAG Commands}, where the @command{jtag_reset}
  1650. command is presented.)
  1651. @end itemize
  1652. There can also be other issues.
  1653. Some devices don't fully conform to the JTAG specifications.
  1654. Trivial system-specific differences are common, such as
  1655. SRST and TRST using slightly different names.
  1656. There are also vendors who distribute key JTAG documentation for
  1657. their chips only to developers who have signed a Non-Disclosure
  1658. Agreement (NDA).
  1659. Sometimes there are chip-specific extensions like a requirement to use
  1660. the normally-optional TRST signal (precluding use of JTAG adapters which
  1661. don't pass TRST through), or needing extra steps to complete a TAP reset.
  1662. In short, SRST and especially TRST handling may be very finicky,
  1663. needing to cope with both architecture and board specific constraints.
  1664. @section Commands for Handling Resets
  1665. @deffn {Command} jtag_nsrst_delay milliseconds
  1666. How long (in milliseconds) OpenOCD should wait after deasserting
  1667. nSRST (active-low system reset) before starting new JTAG operations.
  1668. When a board has a reset button connected to SRST line it will
  1669. probably have hardware debouncing, implying you should use this.
  1670. @end deffn
  1671. @deffn {Command} jtag_ntrst_delay milliseconds
  1672. How long (in milliseconds) OpenOCD should wait after deasserting
  1673. nTRST (active-low JTAG TAP reset) before starting new JTAG operations.
  1674. @end deffn
  1675. @deffn {Command} reset_config mode_flag ...
  1676. This command tells OpenOCD the reset configuration
  1677. of your combination of JTAG board and target in target
  1678. configuration scripts.
  1679. Information earlier in this section describes the kind of problems
  1680. the command is intended to address (@pxref{SRST and TRST Issues}).
  1681. As a rule this command belongs only in board config files,
  1682. describing issues like @emph{board doesn't connect TRST};
  1683. or in user config files, addressing limitations derived
  1684. from a particular combination of interface and board.
  1685. (An unlikely example would be using a TRST-only adapter
  1686. with a board that only wires up SRST.)
  1687. The @var{mode_flag} options can be specified in any order, but only one
  1688. of each type -- @var{signals}, @var{combination}, @var{trst_type},
  1689. and @var{srst_type} -- may be specified at a time.
  1690. If you don't provide a new value for a given type, its previous
  1691. value (perhaps the default) is unchanged.
  1692. For example, this means that you don't need to say anything at all about
  1693. TRST just to declare that if the JTAG adapter should want to drive SRST,
  1694. it must explicitly be driven high (@option{srst_push_pull}).
  1695. @var{signals} can specify which of the reset signals are connected.
  1696. For example, If the JTAG interface provides SRST, but the board doesn't
  1697. connect that signal properly, then OpenOCD can't use it.
  1698. Possible values are @option{none} (the default), @option{trst_only},
  1699. @option{srst_only} and @option{trst_and_srst}.
  1700. @quotation Tip
  1701. If your board provides SRST or TRST through the JTAG connector,
  1702. you must declare that or else those signals will not be used.
  1703. @end quotation
  1704. The @var{combination} is an optional value specifying broken reset
  1705. signal implementations.
  1706. The default behaviour if no option given is @option{separate},
  1707. indicating everything behaves normally.
  1708. @option{srst_pulls_trst} states that the
  1709. test logic is reset together with the reset of the system (e.g. Philips
  1710. LPC2000, "broken" board layout), @option{trst_pulls_srst} says that
  1711. the system is reset together with the test logic (only hypothetical, I
  1712. haven't seen hardware with such a bug, and can be worked around).
  1713. @option{combined} implies both @option{srst_pulls_trst} and
  1714. @option{trst_pulls_srst}.
  1715. @option{srst_gates_jtag} indicates that asserting SRST gates the
  1716. JTAG clock. This means that no communication can happen on JTAG
  1717. while SRST is asserted.
  1718. The optional @var{trst_type} and @var{srst_type} parameters allow the
  1719. driver mode of each reset line to be specified. These values only affect
  1720. JTAG interfaces with support for different driver modes, like the Amontec
  1721. JTAGkey and JTAGAccelerator. Also, they are necessarily ignored if the
  1722. relevant signal (TRST or SRST) is not connected.
  1723. Possible @var{trst_type} driver modes for the test reset signal (TRST)
  1724. are @option{trst_push_pull} (default) and @option{trst_open_drain}.
  1725. Most boards connect this signal to a pulldown, so the JTAG TAPs
  1726. never leave reset unless they are hooked up to a JTAG adapter.
  1727. Possible @var{srst_type} driver modes for the system reset signal (SRST)
  1728. are the default @option{srst_open_drain}, and @option{srst_push_pull}.
  1729. Most boards connect this signal to a pullup, and allow the
  1730. signal to be pulled low by various events including system
  1731. powerup and pressing a reset button.
  1732. @end deffn
  1733. @node TAP Declaration
  1734. @chapter TAP Declaration
  1735. @cindex TAP declaration
  1736. @cindex TAP configuration
  1737. @emph{Test Access Ports} (TAPs) are the core of JTAG.
  1738. TAPs serve many roles, including:
  1739. @itemize @bullet
  1740. @item @b{Debug Target} A CPU TAP can be used as a GDB debug target
  1741. @item @b{Flash Programing} Some chips program the flash directly via JTAG.
  1742. Others do it indirectly, making a CPU do it.
  1743. @item @b{Program Download} Using the same CPU support GDB uses,
  1744. you can initialize a DRAM controller, download code to DRAM, and then
  1745. start running that code.
  1746. @item @b{Boundary Scan} Most chips support boundary scan, which
  1747. helps test for board assembly problems like solder bridges
  1748. and missing connections
  1749. @end itemize
  1750. OpenOCD must know about the active TAPs on your board(s).
  1751. Setting up the TAPs is the core task of your configuration files.
  1752. Once those TAPs are set up, you can pass their names to code
  1753. which sets up CPUs and exports them as GDB targets,
  1754. probes flash memory, performs low-level JTAG operations, and more.
  1755. @section Scan Chains
  1756. @cindex scan chain
  1757. TAPs are part of a hardware @dfn{scan chain},
  1758. which is daisy chain of TAPs.
  1759. They also need to be added to
  1760. OpenOCD's software mirror of that hardware list,
  1761. giving each member a name and associating other data with it.
  1762. Simple scan chains, with a single TAP, are common in
  1763. systems with a single microcontroller or microprocessor.
  1764. More complex chips may have several TAPs internally.
  1765. Very complex scan chains might have a dozen or more TAPs:
  1766. several in one chip, more in the next, and connecting
  1767. to other boards with their own chips and TAPs.
  1768. You can display the list with the @command{scan_chain} command.
  1769. (Don't confuse this with the list displayed by the @command{targets}
  1770. command, presented in the next chapter.
  1771. That only displays TAPs for CPUs which are configured as
  1772. debugging targets.)
  1773. Here's what the scan chain might look like for a chip more than one TAP:
  1774. @verbatim
  1775. TapName Enabled IdCode Expected IrLen IrCap IrMask Instr
  1776. -- ------------------ ------- ---------- ---------- ----- ----- ------ -----
  1777. 0 omap5912.dsp Y 0x03df1d81 0x03df1d81 38 0 0 0x...
  1778. 1 omap5912.arm Y 0x0692602f 0x0692602f 4 0x1 0 0xc
  1779. 2 omap5912.unknown Y 0x00000000 0x00000000 8 0 0 0xff
  1780. @end verbatim
  1781. Unfortunately those TAPs can't always be autoconfigured,
  1782. because not all devices provide good support for that.
  1783. JTAG doesn't require supporting IDCODE instructions, and
  1784. chips with JTAG routers may not link TAPs into the chain
  1785. until they are told to do so.
  1786. The configuration mechanism currently supported by OpenOCD
  1787. requires explicit configuration of all TAP devices using
  1788. @command{jtag newtap} commands, as detailed later in this chapter.
  1789. A command like this would declare one tap and name it @code{chip1.cpu}:
  1790. @example
  1791. jtag newtap chip1 cpu -irlen 7 -ircapture 0x01 -irmask 0x55
  1792. @end example
  1793. Each target configuration file lists the TAPs provided
  1794. by a given chip.
  1795. Board configuration files combine all the targets on a board,
  1796. and so forth.
  1797. Note that @emph{the order in which TAPs are declared is very important.}
  1798. It must match the order in the JTAG scan chain, both inside
  1799. a single chip and between them.
  1800. @xref{FAQ TAP Order}.
  1801. For example, the ST Microsystems STR912 chip has
  1802. three separate TAPs@footnote{See the ST
  1803. document titled: @emph{STR91xFAxxx, Section 3.15 Jtag Interface, Page:
  1804. 28/102, Figure 3: JTAG chaining inside the STR91xFA}.
  1805. @url{http://eu.st.com/stonline/products/literature/ds/13495.pdf}}.
  1806. To configure those taps, @file{target/str912.cfg}
  1807. includes commands something like this:
  1808. @example
  1809. jtag newtap str912 flash ... params ...
  1810. jtag newtap str912 cpu ... params ...
  1811. jtag newtap str912 bs ... params ...
  1812. @end example
  1813. Actual config files use a variable instead of literals like
  1814. @option{str912}, to support more than one chip of each type.
  1815. @xref{Config File Guidelines}.
  1816. @deffn Command {jtag names}
  1817. Returns the names of all current TAPs in the scan chain.
  1818. Use @command{jtag cget} or @command{jtag tapisenabled}
  1819. to examine attributes and state of each TAP.
  1820. @example
  1821. foreach t [jtag names] @{
  1822. puts [format "TAP: %s\n" $t]
  1823. @}
  1824. @end example
  1825. @end deffn
  1826. @deffn Command {scan_chain}
  1827. Displays the TAPs in the scan chain configuration,
  1828. and their status.
  1829. The set of TAPs listed by this command is fixed by
  1830. exiting the OpenOCD configuration stage,
  1831. but systems with a JTAG router can
  1832. enable or disable TAPs dynamically.
  1833. In addition to the enable/disable status, the contents of
  1834. each TAP's instruction register can also change.
  1835. @end deffn
  1836. @c FIXME! "jtag cget" should be able to return all TAP
  1837. @c attributes, like "$target_name cget" does for targets.
  1838. @c Probably want "jtag eventlist", and a "tap-reset" event
  1839. @c (on entry to RESET state).
  1840. @section TAP Names
  1841. @cindex dotted name
  1842. When TAP objects are declared with @command{jtag newtap},
  1843. a @dfn{dotted.name} is created for the TAP, combining the
  1844. name of a module (usually a chip) and a label for the TAP.
  1845. For example: @code{xilinx.tap}, @code{str912.flash},
  1846. @code{omap3530.jrc}, @code{dm6446.dsp}, or @code{stm32.cpu}.
  1847. Many other commands use that dotted.name to manipulate or
  1848. refer to the TAP. For example, CPU configuration uses the
  1849. name, as does declaration of NAND or NOR flash banks.
  1850. The components of a dotted name should follow ``C'' symbol
  1851. name rules: start with an alphabetic character, then numbers
  1852. and underscores are OK; while others (including dots!) are not.
  1853. @quotation Tip
  1854. In older code, JTAG TAPs were numbered from 0..N.
  1855. This feature is still present.
  1856. However its use is highly discouraged, and
  1857. should not be relied on; it will be removed by mid-2010.
  1858. Update all of your scripts to use TAP names rather than numbers,
  1859. by paying attention to the runtime warnings they trigger.
  1860. Using TAP numbers in target configuration scripts prevents
  1861. reusing those scripts on boards with multiple targets.
  1862. @end quotation
  1863. @section TAP Declaration Commands
  1864. @c shouldn't this be(come) a {Config Command}?
  1865. @anchor{jtag newtap}
  1866. @deffn Command {jtag newtap} chipname tapname configparams...
  1867. Declares a new TAP with the dotted name @var{chipname}.@var{tapname},
  1868. and configured according to the various @var{configparams}.
  1869. The @var{chipname} is a symbolic name for the chip.
  1870. Conventionally target config files use @code{$_CHIPNAME},
  1871. defaulting to the model name given by the chip vendor but
  1872. overridable.
  1873. @cindex TAP naming convention
  1874. The @var{tapname} reflects the role of that TAP,
  1875. and should follow this convention:
  1876. @itemize @bullet
  1877. @item @code{bs} -- For boundary scan if this is a seperate TAP;
  1878. @item @code{cpu} -- The main CPU of the chip, alternatively
  1879. @code{arm} and @code{dsp} on chips with both ARM and DSP CPUs,
  1880. @code{arm1} and @code{arm2} on chips two ARMs, and so forth;
  1881. @item @code{etb} -- For an embedded trace buffer (example: an ARM ETB11);
  1882. @item @code{flash} -- If the chip has a flash TAP, like the str912;
  1883. @item @code{jrc} -- For JTAG route controller (example: the ICEpick modules
  1884. on many Texas Instruments chips, like the OMAP3530 on Beagleboards);
  1885. @item @code{tap} -- Should be used only FPGA or CPLD like devices
  1886. with a single TAP;
  1887. @item @code{unknownN} -- If you have no idea what the TAP is for (N is a number);
  1888. @item @emph{when in doubt} -- Use the chip maker's name in their data sheet.
  1889. For example, the Freescale IMX31 has a SDMA (Smart DMA) with
  1890. a JTAG TAP; that TAP should be named @code{sdma}.
  1891. @end itemize
  1892. Every TAP requires at least the following @var{configparams}:
  1893. @itemize @bullet
  1894. @item @code{-ircapture} @var{NUMBER}
  1895. @*The bit pattern loaded by the TAP into the JTAG shift register
  1896. on entry to the @sc{ircapture} state, such as 0x01.
  1897. JTAG requires the two LSBs of this value to be 01.
  1898. The value is used to verify that instruction scans work correctly.
  1899. @item @code{-irlen} @var{NUMBER}
  1900. @*The length in bits of the
  1901. instruction register, such as 4 or 5 bits.
  1902. @item @code{-irmask} @var{NUMBER}
  1903. @*A mask for the IR register.
  1904. For some devices, there are bits in the IR that aren't used.
  1905. This lets OpenOCD mask them off when doing IDCODE comparisons.
  1906. In general, this should just be all ones for the size of the IR.
  1907. @end itemize
  1908. A TAP may also provide optional @var{configparams}:
  1909. @itemize @bullet
  1910. @item @code{-disable} (or @code{-enable})
  1911. @*Use the @code{-disable} parameter to flag a TAP which is not
  1912. linked in to the scan chain after a reset using either TRST
  1913. or the JTAG state machine's @sc{reset} state.
  1914. You may use @code{-enable} to highlight the default state
  1915. (the TAP is linked in).
  1916. @xref{Enabling and Disabling TAPs}.
  1917. @item @code{-expected-id} @var{number}
  1918. @*A non-zero value represents the expected 32-bit IDCODE
  1919. found when the JTAG chain is examined.
  1920. These codes are not required by all JTAG devices.
  1921. @emph{Repeat the option} as many times as required if more than one
  1922. ID code could appear (for example, multiple versions).
  1923. @end itemize
  1924. @end deffn
  1925. @c @deffn Command {jtag arp_init-reset}
  1926. @c ... more or less "init" ?
  1927. @anchor{Enabling and Disabling TAPs}
  1928. @section Enabling and Disabling TAPs
  1929. @cindex TAP events
  1930. @cindex JTAG Route Controller
  1931. @cindex jrc
  1932. In some systems, a @dfn{JTAG Route Controller} (JRC)
  1933. is used to enable and/or disable specific JTAG TAPs.
  1934. Many ARM based chips from Texas Instruments include
  1935. an ``ICEpick'' module, which is a JRC.
  1936. Such chips include DaVinci and OMAP3 processors.
  1937. A given TAP may not be visible until the JRC has been
  1938. told to link it into the scan chain; and if the JRC
  1939. has been told to unlink that TAP, it will no longer
  1940. be visible.
  1941. Such routers address problems that JTAG ``bypass mode''
  1942. ignores, such as:
  1943. @itemize
  1944. @item The scan chain can only go as fast as its slowest TAP.
  1945. @item Having many TAPs slows instruction scans, since all
  1946. TAPs receive new instructions.
  1947. @item TAPs in the scan chain must be powered up, which wastes
  1948. power and prevents debugging some power management mechanisms.
  1949. @end itemize
  1950. The IEEE 1149.1 JTAG standard has no concept of a ``disabled'' tap,
  1951. as implied by the existence of JTAG routers.
  1952. However, the upcoming IEEE 1149.7 framework (layered on top of JTAG)
  1953. does include a kind of JTAG router functionality.
  1954. @c (a) currently the event handlers don't seem to be able to
  1955. @c fail in a way that could lead to no-change-of-state.
  1956. @c (b) eventually non-event configuration should be possible,
  1957. @c in which case some this documentation must move.
  1958. @deffn Command {jtag cget} dotted.name @option{-event} name
  1959. @deffnx Command {jtag configure} dotted.name @option{-event} name string
  1960. At this writing this mechanism is used only for event handling.
  1961. Three events are available. Two events relate to TAP enabling
  1962. and disabling, one to post reset handling.
  1963. The @code{configure} subcommand assigns an event handler,
  1964. a TCL string which is evaluated when the event is triggered.
  1965. The @code{cget} subcommand returns that handler.
  1966. The three possible values for an event @var{name} are @option{tap-disable}, @option{tap-enable} and @option{post-reset}.
  1967. So for example, when defining a TAP for a CPU connected to
  1968. a JTAG router, you should define TAP event handlers using
  1969. code that looks something like this:
  1970. @example
  1971. jtag configure CHIP.cpu -event tap-enable @{
  1972. echo "Enabling CPU TAP"
  1973. ... jtag operations using CHIP.jrc
  1974. @}
  1975. jtag configure CHIP.cpu -event tap-disable @{
  1976. echo "Disabling CPU TAP"
  1977. ... jtag operations using CHIP.jrc
  1978. @}
  1979. @end example
  1980. If you need some post reset action, you can do:
  1981. @example
  1982. jtag configure CHIP.cpu -event post-reset @{
  1983. echo "Reset done"
  1984. ... jtag operations to be done after reset
  1985. @}
  1986. @end example
  1987. @end deffn
  1988. @deffn Command {jtag tapdisable} dotted.name
  1989. @deffnx Command {jtag tapenable} dotted.name
  1990. @deffnx Command {jtag tapisenabled} dotted.name
  1991. These three commands all return the string "1" if the tap
  1992. specified by @var{dotted.name} is enabled,
  1993. and "0" if it is disbabled.
  1994. The @command{tapenable} variant first enables the tap
  1995. by sending it a @option{tap-enable} event.
  1996. The @command{tapdisable} variant first disables the tap
  1997. by sending it a @option{tap-disable} event.
  1998. @quotation Note
  1999. Humans will find the @command{scan_chain} command more helpful
  2000. than the script-oriented @command{tapisenabled}
  2001. for querying the state of the JTAG taps.
  2002. @end quotation
  2003. @end deffn
  2004. @node CPU Configuration
  2005. @chapter CPU Configuration
  2006. @cindex GDB target
  2007. This chapter discusses how to set up GDB debug targets for CPUs.
  2008. You can also access these targets without GDB
  2009. (@pxref{Architecture and Core Commands},
  2010. and @ref{Target State handling}) and
  2011. through various kinds of NAND and NOR flash commands.
  2012. If you have multiple CPUs you can have multiple such targets.
  2013. We'll start by looking at how to examine the targets you have,
  2014. then look at how to add one more target and how to configure it.
  2015. @section Target List
  2016. @cindex target, current
  2017. @cindex target, list
  2018. All targets that have been set up are part of a list,
  2019. where each member has a name.
  2020. That name should normally be the same as the TAP name.
  2021. You can display the list with the @command{targets}
  2022. (plural!) command.
  2023. This display often has only one CPU; here's what it might
  2024. look like with more than one:
  2025. @verbatim
  2026. TargetName Type Endian TapName State
  2027. -- ------------------ ---------- ------ ------------------ ------------
  2028. 0* at91rm9200.cpu arm920t little at91rm9200.cpu running
  2029. 1 MyTarget cortex_m3 little mychip.foo tap-disabled
  2030. @end verbatim
  2031. One member of that list is the @dfn{current target}, which
  2032. is implicitly referenced by many commands.
  2033. It's the one marked with a @code{*} near the target name.
  2034. In particular, memory addresses often refer to the address
  2035. space seen by that current target.
  2036. Commands like @command{mdw} (memory display words)
  2037. and @command{flash erase_address} (erase NOR flash blocks)
  2038. are examples; and there are many more.
  2039. Several commands let you examine the list of targets:
  2040. @deffn Command {target count}
  2041. @emph{Note: target numbers are deprecated; don't use them.
  2042. They will be removed shortly after August 2010, including this command.
  2043. Iterate target using @command{target names}, not by counting.}
  2044. Returns the number of targets, @math{N}.
  2045. The highest numbered target is @math{N - 1}.
  2046. @example
  2047. set c [target count]
  2048. for @{ set x 0 @} @{ $x < $c @} @{ incr x @} @{
  2049. # Assuming you have created this function
  2050. print_target_details $x
  2051. @}
  2052. @end example
  2053. @end deffn
  2054. @deffn Command {target current}
  2055. Returns the name of the current target.
  2056. @end deffn
  2057. @deffn Command {target names}
  2058. Lists the names of all current targets in the list.
  2059. @example
  2060. foreach t [target names] @{
  2061. puts [format "Target: %s\n" $t]
  2062. @}
  2063. @end example
  2064. @end deffn
  2065. @deffn Command {target number} number
  2066. @emph{Note: target numbers are deprecated; don't use them.
  2067. They will be removed shortly after August 2010, including this command.}
  2068. The list of targets is numbered starting at zero.
  2069. This command returns the name of the target at index @var{number}.
  2070. @example
  2071. set thename [target number $x]
  2072. puts [format "Target %d is: %s\n" $x $thename]
  2073. @end example
  2074. @end deffn
  2075. @c yep, "target list" would have been better.
  2076. @c plus maybe "target setdefault".
  2077. @deffn Command targets [name]
  2078. @emph{Note: the name of this command is plural. Other target
  2079. command names are singular.}
  2080. With no parameter, this command displays a table of all known
  2081. targets in a user friendly form.
  2082. With a parameter, this command sets the current target to
  2083. the given target with the given @var{name}; this is
  2084. only relevant on boards which have more than one target.
  2085. @end deffn
  2086. @section Target CPU Types and Variants
  2087. @cindex target type
  2088. @cindex CPU type
  2089. @cindex CPU variant
  2090. Each target has a @dfn{CPU type}, as shown in the output of
  2091. the @command{targets} command. You need to specify that type
  2092. when calling @command{target create}.
  2093. The CPU type indicates more than just the instruction set.
  2094. It also indicates how that instruction set is implemented,
  2095. what kind of debug support it integrates,
  2096. whether it has an MMU (and if so, what kind),
  2097. what core-specific commands may be available
  2098. (@pxref{Architecture and Core Commands}),
  2099. and more.
  2100. For some CPU types, OpenOCD also defines @dfn{variants} which
  2101. indicate differences that affect their handling.
  2102. For example, a particular implementation bug might need to be
  2103. worked around in some chip versions.
  2104. It's easy to see what target types are supported,
  2105. since there's a command to list them.
  2106. However, there is currently no way to list what target variants
  2107. are supported (other than by reading the OpenOCD source code).
  2108. @anchor{target types}
  2109. @deffn Command {target types}
  2110. Lists all supported target types.
  2111. At this writing, the supported CPU types and variants are:
  2112. @itemize @bullet
  2113. @item @code{arm11} -- this is a generation of ARMv6 cores
  2114. @item @code{arm720t} -- this is an ARMv4 core
  2115. @item @code{arm7tdmi} -- this is an ARMv4 core
  2116. @item @code{arm920t} -- this is an ARMv5 core
  2117. @item @code{arm926ejs} -- this is an ARMv5 core
  2118. @item @code{arm966e} -- this is an ARMv5 core
  2119. @item @code{arm9tdmi} -- this is an ARMv4 core
  2120. @item @code{avr} -- implements Atmel's 8-bit AVR instruction set.
  2121. (Support for this is preliminary and incomplete.)
  2122. @item @code{cortex_a8} -- this is an ARMv7 core
  2123. @item @code{cortex_m3} -- this is an ARMv7 core, supporting only the
  2124. compact Thumb2 instruction set. It supports one variant:
  2125. @itemize @minus
  2126. @item @code{lm3s} ... Use this when debugging older Stellaris LM3S targets.
  2127. This will cause OpenOCD to use a software reset rather than asserting
  2128. SRST, to avoid a issue with clearing the debug registers.
  2129. This is fixed in Fury Rev B, DustDevil Rev B, Tempest; these revisions will
  2130. be detected and the normal reset behaviour used.
  2131. @end itemize
  2132. @item @code{fa526} -- resembles arm920 (w/o Thumb)
  2133. @item @code{feroceon} -- resembles arm926
  2134. @item @code{mips_m4k} -- a MIPS core. This supports one variant:
  2135. @itemize @minus
  2136. @item @code{ejtag_srst} ... Use this when debugging targets that do not
  2137. provide a functional SRST line on the EJTAG connector. This causes
  2138. OpenOCD to instead use an EJTAG software reset command to reset the
  2139. processor.
  2140. You still need to enable @option{srst} on the @command{reset_config}
  2141. command to enable OpenOCD hardware reset functionality.
  2142. @end itemize
  2143. @item @code{xscale} -- this is actually an architecture,
  2144. not a CPU type. It is based on the ARMv5 architecture.
  2145. There are several variants defined:
  2146. @itemize @minus
  2147. @item @code{ixp42x}, @code{ixp45x}, @code{ixp46x},
  2148. @code{pxa27x} ... instruction register length is 7 bits
  2149. @item @code{pxa250}, @code{pxa255},
  2150. @code{pxa26x} ... instruction register length is 5 bits
  2151. @end itemize
  2152. @end itemize
  2153. @end deffn
  2154. To avoid being confused by the variety of ARM based cores, remember
  2155. this key point: @emph{ARM is a technology licencing company}.
  2156. (See: @url{http://www.arm.com}.)
  2157. The CPU name used by OpenOCD will reflect the CPU design that was
  2158. licenced, not a vendor brand which incorporates that design.
  2159. Name prefixes like arm7, arm9, arm11, and cortex
  2160. reflect design generations;
  2161. while names like ARMv4, ARMv5, ARMv6, and ARMv7
  2162. reflect an architecture version implemented by a CPU design.
  2163. @anchor{Target Configuration}
  2164. @section Target Configuration
  2165. Before creating a ``target'', you must have added its TAP to the scan chain.
  2166. When you've added that TAP, you will have a @code{dotted.name}
  2167. which is used to set up the CPU support.
  2168. The chip-specific configuration file will normally configure its CPU(s)
  2169. right after it adds all of the chip's TAPs to the scan chain.
  2170. Although you can set up a target in one step, it's often clearer if you
  2171. use shorter commands and do it in two steps: create it, then configure
  2172. optional parts.
  2173. All operations on the target after it's created will use a new
  2174. command, created as part of target creation.
  2175. The two main things to configure after target creation are
  2176. a work area, which usually has target-specific defaults even
  2177. if the board setup code overrides them later;
  2178. and event handlers (@pxref{Target Events}), which tend
  2179. to be much more board-specific.
  2180. The key steps you use might look something like this
  2181. @example
  2182. target create MyTarget cortex_m3 -chain-position mychip.cpu
  2183. $MyTarget configure -work-area-phys 0x08000 -work-area-size 8096
  2184. $MyTarget configure -event reset-deassert-pre @{ jtag_rclk 5 @}
  2185. $MyTarget configure -event reset-init @{ myboard_reinit @}
  2186. @end example
  2187. You should specify a working area if you can; typically it uses some
  2188. on-chip SRAM.
  2189. Such a working area can speed up many things, including bulk
  2190. writes to target memory;
  2191. flash operations like checking to see if memory needs to be erased;
  2192. GDB memory checksumming;
  2193. and more.
  2194. @quotation Warning
  2195. On more complex chips, the work area can become
  2196. inaccessible when application code
  2197. (such as an operating system)
  2198. enables or disables the MMU.
  2199. For example, the particular MMU context used to acess the virtual
  2200. address will probably matter ... and that context might not have
  2201. easy access to other addresses needed.
  2202. At this writing, OpenOCD doesn't have much MMU intelligence.
  2203. @end quotation
  2204. It's often very useful to define a @code{reset-init} event handler.
  2205. For systems that are normally used with a boot loader,
  2206. common tasks include updating clocks and initializing memory
  2207. controllers.
  2208. That may be needed to let you write the boot loader into flash,
  2209. in order to ``de-brick'' your board; or to load programs into
  2210. external DDR memory without having run the boot loader.
  2211. @deffn Command {target create} target_name type configparams...
  2212. This command creates a GDB debug target that refers to a specific JTAG tap.
  2213. It enters that target into a list, and creates a new
  2214. command (@command{@var{target_name}}) which is used for various
  2215. purposes including additional configuration.
  2216. @itemize @bullet
  2217. @item @var{target_name} ... is the name of the debug target.
  2218. By convention this should be the same as the @emph{dotted.name}
  2219. of the TAP associated with this target, which must be specified here
  2220. using the @code{-chain-position @var{dotted.name}} configparam.
  2221. This name is also used to create the target object command,
  2222. referred to here as @command{$target_name},
  2223. and in other places the target needs to be identified.
  2224. @item @var{type} ... specifies the target type. @xref{target types}.
  2225. @item @var{configparams} ... all parameters accepted by
  2226. @command{$target_name configure} are permitted.
  2227. If the target is big-endian, set it here with @code{-endian big}.
  2228. If the variant matters, set it here with @code{-variant}.
  2229. You @emph{must} set the @code{-chain-position @var{dotted.name}} here.
  2230. @end itemize
  2231. @end deffn
  2232. @deffn Command {$target_name configure} configparams...
  2233. The options accepted by this command may also be
  2234. specified as parameters to @command{target create}.
  2235. Their values can later be queried one at a time by
  2236. using the @command{$target_name cget} command.
  2237. @emph{Warning:} changing some of these after setup is dangerous.
  2238. For example, moving a target from one TAP to another;
  2239. and changing its endianness or variant.
  2240. @itemize @bullet
  2241. @item @code{-chain-position} @var{dotted.name} -- names the TAP
  2242. used to access this target.
  2243. @item @code{-endian} (@option{big}|@option{little}) -- specifies
  2244. whether the CPU uses big or little endian conventions
  2245. @item @code{-event} @var{event_name} @var{event_body} --
  2246. @xref{Target Events}.
  2247. Note that this updates a list of named event handlers.
  2248. Calling this twice with two different event names assigns
  2249. two different handlers, but calling it twice with the
  2250. same event name assigns only one handler.
  2251. @item @code{-variant} @var{name} -- specifies a variant of the target,
  2252. which OpenOCD needs to know about.
  2253. @item @code{-work-area-backup} (@option{0}|@option{1}) -- says
  2254. whether the work area gets backed up; by default,
  2255. @emph{it is not backed up.}
  2256. When possible, use a working_area that doesn't need to be backed up,
  2257. since performing a backup slows down operations.
  2258. For example, the beginning of an SRAM block is likely to
  2259. be used by most build systems, but the end is often unused.
  2260. @item @code{-work-area-size} @var{size} -- specify/set the work area
  2261. @item @code{-work-area-phys} @var{address} -- set the work area
  2262. base @var{address} to be used when no MMU is active.
  2263. @item @code{-work-area-virt} @var{address} -- set the work area
  2264. base @var{address} to be used when an MMU is active.
  2265. @end itemize
  2266. @end deffn
  2267. @section Other $target_name Commands
  2268. @cindex object command
  2269. The Tcl/Tk language has the concept of object commands,
  2270. and OpenOCD adopts that same model for targets.
  2271. A good Tk example is a on screen button.
  2272. Once a button is created a button
  2273. has a name (a path in Tk terms) and that name is useable as a first
  2274. class command. For example in Tk, one can create a button and later
  2275. configure it like this:
  2276. @example
  2277. # Create
  2278. button .foobar -background red -command @{ foo @}
  2279. # Modify
  2280. .foobar configure -foreground blue
  2281. # Query
  2282. set x [.foobar cget -background]
  2283. # Report
  2284. puts [format "The button is %s" $x]
  2285. @end example
  2286. In OpenOCD's terms, the ``target'' is an object just like a Tcl/Tk
  2287. button, and its object commands are invoked the same way.
  2288. @example
  2289. str912.cpu mww 0x1234 0x42
  2290. omap3530.cpu mww 0x5555 123
  2291. @end example
  2292. The commands supported by OpenOCD target objects are:
  2293. @deffn Command {$target_name arp_examine}
  2294. @deffnx Command {$target_name arp_halt}
  2295. @deffnx Command {$target_name arp_poll}
  2296. @deffnx Command {$target_name arp_reset}
  2297. @deffnx Command {$target_name arp_waitstate}
  2298. Internal OpenOCD scripts (most notably @file{startup.tcl})
  2299. use these to deal with specific reset cases.
  2300. They are not otherwise documented here.
  2301. @end deffn
  2302. @deffn Command {$target_name array2mem} arrayname width address count
  2303. @deffnx Command {$target_name mem2array} arrayname width address count
  2304. These provide an efficient script-oriented interface to memory.
  2305. The @code{array2mem} primitive writes bytes, halfwords, or words;
  2306. while @code{mem2array} reads them.
  2307. In both cases, the TCL side uses an array, and
  2308. the target side uses raw memory.
  2309. The efficiency comes from enabling the use of
  2310. bulk JTAG data transfer operations.
  2311. The script orientation comes from working with data
  2312. values that are packaged for use by TCL scripts;
  2313. @command{mdw} type primitives only print data they retrieve,
  2314. and neither store nor return those values.
  2315. @itemize
  2316. @item @var{arrayname} ... is the name of an array variable
  2317. @item @var{width} ... is 8/16/32 - indicating the memory access size
  2318. @item @var{address} ... is the target memory address
  2319. @item @var{count} ... is the number of elements to process
  2320. @end itemize
  2321. @end deffn
  2322. @deffn Command {$target_name cget} queryparm
  2323. Each configuration parameter accepted by
  2324. @command{$target_name configure}
  2325. can be individually queried, to return its current value.
  2326. The @var{queryparm} is a parameter name
  2327. accepted by that command, such as @code{-work-area-phys}.
  2328. There are a few special cases:
  2329. @itemize @bullet
  2330. @item @code{-event} @var{event_name} -- returns the handler for the
  2331. event named @var{event_name}.
  2332. This is a special case because setting a handler requires
  2333. two parameters.
  2334. @item @code{-type} -- returns the target type.
  2335. This is a special case because this is set using
  2336. @command{target create} and can't be changed
  2337. using @command{$target_name configure}.
  2338. @end itemize
  2339. For example, if you wanted to summarize information about
  2340. all the targets you might use something like this:
  2341. @example
  2342. foreach name [target names] @{
  2343. set y [$name cget -endian]
  2344. set z [$name cget -type]
  2345. puts [format "Chip %d is %s, Endian: %s, type: %s" \
  2346. $x $name $y $z]
  2347. @}
  2348. @end example
  2349. @end deffn
  2350. @anchor{target curstate}
  2351. @deffn Command {$target_name curstate}
  2352. Displays the current target state:
  2353. @code{debug-running},
  2354. @code{halted},
  2355. @code{reset},
  2356. @code{running}, or @code{unknown}.
  2357. (Also, @pxref{Event Polling}.)
  2358. @end deffn
  2359. @deffn Command {$target_name eventlist}
  2360. Displays a table listing all event handlers
  2361. currently associated with this target.
  2362. @xref{Target Events}.
  2363. @end deffn
  2364. @deffn Command {$target_name invoke-event} event_name
  2365. Invokes the handler for the event named @var{event_name}.
  2366. (This is primarily intended for use by OpenOCD framework
  2367. code, for example by the reset code in @file{startup.tcl}.)
  2368. @end deffn
  2369. @deffn Command {$target_name mdw} addr [count]
  2370. @deffnx Command {$target_name mdh} addr [count]
  2371. @deffnx Command {$target_name mdb} addr [count]
  2372. Display contents of address @var{addr}, as
  2373. 32-bit words (@command{mdw}), 16-bit halfwords (@command{mdh}),
  2374. or 8-bit bytes (@command{mdb}).
  2375. If @var{count} is specified, displays that many units.
  2376. (If you want to manipulate the data instead of displaying it,
  2377. see the @code{mem2array} primitives.)
  2378. @end deffn
  2379. @deffn Command {$target_name mww} addr word
  2380. @deffnx Command {$target_name mwh} addr halfword
  2381. @deffnx Command {$target_name mwb} addr byte
  2382. Writes the specified @var{word} (32 bits),
  2383. @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
  2384. at the specified address @var{addr}.
  2385. @end deffn
  2386. @anchor{Target Events}
  2387. @section Target Events
  2388. @cindex events
  2389. At various times, certain things can happen, or you want them to happen.
  2390. For example:
  2391. @itemize @bullet
  2392. @item What should happen when GDB connects? Should your target reset?
  2393. @item When GDB tries to flash the target, do you need to enable the flash via a special command?
  2394. @item During reset, do you need to write to certain memory locations
  2395. to set up system clocks or
  2396. to reconfigure the SDRAM?
  2397. @end itemize
  2398. All of the above items can be addressed by target event handlers.
  2399. These are set up by @command{$target_name configure -event} or
  2400. @command{target create ... -event}.
  2401. The programmer's model matches the @code{-command} option used in Tcl/Tk
  2402. buttons and events. The two examples below act the same, but one creates
  2403. and invokes a small procedure while the other inlines it.
  2404. @example
  2405. proc my_attach_proc @{ @} @{
  2406. echo "Reset..."
  2407. reset halt
  2408. @}
  2409. mychip.cpu configure -event gdb-attach my_attach_proc
  2410. mychip.cpu configure -event gdb-attach @{
  2411. echo "Reset..."
  2412. reset halt
  2413. @}
  2414. @end example
  2415. The following target events are defined:
  2416. @itemize @bullet
  2417. @item @b{debug-halted}
  2418. @* The target has halted for debug reasons (i.e.: breakpoint)
  2419. @item @b{debug-resumed}
  2420. @* The target has resumed (i.e.: gdb said run)
  2421. @item @b{early-halted}
  2422. @* Occurs early in the halt process
  2423. @ignore
  2424. @item @b{examine-end}
  2425. @* Currently not used (goal: when JTAG examine completes)
  2426. @item @b{examine-start}
  2427. @* Currently not used (goal: when JTAG examine starts)
  2428. @end ignore
  2429. @item @b{gdb-attach}
  2430. @* When GDB connects
  2431. @item @b{gdb-detach}
  2432. @* When GDB disconnects
  2433. @item @b{gdb-end}
  2434. @* When the target has halted and GDB is not doing anything (see early halt)
  2435. @item @b{gdb-flash-erase-start}
  2436. @* Before the GDB flash process tries to erase the flash
  2437. @item @b{gdb-flash-erase-end}
  2438. @* After the GDB flash process has finished erasing the flash
  2439. @item @b{gdb-flash-write-start}
  2440. @* Before GDB writes to the flash
  2441. @item @b{gdb-flash-write-end}
  2442. @* After GDB writes to the flash
  2443. @item @b{gdb-start}
  2444. @* Before the target steps, gdb is trying to start/resume the target
  2445. @item @b{halted}
  2446. @* The target has halted
  2447. @ignore
  2448. @item @b{old-gdb_program_config}
  2449. @* DO NOT USE THIS: Used internally
  2450. @item @b{old-pre_resume}
  2451. @* DO NOT USE THIS: Used internally
  2452. @end ignore
  2453. @item @b{reset-assert-pre}
  2454. @* Issued as part of @command{reset} processing
  2455. after SRST and/or TRST were activated and deactivated,
  2456. but before SRST alone is re-asserted on the tap.
  2457. @item @b{reset-assert-post}
  2458. @* Issued as part of @command{reset} processing
  2459. when SRST is asserted on the tap.
  2460. @item @b{reset-deassert-pre}
  2461. @* Issued as part of @command{reset} processing
  2462. when SRST is about to be released on the tap.
  2463. @item @b{reset-deassert-post}
  2464. @* Issued as part of @command{reset} processing
  2465. when SRST has been released on the tap.
  2466. @item @b{reset-end}
  2467. @* Issued as the final step in @command{reset} processing.
  2468. @ignore
  2469. @item @b{reset-halt-post}
  2470. @* Currently not used
  2471. @item @b{reset-halt-pre}
  2472. @* Currently not used
  2473. @end ignore
  2474. @item @b{reset-init}
  2475. @* Used by @b{reset init} command for board-specific initialization.
  2476. This event fires after @emph{reset-deassert-post}.
  2477. This is where you would configure PLLs and clocking, set up DRAM so
  2478. you can download programs that don't fit in on-chip SRAM, set up pin
  2479. multiplexing, and so on.
  2480. (You may be able to switch to a fast JTAG clock rate here, after
  2481. the target clocks are fully set up.)
  2482. @item @b{reset-start}
  2483. @* Issued as part of @command{reset} processing
  2484. before either SRST or TRST are activated.
  2485. This is the most robust place to switch to a low JTAG clock rate, if
  2486. SRST disables PLLs needed to use a fast clock.
  2487. @ignore
  2488. @item @b{reset-wait-pos}
  2489. @* Currently not used
  2490. @item @b{reset-wait-pre}
  2491. @* Currently not used
  2492. @end ignore
  2493. @item @b{resume-start}
  2494. @* Before any target is resumed
  2495. @item @b{resume-end}
  2496. @* After all targets have resumed
  2497. @item @b{resume-ok}
  2498. @* Success
  2499. @item @b{resumed}
  2500. @* Target has resumed
  2501. @end itemize
  2502. @node Flash Commands
  2503. @chapter Flash Commands
  2504. OpenOCD has different commands for NOR and NAND flash;
  2505. the ``flash'' command works with NOR flash, while
  2506. the ``nand'' command works with NAND flash.
  2507. This partially reflects different hardware technologies:
  2508. NOR flash usually supports direct CPU instruction and data bus access,
  2509. while data from a NAND flash must be copied to memory before it can be
  2510. used. (SPI flash must also be copied to memory before use.)
  2511. However, the documentation also uses ``flash'' as a generic term;
  2512. for example, ``Put flash configuration in board-specific files''.
  2513. Flash Steps:
  2514. @enumerate
  2515. @item Configure via the command @command{flash bank}
  2516. @* Do this in a board-specific configuration file,
  2517. passing parameters as needed by the driver.
  2518. @item Operate on the flash via @command{flash subcommand}
  2519. @* Often commands to manipulate the flash are typed by a human, or run
  2520. via a script in some automated way. Common tasks include writing a
  2521. boot loader, operating system, or other data.
  2522. @item GDB Flashing
  2523. @* Flashing via GDB requires the flash be configured via ``flash
  2524. bank'', and the GDB flash features be enabled.
  2525. @xref{GDB Configuration}.
  2526. @end enumerate
  2527. Many CPUs have the ablity to ``boot'' from the first flash bank.
  2528. This means that misprogramming that bank can ``brick'' a system,
  2529. so that it can't boot.
  2530. JTAG tools, like OpenOCD, are often then used to ``de-brick'' the
  2531. board by (re)installing working boot firmware.
  2532. @anchor{NOR Configuration}
  2533. @section Flash Configuration Commands
  2534. @cindex flash configuration
  2535. @deffn {Config Command} {flash bank} driver base size chip_width bus_width target [driver_options]
  2536. Configures a flash bank which provides persistent storage
  2537. for addresses from @math{base} to @math{base + size - 1}.
  2538. These banks will often be visible to GDB through the target's memory map.
  2539. In some cases, configuring a flash bank will activate extra commands;
  2540. see the driver-specific documentation.
  2541. @itemize @bullet
  2542. @item @var{driver} ... identifies the controller driver
  2543. associated with the flash bank being declared.
  2544. This is usually @code{cfi} for external flash, or else
  2545. the name of a microcontroller with embedded flash memory.
  2546. @xref{Flash Driver List}.
  2547. @item @var{base} ... Base address of the flash chip.
  2548. @item @var{size} ... Size of the chip, in bytes.
  2549. For some drivers, this value is detected from the hardware.
  2550. @item @var{chip_width} ... Width of the flash chip, in bytes;
  2551. ignored for most microcontroller drivers.
  2552. @item @var{bus_width} ... Width of the data bus used to access the
  2553. chip, in bytes; ignored for most microcontroller drivers.
  2554. @item @var{target} ... Names the target used to issue
  2555. commands to the flash controller.
  2556. @comment Actually, it's currently a controller-specific parameter...
  2557. @item @var{driver_options} ... drivers may support, or require,
  2558. additional parameters. See the driver-specific documentation
  2559. for more information.
  2560. @end itemize
  2561. @quotation Note
  2562. This command is not available after OpenOCD initialization has completed.
  2563. Use it in board specific configuration files, not interactively.
  2564. @end quotation
  2565. @end deffn
  2566. @comment the REAL name for this command is "ocd_flash_banks"
  2567. @comment less confusing would be: "flash list" (like "nand list")
  2568. @deffn Command {flash banks}
  2569. Prints a one-line summary of each device declared
  2570. using @command{flash bank}, numbered from zero.
  2571. Note that this is the @emph{plural} form;
  2572. the @emph{singular} form is a very different command.
  2573. @end deffn
  2574. @deffn Command {flash probe} num
  2575. Identify the flash, or validate the parameters of the configured flash. Operation
  2576. depends on the flash type.
  2577. The @var{num} parameter is a value shown by @command{flash banks}.
  2578. Most flash commands will implicitly @emph{autoprobe} the bank;
  2579. flash drivers can distinguish between probing and autoprobing,
  2580. but most don't bother.
  2581. @end deffn
  2582. @section Erasing, Reading, Writing to Flash
  2583. @cindex flash erasing
  2584. @cindex flash reading
  2585. @cindex flash writing
  2586. @cindex flash programming
  2587. One feature distinguishing NOR flash from NAND or serial flash technologies
  2588. is that for read access, it acts exactly like any other addressible memory.
  2589. This means you can use normal memory read commands like @command{mdw} or
  2590. @command{dump_image} with it, with no special @command{flash} subcommands.
  2591. @xref{Memory access}, and @ref{Image access}.
  2592. Write access works differently. Flash memory normally needs to be erased
  2593. before it's written. Erasing a sector turns all of its bits to ones, and
  2594. writing can turn ones into zeroes. This is why there are special commands
  2595. for interactive erasing and writing, and why GDB needs to know which parts
  2596. of the address space hold NOR flash memory.
  2597. @quotation Note
  2598. Most of these erase and write commands leverage the fact that NOR flash
  2599. chips consume target address space. They implicitly refer to the current
  2600. JTAG target, and map from an address in that target's address space
  2601. back to a flash bank.
  2602. @comment In May 2009, those mappings may fail if any bank associated
  2603. @comment with that target doesn't succesfuly autoprobe ... bug worth fixing?
  2604. A few commands use abstract addressing based on bank and sector numbers,
  2605. and don't depend on searching the current target and its address space.
  2606. Avoid confusing the two command models.
  2607. @end quotation
  2608. Some flash chips implement software protection against accidental writes,
  2609. since such buggy writes could in some cases ``brick'' a system.
  2610. For such systems, erasing and writing may require sector protection to be
  2611. disabled first.
  2612. Examples include CFI flash such as ``Intel Advanced Bootblock flash'',
  2613. and AT91SAM7 on-chip flash.
  2614. @xref{flash protect}.
  2615. @anchor{flash erase_sector}
  2616. @deffn Command {flash erase_sector} num first last
  2617. Erase sectors in bank @var{num}, starting at sector @var{first} up to and including
  2618. @var{last}. Sector numbering starts at 0.
  2619. The @var{num} parameter is a value shown by @command{flash banks}.
  2620. @end deffn
  2621. @deffn Command {flash erase_address} address length
  2622. Erase sectors starting at @var{address} for @var{length} bytes.
  2623. The flash bank to use is inferred from the @var{address}, and
  2624. the specified length must stay within that bank.
  2625. As a special case, when @var{length} is zero and @var{address} is
  2626. the start of the bank, the whole flash is erased.
  2627. @end deffn
  2628. @deffn Command {flash fillw} address word length
  2629. @deffnx Command {flash fillh} address halfword length
  2630. @deffnx Command {flash fillb} address byte length
  2631. Fills flash memory with the specified @var{word} (32 bits),
  2632. @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
  2633. starting at @var{address} and continuing
  2634. for @var{length} units (word/halfword/byte).
  2635. No erasure is done before writing; when needed, that must be done
  2636. before issuing this command.
  2637. Writes are done in blocks of up to 1024 bytes, and each write is
  2638. verified by reading back the data and comparing it to what was written.
  2639. The flash bank to use is inferred from the @var{address} of
  2640. each block, and the specified length must stay within that bank.
  2641. @end deffn
  2642. @comment no current checks for errors if fill blocks touch multiple banks!
  2643. @anchor{flash write_bank}
  2644. @deffn Command {flash write_bank} num filename offset
  2645. Write the binary @file{filename} to flash bank @var{num},
  2646. starting at @var{offset} bytes from the beginning of the bank.
  2647. The @var{num} parameter is a value shown by @command{flash banks}.
  2648. @end deffn
  2649. @anchor{flash write_image}
  2650. @deffn Command {flash write_image} [erase] filename [offset] [type]
  2651. Write the image @file{filename} to the current target's flash bank(s).
  2652. A relocation @var{offset} may be specified, in which case it is added
  2653. to the base address for each section in the image.
  2654. The file [@var{type}] can be specified
  2655. explicitly as @option{bin} (binary), @option{ihex} (Intel hex),
  2656. @option{elf} (ELF file), @option{s19} (Motorola s19).
  2657. @option{mem}, or @option{builder}.
  2658. The relevant flash sectors will be erased prior to programming
  2659. if the @option{erase} parameter is given.
  2660. The flash bank to use is inferred from the @var{address} of
  2661. each image segment.
  2662. @end deffn
  2663. @section Other Flash commands
  2664. @cindex flash protection
  2665. @deffn Command {flash erase_check} num
  2666. Check erase state of sectors in flash bank @var{num},
  2667. and display that status.
  2668. The @var{num} parameter is a value shown by @command{flash banks}.
  2669. This is the only operation that
  2670. updates the erase state information displayed by @option{flash info}. That means you have
  2671. to issue an @command{flash erase_check} command after erasing or programming the device
  2672. to get updated information.
  2673. (Code execution may have invalidated any state records kept by OpenOCD.)
  2674. @end deffn
  2675. @deffn Command {flash info} num
  2676. Print info about flash bank @var{num}
  2677. The @var{num} parameter is a value shown by @command{flash banks}.
  2678. The information includes per-sector protect status.
  2679. @end deffn
  2680. @anchor{flash protect}
  2681. @deffn Command {flash protect} num first last (on|off)
  2682. Enable (@var{on}) or disable (@var{off}) protection of flash sectors
  2683. @var{first} to @var{last} of flash bank @var{num}.
  2684. The @var{num} parameter is a value shown by @command{flash banks}.
  2685. @end deffn
  2686. @deffn Command {flash protect_check} num
  2687. Check protection state of sectors in flash bank @var{num}.
  2688. The @var{num} parameter is a value shown by @command{flash banks}.
  2689. @comment @option{flash erase_sector} using the same syntax.
  2690. @end deffn
  2691. @anchor{Flash Driver List}
  2692. @section Flash Drivers, Options, and Commands
  2693. As noted above, the @command{flash bank} command requires a driver name,
  2694. and allows driver-specific options and behaviors.
  2695. Some drivers also activate driver-specific commands.
  2696. @subsection External Flash
  2697. @deffn {Flash Driver} cfi
  2698. @cindex Common Flash Interface
  2699. @cindex CFI
  2700. The ``Common Flash Interface'' (CFI) is the main standard for
  2701. external NOR flash chips, each of which connects to a
  2702. specific external chip select on the CPU.
  2703. Frequently the first such chip is used to boot the system.
  2704. Your board's @code{reset-init} handler might need to
  2705. configure additional chip selects using other commands (like: @command{mww} to
  2706. configure a bus and its timings) , or
  2707. perhaps configure a GPIO pin that controls the ``write protect'' pin
  2708. on the flash chip.
  2709. The CFI driver can use a target-specific working area to significantly
  2710. speed up operation.
  2711. The CFI driver can accept the following optional parameters, in any order:
  2712. @itemize
  2713. @item @var{jedec_probe} ... is used to detect certain non-CFI flash ROMs,
  2714. like AM29LV010 and similar types.
  2715. @item @var{x16_as_x8} ... when a 16-bit flash is hooked up to an 8-bit bus.
  2716. @end itemize
  2717. To configure two adjacent banks of 16 MBytes each, both sixteen bits (two bytes)
  2718. wide on a sixteen bit bus:
  2719. @example
  2720. flash bank cfi 0x00000000 0x01000000 2 2 $_TARGETNAME
  2721. flash bank cfi 0x01000000 0x01000000 2 2 $_TARGETNAME
  2722. @end example
  2723. @c "cfi part_id" disabled
  2724. @end deffn
  2725. @subsection Internal Flash (Microcontrollers)
  2726. @deffn {Flash Driver} aduc702x
  2727. The ADUC702x analog microcontrollers from Analog Devices
  2728. include internal flash and use ARM7TDMI cores.
  2729. The aduc702x flash driver works with models ADUC7019 through ADUC7028.
  2730. The setup command only requires the @var{target} argument
  2731. since all devices in this family have the same memory layout.
  2732. @example
  2733. flash bank aduc702x 0 0 0 0 $_TARGETNAME
  2734. @end example
  2735. @end deffn
  2736. @deffn {Flash Driver} at91sam3
  2737. @cindex at91sam3
  2738. All members of the AT91SAM3 microcontroller family from
  2739. Atmel include internal flash and use ARM's Cortex-M3 core. The driver
  2740. currently (6/22/09) recognizes the AT91SAM3U[1/2/4][C/E] chips. Note
  2741. that the driver was orginaly developed and tested using the
  2742. AT91SAM3U4E, using a SAM3U-EK eval board. Support for other chips in
  2743. the family was cribbed from the data sheet. @emph{Note to future
  2744. readers/updaters: Please remove this worrysome comment after other
  2745. chips are confirmed.}
  2746. The AT91SAM3U4[E/C] (256K) chips have two flash banks; most other chips
  2747. have one flash bank. In all cases the flash banks are at
  2748. the following fixed locations:
  2749. @example
  2750. # Flash bank 0 - all chips
  2751. flash bank at91sam3 0x00080000 0 1 1 $_TARGETNAME
  2752. # Flash bank 1 - only 256K chips
  2753. flash bank at91sam3 0x00100000 0 1 1 $_TARGETNAME
  2754. @end example
  2755. Internally, the AT91SAM3 flash memory is organized as follows.
  2756. Unlike the AT91SAM7 chips, these are not used as parameters
  2757. to the @command{flash bank} command:
  2758. @itemize
  2759. @item @emph{N-Banks:} 256K chips have 2 banks, others have 1 bank.
  2760. @item @emph{Bank Size:} 128K/64K Per flash bank
  2761. @item @emph{Sectors:} 16 or 8 per bank
  2762. @item @emph{SectorSize:} 8K Per Sector
  2763. @item @emph{PageSize:} 256 bytes per page. Note that OpenOCD operates on 'sector' sizes, not page sizes.
  2764. @end itemize
  2765. The AT91SAM3 driver adds some additional commands:
  2766. @deffn Command {at91sam3 gpnvm}
  2767. @deffnx Command {at91sam3 gpnvm clear} number
  2768. @deffnx Command {at91sam3 gpnvm set} number
  2769. @deffnx Command {at91sam3 gpnvm show} [@option{all}|number]
  2770. With no parameters, @command{show} or @command{show all},
  2771. shows the status of all GPNVM bits.
  2772. With @command{show} @var{number}, displays that bit.
  2773. With @command{set} @var{number} or @command{clear} @var{number},
  2774. modifies that GPNVM bit.
  2775. @end deffn
  2776. @deffn Command {at91sam3 info}
  2777. This command attempts to display information about the AT91SAM3
  2778. chip. @emph{First} it read the @code{CHIPID_CIDR} [address 0x400e0740, see
  2779. Section 28.2.1, page 505 of the AT91SAM3U 29/may/2009 datasheet,
  2780. document id: doc6430A] and decodes the values. @emph{Second} it reads the
  2781. various clock configuration registers and attempts to display how it
  2782. believes the chip is configured. By default, the SLOWCLK is assumed to
  2783. be 32768 Hz, see the command @command{at91sam3 slowclk}.
  2784. @end deffn
  2785. @deffn Command {at91sam3 slowclk} [value]
  2786. This command shows/sets the slow clock frequency used in the
  2787. @command{at91sam3 info} command calculations above.
  2788. @end deffn
  2789. @end deffn
  2790. @deffn {Flash Driver} at91sam7
  2791. All members of the AT91SAM7 microcontroller family from Atmel include
  2792. internal flash and use ARM7TDMI cores. The driver automatically
  2793. recognizes a number of these chips using the chip identification
  2794. register, and autoconfigures itself.
  2795. @example
  2796. flash bank at91sam7 0 0 0 0 $_TARGETNAME
  2797. @end example
  2798. For chips which are not recognized by the controller driver, you must
  2799. provide additional parameters in the following order:
  2800. @itemize
  2801. @item @var{chip_model} ... label used with @command{flash info}
  2802. @item @var{banks}
  2803. @item @var{sectors_per_bank}
  2804. @item @var{pages_per_sector}
  2805. @item @var{pages_size}
  2806. @item @var{num_nvm_bits}
  2807. @item @var{freq_khz} ... required if an external clock is provided,
  2808. optional (but recommended) when the oscillator frequency is known
  2809. @end itemize
  2810. It is recommended that you provide zeroes for all of those values
  2811. except the clock frequency, so that everything except that frequency
  2812. will be autoconfigured.
  2813. Knowing the frequency helps ensure correct timings for flash access.
  2814. The flash controller handles erases automatically on a page (128/256 byte)
  2815. basis, so explicit erase commands are not necessary for flash programming.
  2816. However, there is an ``EraseAll`` command that can erase an entire flash
  2817. plane (of up to 256KB), and it will be used automatically when you issue
  2818. @command{flash erase_sector} or @command{flash erase_address} commands.
  2819. @deffn Command {at91sam7 gpnvm} bitnum (@option{set}|@option{clear})
  2820. Set or clear a ``General Purpose Non-Volatle Memory'' (GPNVM)
  2821. bit for the processor. Each processor has a number of such bits,
  2822. used for controlling features such as brownout detection (so they
  2823. are not truly general purpose).
  2824. @quotation Note
  2825. This assumes that the first flash bank (number 0) is associated with
  2826. the appropriate at91sam7 target.
  2827. @end quotation
  2828. @end deffn
  2829. @end deffn
  2830. @deffn {Flash Driver} avr
  2831. The AVR 8-bit microcontrollers from Atmel integrate flash memory.
  2832. @emph{The current implementation is incomplete.}
  2833. @comment - defines mass_erase ... pointless given flash_erase_address
  2834. @end deffn
  2835. @deffn {Flash Driver} ecosflash
  2836. @emph{No idea what this is...}
  2837. The @var{ecosflash} driver defines one mandatory parameter,
  2838. the name of a modules of target code which is downloaded
  2839. and executed.
  2840. @end deffn
  2841. @deffn {Flash Driver} lpc2000
  2842. Most members of the LPC1700 and LPC2000 microcontroller families from NXP
  2843. include internal flash and use Cortex-M3 (LPC1700) or ARM7TDMI (LPC2000) cores.
  2844. @quotation Note
  2845. There are LPC2000 devices which are not supported by the @var{lpc2000}
  2846. driver:
  2847. The LPC2888 is supported by the @var{lpc288x} driver.
  2848. The LPC29xx family is supported by the @var{lpc2900} driver.
  2849. @end quotation
  2850. The @var{lpc2000} driver defines two mandatory and one optional parameters,
  2851. which must appear in the following order:
  2852. @itemize
  2853. @item @var{variant} ... required, may be
  2854. @var{lpc2000_v1} (older LPC21xx and LPC22xx)
  2855. @var{lpc2000_v2} (LPC213x, LPC214x, LPC210[123], LPC23xx and LPC24xx)
  2856. or @var{lpc1700} (LPC175x and LPC176x)
  2857. @item @var{clock_kHz} ... the frequency, in kiloHertz,
  2858. at which the core is running
  2859. @item @var{calc_checksum} ... optional (but you probably want to provide this!),
  2860. telling the driver to calculate a valid checksum for the exception vector table.
  2861. @end itemize
  2862. LPC flashes don't require the chip and bus width to be specified.
  2863. @example
  2864. flash bank lpc2000 0x0 0x7d000 0 0 $_TARGETNAME \
  2865. lpc2000_v2 14765 calc_checksum
  2866. @end example
  2867. @deffn {Command} {lpc2000 part_id} bank
  2868. Displays the four byte part identifier associated with
  2869. the specified flash @var{bank}.
  2870. @end deffn
  2871. @end deffn
  2872. @deffn {Flash Driver} lpc288x
  2873. The LPC2888 microcontroller from NXP needs slightly different flash
  2874. support from its lpc2000 siblings.
  2875. The @var{lpc288x} driver defines one mandatory parameter,
  2876. the programming clock rate in Hz.
  2877. LPC flashes don't require the chip and bus width to be specified.
  2878. @example
  2879. flash bank lpc288x 0 0 0 0 $_TARGETNAME 12000000
  2880. @end example
  2881. @end deffn
  2882. @deffn {Flash Driver} lpc2900
  2883. This driver supports the LPC29xx ARM968E based microcontroller family
  2884. from NXP.
  2885. The predefined parameters @var{base}, @var{size}, @var{chip_width} and
  2886. @var{bus_width} of the @code{flash bank} command are ignored. Flash size and
  2887. sector layout are auto-configured by the driver.
  2888. The driver has one additional mandatory parameter: The CPU clock rate
  2889. (in kHz) at the time the flash operations will take place. Most of the time this
  2890. will not be the crystal frequency, but a higher PLL frequency. The
  2891. @code{reset-init} event handler in the board script is usually the place where
  2892. you start the PLL.
  2893. The driver rejects flashless devices (currently the LPC2930).
  2894. The EEPROM in LPC2900 devices is not mapped directly into the address space.
  2895. It must be handled much more like NAND flash memory, and will therefore be
  2896. handled by a separate @code{lpc2900_eeprom} driver (not yet available).
  2897. Sector protection in terms of the LPC2900 is handled transparently. Every time a
  2898. sector needs to be erased or programmed, it is automatically unprotected.
  2899. What is shown as protection status in the @code{flash info} command, is
  2900. actually the LPC2900 @emph{sector security}. This is a mechanism to prevent a
  2901. sector from ever being erased or programmed again. As this is an irreversible
  2902. mechanism, it is handled by a special command (@code{lpc2900 secure_sector}),
  2903. and not by the standard @code{flash protect} command.
  2904. Example for a 125 MHz clock frequency:
  2905. @example
  2906. flash bank lpc2900 0 0 0 0 $_TARGETNAME 125000
  2907. @end example
  2908. Some @code{lpc2900}-specific commands are defined. In the following command list,
  2909. the @var{bank} parameter is the bank number as obtained by the
  2910. @code{flash banks} command.
  2911. @deffn Command {lpc2900 signature} bank
  2912. Calculates a 128-bit hash value, the @emph{signature}, from the whole flash
  2913. content. This is a hardware feature of the flash block, hence the calculation is
  2914. very fast. You may use this to verify the content of a programmed device against
  2915. a known signature.
  2916. Example:
  2917. @example
  2918. lpc2900 signature 0
  2919. signature: 0x5f40cdc8:0xc64e592e:0x10490f89:0x32a0f317
  2920. @end example
  2921. @end deffn
  2922. @deffn Command {lpc2900 read_custom} bank filename
  2923. Reads the 912 bytes of customer information from the flash index sector, and
  2924. saves it to a file in binary format.
  2925. Example:
  2926. @example
  2927. lpc2900 read_custom 0 /path_to/customer_info.bin
  2928. @end example
  2929. @end deffn
  2930. The index sector of the flash is a @emph{write-only} sector. It cannot be
  2931. erased! In order to guard against unintentional write access, all following
  2932. commands need to be preceeded by a successful call to the @code{password}
  2933. command:
  2934. @deffn Command {lpc2900 password} bank password
  2935. You need to use this command right before each of the following commands:
  2936. @code{lpc2900 write_custom}, @code{lpc2900 secure_sector},
  2937. @code{lpc2900 secure_jtag}.
  2938. The password string is fixed to "I_know_what_I_am_doing".
  2939. Example:
  2940. @example
  2941. lpc2900 password 0 I_know_what_I_am_doing
  2942. Potentially dangerous operation allowed in next command!
  2943. @end example
  2944. @end deffn
  2945. @deffn Command {lpc2900 write_custom} bank filename type
  2946. Writes the content of the file into the customer info space of the flash index
  2947. sector. The filetype can be specified with the @var{type} field. Possible values
  2948. for @var{type} are: @var{bin} (binary), @var{ihex} (Intel hex format),
  2949. @var{elf} (ELF binary) or @var{s19} (Motorola S-records). The file must
  2950. contain a single section, and the contained data length must be exactly
  2951. 912 bytes.
  2952. @quotation Attention
  2953. This cannot be reverted! Be careful!
  2954. @end quotation
  2955. Example:
  2956. @example
  2957. lpc2900 write_custom 0 /path_to/customer_info.bin bin
  2958. @end example
  2959. @end deffn
  2960. @deffn Command {lpc2900 secure_sector} bank first last
  2961. Secures the sector range from @var{first} to @var{last} (including) against
  2962. further program and erase operations. The sector security will be effective
  2963. after the next power cycle.
  2964. @quotation Attention
  2965. This cannot be reverted! Be careful!
  2966. @end quotation
  2967. Secured sectors appear as @emph{protected} in the @code{flash info} command.
  2968. Example:
  2969. @example
  2970. lpc2900 secure_sector 0 1 1
  2971. flash info 0
  2972. #0 : lpc2900 at 0x20000000, size 0x000c0000, (...)
  2973. # 0: 0x00000000 (0x2000 8kB) not protected
  2974. # 1: 0x00002000 (0x2000 8kB) protected
  2975. # 2: 0x00004000 (0x2000 8kB) not protected
  2976. @end example
  2977. @end deffn
  2978. @deffn Command {lpc2900 secure_jtag} bank
  2979. Irreversibly disable the JTAG port. The new JTAG security setting will be
  2980. effective after the next power cycle.
  2981. @quotation Attention
  2982. This cannot be reverted! Be careful!
  2983. @end quotation
  2984. Examples:
  2985. @example
  2986. lpc2900 secure_jtag 0
  2987. @end example
  2988. @end deffn
  2989. @end deffn
  2990. @deffn {Flash Driver} ocl
  2991. @emph{No idea what this is, other than using some arm7/arm9 core.}
  2992. @example
  2993. flash bank ocl 0 0 0 0 $_TARGETNAME
  2994. @end example
  2995. @end deffn
  2996. @deffn {Flash Driver} pic32mx
  2997. The PIC32MX microcontrollers are based on the MIPS 4K cores,
  2998. and integrate flash memory.
  2999. @emph{The current implementation is incomplete.}
  3000. @example
  3001. flash bank pix32mx 0 0 0 0 $_TARGETNAME
  3002. @end example
  3003. @comment numerous *disabled* commands are defined:
  3004. @comment - chip_erase ... pointless given flash_erase_address
  3005. @comment - lock, unlock ... pointless given protect on/off (yes?)
  3006. @comment - pgm_word ... shouldn't bank be deduced from address??
  3007. Some pic32mx-specific commands are defined:
  3008. @deffn Command {pic32mx pgm_word} address value bank
  3009. Programs the specified 32-bit @var{value} at the given @var{address}
  3010. in the specified chip @var{bank}.
  3011. @end deffn
  3012. @end deffn
  3013. @deffn {Flash Driver} stellaris
  3014. All members of the Stellaris LM3Sxxx microcontroller family from
  3015. Texas Instruments
  3016. include internal flash and use ARM Cortex M3 cores.
  3017. The driver automatically recognizes a number of these chips using
  3018. the chip identification register, and autoconfigures itself.
  3019. @footnote{Currently there is a @command{stellaris mass_erase} command.
  3020. That seems pointless since the same effect can be had using the
  3021. standard @command{flash erase_address} command.}
  3022. @example
  3023. flash bank stellaris 0 0 0 0 $_TARGETNAME
  3024. @end example
  3025. @end deffn
  3026. @deffn {Flash Driver} stm32x
  3027. All members of the STM32 microcontroller family from ST Microelectronics
  3028. include internal flash and use ARM Cortex M3 cores.
  3029. The driver automatically recognizes a number of these chips using
  3030. the chip identification register, and autoconfigures itself.
  3031. @example
  3032. flash bank stm32x 0 0 0 0 $_TARGETNAME
  3033. @end example
  3034. Some stm32x-specific commands
  3035. @footnote{Currently there is a @command{stm32x mass_erase} command.
  3036. That seems pointless since the same effect can be had using the
  3037. standard @command{flash erase_address} command.}
  3038. are defined:
  3039. @deffn Command {stm32x lock} num
  3040. Locks the entire stm32 device.
  3041. The @var{num} parameter is a value shown by @command{flash banks}.
  3042. @end deffn
  3043. @deffn Command {stm32x unlock} num
  3044. Unlocks the entire stm32 device.
  3045. The @var{num} parameter is a value shown by @command{flash banks}.
  3046. @end deffn
  3047. @deffn Command {stm32x options_read} num
  3048. Read and display the stm32 option bytes written by
  3049. the @command{stm32x options_write} command.
  3050. The @var{num} parameter is a value shown by @command{flash banks}.
  3051. @end deffn
  3052. @deffn Command {stm32x options_write} num (@option{SWWDG}|@option{HWWDG}) (@option{RSTSTNDBY}|@option{NORSTSTNDBY}) (@option{RSTSTOP}|@option{NORSTSTOP})
  3053. Writes the stm32 option byte with the specified values.
  3054. The @var{num} parameter is a value shown by @command{flash banks}.
  3055. @end deffn
  3056. @end deffn
  3057. @deffn {Flash Driver} str7x
  3058. All members of the STR7 microcontroller family from ST Microelectronics
  3059. include internal flash and use ARM7TDMI cores.
  3060. The @var{str7x} driver defines one mandatory parameter, @var{variant},
  3061. which is either @code{STR71x}, @code{STR73x} or @code{STR75x}.
  3062. @example
  3063. flash bank str7x 0x40000000 0x00040000 0 0 $_TARGETNAME STR71x
  3064. @end example
  3065. @deffn Command {str7x disable_jtag} bank
  3066. Activate the Debug/Readout protection mechanism
  3067. for the specified flash bank.
  3068. @end deffn
  3069. @end deffn
  3070. @deffn {Flash Driver} str9x
  3071. Most members of the STR9 microcontroller family from ST Microelectronics
  3072. include internal flash and use ARM966E cores.
  3073. The str9 needs the flash controller to be configured using
  3074. the @command{str9x flash_config} command prior to Flash programming.
  3075. @example
  3076. flash bank str9x 0x40000000 0x00040000 0 0 $_TARGETNAME
  3077. str9x flash_config 0 4 2 0 0x80000
  3078. @end example
  3079. @deffn Command {str9x flash_config} num bbsr nbbsr bbadr nbbadr
  3080. Configures the str9 flash controller.
  3081. The @var{num} parameter is a value shown by @command{flash banks}.
  3082. @itemize @bullet
  3083. @item @var{bbsr} - Boot Bank Size register
  3084. @item @var{nbbsr} - Non Boot Bank Size register
  3085. @item @var{bbadr} - Boot Bank Start Address register
  3086. @item @var{nbbadr} - Boot Bank Start Address register
  3087. @end itemize
  3088. @end deffn
  3089. @end deffn
  3090. @deffn {Flash Driver} tms470
  3091. Most members of the TMS470 microcontroller family from Texas Instruments
  3092. include internal flash and use ARM7TDMI cores.
  3093. This driver doesn't require the chip and bus width to be specified.
  3094. Some tms470-specific commands are defined:
  3095. @deffn Command {tms470 flash_keyset} key0 key1 key2 key3
  3096. Saves programming keys in a register, to enable flash erase and write commands.
  3097. @end deffn
  3098. @deffn Command {tms470 osc_mhz} clock_mhz
  3099. Reports the clock speed, which is used to calculate timings.
  3100. @end deffn
  3101. @deffn Command {tms470 plldis} (0|1)
  3102. Disables (@var{1}) or enables (@var{0}) use of the PLL to speed up
  3103. the flash clock.
  3104. @end deffn
  3105. @end deffn
  3106. @subsection str9xpec driver
  3107. @cindex str9xpec
  3108. Here is some background info to help
  3109. you better understand how this driver works. OpenOCD has two flash drivers for
  3110. the str9:
  3111. @enumerate
  3112. @item
  3113. Standard driver @option{str9x} programmed via the str9 core. Normally used for
  3114. flash programming as it is faster than the @option{str9xpec} driver.
  3115. @item
  3116. Direct programming @option{str9xpec} using the flash controller. This is an
  3117. ISC compilant (IEEE 1532) tap connected in series with the str9 core. The str9
  3118. core does not need to be running to program using this flash driver. Typical use
  3119. for this driver is locking/unlocking the target and programming the option bytes.
  3120. @end enumerate
  3121. Before we run any commands using the @option{str9xpec} driver we must first disable
  3122. the str9 core. This example assumes the @option{str9xpec} driver has been
  3123. configured for flash bank 0.
  3124. @example
  3125. # assert srst, we do not want core running
  3126. # while accessing str9xpec flash driver
  3127. jtag_reset 0 1
  3128. # turn off target polling
  3129. poll off
  3130. # disable str9 core
  3131. str9xpec enable_turbo 0
  3132. # read option bytes
  3133. str9xpec options_read 0
  3134. # re-enable str9 core
  3135. str9xpec disable_turbo 0
  3136. poll on
  3137. reset halt
  3138. @end example
  3139. The above example will read the str9 option bytes.
  3140. When performing a unlock remember that you will not be able to halt the str9 - it
  3141. has been locked. Halting the core is not required for the @option{str9xpec} driver
  3142. as mentioned above, just issue the commands above manually or from a telnet prompt.
  3143. @deffn {Flash Driver} str9xpec
  3144. Only use this driver for locking/unlocking the device or configuring the option bytes.
  3145. Use the standard str9 driver for programming.
  3146. Before using the flash commands the turbo mode must be enabled using the
  3147. @command{str9xpec enable_turbo} command.
  3148. Several str9xpec-specific commands are defined:
  3149. @deffn Command {str9xpec disable_turbo} num
  3150. Restore the str9 into JTAG chain.
  3151. @end deffn
  3152. @deffn Command {str9xpec enable_turbo} num
  3153. Enable turbo mode, will simply remove the str9 from the chain and talk
  3154. directly to the embedded flash controller.
  3155. @end deffn
  3156. @deffn Command {str9xpec lock} num
  3157. Lock str9 device. The str9 will only respond to an unlock command that will
  3158. erase the device.
  3159. @end deffn
  3160. @deffn Command {str9xpec part_id} num
  3161. Prints the part identifier for bank @var{num}.
  3162. @end deffn
  3163. @deffn Command {str9xpec options_cmap} num (@option{bank0}|@option{bank1})
  3164. Configure str9 boot bank.
  3165. @end deffn
  3166. @deffn Command {str9xpec options_lvdsel} num (@option{vdd}|@option{vdd_vddq})
  3167. Configure str9 lvd source.
  3168. @end deffn
  3169. @deffn Command {str9xpec options_lvdthd} num (@option{2.4v}|@option{2.7v})
  3170. Configure str9 lvd threshold.
  3171. @end deffn
  3172. @deffn Command {str9xpec options_lvdwarn} bank (@option{vdd}|@option{vdd_vddq})
  3173. Configure str9 lvd reset warning source.
  3174. @end deffn
  3175. @deffn Command {str9xpec options_read} num
  3176. Read str9 option bytes.
  3177. @end deffn
  3178. @deffn Command {str9xpec options_write} num
  3179. Write str9 option bytes.
  3180. @end deffn
  3181. @deffn Command {str9xpec unlock} num
  3182. unlock str9 device.
  3183. @end deffn
  3184. @end deffn
  3185. @section mFlash
  3186. @subsection mFlash Configuration
  3187. @cindex mFlash Configuration
  3188. @deffn {Config Command} {mflash bank} soc base RST_pin target
  3189. Configures a mflash for @var{soc} host bank at
  3190. address @var{base}.
  3191. The pin number format depends on the host GPIO naming convention.
  3192. Currently, the mflash driver supports s3c2440 and pxa270.
  3193. Example for s3c2440 mflash where @var{RST pin} is GPIO B1:
  3194. @example
  3195. mflash bank s3c2440 0x10000000 1b 0
  3196. @end example
  3197. Example for pxa270 mflash where @var{RST pin} is GPIO 43:
  3198. @example
  3199. mflash bank pxa270 0x08000000 43 0
  3200. @end example
  3201. @end deffn
  3202. @subsection mFlash commands
  3203. @cindex mFlash commands
  3204. @deffn Command {mflash config pll} frequency
  3205. Configure mflash PLL.
  3206. The @var{frequency} is the mflash input frequency, in Hz.
  3207. Issuing this command will erase mflash's whole internal nand and write new pll.
  3208. After this command, mflash needs power-on-reset for normal operation.
  3209. If pll was newly configured, storage and boot(optional) info also need to be update.
  3210. @end deffn
  3211. @deffn Command {mflash config boot}
  3212. Configure bootable option.
  3213. If bootable option is set, mflash offer the first 8 sectors
  3214. (4kB) for boot.
  3215. @end deffn
  3216. @deffn Command {mflash config storage}
  3217. Configure storage information.
  3218. For the normal storage operation, this information must be
  3219. written.
  3220. @end deffn
  3221. @deffn Command {mflash dump} num filename offset size
  3222. Dump @var{size} bytes, starting at @var{offset} bytes from the
  3223. beginning of the bank @var{num}, to the file named @var{filename}.
  3224. @end deffn
  3225. @deffn Command {mflash probe}
  3226. Probe mflash.
  3227. @end deffn
  3228. @deffn Command {mflash write} num filename offset
  3229. Write the binary file @var{filename} to mflash bank @var{num}, starting at
  3230. @var{offset} bytes from the beginning of the bank.
  3231. @end deffn
  3232. @node NAND Flash Commands
  3233. @chapter NAND Flash Commands
  3234. @cindex NAND
  3235. Compared to NOR or SPI flash, NAND devices are inexpensive
  3236. and high density. Today's NAND chips, and multi-chip modules,
  3237. commonly hold multiple GigaBytes of data.
  3238. NAND chips consist of a number of ``erase blocks'' of a given
  3239. size (such as 128 KBytes), each of which is divided into a
  3240. number of pages (of perhaps 512 or 2048 bytes each). Each
  3241. page of a NAND flash has an ``out of band'' (OOB) area to hold
  3242. Error Correcting Code (ECC) and other metadata, usually 16 bytes
  3243. of OOB for every 512 bytes of page data.
  3244. One key characteristic of NAND flash is that its error rate
  3245. is higher than that of NOR flash. In normal operation, that
  3246. ECC is used to correct and detect errors. However, NAND
  3247. blocks can also wear out and become unusable; those blocks
  3248. are then marked "bad". NAND chips are even shipped from the
  3249. manufacturer with a few bad blocks. The highest density chips
  3250. use a technology (MLC) that wears out more quickly, so ECC
  3251. support is increasingly important as a way to detect blocks
  3252. that have begun to fail, and help to preserve data integrity
  3253. with techniques such as wear leveling.
  3254. Software is used to manage the ECC. Some controllers don't
  3255. support ECC directly; in those cases, software ECC is used.
  3256. Other controllers speed up the ECC calculations with hardware.
  3257. Single-bit error correction hardware is routine. Controllers
  3258. geared for newer MLC chips may correct 4 or more errors for
  3259. every 512 bytes of data.
  3260. You will need to make sure that any data you write using
  3261. OpenOCD includes the apppropriate kind of ECC. For example,
  3262. that may mean passing the @code{oob_softecc} flag when
  3263. writing NAND data, or ensuring that the correct hardware
  3264. ECC mode is used.
  3265. The basic steps for using NAND devices include:
  3266. @enumerate
  3267. @item Declare via the command @command{nand device}
  3268. @* Do this in a board-specific configuration file,
  3269. passing parameters as needed by the controller.
  3270. @item Configure each device using @command{nand probe}.
  3271. @* Do this only after the associated target is set up,
  3272. such as in its reset-init script or in procures defined
  3273. to access that device.
  3274. @item Operate on the flash via @command{nand subcommand}
  3275. @* Often commands to manipulate the flash are typed by a human, or run
  3276. via a script in some automated way. Common task include writing a
  3277. boot loader, operating system, or other data needed to initialize or
  3278. de-brick a board.
  3279. @end enumerate
  3280. @b{NOTE:} At the time this text was written, the largest NAND
  3281. flash fully supported by OpenOCD is 2 GiBytes (16 GiBits).
  3282. This is because the variables used to hold offsets and lengths
  3283. are only 32 bits wide.
  3284. (Larger chips may work in some cases, unless an offset or length
  3285. is larger than 0xffffffff, the largest 32-bit unsigned integer.)
  3286. Some larger devices will work, since they are actually multi-chip
  3287. modules with two smaller chips and individual chipselect lines.
  3288. @anchor{NAND Configuration}
  3289. @section NAND Configuration Commands
  3290. @cindex NAND configuration
  3291. NAND chips must be declared in configuration scripts,
  3292. plus some additional configuration that's done after
  3293. OpenOCD has initialized.
  3294. @deffn {Config Command} {nand device} controller target [configparams...]
  3295. Declares a NAND device, which can be read and written to
  3296. after it has been configured through @command{nand probe}.
  3297. In OpenOCD, devices are single chips; this is unlike some
  3298. operating systems, which may manage multiple chips as if
  3299. they were a single (larger) device.
  3300. In some cases, configuring a device will activate extra
  3301. commands; see the controller-specific documentation.
  3302. @b{NOTE:} This command is not available after OpenOCD
  3303. initialization has completed. Use it in board specific
  3304. configuration files, not interactively.
  3305. @itemize @bullet
  3306. @item @var{controller} ... identifies the controller driver
  3307. associated with the NAND device being declared.
  3308. @xref{NAND Driver List}.
  3309. @item @var{target} ... names the target used when issuing
  3310. commands to the NAND controller.
  3311. @comment Actually, it's currently a controller-specific parameter...
  3312. @item @var{configparams} ... controllers may support, or require,
  3313. additional parameters. See the controller-specific documentation
  3314. for more information.
  3315. @end itemize
  3316. @end deffn
  3317. @deffn Command {nand list}
  3318. Prints a summary of each device declared
  3319. using @command{nand device}, numbered from zero.
  3320. Note that un-probed devices show no details.
  3321. @example
  3322. > nand list
  3323. #0: NAND 1GiB 3,3V 8-bit (Micron) pagesize: 2048, buswidth: 8,
  3324. blocksize: 131072, blocks: 8192
  3325. #1: NAND 1GiB 3,3V 8-bit (Micron) pagesize: 2048, buswidth: 8,
  3326. blocksize: 131072, blocks: 8192
  3327. >
  3328. @end example
  3329. @end deffn
  3330. @deffn Command {nand probe} num
  3331. Probes the specified device to determine key characteristics
  3332. like its page and block sizes, and how many blocks it has.
  3333. The @var{num} parameter is the value shown by @command{nand list}.
  3334. You must (successfully) probe a device before you can use
  3335. it with most other NAND commands.
  3336. @end deffn
  3337. @section Erasing, Reading, Writing to NAND Flash
  3338. @deffn Command {nand dump} num filename offset length [oob_option]
  3339. @cindex NAND reading
  3340. Reads binary data from the NAND device and writes it to the file,
  3341. starting at the specified offset.
  3342. The @var{num} parameter is the value shown by @command{nand list}.
  3343. Use a complete path name for @var{filename}, so you don't depend
  3344. on the directory used to start the OpenOCD server.
  3345. The @var{offset} and @var{length} must be exact multiples of the
  3346. device's page size. They describe a data region; the OOB data
  3347. associated with each such page may also be accessed.
  3348. @b{NOTE:} At the time this text was written, no error correction
  3349. was done on the data that's read, unless raw access was disabled
  3350. and the underlying NAND controller driver had a @code{read_page}
  3351. method which handled that error correction.
  3352. By default, only page data is saved to the specified file.
  3353. Use an @var{oob_option} parameter to save OOB data:
  3354. @itemize @bullet
  3355. @item no oob_* parameter
  3356. @*Output file holds only page data; OOB is discarded.
  3357. @item @code{oob_raw}
  3358. @*Output file interleaves page data and OOB data;
  3359. the file will be longer than "length" by the size of the
  3360. spare areas associated with each data page.
  3361. Note that this kind of "raw" access is different from
  3362. what's implied by @command{nand raw_access}, which just
  3363. controls whether a hardware-aware access method is used.
  3364. @item @code{oob_only}
  3365. @*Output file has only raw OOB data, and will
  3366. be smaller than "length" since it will contain only the
  3367. spare areas associated with each data page.
  3368. @end itemize
  3369. @end deffn
  3370. @deffn Command {nand erase} num [offset length]
  3371. @cindex NAND erasing
  3372. @cindex NAND programming
  3373. Erases blocks on the specified NAND device, starting at the
  3374. specified @var{offset} and continuing for @var{length} bytes.
  3375. Both of those values must be exact multiples of the device's
  3376. block size, and the region they specify must fit entirely in the chip.
  3377. If those parameters are not specified,
  3378. the whole NAND chip will be erased.
  3379. The @var{num} parameter is the value shown by @command{nand list}.
  3380. @b{NOTE:} This command will try to erase bad blocks, when told
  3381. to do so, which will probably invalidate the manufacturer's bad
  3382. block marker.
  3383. For the remainder of the current server session, @command{nand info}
  3384. will still report that the block ``is'' bad.
  3385. @end deffn
  3386. @deffn Command {nand write} num filename offset [option...]
  3387. @cindex NAND writing
  3388. @cindex NAND programming
  3389. Writes binary data from the file into the specified NAND device,
  3390. starting at the specified offset. Those pages should already
  3391. have been erased; you can't change zero bits to one bits.
  3392. The @var{num} parameter is the value shown by @command{nand list}.
  3393. Use a complete path name for @var{filename}, so you don't depend
  3394. on the directory used to start the OpenOCD server.
  3395. The @var{offset} must be an exact multiple of the device's page size.
  3396. All data in the file will be written, assuming it doesn't run
  3397. past the end of the device.
  3398. Only full pages are written, and any extra space in the last
  3399. page will be filled with 0xff bytes. (That includes OOB data,
  3400. if that's being written.)
  3401. @b{NOTE:} At the time this text was written, bad blocks are
  3402. ignored. That is, this routine will not skip bad blocks,
  3403. but will instead try to write them. This can cause problems.
  3404. Provide at most one @var{option} parameter. With some
  3405. NAND drivers, the meanings of these parameters may change
  3406. if @command{nand raw_access} was used to disable hardware ECC.
  3407. @itemize @bullet
  3408. @item no oob_* parameter
  3409. @*File has only page data, which is written.
  3410. If raw acccess is in use, the OOB area will not be written.
  3411. Otherwise, if the underlying NAND controller driver has
  3412. a @code{write_page} routine, that routine may write the OOB
  3413. with hardware-computed ECC data.
  3414. @item @code{oob_only}
  3415. @*File has only raw OOB data, which is written to the OOB area.
  3416. Each page's data area stays untouched. @i{This can be a dangerous
  3417. option}, since it can invalidate the ECC data.
  3418. You may need to force raw access to use this mode.
  3419. @item @code{oob_raw}
  3420. @*File interleaves data and OOB data, both of which are written
  3421. If raw access is enabled, the data is written first, then the
  3422. un-altered OOB.
  3423. Otherwise, if the underlying NAND controller driver has
  3424. a @code{write_page} routine, that routine may modify the OOB
  3425. before it's written, to include hardware-computed ECC data.
  3426. @item @code{oob_softecc}
  3427. @*File has only page data, which is written.
  3428. The OOB area is filled with 0xff, except for a standard 1-bit
  3429. software ECC code stored in conventional locations.
  3430. You might need to force raw access to use this mode, to prevent
  3431. the underlying driver from applying hardware ECC.
  3432. @item @code{oob_softecc_kw}
  3433. @*File has only page data, which is written.
  3434. The OOB area is filled with 0xff, except for a 4-bit software ECC
  3435. specific to the boot ROM in Marvell Kirkwood SoCs.
  3436. You might need to force raw access to use this mode, to prevent
  3437. the underlying driver from applying hardware ECC.
  3438. @end itemize
  3439. @end deffn
  3440. @section Other NAND commands
  3441. @cindex NAND other commands
  3442. @deffn Command {nand check_bad_blocks} [offset length]
  3443. Checks for manufacturer bad block markers on the specified NAND
  3444. device. If no parameters are provided, checks the whole
  3445. device; otherwise, starts at the specified @var{offset} and
  3446. continues for @var{length} bytes.
  3447. Both of those values must be exact multiples of the device's
  3448. block size, and the region they specify must fit entirely in the chip.
  3449. The @var{num} parameter is the value shown by @command{nand list}.
  3450. @b{NOTE:} Before using this command you should force raw access
  3451. with @command{nand raw_access enable} to ensure that the underlying
  3452. driver will not try to apply hardware ECC.
  3453. @end deffn
  3454. @deffn Command {nand info} num
  3455. The @var{num} parameter is the value shown by @command{nand list}.
  3456. This prints the one-line summary from "nand list", plus for
  3457. devices which have been probed this also prints any known
  3458. status for each block.
  3459. @end deffn
  3460. @deffn Command {nand raw_access} num (@option{enable}|@option{disable})
  3461. Sets or clears an flag affecting how page I/O is done.
  3462. The @var{num} parameter is the value shown by @command{nand list}.
  3463. This flag is cleared (disabled) by default, but changing that
  3464. value won't affect all NAND devices. The key factor is whether
  3465. the underlying driver provides @code{read_page} or @code{write_page}
  3466. methods. If it doesn't provide those methods, the setting of
  3467. this flag is irrelevant; all access is effectively ``raw''.
  3468. When those methods exist, they are normally used when reading
  3469. data (@command{nand dump} or reading bad block markers) or
  3470. writing it (@command{nand write}). However, enabling
  3471. raw access (setting the flag) prevents use of those methods,
  3472. bypassing hardware ECC logic.
  3473. @i{This can be a dangerous option}, since writing blocks
  3474. with the wrong ECC data can cause them to be marked as bad.
  3475. @end deffn
  3476. @anchor{NAND Driver List}
  3477. @section NAND Drivers, Options, and Commands
  3478. As noted above, the @command{nand device} command allows
  3479. driver-specific options and behaviors.
  3480. Some controllers also activate controller-specific commands.
  3481. @deffn {NAND Driver} davinci
  3482. This driver handles the NAND controllers found on DaVinci family
  3483. chips from Texas Instruments.
  3484. It takes three extra parameters:
  3485. address of the NAND chip;
  3486. hardware ECC mode to use (@option{hwecc1},
  3487. @option{hwecc4}, @option{hwecc4_infix});
  3488. address of the AEMIF controller on this processor.
  3489. @example
  3490. nand device davinci dm355.arm 0x02000000 hwecc4 0x01e10000
  3491. @end example
  3492. All DaVinci processors support the single-bit ECC hardware,
  3493. and newer ones also support the four-bit ECC hardware.
  3494. The @code{write_page} and @code{read_page} methods are used
  3495. to implement those ECC modes, unless they are disabled using
  3496. the @command{nand raw_access} command.
  3497. @end deffn
  3498. @deffn {NAND Driver} lpc3180
  3499. These controllers require an extra @command{nand device}
  3500. parameter: the clock rate used by the controller.
  3501. @deffn Command {lpc3180 select} num [mlc|slc]
  3502. Configures use of the MLC or SLC controller mode.
  3503. MLC implies use of hardware ECC.
  3504. The @var{num} parameter is the value shown by @command{nand list}.
  3505. @end deffn
  3506. At this writing, this driver includes @code{write_page}
  3507. and @code{read_page} methods. Using @command{nand raw_access}
  3508. to disable those methods will prevent use of hardware ECC
  3509. in the MLC controller mode, but won't change SLC behavior.
  3510. @end deffn
  3511. @comment current lpc3180 code won't issue 5-byte address cycles
  3512. @deffn {NAND Driver} orion
  3513. These controllers require an extra @command{nand device}
  3514. parameter: the address of the controller.
  3515. @example
  3516. nand device orion 0xd8000000
  3517. @end example
  3518. These controllers don't define any specialized commands.
  3519. At this writing, their drivers don't include @code{write_page}
  3520. or @code{read_page} methods, so @command{nand raw_access} won't
  3521. change any behavior.
  3522. @end deffn
  3523. @deffn {NAND Driver} s3c2410
  3524. @deffnx {NAND Driver} s3c2412
  3525. @deffnx {NAND Driver} s3c2440
  3526. @deffnx {NAND Driver} s3c2443
  3527. These S3C24xx family controllers don't have any special
  3528. @command{nand device} options, and don't define any
  3529. specialized commands.
  3530. At this writing, their drivers don't include @code{write_page}
  3531. or @code{read_page} methods, so @command{nand raw_access} won't
  3532. change any behavior.
  3533. @end deffn
  3534. @node PLD/FPGA Commands
  3535. @chapter PLD/FPGA Commands
  3536. @cindex PLD
  3537. @cindex FPGA
  3538. Programmable Logic Devices (PLDs) and the more flexible
  3539. Field Programmable Gate Arrays (FPGAs) are both types of programmable hardware.
  3540. OpenOCD can support programming them.
  3541. Although PLDs are generally restrictive (cells are less functional, and
  3542. there are no special purpose cells for memory or computational tasks),
  3543. they share the same OpenOCD infrastructure.
  3544. Accordingly, both are called PLDs here.
  3545. @section PLD/FPGA Configuration and Commands
  3546. As it does for JTAG TAPs, debug targets, and flash chips (both NOR and NAND),
  3547. OpenOCD maintains a list of PLDs available for use in various commands.
  3548. Also, each such PLD requires a driver.
  3549. They are referenced by the number shown by the @command{pld devices} command,
  3550. and new PLDs are defined by @command{pld device driver_name}.
  3551. @deffn {Config Command} {pld device} driver_name tap_name [driver_options]
  3552. Defines a new PLD device, supported by driver @var{driver_name},
  3553. using the TAP named @var{tap_name}.
  3554. The driver may make use of any @var{driver_options} to configure its
  3555. behavior.
  3556. @end deffn
  3557. @deffn {Command} {pld devices}
  3558. Lists the PLDs and their numbers.
  3559. @end deffn
  3560. @deffn {Command} {pld load} num filename
  3561. Loads the file @file{filename} into the PLD identified by @var{num}.
  3562. The file format must be inferred by the driver.
  3563. @end deffn
  3564. @section PLD/FPGA Drivers, Options, and Commands
  3565. Drivers may support PLD-specific options to the @command{pld device}
  3566. definition command, and may also define commands usable only with
  3567. that particular type of PLD.
  3568. @deffn {FPGA Driver} virtex2
  3569. Virtex-II is a family of FPGAs sold by Xilinx.
  3570. It supports the IEEE 1532 standard for In-System Configuration (ISC).
  3571. No driver-specific PLD definition options are used,
  3572. and one driver-specific command is defined.
  3573. @deffn {Command} {virtex2 read_stat} num
  3574. Reads and displays the Virtex-II status register (STAT)
  3575. for FPGA @var{num}.
  3576. @end deffn
  3577. @end deffn
  3578. @node General Commands
  3579. @chapter General Commands
  3580. @cindex commands
  3581. The commands documented in this chapter here are common commands that
  3582. you, as a human, may want to type and see the output of. Configuration type
  3583. commands are documented elsewhere.
  3584. Intent:
  3585. @itemize @bullet
  3586. @item @b{Source Of Commands}
  3587. @* OpenOCD commands can occur in a configuration script (discussed
  3588. elsewhere) or typed manually by a human or supplied programatically,
  3589. or via one of several TCP/IP Ports.
  3590. @item @b{From the human}
  3591. @* A human should interact with the telnet interface (default port: 4444)
  3592. or via GDB (default port 3333).
  3593. To issue commands from within a GDB session, use the @option{monitor}
  3594. command, e.g. use @option{monitor poll} to issue the @option{poll}
  3595. command. All output is relayed through the GDB session.
  3596. @item @b{Machine Interface}
  3597. The Tcl interface's intent is to be a machine interface. The default Tcl
  3598. port is 5555.
  3599. @end itemize
  3600. @section Daemon Commands
  3601. @deffn {Command} exit
  3602. Exits the current telnet session.
  3603. @end deffn
  3604. @c note EXTREMELY ANNOYING word wrap at column 75
  3605. @c even when lines are e.g. 100+ columns ...
  3606. @c coded in startup.tcl
  3607. @deffn {Command} help [string]
  3608. With no parameters, prints help text for all commands.
  3609. Otherwise, prints each helptext containing @var{string}.
  3610. Not every command provides helptext.
  3611. @end deffn
  3612. @deffn Command sleep msec [@option{busy}]
  3613. Wait for at least @var{msec} milliseconds before resuming.
  3614. If @option{busy} is passed, busy-wait instead of sleeping.
  3615. (This option is strongly discouraged.)
  3616. Useful in connection with script files
  3617. (@command{script} command and @command{target_name} configuration).
  3618. @end deffn
  3619. @deffn Command shutdown
  3620. Close the OpenOCD daemon, disconnecting all clients (GDB, telnet, other).
  3621. @end deffn
  3622. @anchor{debug_level}
  3623. @deffn Command debug_level [n]
  3624. @cindex message level
  3625. Display debug level.
  3626. If @var{n} (from 0..3) is provided, then set it to that level.
  3627. This affects the kind of messages sent to the server log.
  3628. Level 0 is error messages only;
  3629. level 1 adds warnings;
  3630. level 2 adds informational messages;
  3631. and level 3 adds debugging messages.
  3632. The default is level 2, but that can be overridden on
  3633. the command line along with the location of that log
  3634. file (which is normally the server's standard output).
  3635. @xref{Running}.
  3636. @end deffn
  3637. @deffn Command fast (@option{enable}|@option{disable})
  3638. Default disabled.
  3639. Set default behaviour of OpenOCD to be "fast and dangerous".
  3640. At this writing, this only affects the defaults for two ARM7/ARM9 parameters:
  3641. fast memory access, and DCC downloads. Those parameters may still be
  3642. individually overridden.
  3643. The target specific "dangerous" optimisation tweaking options may come and go
  3644. as more robust and user friendly ways are found to ensure maximum throughput
  3645. and robustness with a minimum of configuration.
  3646. Typically the "fast enable" is specified first on the command line:
  3647. @example
  3648. openocd -c "fast enable" -c "interface dummy" -f target/str710.cfg
  3649. @end example
  3650. @end deffn
  3651. @deffn Command echo message
  3652. Logs a message at "user" priority.
  3653. Output @var{message} to stdout.
  3654. @example
  3655. echo "Downloading kernel -- please wait"
  3656. @end example
  3657. @end deffn
  3658. @deffn Command log_output [filename]
  3659. Redirect logging to @var{filename};
  3660. the initial log output channel is stderr.
  3661. @end deffn
  3662. @anchor{Target State handling}
  3663. @section Target State handling
  3664. @cindex reset
  3665. @cindex halt
  3666. @cindex target initialization
  3667. In this section ``target'' refers to a CPU configured as
  3668. shown earlier (@pxref{CPU Configuration}).
  3669. These commands, like many, implicitly refer to
  3670. a current target which is used to perform the
  3671. various operations. The current target may be changed
  3672. by using @command{targets} command with the name of the
  3673. target which should become current.
  3674. @deffn Command reg [(number|name) [value]]
  3675. Access a single register by @var{number} or by its @var{name}.
  3676. @emph{With no arguments}:
  3677. list all available registers for the current target,
  3678. showing number, name, size, value, and cache status.
  3679. @emph{With number/name}: display that register's value.
  3680. @emph{With both number/name and value}: set register's value.
  3681. Cores may have surprisingly many registers in their
  3682. Debug and trace infrastructure:
  3683. @example
  3684. > reg
  3685. (0) r0 (/32): 0x0000D3C2 (dirty: 1, valid: 1)
  3686. (1) r1 (/32): 0xFD61F31C (dirty: 0, valid: 1)
  3687. (2) r2 (/32): 0x00022551 (dirty: 0, valid: 1)
  3688. ...
  3689. (164) ETM_CONTEXTID_COMPARATOR_MASK (/32): \
  3690. 0x00000000 (dirty: 0, valid: 0)
  3691. >
  3692. @end example
  3693. @end deffn
  3694. @deffn Command halt [ms]
  3695. @deffnx Command wait_halt [ms]
  3696. The @command{halt} command first sends a halt request to the target,
  3697. which @command{wait_halt} doesn't.
  3698. Otherwise these behave the same: wait up to @var{ms} milliseconds,
  3699. or 5 seconds if there is no parameter, for the target to halt
  3700. (and enter debug mode).
  3701. Using 0 as the @var{ms} parameter prevents OpenOCD from waiting.
  3702. @quotation Warning
  3703. On ARM cores, software using the @emph{wait for interrupt} operation
  3704. often blocks the JTAG access needed by a @command{halt} command.
  3705. This is because that operation also puts the core into a low
  3706. power mode by gating the core clock;
  3707. but the core clock is needed to detect JTAG clock transitions.
  3708. One partial workaround uses adaptive clocking: when the core is
  3709. interrupted the operation completes, then JTAG clocks are accepted
  3710. at least until the interrupt handler completes.
  3711. However, this workaround is often unusable since the processor, board,
  3712. and JTAG adapter must all support adaptive JTAG clocking.
  3713. Also, it can't work until an interrupt is issued.
  3714. A more complete workaround is to not use that operation while you
  3715. work with a JTAG debugger.
  3716. Tasking environments generaly have idle loops where the body is the
  3717. @emph{wait for interrupt} operation.
  3718. (On older cores, it is a coprocessor action;
  3719. newer cores have a @option{wfi} instruction.)
  3720. Such loops can just remove that operation, at the cost of higher
  3721. power consumption (because the CPU is needlessly clocked).
  3722. @end quotation
  3723. @end deffn
  3724. @deffn Command resume [address]
  3725. Resume the target at its current code position,
  3726. or the optional @var{address} if it is provided.
  3727. OpenOCD will wait 5 seconds for the target to resume.
  3728. @end deffn
  3729. @deffn Command step [address]
  3730. Single-step the target at its current code position,
  3731. or the optional @var{address} if it is provided.
  3732. @end deffn
  3733. @anchor{Reset Command}
  3734. @deffn Command reset
  3735. @deffnx Command {reset run}
  3736. @deffnx Command {reset halt}
  3737. @deffnx Command {reset init}
  3738. Perform as hard a reset as possible, using SRST if possible.
  3739. @emph{All defined targets will be reset, and target
  3740. events will fire during the reset sequence.}
  3741. The optional parameter specifies what should
  3742. happen after the reset.
  3743. If there is no parameter, a @command{reset run} is executed.
  3744. The other options will not work on all systems.
  3745. @xref{Reset Configuration}.
  3746. @itemize @minus
  3747. @item @b{run} Let the target run
  3748. @item @b{halt} Immediately halt the target
  3749. @item @b{init} Immediately halt the target, and execute the reset-init script
  3750. @end itemize
  3751. @end deffn
  3752. @deffn Command soft_reset_halt
  3753. Requesting target halt and executing a soft reset. This is often used
  3754. when a target cannot be reset and halted. The target, after reset is
  3755. released begins to execute code. OpenOCD attempts to stop the CPU and
  3756. then sets the program counter back to the reset vector. Unfortunately
  3757. the code that was executed may have left the hardware in an unknown
  3758. state.
  3759. @end deffn
  3760. @section I/O Utilities
  3761. These commands are available when
  3762. OpenOCD is built with @option{--enable-ioutil}.
  3763. They are mainly useful on embedded targets,
  3764. notably the ZY1000.
  3765. Hosts with operating systems have complementary tools.
  3766. @emph{Note:} there are several more such commands.
  3767. @deffn Command append_file filename [string]*
  3768. Appends the @var{string} parameters to
  3769. the text file @file{filename}.
  3770. Each string except the last one is followed by one space.
  3771. The last string is followed by a newline.
  3772. @end deffn
  3773. @deffn Command cat filename
  3774. Reads and displays the text file @file{filename}.
  3775. @end deffn
  3776. @deffn Command cp src_filename dest_filename
  3777. Copies contents from the file @file{src_filename}
  3778. into @file{dest_filename}.
  3779. @end deffn
  3780. @deffn Command ip
  3781. @emph{No description provided.}
  3782. @end deffn
  3783. @deffn Command ls
  3784. @emph{No description provided.}
  3785. @end deffn
  3786. @deffn Command mac
  3787. @emph{No description provided.}
  3788. @end deffn
  3789. @deffn Command meminfo
  3790. Display available RAM memory on OpenOCD host.
  3791. Used in OpenOCD regression testing scripts.
  3792. @end deffn
  3793. @deffn Command peek
  3794. @emph{No description provided.}
  3795. @end deffn
  3796. @deffn Command poke
  3797. @emph{No description provided.}
  3798. @end deffn
  3799. @deffn Command rm filename
  3800. @c "rm" has both normal and Jim-level versions??
  3801. Unlinks the file @file{filename}.
  3802. @end deffn
  3803. @deffn Command trunc filename
  3804. Removes all data in the file @file{filename}.
  3805. @end deffn
  3806. @anchor{Memory access}
  3807. @section Memory access commands
  3808. @cindex memory access
  3809. These commands allow accesses of a specific size to the memory
  3810. system. Often these are used to configure the current target in some
  3811. special way. For example - one may need to write certain values to the
  3812. SDRAM controller to enable SDRAM.
  3813. @enumerate
  3814. @item Use the @command{targets} (plural) command
  3815. to change the current target.
  3816. @item In system level scripts these commands are deprecated.
  3817. Please use their TARGET object siblings to avoid making assumptions
  3818. about what TAP is the current target, or about MMU configuration.
  3819. @end enumerate
  3820. @deffn Command mdw addr [count]
  3821. @deffnx Command mdh addr [count]
  3822. @deffnx Command mdb addr [count]
  3823. Display contents of address @var{addr}, as
  3824. 32-bit words (@command{mdw}), 16-bit halfwords (@command{mdh}),
  3825. or 8-bit bytes (@command{mdb}).
  3826. If @var{count} is specified, displays that many units.
  3827. (If you want to manipulate the data instead of displaying it,
  3828. see the @code{mem2array} primitives.)
  3829. @end deffn
  3830. @deffn Command mww addr word
  3831. @deffnx Command mwh addr halfword
  3832. @deffnx Command mwb addr byte
  3833. Writes the specified @var{word} (32 bits),
  3834. @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
  3835. at the specified address @var{addr}.
  3836. @end deffn
  3837. @anchor{Image access}
  3838. @section Image loading commands
  3839. @cindex image loading
  3840. @cindex image dumping
  3841. @anchor{dump_image}
  3842. @deffn Command {dump_image} filename address size
  3843. Dump @var{size} bytes of target memory starting at @var{address} to the
  3844. binary file named @var{filename}.
  3845. @end deffn
  3846. @deffn Command {fast_load}
  3847. Loads an image stored in memory by @command{fast_load_image} to the
  3848. current target. Must be preceeded by fast_load_image.
  3849. @end deffn
  3850. @deffn Command {fast_load_image} filename address [@option{bin}|@option{ihex}|@option{elf}]
  3851. Normally you should be using @command{load_image} or GDB load. However, for
  3852. testing purposes or when I/O overhead is significant(OpenOCD running on an embedded
  3853. host), storing the image in memory and uploading the image to the target
  3854. can be a way to upload e.g. multiple debug sessions when the binary does not change.
  3855. Arguments are the same as @command{load_image}, but the image is stored in OpenOCD host
  3856. memory, i.e. does not affect target. This approach is also useful when profiling
  3857. target programming performance as I/O and target programming can easily be profiled
  3858. separately.
  3859. @end deffn
  3860. @anchor{load_image}
  3861. @deffn Command {load_image} filename address [@option{bin}|@option{ihex}|@option{elf}]
  3862. Load image from file @var{filename} to target memory at @var{address}.
  3863. The file format may optionally be specified
  3864. (@option{bin}, @option{ihex}, or @option{elf})
  3865. @end deffn
  3866. @deffn Command {test_image} filename [address [@option{bin}|@option{ihex}|@option{elf}]]
  3867. Displays image section sizes and addresses
  3868. as if @var{filename} were loaded into target memory
  3869. starting at @var{address} (defaults to zero).
  3870. The file format may optionally be specified
  3871. (@option{bin}, @option{ihex}, or @option{elf})
  3872. @end deffn
  3873. @deffn Command {verify_image} filename address [@option{bin}|@option{ihex}|@option{elf}]
  3874. Verify @var{filename} against target memory starting at @var{address}.
  3875. The file format may optionally be specified
  3876. (@option{bin}, @option{ihex}, or @option{elf})
  3877. This will first attempt a comparison using a CRC checksum, if this fails it will try a binary compare.
  3878. @end deffn
  3879. @section Breakpoint and Watchpoint commands
  3880. @cindex breakpoint
  3881. @cindex watchpoint
  3882. CPUs often make debug modules accessible through JTAG, with
  3883. hardware support for a handful of code breakpoints and data
  3884. watchpoints.
  3885. In addition, CPUs almost always support software breakpoints.
  3886. @deffn Command {bp} [address len [@option{hw}]]
  3887. With no parameters, lists all active breakpoints.
  3888. Else sets a breakpoint on code execution starting
  3889. at @var{address} for @var{length} bytes.
  3890. This is a software breakpoint, unless @option{hw} is specified
  3891. in which case it will be a hardware breakpoint.
  3892. (@xref{arm9tdmi vector_catch}, or @pxref{xscale vector_catch},
  3893. for similar mechanisms that do not consume hardware breakpoints.)
  3894. @end deffn
  3895. @deffn Command {rbp} address
  3896. Remove the breakpoint at @var{address}.
  3897. @end deffn
  3898. @deffn Command {rwp} address
  3899. Remove data watchpoint on @var{address}
  3900. @end deffn
  3901. @deffn Command {wp} [address len [(@option{r}|@option{w}|@option{a}) [value [mask]]]]
  3902. With no parameters, lists all active watchpoints.
  3903. Else sets a data watchpoint on data from @var{address} for @var{length} bytes.
  3904. The watch point is an "access" watchpoint unless
  3905. the @option{r} or @option{w} parameter is provided,
  3906. defining it as respectively a read or write watchpoint.
  3907. If a @var{value} is provided, that value is used when determining if
  3908. the watchpoint should trigger. The value may be first be masked
  3909. using @var{mask} to mark ``don't care'' fields.
  3910. @end deffn
  3911. @section Misc Commands
  3912. @cindex profiling
  3913. @deffn Command {profile} seconds filename
  3914. Profiling samples the CPU's program counter as quickly as possible,
  3915. which is useful for non-intrusive stochastic profiling.
  3916. Saves up to 10000 sampines in @file{filename} using ``gmon.out'' format.
  3917. @end deffn
  3918. @deffn Command {version}
  3919. Displays a string identifying the version of this OpenOCD server.
  3920. @end deffn
  3921. @deffn Command {virt2phys} virtual_address
  3922. Requests the current target to map the specified @var{virtual_address}
  3923. to its corresponding physical address, and displays the result.
  3924. @end deffn
  3925. @node Architecture and Core Commands
  3926. @chapter Architecture and Core Commands
  3927. @cindex Architecture Specific Commands
  3928. @cindex Core Specific Commands
  3929. Most CPUs have specialized JTAG operations to support debugging.
  3930. OpenOCD packages most such operations in its standard command framework.
  3931. Some of those operations don't fit well in that framework, so they are
  3932. exposed here as architecture or implementation (core) specific commands.
  3933. @anchor{ARM Hardware Tracing}
  3934. @section ARM Hardware Tracing
  3935. @cindex tracing
  3936. @cindex ETM
  3937. @cindex ETB
  3938. CPUs based on ARM cores may include standard tracing interfaces,
  3939. based on an ``Embedded Trace Module'' (ETM) which sends voluminous
  3940. address and data bus trace records to a ``Trace Port''.
  3941. @itemize
  3942. @item
  3943. Development-oriented boards will sometimes provide a high speed
  3944. trace connector for collecting that data, when the particular CPU
  3945. supports such an interface.
  3946. (The standard connector is a 38-pin Mictor, with both JTAG
  3947. and trace port support.)
  3948. Those trace connectors are supported by higher end JTAG adapters
  3949. and some logic analyzer modules; frequently those modules can
  3950. buffer several megabytes of trace data.
  3951. Configuring an ETM coupled to such an external trace port belongs
  3952. in the board-specific configuration file.
  3953. @item
  3954. If the CPU doesn't provide an external interface, it probably
  3955. has an ``Embedded Trace Buffer'' (ETB) on the chip, which is a
  3956. dedicated SRAM. 4KBytes is one common ETB size.
  3957. Configuring an ETM coupled only to an ETB belongs in the CPU-specific
  3958. (target) configuration file, since it works the same on all boards.
  3959. @end itemize
  3960. ETM support in OpenOCD doesn't seem to be widely used yet.
  3961. @quotation Issues
  3962. ETM support may be buggy, and at least some @command{etm config}
  3963. parameters should be detected by asking the ETM for them.
  3964. It seems like a GDB hookup should be possible,
  3965. as well as triggering trace on specific events
  3966. (perhaps @emph{handling IRQ 23} or @emph{calls foo()}).
  3967. There should be GUI tools to manipulate saved trace data and help
  3968. analyse it in conjunction with the source code.
  3969. It's unclear how much of a common interface is shared
  3970. with the current XScale trace support, or should be
  3971. shared with eventual Nexus-style trace module support.
  3972. @end quotation
  3973. @subsection ETM Configuration
  3974. ETM setup is coupled with the trace port driver configuration.
  3975. @deffn {Config Command} {etm config} target width mode clocking driver
  3976. Declares the ETM associated with @var{target}, and associates it
  3977. with a given trace port @var{driver}. @xref{Trace Port Drivers}.
  3978. Several of the parameters must reflect the trace port configuration.
  3979. The @var{width} must be either 4, 8, or 16.
  3980. The @var{mode} must be @option{normal}, @option{multiplexted},
  3981. or @option{demultiplexted}.
  3982. The @var{clocking} must be @option{half} or @option{full}.
  3983. @quotation Note
  3984. You can see the ETM registers using the @command{reg} command, although
  3985. not all of those possible registers are present in every ETM.
  3986. @end quotation
  3987. @end deffn
  3988. @deffn Command {etm info}
  3989. Displays information about the current target's ETM.
  3990. @end deffn
  3991. @deffn Command {etm status}
  3992. Displays status of the current target's ETM:
  3993. is the ETM idle, or is it collecting data?
  3994. Did trace data overflow?
  3995. Was it triggered?
  3996. @end deffn
  3997. @deffn Command {etm tracemode} [type context_id_bits cycle_accurate branch_output]
  3998. Displays what data that ETM will collect.
  3999. If arguments are provided, first configures that data.
  4000. When the configuration changes, tracing is stopped
  4001. and any buffered trace data is invalidated.
  4002. @itemize
  4003. @item @var{type} ... one of
  4004. @option{none} (save nothing),
  4005. @option{data} (save data),
  4006. @option{address} (save addresses),
  4007. @option{all} (save data and addresses)
  4008. @item @var{context_id_bits} ... 0, 8, 16, or 32
  4009. @item @var{cycle_accurate} ... @option{enable} or @option{disable}
  4010. @item @var{branch_output} ... @option{enable} or @option{disable}
  4011. @end itemize
  4012. @end deffn
  4013. @deffn Command {etm trigger_percent} percent
  4014. @emph{Buggy and effectively a NOP ... @var{percent} from 2..100}
  4015. @end deffn
  4016. @subsection ETM Trace Operation
  4017. After setting up the ETM, you can use it to collect data.
  4018. That data can be exported to files for later analysis.
  4019. It can also be parsed with OpenOCD, for basic sanity checking.
  4020. @deffn Command {etm analyze}
  4021. Reads trace data into memory, if it wasn't already present.
  4022. Decodes and prints the data that was collected.
  4023. @end deffn
  4024. @deffn Command {etm dump} filename
  4025. Stores the captured trace data in @file{filename}.
  4026. @end deffn
  4027. @deffn Command {etm image} filename [base_address] [type]
  4028. Opens an image file.
  4029. @end deffn
  4030. @deffn Command {etm load} filename
  4031. Loads captured trace data from @file{filename}.
  4032. @end deffn
  4033. @deffn Command {etm start}
  4034. Starts trace data collection.
  4035. @end deffn
  4036. @deffn Command {etm stop}
  4037. Stops trace data collection.
  4038. @end deffn
  4039. @anchor{Trace Port Drivers}
  4040. @subsection Trace Port Drivers
  4041. To use an ETM trace port it must be associated with a driver.
  4042. @deffn {Trace Port Driver} dummy
  4043. Use the @option{dummy} driver if you are configuring an ETM that's
  4044. not connected to anything (on-chip ETB or off-chip trace connector).
  4045. @emph{This driver lets OpenOCD talk to the ETM, but it does not expose
  4046. any trace data collection.}
  4047. @deffn {Config Command} {etm_dummy config} target
  4048. Associates the ETM for @var{target} with a dummy driver.
  4049. @end deffn
  4050. @end deffn
  4051. @deffn {Trace Port Driver} etb
  4052. Use the @option{etb} driver if you are configuring an ETM
  4053. to use on-chip ETB memory.
  4054. @deffn {Config Command} {etb config} target etb_tap
  4055. Associates the ETM for @var{target} with the ETB at @var{etb_tap}.
  4056. You can see the ETB registers using the @command{reg} command.
  4057. @end deffn
  4058. @end deffn
  4059. @deffn {Trace Port Driver} oocd_trace
  4060. This driver isn't available unless OpenOCD was explicitly configured
  4061. with the @option{--enable-oocd_trace} option. You probably don't want
  4062. to configure it unless you've built the appropriate prototype hardware;
  4063. it's @emph{proof-of-concept} software.
  4064. Use the @option{oocd_trace} driver if you are configuring an ETM that's
  4065. connected to an off-chip trace connector.
  4066. @deffn {Config Command} {oocd_trace config} target tty
  4067. Associates the ETM for @var{target} with a trace driver which
  4068. collects data through the serial port @var{tty}.
  4069. @end deffn
  4070. @deffn Command {oocd_trace resync}
  4071. Re-synchronizes with the capture clock.
  4072. @end deffn
  4073. @deffn Command {oocd_trace status}
  4074. Reports whether the capture clock is locked or not.
  4075. @end deffn
  4076. @end deffn
  4077. @section ARMv4 and ARMv5 Architecture
  4078. @cindex ARMv4
  4079. @cindex ARMv5
  4080. These commands are specific to ARM architecture v4 and v5,
  4081. including all ARM7 or ARM9 systems and Intel XScale.
  4082. They are available in addition to other core-specific
  4083. commands that may be available.
  4084. @deffn Command {armv4_5 core_state} [@option{arm}|@option{thumb}]
  4085. Displays the core_state, optionally changing it to process
  4086. either @option{arm} or @option{thumb} instructions.
  4087. The target may later be resumed in the currently set core_state.
  4088. (Processors may also support the Jazelle state, but
  4089. that is not currently supported in OpenOCD.)
  4090. @end deffn
  4091. @deffn Command {armv4_5 disassemble} address [count [@option{thumb}]]
  4092. @cindex disassemble
  4093. Disassembles @var{count} instructions starting at @var{address}.
  4094. If @var{count} is not specified, a single instruction is disassembled.
  4095. If @option{thumb} is specified, or the low bit of the address is set,
  4096. Thumb (16-bit) instructions are used;
  4097. else ARM (32-bit) instructions are used.
  4098. (Processors may also support the Jazelle state, but
  4099. those instructions are not currently understood by OpenOCD.)
  4100. @end deffn
  4101. @deffn Command {armv4_5 reg}
  4102. Display a table of all banked core registers, fetching the current value from every
  4103. core mode if necessary. OpenOCD versions before rev. 60 didn't fetch the current
  4104. register value.
  4105. @end deffn
  4106. @subsection ARM7 and ARM9 specific commands
  4107. @cindex ARM7
  4108. @cindex ARM9
  4109. These commands are specific to ARM7 and ARM9 cores, like ARM7TDMI, ARM720T,
  4110. ARM9TDMI, ARM920T or ARM926EJ-S.
  4111. They are available in addition to the ARMv4/5 commands,
  4112. and any other core-specific commands that may be available.
  4113. @deffn Command {arm7_9 dbgrq} (@option{enable}|@option{disable})
  4114. Control use of the EmbeddedIce DBGRQ signal to force entry into debug mode,
  4115. instead of breakpoints. This should be
  4116. safe for all but ARM7TDMI--S cores (like Philips LPC).
  4117. This feature is enabled by default on most ARM9 cores,
  4118. including ARM9TDMI, ARM920T, and ARM926EJ-S.
  4119. @end deffn
  4120. @deffn Command {arm7_9 dcc_downloads} (@option{enable}|@option{disable})
  4121. @cindex DCC
  4122. Control the use of the debug communications channel (DCC) to write larger (>128 byte)
  4123. amounts of memory. DCC downloads offer a huge speed increase, but might be
  4124. unsafe, especially with targets running at very low speeds. This command was introduced
  4125. with OpenOCD rev. 60, and requires a few bytes of working area.
  4126. @end deffn
  4127. @anchor{arm7_9 fast_memory_access}
  4128. @deffn Command {arm7_9 fast_memory_access} (@option{enable}|@option{disable})
  4129. Enable or disable memory writes and reads that don't check completion of
  4130. the operation. This provides a huge speed increase, especially with USB JTAG
  4131. cables (FT2232), but might be unsafe if used with targets running at very low
  4132. speeds, like the 32kHz startup clock of an AT91RM9200.
  4133. @end deffn
  4134. @deffn {Debug Command} {arm7_9 write_core_reg} num mode word
  4135. @emph{This is intended for use while debugging OpenOCD; you probably
  4136. shouldn't use it.}
  4137. Writes a 32-bit @var{word} to register @var{num} (from 0 to 16)
  4138. as used in the specified @var{mode}
  4139. (where e.g. mode 16 is "user" and mode 19 is "supervisor";
  4140. the M4..M0 bits of the PSR).
  4141. Registers 0..15 are the normal CPU registers such as r0(0), r1(1) ... pc(15).
  4142. Register 16 is the mode-specific SPSR,
  4143. unless the specified mode is 0xffffffff (32-bit all-ones)
  4144. in which case register 16 is the CPSR.
  4145. The write goes directly to the CPU, bypassing the register cache.
  4146. @end deffn
  4147. @deffn {Debug Command} {arm7_9 write_xpsr} word (@option{0}|@option{1})
  4148. @emph{This is intended for use while debugging OpenOCD; you probably
  4149. shouldn't use it.}
  4150. If the second parameter is zero, writes @var{word} to the
  4151. Current Program Status register (CPSR).
  4152. Else writes @var{word} to the current mode's Saved PSR (SPSR).
  4153. In both cases, this bypasses the register cache.
  4154. @end deffn
  4155. @deffn {Debug Command} {arm7_9 write_xpsr_im8} byte rotate (@option{0}|@option{1})
  4156. @emph{This is intended for use while debugging OpenOCD; you probably
  4157. shouldn't use it.}
  4158. Writes eight bits to the CPSR or SPSR,
  4159. first rotating them by @math{2*rotate} bits,
  4160. and bypassing the register cache.
  4161. This has lower JTAG overhead than writing the entire CPSR or SPSR
  4162. with @command{arm7_9 write_xpsr}.
  4163. @end deffn
  4164. @subsection ARM720T specific commands
  4165. @cindex ARM720T
  4166. These commands are available to ARM720T based CPUs,
  4167. which are implementations of the ARMv4T architecture
  4168. based on the ARM7TDMI-S integer core.
  4169. They are available in addition to the ARMv4/5 and ARM7/ARM9 commands.
  4170. @deffn Command {arm720t cp15} regnum [value]
  4171. Display cp15 register @var{regnum};
  4172. else if a @var{value} is provided, that value is written to that register.
  4173. @end deffn
  4174. @deffn Command {arm720t mdw_phys} addr [count]
  4175. @deffnx Command {arm720t mdh_phys} addr [count]
  4176. @deffnx Command {arm720t mdb_phys} addr [count]
  4177. Display contents of physical address @var{addr}, as
  4178. 32-bit words (@command{mdw_phys}), 16-bit halfwords (@command{mdh_phys}),
  4179. or 8-bit bytes (@command{mdb_phys}).
  4180. If @var{count} is specified, displays that many units.
  4181. @end deffn
  4182. @deffn Command {arm720t mww_phys} addr word
  4183. @deffnx Command {arm720t mwh_phys} addr halfword
  4184. @deffnx Command {arm720t mwb_phys} addr byte
  4185. Writes the specified @var{word} (32 bits),
  4186. @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
  4187. at the specified physical address @var{addr}.
  4188. @end deffn
  4189. @deffn Command {arm720t virt2phys} va
  4190. Translate a virtual address @var{va} to a physical address
  4191. and display the result.
  4192. @end deffn
  4193. @subsection ARM9 specific commands
  4194. @cindex ARM9
  4195. ARM9-family cores are built around ARM9TDMI or ARM9E (including ARM9EJS)
  4196. integer processors.
  4197. Such cores include the ARM920T, ARM926EJ-S, and ARM966.
  4198. For historical reasons, one command shared by these cores starts
  4199. with the @command{arm9tdmi} prefix.
  4200. This is true even for ARM9E based processors, which implement the
  4201. ARMv5TE architecture instead of ARMv4T.
  4202. @c 9-june-2009: tried this on arm920t, it didn't work.
  4203. @c no-params always lists nothing caught, and that's how it acts.
  4204. @anchor{arm9tdmi vector_catch}
  4205. @deffn Command {arm9tdmi vector_catch} [@option{all}|@option{none}|list]
  4206. @cindex vector_catch
  4207. Vector Catch hardware provides a sort of dedicated breakpoint
  4208. for hardware events such as reset, interrupt, and abort.
  4209. You can use this to conserve normal breakpoint resources,
  4210. so long as you're not concerned with code that branches directly
  4211. to those hardware vectors.
  4212. This always finishes by listing the current configuration.
  4213. If parameters are provided, it first reconfigures the
  4214. vector catch hardware to intercept
  4215. @option{all} of the hardware vectors,
  4216. @option{none} of them,
  4217. or a list with one or more of the following:
  4218. @option{reset} @option{undef} @option{swi} @option{pabt} @option{dabt} @option{reserved}
  4219. @option{irq} @option{fiq}.
  4220. @end deffn
  4221. @subsection ARM920T specific commands
  4222. @cindex ARM920T
  4223. These commands are available to ARM920T based CPUs,
  4224. which are implementations of the ARMv4T architecture
  4225. built using the ARM9TDMI integer core.
  4226. They are available in addition to the ARMv4/5, ARM7/ARM9,
  4227. and ARM9TDMI commands.
  4228. @deffn Command {arm920t cache_info}
  4229. Print information about the caches found. This allows to see whether your target
  4230. is an ARM920T (2x16kByte cache) or ARM922T (2x8kByte cache).
  4231. @end deffn
  4232. @deffn Command {arm920t cp15} regnum [value]
  4233. Display cp15 register @var{regnum};
  4234. else if a @var{value} is provided, that value is written to that register.
  4235. @end deffn
  4236. @deffn Command {arm920t cp15i} opcode [value [address]]
  4237. Interpreted access using cp15 @var{opcode}.
  4238. If no @var{value} is provided, the result is displayed.
  4239. Else if that value is written using the specified @var{address},
  4240. or using zero if no other address is not provided.
  4241. @end deffn
  4242. @deffn Command {arm920t mdw_phys} addr [count]
  4243. @deffnx Command {arm920t mdh_phys} addr [count]
  4244. @deffnx Command {arm920t mdb_phys} addr [count]
  4245. Display contents of physical address @var{addr}, as
  4246. 32-bit words (@command{mdw_phys}), 16-bit halfwords (@command{mdh_phys}),
  4247. or 8-bit bytes (@command{mdb_phys}).
  4248. If @var{count} is specified, displays that many units.
  4249. @end deffn
  4250. @deffn Command {arm920t mww_phys} addr word
  4251. @deffnx Command {arm920t mwh_phys} addr halfword
  4252. @deffnx Command {arm920t mwb_phys} addr byte
  4253. Writes the specified @var{word} (32 bits),
  4254. @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
  4255. at the specified physical address @var{addr}.
  4256. @end deffn
  4257. @deffn Command {arm920t read_cache} filename
  4258. Dump the content of ICache and DCache to a file named @file{filename}.
  4259. @end deffn
  4260. @deffn Command {arm920t read_mmu} filename
  4261. Dump the content of the ITLB and DTLB to a file named @file{filename}.
  4262. @end deffn
  4263. @deffn Command {arm920t virt2phys} va
  4264. Translate a virtual address @var{va} to a physical address
  4265. and display the result.
  4266. @end deffn
  4267. @subsection ARM926ej-s specific commands
  4268. @cindex ARM926ej-s
  4269. These commands are available to ARM926ej-s based CPUs,
  4270. which are implementations of the ARMv5TEJ architecture
  4271. based on the ARM9EJ-S integer core.
  4272. They are available in addition to the ARMv4/5, ARM7/ARM9,
  4273. and ARM9TDMI commands.
  4274. The Feroceon cores also support these commands, although
  4275. they are not built from ARM926ej-s designs.
  4276. @deffn Command {arm926ejs cache_info}
  4277. Print information about the caches found.
  4278. @end deffn
  4279. @deffn Command {arm926ejs cp15} opcode1 opcode2 CRn CRm regnum [value]
  4280. Accesses cp15 register @var{regnum} using
  4281. @var{opcode1}, @var{opcode2}, @var{CRn}, and @var{CRm}.
  4282. If a @var{value} is provided, that value is written to that register.
  4283. Else that register is read and displayed.
  4284. @end deffn
  4285. @deffn Command {arm926ejs mdw_phys} addr [count]
  4286. @deffnx Command {arm926ejs mdh_phys} addr [count]
  4287. @deffnx Command {arm926ejs mdb_phys} addr [count]
  4288. Display contents of physical address @var{addr}, as
  4289. 32-bit words (@command{mdw_phys}), 16-bit halfwords (@command{mdh_phys}),
  4290. or 8-bit bytes (@command{mdb_phys}).
  4291. If @var{count} is specified, displays that many units.
  4292. @end deffn
  4293. @deffn Command {arm926ejs mww_phys} addr word
  4294. @deffnx Command {arm926ejs mwh_phys} addr halfword
  4295. @deffnx Command {arm926ejs mwb_phys} addr byte
  4296. Writes the specified @var{word} (32 bits),
  4297. @var{halfword} (16 bits), or @var{byte} (8-bit) pattern,
  4298. at the specified physical address @var{addr}.
  4299. @end deffn
  4300. @deffn Command {arm926ejs virt2phys} va
  4301. Translate a virtual address @var{va} to a physical address
  4302. and display the result.
  4303. @end deffn
  4304. @subsection ARM966E specific commands
  4305. @cindex ARM966E
  4306. These commands are available to ARM966 based CPUs,
  4307. which are implementations of the ARMv5TE architecture.
  4308. They are available in addition to the ARMv4/5, ARM7/ARM9,
  4309. and ARM9TDMI commands.
  4310. @deffn Command {arm966e cp15} regnum [value]
  4311. Display cp15 register @var{regnum};
  4312. else if a @var{value} is provided, that value is written to that register.
  4313. @end deffn
  4314. @subsection XScale specific commands
  4315. @cindex XScale
  4316. Some notes about the debug implementation on the XScale CPUs:
  4317. The XScale CPU provides a special debug-only mini-instruction cache
  4318. (mini-IC) in which exception vectors and target-resident debug handler
  4319. code are placed by OpenOCD. In order to get access to the CPU, OpenOCD
  4320. must point vector 0 (the reset vector) to the entry of the debug
  4321. handler. However, this means that the complete first cacheline in the
  4322. mini-IC is marked valid, which makes the CPU fetch all exception
  4323. handlers from the mini-IC, ignoring the code in RAM.
  4324. OpenOCD currently does not sync the mini-IC entries with the RAM
  4325. contents (which would fail anyway while the target is running), so
  4326. the user must provide appropriate values using the @code{xscale
  4327. vector_table} command.
  4328. It is recommended to place a pc-relative indirect branch in the vector
  4329. table, and put the branch destination somewhere in memory. Doing so
  4330. makes sure the code in the vector table stays constant regardless of
  4331. code layout in memory:
  4332. @example
  4333. _vectors:
  4334. ldr pc,[pc,#0x100-8]
  4335. ldr pc,[pc,#0x100-8]
  4336. ldr pc,[pc,#0x100-8]
  4337. ldr pc,[pc,#0x100-8]
  4338. ldr pc,[pc,#0x100-8]
  4339. ldr pc,[pc,#0x100-8]
  4340. ldr pc,[pc,#0x100-8]
  4341. ldr pc,[pc,#0x100-8]
  4342. .org 0x100
  4343. .long real_reset_vector
  4344. .long real_ui_handler
  4345. .long real_swi_handler
  4346. .long real_pf_abort
  4347. .long real_data_abort
  4348. .long 0 /* unused */
  4349. .long real_irq_handler
  4350. .long real_fiq_handler
  4351. @end example
  4352. The debug handler must be placed somewhere in the address space using
  4353. the @code{xscale debug_handler} command. The allowed locations for the
  4354. debug handler are either (0x800 - 0x1fef800) or (0xfe000800 -
  4355. 0xfffff800). The default value is 0xfe000800.
  4356. These commands are available to XScale based CPUs,
  4357. which are implementations of the ARMv5TE architecture.
  4358. @deffn Command {xscale analyze_trace}
  4359. Displays the contents of the trace buffer.
  4360. @end deffn
  4361. @deffn Command {xscale cache_clean_address} address
  4362. Changes the address used when cleaning the data cache.
  4363. @end deffn
  4364. @deffn Command {xscale cache_info}
  4365. Displays information about the CPU caches.
  4366. @end deffn
  4367. @deffn Command {xscale cp15} regnum [value]
  4368. Display cp15 register @var{regnum};
  4369. else if a @var{value} is provided, that value is written to that register.
  4370. @end deffn
  4371. @deffn Command {xscale debug_handler} target address
  4372. Changes the address used for the specified target's debug handler.
  4373. @end deffn
  4374. @deffn Command {xscale dcache} (@option{enable}|@option{disable})
  4375. Enables or disable the CPU's data cache.
  4376. @end deffn
  4377. @deffn Command {xscale dump_trace} filename
  4378. Dumps the raw contents of the trace buffer to @file{filename}.
  4379. @end deffn
  4380. @deffn Command {xscale icache} (@option{enable}|@option{disable})
  4381. Enables or disable the CPU's instruction cache.
  4382. @end deffn
  4383. @deffn Command {xscale mmu} (@option{enable}|@option{disable})
  4384. Enables or disable the CPU's memory management unit.
  4385. @end deffn
  4386. @deffn Command {xscale trace_buffer} (@option{enable}|@option{disable}) [@option{fill} [n] | @option{wrap}]
  4387. Enables or disables the trace buffer,
  4388. and controls how it is emptied.
  4389. @end deffn
  4390. @deffn Command {xscale trace_image} filename [offset [type]]
  4391. Opens a trace image from @file{filename}, optionally rebasing
  4392. its segment addresses by @var{offset}.
  4393. The image @var{type} may be one of
  4394. @option{bin} (binary), @option{ihex} (Intel hex),
  4395. @option{elf} (ELF file), @option{s19} (Motorola s19),
  4396. @option{mem}, or @option{builder}.
  4397. @end deffn
  4398. @anchor{xscale vector_catch}
  4399. @deffn Command {xscale vector_catch} [mask]
  4400. @cindex vector_catch
  4401. Display a bitmask showing the hardware vectors to catch.
  4402. If the optional parameter is provided, first set the bitmask to that value.
  4403. The mask bits correspond with bit 16..23 in the DCSR:
  4404. @example
  4405. 0x01 Trap Reset
  4406. 0x02 Trap Undefined Instructions
  4407. 0x04 Trap Software Interrupt
  4408. 0x08 Trap Prefetch Abort
  4409. 0x10 Trap Data Abort
  4410. 0x20 reserved
  4411. 0x40 Trap IRQ
  4412. 0x80 Trap FIQ
  4413. @end example
  4414. @end deffn
  4415. @anchor{xscale vector_table}
  4416. @deffn Command {xscale vector_table} [<low|high> <index> <value>]
  4417. @cindex vector_table
  4418. Set an entry in the mini-IC vector table. There are two tables: one for
  4419. low vectors (at 0x00000000), and one for high vectors (0xFFFF0000), each
  4420. holding the 8 exception vectors. @var{index} can be 1-7, because vector 0
  4421. points to the debug handler entry and can not be overwritten.
  4422. @var{value} holds the 32-bit opcode that is placed in the mini-IC.
  4423. Without arguments, the current settings are displayed.
  4424. @end deffn
  4425. @section ARMv6 Architecture
  4426. @cindex ARMv6
  4427. @subsection ARM11 specific commands
  4428. @cindex ARM11
  4429. @deffn Command {arm11 mcr} pX opc1 CRn CRm opc2 value
  4430. Write @var{value} to a coprocessor @var{pX} register
  4431. passing parameters @var{CRn},
  4432. @var{CRm}, opcodes @var{opc1} and @var{opc2},
  4433. and the MCR instruction.
  4434. (The difference beween this and the MCR2 instruction is
  4435. one bit in the encoding, effecively a fifth parameter.)
  4436. @end deffn
  4437. @deffn Command {arm11 memwrite burst} [value]
  4438. Displays the value of the memwrite burst-enable flag,
  4439. which is enabled by default.
  4440. If @var{value} is defined, first assigns that.
  4441. @end deffn
  4442. @deffn Command {arm11 memwrite error_fatal} [value]
  4443. Displays the value of the memwrite error_fatal flag,
  4444. which is enabled by default.
  4445. If @var{value} is defined, first assigns that.
  4446. @end deffn
  4447. @deffn Command {arm11 mrc} pX opc1 CRn CRm opc2
  4448. Read a coprocessor @var{pX} register passing parameters @var{CRn},
  4449. @var{CRm}, opcodes @var{opc1} and @var{opc2},
  4450. and the MRC instruction.
  4451. (The difference beween this and the MRC2 instruction is
  4452. one bit in the encoding, effecively a fifth parameter.)
  4453. Displays the result.
  4454. @end deffn
  4455. @deffn Command {arm11 no_increment} [value]
  4456. Displays the value of the flag controlling whether
  4457. some read or write operations increment the pointer
  4458. (the default behavior) or not (acting like a FIFO).
  4459. If @var{value} is defined, first assigns that.
  4460. @end deffn
  4461. @deffn Command {arm11 step_irq_enable} [value]
  4462. Displays the value of the flag controlling whether
  4463. IRQs are enabled during single stepping;
  4464. they is disabled by default.
  4465. If @var{value} is defined, first assigns that.
  4466. @end deffn
  4467. @section ARMv7 Architecture
  4468. @cindex ARMv7
  4469. @subsection ARMv7 Debug Access Port (DAP) specific commands
  4470. @cindex Debug Access Port
  4471. @cindex DAP
  4472. These commands are specific to ARM architecture v7 Debug Access Port (DAP),
  4473. included on cortex-m3 and cortex-a8 systems.
  4474. They are available in addition to other core-specific commands that may be available.
  4475. @deffn Command {dap info} [num]
  4476. Displays dap info for ap @var{num}, defaulting to the currently selected AP.
  4477. @end deffn
  4478. @deffn Command {dap apsel} [num]
  4479. Select AP @var{num}, defaulting to 0.
  4480. @end deffn
  4481. @deffn Command {dap apid} [num]
  4482. Displays id register from AP @var{num},
  4483. defaulting to the currently selected AP.
  4484. @end deffn
  4485. @deffn Command {dap baseaddr} [num]
  4486. Displays debug base address from AP @var{num},
  4487. defaulting to the currently selected AP.
  4488. @end deffn
  4489. @deffn Command {dap memaccess} [value]
  4490. Displays the number of extra tck for mem-ap memory bus access [0-255].
  4491. If @var{value} is defined, first assigns that.
  4492. @end deffn
  4493. @subsection ARMv7-A specific commands
  4494. @cindex ARMv7-A
  4495. @deffn Command {armv7a disassemble} address [count [@option{thumb}]]
  4496. @cindex disassemble
  4497. Disassembles @var{count} instructions starting at @var{address}.
  4498. If @var{count} is not specified, a single instruction is disassembled.
  4499. If @option{thumb} is specified, or the low bit of the address is set,
  4500. Thumb2 (mixed 16/32-bit) instructions are used;
  4501. else ARM (32-bit) instructions are used.
  4502. With a handful of exceptions, ThumbEE instructions are the same as Thumb2;
  4503. ThumbEE disassembly currently has no explicit support.
  4504. (Processors may also support the Jazelle state, but
  4505. those instructions are not currently understood by OpenOCD.)
  4506. @end deffn
  4507. @subsection Cortex-M3 specific commands
  4508. @cindex Cortex-M3
  4509. @deffn Command {cortex_m3 disassemble} address [count]
  4510. @cindex disassemble
  4511. Disassembles @var{count} Thumb2 instructions starting at @var{address}.
  4512. If @var{count} is not specified, a single instruction is disassembled.
  4513. @end deffn
  4514. @deffn Command {cortex_m3 maskisr} (@option{on}|@option{off})
  4515. Control masking (disabling) interrupts during target step/resume.
  4516. @end deffn
  4517. @deffn Command {cortex_m3 vector_catch} [@option{all}|@option{none}|list]
  4518. @cindex vector_catch
  4519. Vector Catch hardware provides dedicated breakpoints
  4520. for certain hardware events.
  4521. Parameters request interception of
  4522. @option{all} of these hardware event vectors,
  4523. @option{none} of them,
  4524. or one or more of the following:
  4525. @option{hard_err} for a HardFault exception;
  4526. @option{mm_err} for a MemManage exception;
  4527. @option{bus_err} for a BusFault exception;
  4528. @option{irq_err},
  4529. @option{state_err},
  4530. @option{chk_err}, or
  4531. @option{nocp_err} for various UsageFault exceptions; or
  4532. @option{reset}.
  4533. If NVIC setup code does not enable them,
  4534. MemManage, BusFault, and UsageFault exceptions
  4535. are mapped to HardFault.
  4536. UsageFault checks for
  4537. divide-by-zero and unaligned access
  4538. must also be explicitly enabled.
  4539. This finishes by listing the current vector catch configuration.
  4540. @end deffn
  4541. @anchor{Software Debug Messages and Tracing}
  4542. @section Software Debug Messages and Tracing
  4543. @cindex Linux-ARM DCC support
  4544. @cindex tracing
  4545. @cindex libdcc
  4546. @cindex DCC
  4547. OpenOCD can process certain requests from target software. Currently
  4548. @command{target_request debugmsgs}
  4549. is supported only for @option{arm7_9} and @option{cortex_m3} cores.
  4550. These messages are received as part of target polling, so
  4551. you need to have @command{poll on} active to receive them.
  4552. They are intrusive in that they will affect program execution
  4553. times. If that is a problem, @pxref{ARM Hardware Tracing}.
  4554. See @file{libdcc} in the contrib dir for more details.
  4555. In addition to sending strings, characters, and
  4556. arrays of various size integers from the target,
  4557. @file{libdcc} also exports a software trace point mechanism.
  4558. The target being debugged may
  4559. issue trace messages which include a 24-bit @dfn{trace point} number.
  4560. Trace point support includes two distinct mechanisms,
  4561. each supported by a command:
  4562. @itemize
  4563. @item @emph{History} ... A circular buffer of trace points
  4564. can be set up, and then displayed at any time.
  4565. This tracks where code has been, which can be invaluable in
  4566. finding out how some fault was triggered.
  4567. The buffer may overflow, since it collects records continuously.
  4568. It may be useful to use some of the 24 bits to represent a
  4569. particular event, and other bits to hold data.
  4570. @item @emph{Counting} ... An array of counters can be set up,
  4571. and then displayed at any time.
  4572. This can help establish code coverage and identify hot spots.
  4573. The array of counters is directly indexed by the trace point
  4574. number, so trace points with higher numbers are not counted.
  4575. @end itemize
  4576. Linux-ARM kernels have a ``Kernel low-level debugging
  4577. via EmbeddedICE DCC channel'' option (CONFIG_DEBUG_ICEDCC,
  4578. depends on CONFIG_DEBUG_LL) which uses this mechanism to
  4579. deliver messages before a serial console can be activated.
  4580. This is not the same format used by @file{libdcc}.
  4581. Other software, such as the U-Boot boot loader, sometimes
  4582. does the same thing.
  4583. @deffn Command {target_request debugmsgs} [@option{enable}|@option{disable}|@option{charmsg}]
  4584. Displays current handling of target DCC message requests.
  4585. These messages may be sent to the debugger while the target is running.
  4586. The optional @option{enable} and @option{charmsg} parameters
  4587. both enable the messages, while @option{disable} disables them.
  4588. With @option{charmsg} the DCC words each contain one character,
  4589. as used by Linux with CONFIG_DEBUG_ICEDCC;
  4590. otherwise the libdcc format is used.
  4591. @end deffn
  4592. @deffn Command {trace history} (@option{clear}|count)
  4593. With no parameter, displays all the trace points that have triggered
  4594. in the order they triggered.
  4595. With the parameter @option{clear}, erases all current trace history records.
  4596. With a @var{count} parameter, allocates space for that many
  4597. history records.
  4598. @end deffn
  4599. @deffn Command {trace point} (@option{clear}|identifier)
  4600. With no parameter, displays all trace point identifiers and how many times
  4601. they have been triggered.
  4602. With the parameter @option{clear}, erases all current trace point counters.
  4603. With a numeric @var{identifier} parameter, creates a new a trace point counter
  4604. and associates it with that identifier.
  4605. @emph{Important:} The identifier and the trace point number
  4606. are not related except by this command.
  4607. These trace point numbers always start at zero (from server startup,
  4608. or after @command{trace point clear}) and count up from there.
  4609. @end deffn
  4610. @node JTAG Commands
  4611. @chapter JTAG Commands
  4612. @cindex JTAG Commands
  4613. Most general purpose JTAG commands have been presented earlier.
  4614. (@xref{JTAG Speed}, @ref{Reset Configuration}, and @ref{TAP Declaration}.)
  4615. Lower level JTAG commands, as presented here,
  4616. may be needed to work with targets which require special
  4617. attention during operations such as reset or initialization.
  4618. To use these commands you will need to understand some
  4619. of the basics of JTAG, including:
  4620. @itemize @bullet
  4621. @item A JTAG scan chain consists of a sequence of individual TAP
  4622. devices such as a CPUs.
  4623. @item Control operations involve moving each TAP through the same
  4624. standard state machine (in parallel)
  4625. using their shared TMS and clock signals.
  4626. @item Data transfer involves shifting data through the chain of
  4627. instruction or data registers of each TAP, writing new register values
  4628. while the reading previous ones.
  4629. @item Data register sizes are a function of the instruction active in
  4630. a given TAP, while instruction register sizes are fixed for each TAP.
  4631. All TAPs support a BYPASS instruction with a single bit data register.
  4632. @item The way OpenOCD differentiates between TAP devices is by
  4633. shifting different instructions into (and out of) their instruction
  4634. registers.
  4635. @end itemize
  4636. @section Low Level JTAG Commands
  4637. These commands are used by developers who need to access
  4638. JTAG instruction or data registers, possibly controlling
  4639. the order of TAP state transitions.
  4640. If you're not debugging OpenOCD internals, or bringing up a
  4641. new JTAG adapter or a new type of TAP device (like a CPU or
  4642. JTAG router), you probably won't need to use these commands.
  4643. @deffn Command {drscan} tap [numbits value]+ [@option{-endstate} tap_state]
  4644. Loads the data register of @var{tap} with a series of bit fields
  4645. that specify the entire register.
  4646. Each field is @var{numbits} bits long with
  4647. a numeric @var{value} (hexadecimal encouraged).
  4648. The return value holds the original value of each
  4649. of those fields.
  4650. For example, a 38 bit number might be specified as one
  4651. field of 32 bits then one of 6 bits.
  4652. @emph{For portability, never pass fields which are more
  4653. than 32 bits long. Many OpenOCD implementations do not
  4654. support 64-bit (or larger) integer values.}
  4655. All TAPs other than @var{tap} must be in BYPASS mode.
  4656. The single bit in their data registers does not matter.
  4657. When @var{tap_state} is specified, the JTAG state machine is left
  4658. in that state.
  4659. For example @sc{drpause} might be specified, so that more
  4660. instructions can be issued before re-entering the @sc{run/idle} state.
  4661. If the end state is not specified, the @sc{run/idle} state is entered.
  4662. @quotation Warning
  4663. OpenOCD does not record information about data register lengths,
  4664. so @emph{it is important that you get the bit field lengths right}.
  4665. Remember that different JTAG instructions refer to different
  4666. data registers, which may have different lengths.
  4667. Moreover, those lengths may not be fixed;
  4668. the SCAN_N instruction can change the length of
  4669. the register accessed by the INTEST instruction
  4670. (by connecting a different scan chain).
  4671. @end quotation
  4672. @end deffn
  4673. @deffn Command {flush_count}
  4674. Returns the number of times the JTAG queue has been flushed.
  4675. This may be used for performance tuning.
  4676. For example, flushing a queue over USB involves a
  4677. minimum latency, often several milliseconds, which does
  4678. not change with the amount of data which is written.
  4679. You may be able to identify performance problems by finding
  4680. tasks which waste bandwidth by flushing small transfers too often,
  4681. instead of batching them into larger operations.
  4682. @end deffn
  4683. @deffn Command {irscan} [tap instruction]+ [@option{-endstate} tap_state]
  4684. For each @var{tap} listed, loads the instruction register
  4685. with its associated numeric @var{instruction}.
  4686. (The number of bits in that instruction may be displayed
  4687. using the @command{scan_chain} command.)
  4688. For other TAPs, a BYPASS instruction is loaded.
  4689. When @var{tap_state} is specified, the JTAG state machine is left
  4690. in that state.
  4691. For example @sc{irpause} might be specified, so the data register
  4692. can be loaded before re-entering the @sc{run/idle} state.
  4693. If the end state is not specified, the @sc{run/idle} state is entered.
  4694. @quotation Note
  4695. OpenOCD currently supports only a single field for instruction
  4696. register values, unlike data register values.
  4697. For TAPs where the instruction register length is more than 32 bits,
  4698. portable scripts currently must issue only BYPASS instructions.
  4699. @end quotation
  4700. @end deffn
  4701. @deffn Command {jtag_reset} trst srst
  4702. Set values of reset signals.
  4703. The @var{trst} and @var{srst} parameter values may be
  4704. @option{0}, indicating that reset is inactive (pulled or driven high),
  4705. or @option{1}, indicating it is active (pulled or driven low).
  4706. The @command{reset_config} command should already have been used
  4707. to configure how the board and JTAG adapter treat these two
  4708. signals, and to say if either signal is even present.
  4709. @xref{Reset Configuration}.
  4710. @end deffn
  4711. @deffn Command {runtest} @var{num_cycles}
  4712. Move to the @sc{run/idle} state, and execute at least
  4713. @var{num_cycles} of the JTAG clock (TCK).
  4714. Instructions often need some time
  4715. to execute before they take effect.
  4716. @end deffn
  4717. @c tms_sequence (short|long)
  4718. @c ... temporary, debug-only, probably gone before 0.2 ships
  4719. @deffn Command {verify_ircapture} (@option{enable}|@option{disable})
  4720. Verify values captured during @sc{ircapture} and returned
  4721. during IR scans. Default is enabled, but this can be
  4722. overridden by @command{verify_jtag}.
  4723. @end deffn
  4724. @deffn Command {verify_jtag} (@option{enable}|@option{disable})
  4725. Enables verification of DR and IR scans, to help detect
  4726. programming errors. For IR scans, @command{verify_ircapture}
  4727. must also be enabled.
  4728. Default is enabled.
  4729. @end deffn
  4730. @section TAP state names
  4731. @cindex TAP state names
  4732. The @var{tap_state} names used by OpenOCD in the @command{drscan},
  4733. and @command{irscan} commands are:
  4734. @itemize @bullet
  4735. @item @b{RESET} ... should act as if TRST were active
  4736. @item @b{RUN/IDLE} ... don't assume this always means IDLE
  4737. @item @b{DRSELECT}
  4738. @item @b{DRCAPTURE}
  4739. @item @b{DRSHIFT} ... TDI/TDO shifting through the data register
  4740. @item @b{DREXIT1}
  4741. @item @b{DRPAUSE} ... data register ready for update or more shifting
  4742. @item @b{DREXIT2}
  4743. @item @b{DRUPDATE}
  4744. @item @b{IRSELECT}
  4745. @item @b{IRCAPTURE}
  4746. @item @b{IRSHIFT} ... TDI/TDO shifting through the instruction register
  4747. @item @b{IREXIT1}
  4748. @item @b{IRPAUSE} ... instruction register ready for update or more shifting
  4749. @item @b{IREXIT2}
  4750. @item @b{IRUPDATE}
  4751. @end itemize
  4752. Note that only six of those states are fully ``stable'' in the
  4753. face of TMS fixed (low except for @sc{reset})
  4754. and a free-running JTAG clock. For all the
  4755. others, the next TCK transition changes to a new state.
  4756. @itemize @bullet
  4757. @item From @sc{drshift} and @sc{irshift}, clock transitions will
  4758. produce side effects by changing register contents. The values
  4759. to be latched in upcoming @sc{drupdate} or @sc{irupdate} states
  4760. may not be as expected.
  4761. @item @sc{run/idle}, @sc{drpause}, and @sc{irpause} are reasonable
  4762. choices after @command{drscan} or @command{irscan} commands,
  4763. since they are free of JTAG side effects.
  4764. However, @sc{run/idle} may have side effects that appear at other
  4765. levels, such as advancing the ARM9E-S instruction pipeline.
  4766. Consult the documentation for the TAP(s) you are working with.
  4767. @end itemize
  4768. @node Boundary Scan Commands
  4769. @chapter Boundary Scan Commands
  4770. One of the original purposes of JTAG was to support
  4771. boundary scan based hardware testing.
  4772. Although its primary focus is to support On-Chip Debugging,
  4773. OpenOCD also includes some boundary scan commands.
  4774. @section SVF: Serial Vector Format
  4775. @cindex Serial Vector Format
  4776. @cindex SVF
  4777. The Serial Vector Format, better known as @dfn{SVF}, is a
  4778. way to represent JTAG test patterns in text files.
  4779. OpenOCD supports running such test files.
  4780. @deffn Command {svf} filename [@option{quiet}]
  4781. This issues a JTAG reset (Test-Logic-Reset) and then
  4782. runs the SVF script from @file{filename}.
  4783. Unless the @option{quiet} option is specified,
  4784. each command is logged before it is executed.
  4785. @end deffn
  4786. @section XSVF: Xilinx Serial Vector Format
  4787. @cindex Xilinx Serial Vector Format
  4788. @cindex XSVF
  4789. The Xilinx Serial Vector Format, better known as @dfn{XSVF}, is a
  4790. binary representation of SVF which is optimized for use with
  4791. Xilinx devices.
  4792. OpenOCD supports running such test files.
  4793. @quotation Important
  4794. Not all XSVF commands are supported.
  4795. @end quotation
  4796. @deffn Command {xsvf} (tapname|@option{plain}) filename [@option{virt2}] [@option{quiet}]
  4797. This issues a JTAG reset (Test-Logic-Reset) and then
  4798. runs the XSVF script from @file{filename}.
  4799. When a @var{tapname} is specified, the commands are directed at
  4800. that TAP.
  4801. When @option{virt2} is specified, the @sc{xruntest} command counts
  4802. are interpreted as TCK cycles instead of microseconds.
  4803. Unless the @option{quiet} option is specified,
  4804. messages are logged for comments and some retries.
  4805. @end deffn
  4806. @node TFTP
  4807. @chapter TFTP
  4808. @cindex TFTP
  4809. If OpenOCD runs on an embedded host(as ZY1000 does), then TFTP can
  4810. be used to access files on PCs (either the developer's PC or some other PC).
  4811. The way this works on the ZY1000 is to prefix a filename by
  4812. "/tftp/ip/" and append the TFTP path on the TFTP
  4813. server (tftpd). For example,
  4814. @example
  4815. load_image /tftp/10.0.0.96/c:\temp\abc.elf
  4816. @end example
  4817. will load c:\temp\abc.elf from the developer pc (10.0.0.96) into memory as
  4818. if the file was hosted on the embedded host.
  4819. In order to achieve decent performance, you must choose a TFTP server
  4820. that supports a packet size bigger than the default packet size (512 bytes). There
  4821. are numerous TFTP servers out there (free and commercial) and you will have to do
  4822. a bit of googling to find something that fits your requirements.
  4823. @node GDB and OpenOCD
  4824. @chapter GDB and OpenOCD
  4825. @cindex GDB
  4826. OpenOCD complies with the remote gdbserver protocol, and as such can be used
  4827. to debug remote targets.
  4828. @anchor{Connecting to GDB}
  4829. @section Connecting to GDB
  4830. @cindex Connecting to GDB
  4831. Use GDB 6.7 or newer with OpenOCD if you run into trouble. For
  4832. instance GDB 6.3 has a known bug that produces bogus memory access
  4833. errors, which has since been fixed: look up 1836 in
  4834. @url{http://sourceware.org/cgi-bin/gnatsweb.pl?database=gdb}
  4835. OpenOCD can communicate with GDB in two ways:
  4836. @enumerate
  4837. @item
  4838. A socket (TCP/IP) connection is typically started as follows:
  4839. @example
  4840. target remote localhost:3333
  4841. @end example
  4842. This would cause GDB to connect to the gdbserver on the local pc using port 3333.
  4843. @item
  4844. A pipe connection is typically started as follows:
  4845. @example
  4846. target remote | openocd --pipe
  4847. @end example
  4848. This would cause GDB to run OpenOCD and communicate using pipes (stdin/stdout).
  4849. Using this method has the advantage of GDB starting/stopping OpenOCD for the debug
  4850. session.
  4851. @end enumerate
  4852. To list the available OpenOCD commands type @command{monitor help} on the
  4853. GDB command line.
  4854. OpenOCD supports the gdb @option{qSupported} packet, this enables information
  4855. to be sent by the GDB remote server (i.e. OpenOCD) to GDB. Typical information includes
  4856. packet size and the device's memory map.
  4857. Previous versions of OpenOCD required the following GDB options to increase
  4858. the packet size and speed up GDB communication:
  4859. @example
  4860. set remote memory-write-packet-size 1024
  4861. set remote memory-write-packet-size fixed
  4862. set remote memory-read-packet-size 1024
  4863. set remote memory-read-packet-size fixed
  4864. @end example
  4865. This is now handled in the @option{qSupported} PacketSize and should not be required.
  4866. @section Programming using GDB
  4867. @cindex Programming using GDB
  4868. By default the target memory map is sent to GDB. This can be disabled by
  4869. the following OpenOCD configuration option:
  4870. @example
  4871. gdb_memory_map disable
  4872. @end example
  4873. For this to function correctly a valid flash configuration must also be set
  4874. in OpenOCD. For faster performance you should also configure a valid
  4875. working area.
  4876. Informing GDB of the memory map of the target will enable GDB to protect any
  4877. flash areas of the target and use hardware breakpoints by default. This means
  4878. that the OpenOCD option @command{gdb_breakpoint_override} is not required when
  4879. using a memory map. @xref{gdb_breakpoint_override}.
  4880. To view the configured memory map in GDB, use the GDB command @option{info mem}
  4881. All other unassigned addresses within GDB are treated as RAM.
  4882. GDB 6.8 and higher set any memory area not in the memory map as inaccessible.
  4883. This can be changed to the old behaviour by using the following GDB command
  4884. @example
  4885. set mem inaccessible-by-default off
  4886. @end example
  4887. If @command{gdb_flash_program enable} is also used, GDB will be able to
  4888. program any flash memory using the vFlash interface.
  4889. GDB will look at the target memory map when a load command is given, if any
  4890. areas to be programmed lie within the target flash area the vFlash packets
  4891. will be used.
  4892. If the target needs configuring before GDB programming, an event
  4893. script can be executed:
  4894. @example
  4895. $_TARGETNAME configure -event EVENTNAME BODY
  4896. @end example
  4897. To verify any flash programming the GDB command @option{compare-sections}
  4898. can be used.
  4899. @node Tcl Scripting API
  4900. @chapter Tcl Scripting API
  4901. @cindex Tcl Scripting API
  4902. @cindex Tcl scripts
  4903. @section API rules
  4904. The commands are stateless. E.g. the telnet command line has a concept
  4905. of currently active target, the Tcl API proc's take this sort of state
  4906. information as an argument to each proc.
  4907. There are three main types of return values: single value, name value
  4908. pair list and lists.
  4909. Name value pair. The proc 'foo' below returns a name/value pair
  4910. list.
  4911. @verbatim
  4912. > set foo(me) Duane
  4913. > set foo(you) Oyvind
  4914. > set foo(mouse) Micky
  4915. > set foo(duck) Donald
  4916. If one does this:
  4917. > set foo
  4918. The result is:
  4919. me Duane you Oyvind mouse Micky duck Donald
  4920. Thus, to get the names of the associative array is easy:
  4921. foreach { name value } [set foo] {
  4922. puts "Name: $name, Value: $value"
  4923. }
  4924. @end verbatim
  4925. Lists returned must be relatively small. Otherwise a range
  4926. should be passed in to the proc in question.
  4927. @section Internal low-level Commands
  4928. By low-level, the intent is a human would not directly use these commands.
  4929. Low-level commands are (should be) prefixed with "ocd_", e.g.
  4930. @command{ocd_flash_banks}
  4931. is the low level API upon which @command{flash banks} is implemented.
  4932. @itemize @bullet
  4933. @item @b{ocd_mem2array} <@var{varname}> <@var{width}> <@var{addr}> <@var{nelems}>
  4934. Read memory and return as a Tcl array for script processing
  4935. @item @b{ocd_array2mem} <@var{varname}> <@var{width}> <@var{addr}> <@var{nelems}>
  4936. Convert a Tcl array to memory locations and write the values
  4937. @item @b{ocd_flash_banks} <@var{driver}> <@var{base}> <@var{size}> <@var{chip_width}> <@var{bus_width}> <@var{target}> [@option{driver options} ...]
  4938. Return information about the flash banks
  4939. @end itemize
  4940. OpenOCD commands can consist of two words, e.g. "flash banks". The
  4941. @file{startup.tcl} "unknown" proc will translate this into a Tcl proc
  4942. called "flash_banks".
  4943. @section OpenOCD specific Global Variables
  4944. @subsection HostOS
  4945. Real Tcl has ::tcl_platform(), and platform::identify, and many other
  4946. variables. JimTCL, as implemented in OpenOCD creates $HostOS which
  4947. holds one of the following values:
  4948. @itemize @bullet
  4949. @item @b{winxx} Built using Microsoft Visual Studio
  4950. @item @b{linux} Linux is the underlying operating sytem
  4951. @item @b{darwin} Darwin (mac-os) is the underlying operating sytem.
  4952. @item @b{cygwin} Running under Cygwin
  4953. @item @b{mingw32} Running under MingW32
  4954. @item @b{other} Unknown, none of the above.
  4955. @end itemize
  4956. Note: 'winxx' was choosen because today (March-2009) no distinction is made between Win32 and Win64.
  4957. @quotation Note
  4958. We should add support for a variable like Tcl variable
  4959. @code{tcl_platform(platform)}, it should be called
  4960. @code{jim_platform} (because it
  4961. is jim, not real tcl).
  4962. @end quotation
  4963. @node Upgrading
  4964. @chapter Deprecated/Removed Commands
  4965. @cindex Deprecated/Removed Commands
  4966. Certain OpenOCD commands have been deprecated or
  4967. removed during the various revisions.
  4968. Upgrade your scripts as soon as possible.
  4969. These descriptions for old commands may be removed
  4970. a year after the command itself was removed.
  4971. This means that in January 2010 this chapter may
  4972. become much shorter.
  4973. @itemize @bullet
  4974. @item @b{arm7_9 fast_writes}
  4975. @cindex arm7_9 fast_writes
  4976. @*Use @command{arm7_9 fast_memory_access} instead.
  4977. @xref{arm7_9 fast_memory_access}.
  4978. @item @b{endstate}
  4979. @cindex endstate
  4980. @*An buggy old command that would not really work since background polling would wipe out the global endstate
  4981. @item @b{arm7_9 force_hw_bkpts}
  4982. @*Use @command{gdb_breakpoint_override} instead. Note that GDB will use hardware breakpoints
  4983. for flash if the GDB memory map has been set up(default when flash is declared in
  4984. target configuration). @xref{gdb_breakpoint_override}.
  4985. @item @b{arm7_9 sw_bkpts}
  4986. @*On by default. @xref{gdb_breakpoint_override}.
  4987. @item @b{daemon_startup}
  4988. @*this config option has been removed, simply adding @option{init} and @option{reset halt} to
  4989. the end of your config script will give the same behaviour as using @option{daemon_startup reset}
  4990. and @option{target cortex_m3 little reset_halt 0}.
  4991. @item @b{dump_binary}
  4992. @*use @option{dump_image} command with same args. @xref{dump_image}.
  4993. @item @b{flash erase}
  4994. @*use @option{flash erase_sector} command with same args. @xref{flash erase_sector}.
  4995. @item @b{flash write}
  4996. @*use @option{flash write_bank} command with same args. @xref{flash write_bank}.
  4997. @item @b{flash write_binary}
  4998. @*use @option{flash write_bank} command with same args. @xref{flash write_bank}.
  4999. @item @b{flash auto_erase}
  5000. @*use @option{flash write_image} command passing @option{erase} as the first parameter. @xref{flash write_image}.
  5001. @item @b{jtag_device}
  5002. @*use the @command{jtag newtap} command, converting from positional syntax
  5003. to named prefixes, and naming the TAP.
  5004. @xref{jtag newtap}.
  5005. Note that if you try to use the old command, a message will tell you the
  5006. right new command to use; and that the fourth parameter in the old syntax
  5007. was never actually used.
  5008. @example
  5009. OLD: jtag_device 8 0x01 0xe3 0xfe
  5010. NEW: jtag newtap CHIPNAME TAPNAME \
  5011. -irlen 8 -ircapture 0x01 -irmask 0xe3
  5012. @end example
  5013. @item @b{jtag_speed} value
  5014. @*@xref{JTAG Speed}.
  5015. Usually, a value of zero means maximum
  5016. speed. The actual effect of this option depends on the JTAG interface used.
  5017. @itemize @minus
  5018. @item wiggler: maximum speed / @var{number}
  5019. @item ft2232: 6MHz / (@var{number}+1)
  5020. @item amt jtagaccel: 8 / 2**@var{number}
  5021. @item jlink: maximum speed in kHz (0-12000), 0 will use RTCK
  5022. @item rlink: 24MHz / @var{number}, but only for certain values of @var{number}
  5023. @comment end speed list.
  5024. @end itemize
  5025. @item @b{load_binary}
  5026. @*use @option{load_image} command with same args. @xref{load_image}.
  5027. @item @b{run_and_halt_time}
  5028. @*This command has been removed for simpler reset behaviour, it can be simulated with the
  5029. following commands:
  5030. @smallexample
  5031. reset run
  5032. sleep 100
  5033. halt
  5034. @end smallexample
  5035. @item @b{target} <@var{type}> <@var{endian}> <@var{jtag-position}>
  5036. @*use the create subcommand of @option{target}.
  5037. @item @b{target_script} <@var{target#}> <@var{eventname}> <@var{scriptname}>
  5038. @*use <@var{target_name}> configure -event <@var{eventname}> "script <@var{scriptname}>"
  5039. @item @b{working_area}
  5040. @*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.
  5041. @end itemize
  5042. @node FAQ
  5043. @chapter FAQ
  5044. @cindex faq
  5045. @enumerate
  5046. @anchor{FAQ RTCK}
  5047. @item @b{RTCK, also known as: Adaptive Clocking - What is it?}
  5048. @cindex RTCK
  5049. @cindex adaptive clocking
  5050. @*
  5051. In digital circuit design it is often refered to as ``clock
  5052. synchronisation'' the JTAG interface uses one clock (TCK or TCLK)
  5053. operating at some speed, your target is operating at another. The two
  5054. clocks are not synchronised, they are ``asynchronous''
  5055. In order for the two to work together they must be synchronised. Otherwise
  5056. the two systems will get out of sync with each other and nothing will
  5057. work. There are 2 basic options:
  5058. @enumerate
  5059. @item
  5060. Use a special circuit.
  5061. @item
  5062. One clock must be some multiple slower than the other.
  5063. @end enumerate
  5064. @b{Does this really matter?} For some chips and some situations, this
  5065. is a non-issue (i.e.: A 500MHz ARM926) but for others - for example some
  5066. Atmel SAM7 and SAM9 chips start operation from reset at 32kHz -
  5067. program/enable the oscillators and eventually the main clock. It is in
  5068. those critical times you must slow the JTAG clock to sometimes 1 to
  5069. 4kHz.
  5070. Imagine debugging a 500MHz ARM926 hand held battery powered device
  5071. that ``deep sleeps'' at 32kHz between every keystroke. It can be
  5072. painful.
  5073. @b{Solution #1 - A special circuit}
  5074. In order to make use of this, your JTAG dongle must support the RTCK
  5075. feature. Not all dongles support this - keep reading!
  5076. The RTCK signal often found in some ARM chips is used to help with
  5077. this problem. ARM has a good description of the problem described at
  5078. this link: @url{http://www.arm.com/support/faqdev/4170.html} [checked
  5079. 28/nov/2008]. Link title: ``How does the JTAG synchronisation logic
  5080. work? / how does adaptive clocking work?''.
  5081. The nice thing about adaptive clocking is that ``battery powered hand
  5082. held device example'' - the adaptiveness works perfectly all the
  5083. time. One can set a break point or halt the system in the deep power
  5084. down code, slow step out until the system speeds up.
  5085. Note that adaptive clocking may also need to work at the board level,
  5086. when a board-level scan chain has multiple chips.
  5087. Parallel clock voting schemes are good way to implement this,
  5088. both within and between chips, and can easily be implemented
  5089. with a CPLD.
  5090. It's not difficult to have logic fan a module's input TCK signal out
  5091. to each TAP in the scan chain, and then wait until each TAP's RTCK comes
  5092. back with the right polarity before changing the output RTCK signal.
  5093. Texas Instruments makes some clock voting logic available
  5094. for free (with no support) in VHDL form; see
  5095. @url{http://tiexpressdsp.com/index.php/Adaptive_Clocking}
  5096. @b{Solution #2 - Always works - but may be slower}
  5097. Often this is a perfectly acceptable solution.
  5098. In most simple terms: Often the JTAG clock must be 1/10 to 1/12 of
  5099. the target clock speed. But what that ``magic division'' is varies
  5100. depending on the chips on your board.
  5101. @b{ARM rule of thumb} Most ARM based systems require an 6:1 division;
  5102. ARM11 cores use an 8:1 division.
  5103. @b{Xilinx rule of thumb} is 1/12 the clock speed.
  5104. Note: Many FTDI2232C based JTAG dongles are limited to 6MHz.
  5105. You can still debug the 'low power' situations - you just need to
  5106. manually adjust the clock speed at every step. While painful and
  5107. tedious, it is not always practical.
  5108. It is however easy to ``code your way around it'' - i.e.: Cheat a little,
  5109. have a special debug mode in your application that does a ``high power
  5110. sleep''. If you are careful - 98% of your problems can be debugged
  5111. this way.
  5112. Note that on ARM you may need to avoid using the @emph{wait for interrupt}
  5113. operation in your idle loops even if you don't otherwise change the CPU
  5114. clock rate.
  5115. That operation gates the CPU clock, and thus the JTAG clock; which
  5116. prevents JTAG access. One consequence is not being able to @command{halt}
  5117. cores which are executing that @emph{wait for interrupt} operation.
  5118. To set the JTAG frequency use the command:
  5119. @example
  5120. # Example: 1.234MHz
  5121. jtag_khz 1234
  5122. @end example
  5123. @item @b{Win32 Pathnames} Why don't backslashes work in Windows paths?
  5124. OpenOCD uses Tcl and a backslash is an escape char. Use @{ and @}
  5125. around Windows filenames.
  5126. @example
  5127. > echo \a
  5128. > echo @{\a@}
  5129. \a
  5130. > echo "\a"
  5131. >
  5132. @end example
  5133. @item @b{Missing: cygwin1.dll} OpenOCD complains about a missing cygwin1.dll.
  5134. Make sure you have Cygwin installed, or at least a version of OpenOCD that
  5135. claims to come with all the necessary DLLs. When using Cygwin, try launching
  5136. OpenOCD from the Cygwin shell.
  5137. @item @b{Breakpoint Issue} I'm trying to set a breakpoint using GDB (or a frontend like Insight or
  5138. Eclipse), but OpenOCD complains that "Info: arm7_9_common.c:213
  5139. arm7_9_add_breakpoint(): sw breakpoint requested, but software breakpoints not enabled".
  5140. GDB issues software breakpoints when a normal breakpoint is requested, or to implement
  5141. source-line single-stepping. On ARMv4T systems, like ARM7TDMI, ARM720T or ARM920T,
  5142. software breakpoints consume one of the two available hardware breakpoints.
  5143. @item @b{LPC2000 Flash} When erasing or writing LPC2000 on-chip flash, the operation fails at random.
  5144. Make sure the core frequency specified in the @option{flash lpc2000} line matches the
  5145. clock at the time you're programming the flash. If you've specified the crystal's
  5146. frequency, make sure the PLL is disabled. If you've specified the full core speed
  5147. (e.g. 60MHz), make sure the PLL is enabled.
  5148. @item @b{Amontec Chameleon} When debugging using an Amontec Chameleon in its JTAG Accelerator configuration,
  5149. I keep getting "Error: amt_jtagaccel.c:184 amt_wait_scan_busy(): amt_jtagaccel timed
  5150. out while waiting for end of scan, rtck was disabled".
  5151. Make sure your PC's parallel port operates in EPP mode. You might have to try several
  5152. settings in your PC BIOS (ECP, EPP, and different versions of those).
  5153. @item @b{Data Aborts} When debugging with OpenOCD and GDB (plain GDB, Insight, or Eclipse),
  5154. I get lots of "Error: arm7_9_common.c:1771 arm7_9_read_memory():
  5155. memory read caused data abort".
  5156. The errors are non-fatal, and are the result of GDB trying to trace stack frames
  5157. beyond the last valid frame. It might be possible to prevent this by setting up
  5158. a proper "initial" stack frame, if you happen to know what exactly has to
  5159. be done, feel free to add this here.
  5160. @b{Simple:} In your startup code - push 8 registers of zeros onto the
  5161. stack before calling main(). What GDB is doing is ``climbing'' the run
  5162. time stack by reading various values on the stack using the standard
  5163. call frame for the target. GDB keeps going - until one of 2 things
  5164. happen @b{#1} an invalid frame is found, or @b{#2} some huge number of
  5165. stackframes have been processed. By pushing zeros on the stack, GDB
  5166. gracefully stops.
  5167. @b{Debugging Interrupt Service Routines} - In your ISR before you call
  5168. your C code, do the same - artifically push some zeros onto the stack,
  5169. remember to pop them off when the ISR is done.
  5170. @b{Also note:} If you have a multi-threaded operating system, they
  5171. often do not @b{in the intrest of saving memory} waste these few
  5172. bytes. Painful...
  5173. @item @b{JTAG Reset Config} I get the following message in the OpenOCD console (or log file):
  5174. "Warning: arm7_9_common.c:679 arm7_9_assert_reset(): srst resets test logic, too".
  5175. This warning doesn't indicate any serious problem, as long as you don't want to
  5176. debug your core right out of reset. Your .cfg file specified @option{jtag_reset
  5177. trst_and_srst srst_pulls_trst} to tell OpenOCD that either your board,
  5178. your debugger or your target uC (e.g. LPC2000) can't assert the two reset signals
  5179. independently. With this setup, it's not possible to halt the core right out of
  5180. reset, everything else should work fine.
  5181. @item @b{USB Power} When using OpenOCD in conjunction with Amontec JTAGkey and the Yagarto
  5182. toolchain (Eclipse, arm-elf-gcc, arm-elf-gdb), the debugging seems to be
  5183. unstable. When single-stepping over large blocks of code, GDB and OpenOCD
  5184. quit with an error message. Is there a stability issue with OpenOCD?
  5185. No, this is not a stability issue concerning OpenOCD. Most users have solved
  5186. this issue by simply using a self-powered USB hub, which they connect their
  5187. Amontec JTAGkey to. Apparently, some computers do not provide a USB power
  5188. supply stable enough for the Amontec JTAGkey to be operated.
  5189. @b{Laptops running on battery have this problem too...}
  5190. @item @b{USB Power} When using the Amontec JTAGkey, sometimes OpenOCD crashes with the
  5191. following error messages: "Error: ft2232.c:201 ft2232_read(): FT_Read returned:
  5192. 4" and "Error: ft2232.c:365 ft2232_send_and_recv(): couldn't read from FT2232".
  5193. What does that mean and what might be the reason for this?
  5194. First of all, the reason might be the USB power supply. Try using a self-powered
  5195. hub instead of a direct connection to your computer. Secondly, the error code 4
  5196. corresponds to an FT_IO_ERROR, which means that the driver for the FTDI USB
  5197. chip ran into some sort of error - this points us to a USB problem.
  5198. @item @b{GDB Disconnects} When using the Amontec JTAGkey, sometimes OpenOCD crashes with the following
  5199. error message: "Error: gdb_server.c:101 gdb_get_char(): read: 10054".
  5200. What does that mean and what might be the reason for this?
  5201. Error code 10054 corresponds to WSAECONNRESET, which means that the debugger (GDB)
  5202. has closed the connection to OpenOCD. This might be a GDB issue.
  5203. @item @b{LPC2000 Flash} In the configuration file in the section where flash device configurations
  5204. are described, there is a parameter for specifying the clock frequency
  5205. for LPC2000 internal flash devices (e.g. @option{flash bank lpc2000
  5206. 0x0 0x40000 0 0 0 lpc2000_v1 14746 calc_checksum}), which must be
  5207. specified in kilohertz. However, I do have a quartz crystal of a
  5208. frequency that contains fractions of kilohertz (e.g. 14,745,600 Hz,
  5209. i.e. 14,745.600 kHz). Is it possible to specify real numbers for the
  5210. clock frequency?
  5211. No. The clock frequency specified here must be given as an integral number.
  5212. However, this clock frequency is used by the In-Application-Programming (IAP)
  5213. routines of the LPC2000 family only, which seems to be very tolerant concerning
  5214. the given clock frequency, so a slight difference between the specified clock
  5215. frequency and the actual clock frequency will not cause any trouble.
  5216. @item @b{Command Order} Do I have to keep a specific order for the commands in the configuration file?
  5217. Well, yes and no. Commands can be given in arbitrary order, yet the
  5218. devices listed for the JTAG scan chain must be given in the right
  5219. order (jtag newdevice), with the device closest to the TDO-Pin being
  5220. listed first. In general, whenever objects of the same type exist
  5221. which require an index number, then these objects must be given in the
  5222. right order (jtag newtap, targets and flash banks - a target
  5223. references a jtag newtap and a flash bank references a target).
  5224. You can use the ``scan_chain'' command to verify and display the tap order.
  5225. Also, some commands can't execute until after @command{init} has been
  5226. processed. Such commands include @command{nand probe} and everything
  5227. else that needs to write to controller registers, perhaps for setting
  5228. up DRAM and loading it with code.
  5229. @anchor{FAQ TAP Order}
  5230. @item @b{JTAG TAP Order} Do I have to declare the TAPS in some
  5231. particular order?
  5232. Yes; whenever you have more than one, you must declare them in
  5233. the same order used by the hardware.
  5234. Many newer devices have multiple JTAG TAPs. For example: ST
  5235. Microsystems STM32 chips have two TAPs, a ``boundary scan TAP'' and
  5236. ``Cortex-M3'' TAP. Example: The STM32 reference manual, Document ID:
  5237. RM0008, Section 26.5, Figure 259, page 651/681, the ``TDI'' pin is
  5238. connected to the boundary scan TAP, which then connects to the
  5239. Cortex-M3 TAP, which then connects to the TDO pin.
  5240. Thus, the proper order for the STM32 chip is: (1) The Cortex-M3, then
  5241. (2) The boundary scan TAP. If your board includes an additional JTAG
  5242. chip in the scan chain (for example a Xilinx CPLD or FPGA) you could
  5243. place it before or after the STM32 chip in the chain. For example:
  5244. @itemize @bullet
  5245. @item OpenOCD_TDI(output) -> STM32 TDI Pin (BS Input)
  5246. @item STM32 BS TDO (output) -> STM32 Cortex-M3 TDI (input)
  5247. @item STM32 Cortex-M3 TDO (output) -> SM32 TDO Pin
  5248. @item STM32 TDO Pin (output) -> Xilinx TDI Pin (input)
  5249. @item Xilinx TDO Pin -> OpenOCD TDO (input)
  5250. @end itemize
  5251. The ``jtag device'' commands would thus be in the order shown below. Note:
  5252. @itemize @bullet
  5253. @item jtag newtap Xilinx tap -irlen ...
  5254. @item jtag newtap stm32 cpu -irlen ...
  5255. @item jtag newtap stm32 bs -irlen ...
  5256. @item # Create the debug target and say where it is
  5257. @item target create stm32.cpu -chain-position stm32.cpu ...
  5258. @end itemize
  5259. @item @b{SYSCOMP} Sometimes my debugging session terminates with an error. When I look into the
  5260. log file, I can see these error messages: Error: arm7_9_common.c:561
  5261. arm7_9_execute_sys_speed(): timeout waiting for SYSCOMP
  5262. TODO.
  5263. @end enumerate
  5264. @node Tcl Crash Course
  5265. @chapter Tcl Crash Course
  5266. @cindex Tcl
  5267. Not everyone knows Tcl - this is not intended to be a replacement for
  5268. learning Tcl, the intent of this chapter is to give you some idea of
  5269. how the Tcl scripts work.
  5270. This chapter is written with two audiences in mind. (1) OpenOCD users
  5271. who need to understand a bit more of how JIM-Tcl works so they can do
  5272. something useful, and (2) those that want to add a new command to
  5273. OpenOCD.
  5274. @section Tcl Rule #1
  5275. There is a famous joke, it goes like this:
  5276. @enumerate
  5277. @item Rule #1: The wife is always correct
  5278. @item Rule #2: If you think otherwise, See Rule #1
  5279. @end enumerate
  5280. The Tcl equal is this:
  5281. @enumerate
  5282. @item Rule #1: Everything is a string
  5283. @item Rule #2: If you think otherwise, See Rule #1
  5284. @end enumerate
  5285. As in the famous joke, the consequences of Rule #1 are profound. Once
  5286. you understand Rule #1, you will understand Tcl.
  5287. @section Tcl Rule #1b
  5288. There is a second pair of rules.
  5289. @enumerate
  5290. @item Rule #1: Control flow does not exist. Only commands
  5291. @* For example: the classic FOR loop or IF statement is not a control
  5292. flow item, they are commands, there is no such thing as control flow
  5293. in Tcl.
  5294. @item Rule #2: If you think otherwise, See Rule #1
  5295. @* Actually what happens is this: There are commands that by
  5296. convention, act like control flow key words in other languages. One of
  5297. those commands is the word ``for'', another command is ``if''.
  5298. @end enumerate
  5299. @section Per Rule #1 - All Results are strings
  5300. Every Tcl command results in a string. The word ``result'' is used
  5301. deliberatly. No result is just an empty string. Remember: @i{Rule #1 -
  5302. Everything is a string}
  5303. @section Tcl Quoting Operators
  5304. In life of a Tcl script, there are two important periods of time, the
  5305. difference is subtle.
  5306. @enumerate
  5307. @item Parse Time
  5308. @item Evaluation Time
  5309. @end enumerate
  5310. The two key items here are how ``quoted things'' work in Tcl. Tcl has
  5311. three primary quoting constructs, the [square-brackets] the
  5312. @{curly-braces@} and ``double-quotes''
  5313. By now you should know $VARIABLES always start with a $DOLLAR
  5314. sign. BTW: To set a variable, you actually use the command ``set'', as
  5315. in ``set VARNAME VALUE'' much like the ancient BASIC langauge ``let x
  5316. = 1'' statement, but without the equal sign.
  5317. @itemize @bullet
  5318. @item @b{[square-brackets]}
  5319. @* @b{[square-brackets]} are command substitutions. It operates much
  5320. like Unix Shell `back-ticks`. The result of a [square-bracket]
  5321. operation is exactly 1 string. @i{Remember Rule #1 - Everything is a
  5322. string}. These two statements are roughly identical:
  5323. @example
  5324. # bash example
  5325. X=`date`
  5326. echo "The Date is: $X"
  5327. # Tcl example
  5328. set X [date]
  5329. puts "The Date is: $X"
  5330. @end example
  5331. @item @b{``double-quoted-things''}
  5332. @* @b{``double-quoted-things''} are just simply quoted
  5333. text. $VARIABLES and [square-brackets] are expanded in place - the
  5334. result however is exactly 1 string. @i{Remember Rule #1 - Everything
  5335. is a string}
  5336. @example
  5337. set x "Dinner"
  5338. puts "It is now \"[date]\", $x is in 1 hour"
  5339. @end example
  5340. @item @b{@{Curly-Braces@}}
  5341. @*@b{@{Curly-Braces@}} are magic: $VARIABLES and [square-brackets] are
  5342. parsed, but are NOT expanded or executed. @{Curly-Braces@} are like
  5343. 'single-quote' operators in BASH shell scripts, with the added
  5344. feature: @{curly-braces@} can be nested, single quotes can not. @{@{@{this is
  5345. nested 3 times@}@}@} NOTE: [date] is a bad example;
  5346. at this writing, Jim/OpenOCD does not have a date command.
  5347. @end itemize
  5348. @section Consequences of Rule 1/2/3/4
  5349. The consequences of Rule 1 are profound.
  5350. @subsection Tokenisation & Execution.
  5351. Of course, whitespace, blank lines and #comment lines are handled in
  5352. the normal way.
  5353. As a script is parsed, each (multi) line in the script file is
  5354. tokenised and according to the quoting rules. After tokenisation, that
  5355. line is immedatly executed.
  5356. Multi line statements end with one or more ``still-open''
  5357. @{curly-braces@} which - eventually - closes a few lines later.
  5358. @subsection Command Execution
  5359. Remember earlier: There are no ``control flow''
  5360. statements in Tcl. Instead there are COMMANDS that simply act like
  5361. control flow operators.
  5362. Commands are executed like this:
  5363. @enumerate
  5364. @item Parse the next line into (argc) and (argv[]).
  5365. @item Look up (argv[0]) in a table and call its function.
  5366. @item Repeat until End Of File.
  5367. @end enumerate
  5368. It sort of works like this:
  5369. @example
  5370. for(;;)@{
  5371. ReadAndParse( &argc, &argv );
  5372. cmdPtr = LookupCommand( argv[0] );
  5373. (*cmdPtr->Execute)( argc, argv );
  5374. @}
  5375. @end example
  5376. When the command ``proc'' is parsed (which creates a procedure
  5377. function) it gets 3 parameters on the command line. @b{1} the name of
  5378. the proc (function), @b{2} the list of parameters, and @b{3} the body
  5379. of the function. Not the choice of words: LIST and BODY. The PROC
  5380. command stores these items in a table somewhere so it can be found by
  5381. ``LookupCommand()''
  5382. @subsection The FOR command
  5383. The most interesting command to look at is the FOR command. In Tcl,
  5384. the FOR command is normally implemented in C. Remember, FOR is a
  5385. command just like any other command.
  5386. When the ascii text containing the FOR command is parsed, the parser
  5387. produces 5 parameter strings, @i{(If in doubt: Refer to Rule #1)} they
  5388. are:
  5389. @enumerate 0
  5390. @item The ascii text 'for'
  5391. @item The start text
  5392. @item The test expression
  5393. @item The next text
  5394. @item The body text
  5395. @end enumerate
  5396. Sort of reminds you of ``main( int argc, char **argv )'' does it not?
  5397. Remember @i{Rule #1 - Everything is a string.} The key point is this:
  5398. Often many of those parameters are in @{curly-braces@} - thus the
  5399. variables inside are not expanded or replaced until later.
  5400. Remember that every Tcl command looks like the classic ``main( argc,
  5401. argv )'' function in C. In JimTCL - they actually look like this:
  5402. @example
  5403. int
  5404. MyCommand( Jim_Interp *interp,
  5405. int *argc,
  5406. Jim_Obj * const *argvs );
  5407. @end example
  5408. Real Tcl is nearly identical. Although the newer versions have
  5409. introduced a byte-code parser and intepreter, but at the core, it
  5410. still operates in the same basic way.
  5411. @subsection FOR command implementation
  5412. To understand Tcl it is perhaps most helpful to see the FOR
  5413. command. Remember, it is a COMMAND not a control flow structure.
  5414. In Tcl there are two underlying C helper functions.
  5415. Remember Rule #1 - You are a string.
  5416. The @b{first} helper parses and executes commands found in an ascii
  5417. string. Commands can be seperated by semicolons, or newlines. While
  5418. parsing, variables are expanded via the quoting rules.
  5419. The @b{second} helper evaluates an ascii string as a numerical
  5420. expression and returns a value.
  5421. Here is an example of how the @b{FOR} command could be
  5422. implemented. The pseudo code below does not show error handling.
  5423. @example
  5424. void Execute_AsciiString( void *interp, const char *string );
  5425. int Evaluate_AsciiExpression( void *interp, const char *string );
  5426. int
  5427. MyForCommand( void *interp,
  5428. int argc,
  5429. char **argv )
  5430. @{
  5431. if( argc != 5 )@{
  5432. SetResult( interp, "WRONG number of parameters");
  5433. return ERROR;
  5434. @}
  5435. // argv[0] = the ascii string just like C
  5436. // Execute the start statement.
  5437. Execute_AsciiString( interp, argv[1] );
  5438. // Top of loop test
  5439. for(;;)@{
  5440. i = Evaluate_AsciiExpression(interp, argv[2]);
  5441. if( i == 0 )
  5442. break;
  5443. // Execute the body
  5444. Execute_AsciiString( interp, argv[3] );
  5445. // Execute the LOOP part
  5446. Execute_AsciiString( interp, argv[4] );
  5447. @}
  5448. // Return no error
  5449. SetResult( interp, "" );
  5450. return SUCCESS;
  5451. @}
  5452. @end example
  5453. Every other command IF, WHILE, FORMAT, PUTS, EXPR, everything works
  5454. in the same basic way.
  5455. @section OpenOCD Tcl Usage
  5456. @subsection source and find commands
  5457. @b{Where:} In many configuration files
  5458. @* Example: @b{ source [find FILENAME] }
  5459. @*Remember the parsing rules
  5460. @enumerate
  5461. @item The FIND command is in square brackets.
  5462. @* The FIND command is executed with the parameter FILENAME. It should
  5463. find the full path to the named file. The RESULT is a string, which is
  5464. substituted on the orginal command line.
  5465. @item The command source is executed with the resulting filename.
  5466. @* SOURCE reads a file and executes as a script.
  5467. @end enumerate
  5468. @subsection format command
  5469. @b{Where:} Generally occurs in numerous places.
  5470. @* Tcl has no command like @b{printf()}, instead it has @b{format}, which is really more like
  5471. @b{sprintf()}.
  5472. @b{Example}
  5473. @example
  5474. set x 6
  5475. set y 7
  5476. puts [format "The answer: %d" [expr $x * $y]]
  5477. @end example
  5478. @enumerate
  5479. @item The SET command creates 2 variables, X and Y.
  5480. @item The double [nested] EXPR command performs math
  5481. @* The EXPR command produces numerical result as a string.
  5482. @* Refer to Rule #1
  5483. @item The format command is executed, producing a single string
  5484. @* Refer to Rule #1.
  5485. @item The PUTS command outputs the text.
  5486. @end enumerate
  5487. @subsection Body or Inlined Text
  5488. @b{Where:} Various TARGET scripts.
  5489. @example
  5490. #1 Good
  5491. proc someproc @{@} @{
  5492. ... multiple lines of stuff ...
  5493. @}
  5494. $_TARGETNAME configure -event FOO someproc
  5495. #2 Good - no variables
  5496. $_TARGETNAME confgure -event foo "this ; that;"
  5497. #3 Good Curly Braces
  5498. $_TARGETNAME configure -event FOO @{
  5499. puts "Time: [date]"
  5500. @}
  5501. #4 DANGER DANGER DANGER
  5502. $_TARGETNAME configure -event foo "puts \"Time: [date]\""
  5503. @end example
  5504. @enumerate
  5505. @item The $_TARGETNAME is an OpenOCD variable convention.
  5506. @*@b{$_TARGETNAME} represents the last target created, the value changes
  5507. each time a new target is created. Remember the parsing rules. When
  5508. the ascii text is parsed, the @b{$_TARGETNAME} becomes a simple string,
  5509. the name of the target which happens to be a TARGET (object)
  5510. command.
  5511. @item The 2nd parameter to the @option{-event} parameter is a TCBODY
  5512. @*There are 4 examples:
  5513. @enumerate
  5514. @item The TCLBODY is a simple string that happens to be a proc name
  5515. @item The TCLBODY is several simple commands seperated by semicolons
  5516. @item The TCLBODY is a multi-line @{curly-brace@} quoted string
  5517. @item The TCLBODY is a string with variables that get expanded.
  5518. @end enumerate
  5519. In the end, when the target event FOO occurs the TCLBODY is
  5520. evaluated. Method @b{#1} and @b{#2} are functionally identical. For
  5521. Method @b{#3} and @b{#4} it is more interesting. What is the TCLBODY?
  5522. Remember the parsing rules. In case #3, @{curly-braces@} mean the
  5523. $VARS and [square-brackets] are expanded later, when the EVENT occurs,
  5524. and the text is evaluated. In case #4, they are replaced before the
  5525. ``Target Object Command'' is executed. This occurs at the same time
  5526. $_TARGETNAME is replaced. In case #4 the date will never
  5527. change. @{BTW: [date] is a bad example; at this writing,
  5528. Jim/OpenOCD does not have a date command@}
  5529. @end enumerate
  5530. @subsection Global Variables
  5531. @b{Where:} You might discover this when writing your own procs @* In
  5532. simple terms: Inside a PROC, if you need to access a global variable
  5533. you must say so. See also ``upvar''. Example:
  5534. @example
  5535. proc myproc @{ @} @{
  5536. set y 0 #Local variable Y
  5537. global x #Global variable X
  5538. puts [format "X=%d, Y=%d" $x $y]
  5539. @}
  5540. @end example
  5541. @section Other Tcl Hacks
  5542. @b{Dynamic variable creation}
  5543. @example
  5544. # Dynamically create a bunch of variables.
  5545. for @{ set x 0 @} @{ $x < 32 @} @{ set x [expr $x + 1]@} @{
  5546. # Create var name
  5547. set vn [format "BIT%d" $x]
  5548. # Make it a global
  5549. global $vn
  5550. # Set it.
  5551. set $vn [expr (1 << $x)]
  5552. @}
  5553. @end example
  5554. @b{Dynamic proc/command creation}
  5555. @example
  5556. # One "X" function - 5 uart functions.
  5557. foreach who @{A B C D E@}
  5558. proc [format "show_uart%c" $who] @{ @} "show_UARTx $who"
  5559. @}
  5560. @end example
  5561. @node Target Library
  5562. @chapter Target Library
  5563. @cindex Target Library
  5564. OpenOCD comes with a target configuration script library. These scripts can be
  5565. used as-is or serve as a starting point.
  5566. The target library is published together with the OpenOCD executable and
  5567. the path to the target library is in the OpenOCD script search path.
  5568. Similarly there are example scripts for configuring the JTAG interface.
  5569. The command line below uses the example parport configuration script
  5570. that ship with OpenOCD, then configures the str710.cfg target and
  5571. finally issues the init and reset commands. The communication speed
  5572. is set to 10kHz for reset and 8MHz for post reset.
  5573. @example
  5574. openocd -f interface/parport.cfg -f target/str710.cfg \
  5575. -c "init" -c "reset"
  5576. @end example
  5577. To list the target scripts available:
  5578. @example
  5579. $ ls /usr/local/lib/openocd/target
  5580. arm7_fast.cfg lm3s6965.cfg pxa255.cfg stm32.cfg xba_revA3.cfg
  5581. at91eb40a.cfg lpc2148.cfg pxa255_sst.cfg str710.cfg zy1000.cfg
  5582. at91r40008.cfg lpc2294.cfg sam7s256.cfg str912.cfg
  5583. at91sam9260.cfg nslu2.cfg sam7x256.cfg wi-9c.cfg
  5584. @end example
  5585. @include fdl.texi
  5586. @node OpenOCD Concept Index
  5587. @comment DO NOT use the plain word ``Index'', reason: CYGWIN filename
  5588. @comment case issue with ``Index.html'' and ``index.html''
  5589. @comment Occurs when creating ``--html --no-split'' output
  5590. @comment This fix is based on: http://sourceware.org/ml/binutils/2006-05/msg00215.html
  5591. @unnumbered OpenOCD Concept Index
  5592. @printindex cp
  5593. @node Command and Driver Index
  5594. @unnumbered Command and Driver Index
  5595. @printindex fn
  5596. @bye