|
- This file includes highlights of the changes made in the
- OpenOCD 0.4.0 source archive release. See the repository
- history for details about what changed, including bugfixes
- and other issues not mentioned here.
-
- JTAG Layer:
- Support KT-Link JTAG adapter.
-
- Boundary Scan:
- Target Layer:
- General
- - new "reset-assert" event, for systems without SRST
- ARM
- - renamed "armv4_5" command prefix as "arm"
- - recognize TrustZone "Secure Monitor" mode
- - "arm regs" command output changed
- - register names use "sp" not "r13"
- - add top-level "mcr" and "mrc" commands, replacing
- various core-specific operations
- ARM11
- - Preliminary ETM and ETB hookup
- - accelerated "flash erase_check"
- - accelerated GDB memory checksum
- - support "arm regs" command
- - can access all core modes and registers
- Cortex-A8
- - support "arm regs" command
- - can access all core modes and registers
- - supports "reset-assert" event (used on OMAP3530)
- Cortex-M3
- - Exposed DWT registers like cycle counter
-
- Flash Layer:
- 'flash bank' and 'nand device' take <bank_name> as first argument.
- With this, flash/NAND commands allow referencing banks by name:
- - <bank_name>: reference the bank with its defined name
- - <driver_name>[.N]: reference the driver's Nth bank
- New 'nand verify' command to check bank against an image file.
-
- Board, Target, and Interface Configuration Scripts:
- ARM9
- - ETM and ETB hookup for iMX2* targets
- Add $HOME/.openocd to the search path.
-
- Core Jim/TCL Scripting:
- New 'usage' command to provide terse command help.
- Improved command 'help' command output (sorted and indented).
- Improved command handling:
- - Most boolean settings now accept any of the following:
- on/off, enable/disable, true/false, yes/no, 1/0
- - More error checking and reporting.
-
- Documentation:
- New built-in command development documentation and primer.
-
- Build and Release:
- Use --enable-doxygen-pdf to build PDF developer documentation.
-
- For more details about what has changed since the last release,
- see the git repository history. With gitweb, you can browse that
- in various levels of detail.
-
- For older NEWS, see the NEWS files associated with each release
- (i.e. NEWS-<version>).
-
- For more information about contributing test reports, bug fixes, or new
- features and device support, please read the new Developer Manual (or
- the BUGS and PATCHES files in the source archive).
|
