X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=NEWS;h=a744da372b931149bb6bba0b1aeb3b5eb8524bfc;hp=efcf8f619d4bcf91dc0e82bb0db614bb90696d9a;hb=d60ebc0ab535e54f76e734d00d9ac1b5c9b6eb93;hpb=9abad965ab358c1d598f1354842967cad637b284 diff --git a/NEWS b/NEWS index efcf8f619d..a744da372b 100644 --- a/NEWS +++ b/NEWS @@ -1,69 +1,47 @@ This file includes highlights of the changes made in the -OpenOCD 0.4.0 source archive release. See the repository +OpenOCD 0.5.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. + New driver for "Bus Pirate" + Rename various commands so they're not JTAG-specific + There are migration procedures for most of these, but you should + convert your scripts to the new names, since those procedures + will not be around forever. + jtag jinterface ... is now adapter_name + jtag_khz ... is now adapter_khz + jtag_nsrst_delay ... is now adapter_nsrst_delay + jtag_nsrst_assert_width ... is now adapter_nsrst_assert_width 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 - - basic semihosting support - 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 - - watchpoint support - Cortex-A8 - - support "arm regs" command - - can access all core modes and registers - - supports "reset-assert" event (used on OMAP3530) - - watchpoint support - Cortex-M3 - - Exposed DWT registers like cycle counter - ETM, ETB - - "trigger_percent" command moved ETM --> ETB + MIPS: + - "ejtag_srst" variant removed. The same functionality is + obtained by using "reset_config none". + - added PIC32MX software reset support, this means srst is not + required to be connected anymore. Flash Layer: - 'flash bank' and 'nand device' take as first argument. - With this, flash/NAND commands allow referencing banks by name: - - : reference the bank with its defined name - - [.N]: reference the driver's Nth bank - New 'nand verify' command to check bank against an image file. - The "flash erase_address" command now rejects partial sectors; - previously it would silently erase extra data. + New "stellaris recover" command, implements the procedure + to recover locked devices (restoring non-volatile + state to the factory defaults, including erasing + the flash and its protection bits, and possibly + re-enabling hardware debugging). + PIC32MX now uses algorithm for flash programming, this + has increased the performance by approx 96%. Board, Target, and Interface Configuration Scripts: - ARM9 - - ETM and ETB hookup for iMX2* targets - Add $HOME/.openocd to the search path. + Support IAR LPC1768 kickstart board (by Olimex) 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. + New "add_script_search_dir" command, behaviour is the same + as the "-s" cmd line option. Documentation: - New built-in command development documentation and primer. Build and Release: - Use --enable-doxygen-pdf to build PDF developer documentation. - Consider upgrading to libftdi 0.17 if you use that library; it - includes bugfixes which improve FT2232H support. For more details about what has changed since the last release, see the git repository history. With gitweb, you can browse that @@ -74,4 +52,5 @@ For older NEWS, see the NEWS files associated with each release 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). +the BUGS and PATCHES.txt files in the source archive). +