1 This file includes highlights of the changes made in the
2 OpenOCD 0.5.0 source archive release. See the repository
3 history for details about what changed, including bugfixes
4 and other issues not mentioned here.
7 New driver for "Bus Pirate"
8 Rename various commands so they're not JTAG-specific
9 There are migration procedures for most of these, but you should
10 convert your scripts to the new names, since those procedures
11 will not be around forever.
12 jtag jinterface ... is now adapter_name
13 jtag_khz ... is now adapter_khz
14 jtag_nsrst_delay ... is now adapter_nsrst_delay
15 jtag_nsrst_assert_width ... is now adapter_nsrst_assert_width
16 Support Voipac VPACLink JTAG Adapter.
22 - basic semihosting support (ARMv7M).
23 - renamed "armv7m" command prefix as "arm"
25 - "ejtag_srst" variant removed. The same functionality is
26 obtained by using "reset_config none".
27 - added PIC32MX software reset support, this means srst is not
28 required to be connected anymore.
31 New "stellaris recover" command, implements the procedure
32 to recover locked devices (restoring non-volatile
33 state to the factory defaults, including erasing
34 the flash and its protection bits, and possibly
35 re-enabling hardware debugging).
36 PIC32MX now uses algorithm for flash programming, this
37 has increased the performance by approx 96%.
38 New 'pic32mx unlock' cmd to remove readout protection.
39 New STM32 Value Line Support.
40 New 'virtual' flash driver, used to associate other addresses
41 with a flash bank. See pic32mx.cfg for usage.
42 New iMX27 NAND flash controller driver.
44 Board, Target, and Interface Configuration Scripts:
45 Support IAR LPC1768 kickstart board (by Olimex)
46 Support Voipac PXA270/PXA270M module.
47 New $PARPORTADDR tcl variable used to change default
48 parallel port address used.
50 Core Jim/TCL Scripting:
51 New "add_script_search_dir" command, behaviour is the same
52 as the "-s" cmd line option.
58 For more details about what has changed since the last release,
59 see the git repository history. With gitweb, you can browse that
60 in various levels of detail.
62 For older NEWS, see the NEWS files associated with each release
63 (i.e. NEWS-<version>).
65 For more information about contributing test reports, bug fixes, or new
66 features and device support, please read the new Developer Manual (or
67 the BUGS and PATCHES.txt files in the source archive).