X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=NEWS;h=add6c1e9035498574967489daeda9eb5cb3aab56;hp=f56c7a4f38342d5790b64d1862ef700a4db633c5;hb=73988aea1f68390cdc60f6b6b777f7a466935084;hpb=1930e08b99b10969538851bdc28501e5d3ca9f21 diff --git a/NEWS b/NEWS index f56c7a4f38..add6c1e903 100644 --- a/NEWS +++ b/NEWS @@ -1,80 +1,74 @@ -The OpenOCD 0.2.0 source archive release includes numerous improvements -that were made since the initial 0.1.0 source archive release. Many -contributors helped make this release a great success, and the community -of developers and maintainers look forward to any response. +This file includes highlights of the changes made in the +OpenOCD 0.5.0 source archive release. See the repository +history for details about what changed, including bugfixes +and other issues not mentioned here. -In addition to the list of changes below, countless bug fixing and -cleaning was performed across the tree. Various TCL command parameters -must past stricter value checks, and many more error conditions have -been handled correctly. These efforts helped to make the 0.2.0 release -more stable and robust, though some changes may expose latent bugs in -your existing configuration scripts. - -This release does not maintain backward compatibility in all respects, -so some target or configuration scripts may need to be updated. In some -cases, you may also see warnings; resolve those, because they indicate -commands that will be removed in the future. +JTAG Layer: + 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 + Support Voipac VPACLink JTAG Adapter. -The following areas of OpenOCD functionality changed in this release: +Boundary Scan: -JTAG Layer: -- Improves modularity: core, TCL, driver commands, and interface have - been separated, encapsulated, and documented for developers. Mostly. -- Improves JTAG TAP transition tables: - * Makes TAP paths variable length, rather than being fixed at 7 steps. - * Fixes problems with some targets that did not like longer paths. -- Improves JTAG driver/minidriver modularity and encapsulation. -- New drivers: - * Adds stub minidriver for developing new embedded JTAG interfaces. -- Improves drivers: - * ft2232+ftd2xx: - + Adds initial high-speed device support: --enable-ftd2xx-highspeed - + Supports more types of FTDI-based devices. - * jlink: - + Works with more versions of the firmware (v3 and newer) - + Supports dynamically detects device capabilities and limits - * vsllink: - + Supports very long scan chains - * amtjtagaccel: - + Fixes broken ID code detection problems. +Transport framework core ... supporting future work for SWD, SPI, and other +non-JTAG ways to debug targets or program flash. Target Layer: -- New devices: AVR, FA526 -- Improved support: ARM ADI, ARM11, MIPS -- Numerous other bug fixes and improvements + ARM: + - basic semihosting support for ARMv7M. + - renamed "armv7m" command prefix as "arm" + 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. + OTHER: + - preliminary AVR32 AP7000 support. Flash Layer: -- Improved drivers: mflash -- New drivers: AT91SAM3, AVR, Davinci NAND + 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%. + New 'pic32mx unlock' cmd to remove readout protection. + New STM32 Value Line Support. + New 'virtual' flash driver, used to associate other addresses + with a flash bank. See pic32mx.cfg for usage. + New iMX27 NAND flash controller driver. + +Board, Target, and Interface Configuration Scripts: + Support IAR LPC1768 kickstart board (by Olimex) + Support Voipac PXA270/PXA270M module. + New $PARPORTADDR tcl variable used to change default + parallel port address used. + Remove lm3s811.cfg; use "stellaris.cfg" instead -Board, Interface, and Target Configuration Scripts: -- Many new and improved targets and boards are now available. -- Better separation of "board" and "target" configuration -- Moved all TCL files to top-level "tcl" directory in the source tree -- Installation moved from '$pkglibdir/' to '$pkgdatadir/scripts/'. -- Site-specific files should be installed under '$pkgdatadir/site/'; - files that exist this tree will be used in preference to default - distribution configurations in '$pkgdatadir/scripts/'. +Core Jim/TCL Scripting: + New "add_script_search_dir" command, behaviour is the same + as the "-s" cmd line option. Documentation: -- Updated User Guide: http://openocd.berlios.de/doc/html/index.html - * Partially re-written and re-organized. - * Standardized presentation for all commands. - * Covers many drivers and commands that were previously omitted. - * New index for commands and drivers. -- Added Developer Manual: http://openocd.berlios.de/doc/doxygen/index.html - * Now includes architecture, technical primers, style guides, and more. - * Available in-tree and on-line. Build and Release: -- Increased configuration and compilation warning coverage. - * Use --disable-werror to work around build errors caused by warnings. -- Use libtool to produce helper libraries as a step toward "libopenocd". -- New processes and scripting to facilitate future source releases. -For more details about what has changed since 0.1.0, see the ChangeLog -associated with this release. +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-). 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). +