ec297e4bf1
Most of this patch updates documentation and comments for various Luminary boards, supporting two bug fixes by helping to make sense of the current mess: - Recent rev C lm3s811 eval boards didn't work. They must use the ICDI layout, which sets up some signals that the older boards didn't need. This is actually safe and appropriate for *all* recent boards ... so just make "luminary.cfg" use the ICDI layout. - "luminary-lm3s811.cfg", was previously unusable! No VID/PID; and the wrong vendor string. Make it work, but reserve it for older boards where the ICDI layout is wrong. - Default the LM3748 eval board to "luminary.cfg", like the other boards. If someone uses an external JTAG adapter, all boards will use the same workaround (override that default). The difference between the two FT2232 layouts is that eventually the EVB layout will fail cleanly when asked to enable SWO trace, but the ICDI layout will as cleanly be able to enable it. Folk using "luminary.cfg" with Rev B boards won't see anything going wrong until SWO support is (someday) added. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
85 lines
3.0 KiB
Plaintext
85 lines
3.0 KiB
Plaintext
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.
|
|
Support USB-JTAG, Altera USB-Blaster and compatibles.
|
|
|
|
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
|
|
- "etm trigger_debug" command added
|
|
Freescale DSP563xx cores (partial support)
|
|
|
|
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.
|
|
The "flash erase_address" command now rejects partial sectors;
|
|
previously it would silently erase extra data.
|
|
New at91sam9 NAND controller driver.
|
|
|
|
Board, Target, and Interface Configuration Scripts:
|
|
ARM9
|
|
- ETM and ETB hookup for iMX2* targets
|
|
Add $HOME/.openocd to the search path.
|
|
Handle Rev C of LM3S811 eval boards.
|
|
- use "luminary-lm3s811.cfg" for older boards
|
|
- use "luminary.cfg" for RevC and newer
|
|
|
|
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.
|
|
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
|
|
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).
|