You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

NEWS 3.5 KiB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596
  1. This file includes highlights of the changes made in the
  2. OpenOCD 0.4.0 source archive release. See the repository
  3. history for details about what changed, including bugfixes
  4. and other issues not mentioned here.
  5. JTAG Layer:
  6. Support KT-Link JTAG adapter.
  7. Support USB-JTAG, Altera USB-Blaster and compatibles.
  8. Boundary Scan:
  9. Target Layer:
  10. General
  11. - new "reset-assert" event, for systems without SRST
  12. ARM
  13. - supports "reset-assert" event (except on Cortex-M3)
  14. - renamed "armv4_5" command prefix as "arm"
  15. - recognize TrustZone "Secure Monitor" mode
  16. - "arm regs" command output changed
  17. - register names use "sp" not "r13"
  18. - add top-level "mcr" and "mrc" commands, replacing
  19. various core-specific operations
  20. - basic semihosting support (ARM7/ARM9 only, for now)
  21. ARM11
  22. - Should act much more like other ARM cores:
  23. * Preliminary ETM and ETB hookup
  24. * accelerated "flash erase_check"
  25. * accelerated GDB memory checksum
  26. * support "arm regs" command
  27. * can access all core modes and registers
  28. * watchpoint support
  29. - Shares some core debug code with Cortex-A8
  30. Cortex-A8
  31. - Should act much more like other ARM cores:
  32. * support "arm regs" command
  33. * can access all core modes and registers
  34. * watchpoint support
  35. - Shares some core debug code with ARM11
  36. Cortex-M3
  37. - Exposed DWT registers like cycle counter
  38. - vector_catch settings not clobbered by resets
  39. - no longer interferes with firmware's fault handling
  40. ETM, ETB
  41. - "trigger_percent" command moved ETM --> ETB
  42. - "etm trigger_debug" command added
  43. MIPS
  44. - use fastdata writes
  45. Freescale DSP563xx cores (partial support)
  46. Flash Layer:
  47. 'flash bank' and 'nand device' take <bank_name> as first argument.
  48. With this, flash/NAND commands allow referencing banks by name:
  49. - <bank_name>: reference the bank with its defined name
  50. - <driver_name>[.N]: reference the driver's Nth bank
  51. New 'nand verify' command to check bank against an image file.
  52. The "flash erase_address" command now rejects partial sectors;
  53. previously it would silently erase extra data. If you
  54. want to erase the rest of the first and/or last sectors
  55. instead of failing, you must pass an explicit "pad" flag.
  56. New at91sam9 NAND controller driver.
  57. New s3c64xx NAND controller driver.
  58. Board, Target, and Interface Configuration Scripts:
  59. ARM9
  60. - ETM and ETB hookup for iMX2* targets
  61. Add $HOME/.openocd to the search path.
  62. Handle Rev C of LM3S811 eval boards.
  63. - use "luminary-lm3s811.cfg" for older boards
  64. - use "luminary.cfg" for RevC and newer
  65. Core Jim/TCL Scripting:
  66. New 'usage' command to provide terse command help.
  67. Improved command 'help' command output (sorted and indented).
  68. Improved command handling:
  69. - Most boolean settings now accept any of the following:
  70. on/off, enable/disable, true/false, yes/no, 1/0
  71. - More error checking and reporting.
  72. Documentation:
  73. New built-in command development documentation and primer.
  74. Build and Release:
  75. Use --enable-doxygen-pdf to build PDF developer documentation.
  76. Consider upgrading to libftdi 0.17 if you use that library; it
  77. includes bugfixes which improve FT2232H support.
  78. For more details about what has changed since the last release,
  79. see the git repository history. With gitweb, you can browse that
  80. in various levels of detail.
  81. For older NEWS, see the NEWS files associated with each release
  82. (i.e. NEWS-<version>).
  83. For more information about contributing test reports, bug fixes, or new
  84. features and device support, please read the new Developer Manual (or
  85. the BUGS and PATCHES.txt files in the source archive).