1 This file includes highlights of the changes made in the
2 OpenOCD 0.4.0 source archive release. See the repository
3 history for details about what changed, including bugfixes
4 and other issues not mentioned here.
7 Support KT-Link JTAG adapter.
12 - new "reset-assert" event, for systems without SRST
14 - renamed "armv4_5" command prefix as "arm"
15 - recognize TrustZone "Secure Monitor" mode
16 - "arm regs" command output changed
17 - register names use "sp" not "r13"
18 - add top-level "mcr" and "mrc" commands, replacing
19 various core-specific operations
21 - Preliminary ETM and ETB hookup
22 - accelerated "flash erase_check"
23 - accelerated GDB memory checksum
24 - support "arm regs" command
25 - can access all core modes and registers
27 - support "arm regs" command
28 - can access all core modes and registers
29 - supports "reset-assert" event (used on OMAP3530)
31 - Exposed DWT registers like cycle counter
34 'flash bank' and 'nand device' take <bank_name> as first argument.
35 With this, flash/NAND commands allow referencing banks by name:
36 - <bank_name>: reference the bank with its defined name
37 - <driver_name>[.N]: reference the driver's Nth bank
38 New 'nand verify' command to check bank against an image file.
40 Board, Target, and Interface Configuration Scripts:
42 - ETM and ETB hookup for iMX2* targets
43 Add $HOME/.openocd to the search path.
45 Core Jim/TCL Scripting:
46 New 'usage' command to provide terse command help.
47 Improved command 'help' command output (sorted and indented).
48 Improved command handling:
49 - Most boolean settings now accept any of the following:
50 on/off, enable/disable, true/false, yes/no, 1/0
51 - More error checking and reporting.
54 New built-in command development documentation and primer.
57 Use --enable-doxygen-pdf to build PDF developer documentation.
59 For more details about what has changed since the last release,
60 see the git repository history. With gitweb, you can browse that
61 in various levels of detail.
63 For older NEWS, see the NEWS files associated with each release
64 (i.e. NEWS-<version>).
66 For more information about contributing test reports, bug fixes, or new
67 features and device support, please read the new Developer Manual (or
68 the BUGS and PATCHES files in the source archive).