• Important information
• New features
• Known problems
• Program corrections
• User documentation corrections
• Miscellaneous
• Release history

Important information

• The supported JTAG interfaces from Macraigor are mpDemon (via ethernet), usbDemon, usb2Demon and usb2Sprite.
  
• Wiggler and Raven interfaces that uses the parallel port are not supported any longer.
• To use usb2Sprite, select usb2Demon as device in the project settings.

New features

• None.

Known problems

• JTAG Error: Invalid Register Code, when connecting to the Sharp LH79524.
  [EW19382]

• For the Wiggler and Raven interfaces that uses the parallel port, the error message "Unable to load device driver" is shown when starting the debug sesson. It is not fatal and you can continue debugging by clicking Ok.
  [EW19352]

• ARM9 cores with an MMU (for example ARM920T) require special handling by the IAR C-SPY Debugger. To access the virtual address space, the implementation as defined by Macraigor requires a small memory buffer as workspace in RAM.

  The C-SPY driver tries to identify usable RAM by using 64 bytes of RAM below the stack pointer, which is only done when the target application has been stopped. This algorithm is not robust and might fail in some cases. When it fails the typical error message will be "Target Error: Register Buffer Error".
  Example:
  
  --mac_set_temp_reg_buffer=0x400FFC0
  
  This will use 64 bytes of memory starting at physical address 0x400ffc0 as an internal scratch area by the JTAG interface driver.
  If the algorithm to detect RAM fails, the physical address can be provided manually by using the --mac_set_temp_reg_buffer option.

Program corrections

• None.

User documentation corrections

• IAR Embedded Workbench® IDE for ARM® User Guide (UARM-16), removed functions:
  
  
  • Page 12, 217, 241, 495 and 504: Wiggler and Raven interfaces that uses the parallel port are not supported any longer.
    

Miscellaneous

• None.

Release history

V5.40 2009-07-10

New features

• None.

Program corrections

• None.

V5.30 2009-01-23

New features

• None.

Program corrections

• None.

V5.20 2008-06-24

New features

• None.

Program corrections

• For Cortex-M, the hardware breakpoint was not removed when it was cleared. This happened when there is only one breakpoint set.
  [EW20251]

• The disassembly window made accesses to the VICAddress register etc. (0xFFFFFF00 - 0xFFFFFFFF ) when displaying the interrupt vectors at 0x00-0x20. This led to that no IRQs were triggered any more.
  [EW20160]

V5.11 2007-11-28

New features

• Added support for ARM11 and Cortex-M3.

Program corrections

• Downloading very small applications could lead to a crash.

• JTAG scan chain with multiple target option did not work properly.

• When using the Attach to program option and having the stack plugin enabled, the debugger crashed when ending the debug session.
  [EW19229]

V5.10 2007-07-02

New features

• Data breakpoints. For more information, refer to Part 6. C-SPY hardware debugger systems in the EWARM User Guide.

Program corrections

• Using the CPU ARM7TDMI-S resulted in an error message "Invalid Register Code" when starting execution.
  [EW19160]

V4.41A 2006-12-08

Program corrections

• Using XScale, 8/16/32-bits memory accesses in the Memory window failed.

V4.40A 2006-05-18

New features

• Support for usb2Demon and usb2Sprite.

Program corrections

• When using XScale, a problem in the initialization caused the error message "JTAG Error: Invalid parameter for this command"
  [EW17991]

V4.31A 2006-02-03

• None.

V4.30A 2005-06-23

Program corrections

• ARM7 cores with an MMU (eg. ARM720T) failed with the error message:
  JTAG Error: Register Buffer Error
  The register buffer for co-processor access is now set up earlier.
  [EW16759]

V4.20A 2005-01-10

• None.

V4.11A 2004-06-10

Program corrections

• Combining the options Suppress download and Verify download did not work. The combination of the options Suppress download and Verify download should verify the target content without downloading.

V4.10B 2004-03-09

• None.

V4.10A 2004-02-21

Program corrections

• Reading memory blocks > 4K could lead to a JTAG error. This happens for example when using the "verify all" option.
  [EW14831]

V3.40A 2003-07-03

Program corrections

• The user mode registers R8_usr to R14_usr are now fully working.

V3.30A 2003-02-18

• None.

V3.21A 2002-09-30

Program corrections

• Breakpoints in big-endian mode did not work.

V3.20A 2002-06-18

• User-defined JTAG watchpoints are now supported.
• Code breakpoints can now be set in read-only memory.
• When using Raven, it is now possible to connect the debugger to a running system, stop it for debugging, and start it when ending debugging.
• It is now possible to debug hardware with multiple targets on the JTAG chain.
• The disassembler now also displays version 5 instructions.
• The fiq/svc/abt/und/irq mode-specific registers now work correctly.
• Problems in the breakpoint-setting algorithm have been found and corrected.

V3.11A 2001-12-05

• None.

V3.10A 2001-10-02

• First release.

Copyright © 1999-2009 IAR Systems AB.