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"
19 - Preliminary ETM and ETB hookup
20 - accelerated "flash erase_check"
21 - accelerated GDB memory checksum
22 - support "arm regs" command
23 - can access all core modes and registers
25 - support "arm regs" command
26 - can access all core modes and registers
27 - supports "reset-assert" event (used on OMAP3530)
29 - Exposed DWT registers like cycle counter
32 'flash bank' and 'nand device' take <bank_name> as first argument.
33 With this, flash/NAND commands allow referencing banks by name:
34 - <bank_name>: reference the bank with its defined name
35 - <driver_name>[.N]: reference the driver's Nth bank
36 New 'nand verify' command to check bank against an image file.
38 Board, Target, and Interface Configuration Scripts:
40 - ETM and ETB hookup for iMX2* targets
41 Add $HOME/.openocd to the search path.
43 Core Jim/TCL Scripting:
44 New 'usage' command to provide terse command help.
45 Improved command 'help' command output (sorted and indented).
46 Improved command handling:
47 - Most boolean settings now accept any of the following:
48 on/off, enable/disable, true/false, yes/no, 1/0
49 - More error checking and reporting.
52 New built-in command development documentation and primer.
55 Use --enable-doxygen-pdf to build PDF developer documentation.
57 For more details about what has changed since the last release,
58 see the git repository history. With gitweb, you can browse that
59 in various levels of detail.
61 For older NEWS, see the NEWS files associated with each release
62 (i.e. NEWS-<version>).
64 For more information about contributing test reports, bug fixes, or new
65 features and device support, please read the new Developer Manual (or
66 the BUGS and PATCHES files in the source archive).