mww_phys retired. Replaced by generic mww phys in target.c

[openocd] / NEWS

diff --git a/NEWS b/NEWS
index f56c7a4f38342d5790b64d1862ef700a4db633c5..81fce82181091f9ce3f7a3b03df82cd3b1d3f713 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,79 +1,55 @@
-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.
-
-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.
-
-The following areas of OpenOCD functionality changed in this release:
+This file should include highlights of the changes made in the
+OpenOCD openocd-0.3.0 source archive release.  See the repository
+history for details about what changed, including bugfixes and
+other issues not mentioned here.

 
 JTAG Layer:
 
 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.
+    FT2232H (high speed USB) support doesn't need separate configuration
+    New reset_config options for SRST gating the JTAG clock (or not)
+    TAP declaration no longer requires ircapture and mask attributes
+    New "post-reset" event handler for TAP-invariant setup code
+    Overridable Tcl "init_reset" and "jtag_init" procedures

 
 Target Layer:
 
 Target Layer:

-- New devices: AVR, FA526
-- Improved support: ARM ADI, ARM11, MIPS
-- Numerous other bug fixes and improvements
+    New commands for use with Cortex-M3 processors:
+       "cortex_m3 disassemble" ... Thumb2 disassembly (UAL format)
+       "cortex_m3 vector_catch" ... traps certain hardware faults
+               without tying up breakpoint resources
+    If you're willing to help debug it
+       VERY EARLY Cortex-A8 and ARMv7A support
+       Updated BeagleBoard.org hardware support
+    New commands for use with XScale processors: "xscale vector_table"
+    ARM11
+       single stepping support for i.MX31
+       bugfix for missing "arm11" prefix on "arm11 memwrite ..."
+    ETM support
+       Unavailable registers are not listed

 
 Flash Layer:
 
 Flash Layer:

-- Improved drivers: mflash
-- New drivers: AT91SAM3, AVR, Davinci NAND
-
-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/'.
+    The lpc2000 driver handles the new NXP LPC1700 (Cortex-M3) chips
+    New lpc2900 driver for NXP LPC2900 chips (ARM968 based)
+    New "last" flag for NOR "flash erase_sector" and "flash protect"
+    The "nand erase N" command now erases all of bank N
+
+Board, Target, and Interface Configuration Scripts:
+    Amontec JTAGkey2 support
+    Cleanup and additions for the TI/Luminary Stellaris scripts
+    LPC1768 target (and flash) support
+       Keil MCB1700 eval board
+    Samsung s3c2450
+       Mini2440 board
+    Numeric TAP and Target identifiers now trigger warnings
+    PXA255 partially enumerates

 
 Documentation:
 
 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.
+    Capture more debugging and setup advice
+    Notes on target source code changes that may help debugging

 
 Build and Release:
 
 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 ChangeLog associated with this source archive.  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
 
 For more information about contributing test reports, bug fixes, or new
 features and device support, please read the new Developer Manual (or