- Important information
- New features
- Known problems
- Program corrections
- User guide corrections
- Miscellaneous
- Release history
Important information
-
Installation instructions - USB driver for Atmel AVR ONE!
The USB driver for Atmel AVR ONE! is not automatically installed during the product installation. You must manually run the installation AtmelUSB.exe from the installation disk or from the directory drivers in the product installation directory.
New features
- None
Known Problems
-
Buffered auxiliary trace might experience trace buffer overruns for small trace buffers when the option Buffer mode>Pause execution is used. Increase the trace buffer size if this happens.
Program Corrections
User guide corrections
- None
Miscellaneous
- None
Release history
4.21.3 - Service Pack 2 - 2014-09-01
Program corrections
4.21.2 - Service Pack 1 - 2014-07-09
Program corrections
-
The debugger may use an incorrect reset sequence on some devices resulting in failure to connect to the target device.
-
An issue with parsing device configuration data can cause the debugger to use incorrect flash controller addresses on some devices. This results in failed downloads and incorrect fuse handling.
-
EW24003
Trace buffer overrun protection together with data trace write might lock the target in a non-OCD mode when using NanoTrace. Deselect one of the options Transmit queue>Enable overrun protection or Trace data>Enable data trace (write) in the Trace Settings dialog box if you experience this problem.
4.21.1 - 2014-05-28
New features
-
Attach to running target
It is possible to attach the AVR ONE! debug probe to a running target without resetting the target. The AVR ONE! Setup page now contains the additional option Attach to running target. This option must be disabled when you download the application for the first time. You can then end the debug session, select the option, and attach to your running target. This feature is not applicable on all devices.
4.20.2 - 2013-08-28
Program corrections
-
EW24130
Live watch and live memory may trigger unaligned read operations which in turn will cause the communication with the emulator to become unsynchronized.
4.20.1 - 2013-07-05
Program corrections
-
EW23267
The AVRONE! driver no longer times out when using aWire to connect to some UC3 devices. -
EW23248
Download speed when using aWire can now be improved through the use of a "Device Support Module". Please see the on-line documentation for more information concerning this feature. -
EW23103
A threading issue has been corrected. C-SPY no longer crashes if several watch (variable) windows are open at the same time. -
EW22376
The device ID value for UC3B1128 has been corrected. -
EW21383
The diagnostic message issued when Verify Download fails is unclear and can be misleading.
4.10.12 - 2012-06-04
Program corrections
-
EW23241
The emulator driver certifies that the Vdd voltage is above a given threshold level before allowing a debug session to start. The threshold level was previously set to 1.8 V, but as many AVR32 device specifications allow for a Vdd level as low as 1.62 V, the threshold level has been adjusted downwards to 1.55 V.
4.10.10 - 2012-03-06
Program corrections
-
EW22947
The C-SPY emulator driver no longer corrupts status register flags when you debug with interrupts enabled (with the GM bit in the Status Register set to zero).
4.10.9 - 2012-02-29
Program corrections
-
EW23017
C-SPY drivers and the processor module no longer fails to correctly parse the --cpu_info command line option when the path is given as a separate option.
4.10.7 - 2012-02-08
Program corrections
-
EW22074
It is now possible to single-step past breakpoints when interrupts are enabled. -
EW22173
After an upgrade from AVRONE FW v4.f (where the error was verified) to v5.6, a read access outside the flash memory no longer returns garbage data. -
Chip erase now works also for the EVK1104 development board.
4.10.1 - 2011-06-28
- None
3.31 - 2010-10-27
New features
-
C-SPY now supports aWire mode debugging.
-
It is now possible to set the voltage and clock generator frequency for the STK600 development board from the driver tools menu.
Program corrections
-
EW20961
The IDE no longer crashes when you set a data breakpoint. -
EW21717
A race condition in the debugger driver that prevented breakpoint conditions from being properly evaluated has been corrected. The debugger should now stop on breakpoints only when the breakpoint condition evaluates to true and not every time the breakpoint is hit. -
EW21718
The IAR Embedded Workbench IDE should no longer crash when the target system is power down and up again. The debug session might still be terminated if the debugger cannot regain contact with the target hardware. -
EW21831
Multiple image debugging functionality has been added.
3.30 - 2010-02-24
- None
V3.20G - 2010-01-22
- None
V3.20F - 2009-11-20
- None
V3.20E - 2009-11-12
- None
V3.20D - 2009-10-30
-
EW21374
Setting a breakpoint while the target application is running no longer causes the C-SPY driver to freeze, caused by a deadlock situation in the driver.
V3.20C - 2009-09-13
-
EW21342
A problem that could cause the application to terminate when attempting to set a data breakpoint in the Breakpoints window has been corrected.
V3.20B - 2009-07-20
-
A malformed Debug Log message no longer causes the driver to fail to initialize causing an "Exception E1" message box to appear.
V3.20A - 2009-06-15
-
EW20734
Setting up a JTAG chain now works; the driver no longer assumes that there is only a single AVR32 device on the JTAG chain.
V3.10G - 2009-03-10
-
The built-in memory cache in the driver could cause the stack plugin to display incorrect stack usage levels.
-
The build-in memory cache in the driver could prevent writes from C-SPY macros to reach the target hardware. Two new C-SPY macros commands have been added to give control of the cache behavior.
V3.10F - 2009-02-24
- None
V3.10E - 2009-02-06
- None
V3.10D - 2008-12-19
-
EW20645
The AVRONE! driver would erroneously report that the installed firmware version was less than 1.1 when it in fact was less than 2.1. The warning message has been corrected. -
EW20708
The setup of JTAG chain did not work; the driver always assumed that there was only a single AVR32 device on the JTAG chain. This has been corrected.
V3.10A - 2008-09-26
-
Initial release.