AStudio6!2!1153 Readme

42130B-MCU-05/2014
RELEASE NOTES
Atmel Studio 6.2
Welcome to Atmel Studio
Atmel Studio is the integrated development environment from Atmel. It provides
you a modern and powerful environment for doing AVR and ARM development.
Get started by exploring the included example projects. Run your solution on
a starter or evaluation kit. Program and debug your project with the included
simulator, or use one of the powerful on-chip debugging and programming tools
from Atmel. Get productive with the various navigate, refactor and intellisense
features in the included editor. Experience seamless integration with various
Atmel web services like Atmel Video Lounge
1
, Atmel Store
2
and datasheets to
keep you updated and help you to design your solutions.
With strong extension possibilities and online gallery
3
, it is possible for both
designers and 3rd party to provide plug-ins and customize the environment for
best use and productivity.
Atmel Studio carries and integrates the GCC toolchain for both AVR and ARM,
Atmel Software Framework, AVR Assembler and Simulator. All newest Atmel
tools are supported including Embedded Debugger, AVR ONE!, JTAGICE mkII,
JTAGICE3, STK500, STK600, QT600, AVRISP mkII, AVR Dragon, SAM-ICE
and ATMEL-ICE.
For a detailed list of supported devices and tools please see Supported
Devices on page 19.
1
http://atmel.com/video/
2
http://store.atmel.com
3
http://gallery.atmel.com

Atmel Studio 6.2 [RELEASE NOTES]
42130B-MCU-05/2014
2
Table of Contents
Welcome to Atmel Studio ............................................................. 1
1. Installation Instructions ............................................................ 3
1.1. System requirements ............................................................. 3
1.1.1. Supported operating systems ...................................... 3
1.1.2. Supported architectures .............................................. 3
1.1.3. Hardware requirements .............................................. 3
1.2. Downloading and installing ...................................................... 3
2. FAQ ......................................................................................... 5
3. New and Noteworthy .............................................................. 8
3.1. Atmel Studio 6.2 ................................................................... 8
3.2. Atmel Studio 6.1 update 2 ...................................................... 8
3.3. Atmel Studio 6.1 update 1.1 .................................................... 8
3.4. Atmel Studio 6.1 update 1 ...................................................... 8
3.5. Atmel Studio 6.1 ................................................................... 9
3.6. Atmel Studio 6.0 ................................................................... 9
3.7. AVR Studio 5.1 ..................................................................... 9
4. Atmel Studio Extensions ....................................................... 11
5. Bugs and New Features ....................................................... 12
5.1. New features ...................................................................... 12
5.2. Notable bugs fixed ............................................................... 12
5.3. Known issues ..................................................................... 14
6. Supported Devices ................................................................ 19
6.1. AVR UC3 ........................................................................... 19
6.2. AVR Mega .......................................................................... 20
6.3. SAM .................................................................................. 24
6.4. AVR Tiny ........................................................................... 27
6.5. AVR Xmega ........................................................................ 28
7. Device Notes ......................................................................... 31
8. Contact Information and Disclaimer ...................................... 32
8.1. Disclaimer .......................................................................... 32
9. Document Revision History ................................................... 33

42130B-MCU-05/2014
3
1. Installation Instructions
1.1 System requirements
1.1.1 Supported operating systems
Windows XP (x86) with Service Pack 3 - all editions except Starter Edition
Windows Vista (x86 & x64) with Service Pack 1 - all editions except Starter Edition
Windows 7 (x86 and x64)
Windows 8 / 8.1 (x86 and x64)
Windows Server 2003 (x86 & x64) with Service Pack 2
Windows Server 2003 R2 (x86 and x64)
Windows Server 2008 (x86 and x64) with Service Pack 2
Windows Server 2008 R2 (x64)
1.1.2 Supported architectures
32-Bit (x86)
64-Bit (x64)
1.1.3 Hardware requirements
Computer that has a 1.6GHz or faster processor
RAM
1 GB RAM for x86
2 GB RAM for x64
An additional 512 MB RAM if running in a Virtual Machine
4 GB of available hard disk space
A minimum display resolution of 1024 x 768 or higher is recommended
1.2 Downloading and installing
Download the latest Atmel Studio installer.
Atmel Studio 6.2 can be run side by side with Atmel Studio 6.1, Atmel Studio 6.0, AVR Studio 5.0 and
5.1. Uninstallation of previous versions is not required.
Verify the hardware and software requirements from "System Requirements" section.
Make sure you are logged on with Administrative privileges.
Please save all your work before starting, because the installation might prompt you for a restart if
required.
Please disconnect all Atmel USB/Serial hardware devices.
Windows XP users are urged to stay connected to the internet during installation to allow for automatic
certificate updates. See FAQ for more information.
Double click the installer executable file. Please note that this might take some time to extract depending
on H/W configuration.

42130B-MCU-05/2014
4
Atmel Studio Prerequisites installation will start. NOTE : If you have all the prerequisites already installed
then this dialog will not be shown.
If .NET Framework 4.0 is not already installed, the installer will start the .NET Framework setup, Note
that this does not include SP1.
Accept the license agreement and proceed through the installation. If the installer prompts for restart
please do so. After restart the installation will start automatically.
If Visual Studio Isolated shell 2010 is not installed, the installer will start the Microsoft Visual Studio Isolated
Shell (2010) Setup.
Accept the license agreement and proceed through the installation.
The Atmel USB Driver will install/upgrade the existing Jungo USB driver, and will also keep the existing
hardware to work.
Accept the license agreement and proceed through the installation.
Note: If you have previous versions of Jungo USB driver then the installer will update them. The Atmel
USB driver (Jungo USB Driver + SAM USB Driver) is fully compatible with its previous versions. So
AVR Studio 4, Studio 32 and AVR Studio 5.0, 5.1 should continue to work with the updated driver
without any issues.
After this, Atmel Studio installation should start.
Click Next to continue.
Accept the license agreement and continue.
Choose the Destination Directory to Install and click Next.
Review the summary and click Install.
The installation will copy all files and prompt to click Finish.
At the end, the installer will display options to associate files with AVR Studio. Please choose them if you
prefer to open files with the mentioned file extensions in Atmel Studio.
The installer also displays an option to "Start Atmel Studio after completion". If you choose to open, then
please note that Atmel Studio will launch with administrative privileges, since the installer was either
launched as administrator or with elevated privileges (in Windows Vista or later).

42130B-MCU-05/2014
5
2. FAQ
1. What is the Atmel USB Driver?
The Atmel USB Driver is a cumulative installer that bundles the Jungo USB driver for the AVR tools and the
Segger USB Driver for SAM tools.
2. Will Atmel Studio 6.2 work in parallel with Atmel Studio 6.1, Atmel Studio 6.0, AVR Studio 5.0, 5.1,
AVR Studio 4.0 and AVR32 Studio?
Yes, it will work. Note: When you are uninstalling AVR Studio 4.0 or AVR32 Studio please be careful when
you manually delete folders or registry entries after uninstall, as there might be other keys and folders
deployed by Atmel Studio inside Atmel folder and registry paths.
3. I have AVR Studio 4 in my PC. When installing Atmel Studio it updated the Jungo USB driver. Will
AVR Studio 4 still work?
Yes, it will work. If Jungo driver is already present and its version is anything less than the new one, then
the installer will update the Jungo driver you already have. The updated Jungo driver is fully compatible
with its previous versions. So AVR Studio 4 and Studio 32 should continue to work with the updated driver
without any issues.
4. During installation the installer hangs more than 20 minutes while displaying: Atmel Studio
requires the following items to be installed on your computer." A progress bar is running but there
is no indication about real progress
If you have network connectivity that is limited (no internet connectivity), please disconnect the network
or disable all the active network adapters and start installation of Atmel Studio. This happens only on
Windows XP and Windows 2003 based machines.
5. The Atmel Studio installer crashes when installing using the "run as" option in Windows XP (any
architecture) with "Protect my computer ..." option enabled.
Don't use the "run as" option with the "Protect my computer ..." option enabled. The installer will have only
read-only access to some of the registry hives and system folders, causing it to malfunction. This is due
to the DEP option enabled by windows in this mode. Refer to http://blogs.msdn.com/b/aaron_margosis/
archive/2004/09/10/227727.aspx for more information.
6. Atmel Studio and Visual Studio 2010 SP1 conflicts
If Atmel Studio is installed on a machine with Visual Studio 2010 SP1, the following message might be
displayed when starting up Atmel Studio or Visual Studio: "Only some of the Microsoft Visual Studio 2010
products on this computer have been upgraded to Service Pack 1. None will work correctly until all have
been upgraded".
Follow the instructions in the error message dialog to resolve the problem.
7. Atmel Studio cannot find any debuggers or programmers after uninstalling AVR Studio 4.
The AVR Studio 4 installer uninstalls the Jungo USB Driver which is shared by Atmel Studio. Repairing the
Atmel Studio installation might not reinstall Jungo USB Driver. So Download the Atmel USB Driver installer
from the Atmel web and install it.
8. Atmel Studio cannot find any debuggers or programmers when Norton AntiVirus is running
Atmel Studio might not show any connected tools if Norton AntiVirus is running. To make it work make
sure Norton AntiVirus allows atprogram.exe to communicate with the Atmel Studio front-end by adding
atbackend.exe as an exception in the Norton AntiVirus allowed programs. This is the same with any
anti-virus program that by default blocks ports.
9. Windows shows a message box with the following message when attempting to run Atmel Studio
installer: " Windows cannot access the specified device, path or file. You may not have the
appropriate permissions to access the item. "
This might be caused by an anti-virus program blocking the installation of the Atmel Studio. We have seen
this with the Sophos antivirus package. Temporarily disable the Sophos service running on the machine (or
any corresponding anti-virus service), and attempt installation.
10. After installing and starting Atmel Studio in Windows XP, the following error is displayed. "This
application has failed to start because MSVCR100.dll was not found. Re-installing the application
may fix this problem."

42130B-MCU-05/2014
6
This probably means that your PC doesn't have Service Pack 3 for Windows XP installed. Please install
SP3 and then install Atmel Studio again.
11. Atmel Studio takes a very long time to start on my PC, but runs well in a VM environment
The Visual Studio shell (and thus Atmel Studio) does a considerable amount of processing during start-
up. Parts of the operations are WPF operations which benefits greatly by updated graphics libraries and
drivers. Installing the latest graphics driver may give a performance boost both during normal operation
and during start-up.
12. Verification and programming often fails a with a serial port buffer overrun error message when
using STK500
This is a known issue. Due to DPC latency, serial communication can have buffer overruns on the UART
chipset. E.g. other drivers , thus causing A workaround which works for most systems is to use an USB to
serial adapter.
13. Internet Explorer 6 does not display user documentation correctly
This is a known issue, primarily due to the incompatibility of the version of HTML used to prepare the help
content and the IE6 rendering engine. Please update your browser to a later version of IE to resolve the
issue. This problem is only observed with Windows XP and Windows Server 2003.
14. Help Registration fails with error code 401.
One of the common reasons for this failure is because of an corrupted Help Store location. The help store
location is usually %SYSTEMDRIVE%\ProgramData\Microsoft\HelpLibrary for Vista or later machines and
it is %SystemDrive%\Documents and Settings\All Users\Application Data for Windows XP and Windows
Server 2003 based machines. Please clean up this location and try running the installer again.
15. When launching from a guest account, the following error is displayed when starting Atmel Studio:
"Exception has been thrown by the target of an invocation"
Atmel Studio neither installs under guest account and nor runs under it.
16. Can we install and run Atmel Studio from within a Virtual Machine
Yes, with simulator there should be no issues. However with physical devices like debuggers and
programmers, the VM must offer support for physical USB and Serial port connections.
17. How can I reduce the startup time of Atmel Studio?
Make sure you have uninstalled unwanted extensions in studio.
Disable Allow Add-in components to load.
1. Go to Tools Options Add-in/Macro Security.
2. Then uncheck the Allow Add-in components to load option.
Disable the startup page (alternative 1)
1. Disable Show page on Startup in start page.
Disable the startup page (alternative 2)
1. Go to Tools Options Environment Startup At Startup.
2. Select Show empty environment option.
18. How to improve studio performance on XP OS or Single Core System?
Make sure your system has the latest version of the Windows Automation API.
Disable Visual Experience, if you have single core system:
1. Go to Tools Options Environment General.
2. Then uncheck the Automatically adjust visual experience based on client performance, Enable rich
client visual experience and Use H/W graphics acceleration options.

42130B-MCU-05/2014
7
Disable the Editor Track Changes
1. Go to Tools Options Text Editor.
2. Then uncheck the Track Changes option.
Disable the Track Active Item in Solution Explorer
1. Go to Tools Options Projects and Solutions General.
2. Then uncheck the Track Active Item in Solution Explorer option.
19. How to improve studio performance on any OS?
Make sure your system has the latest version of the Windows Automation API.
Exclude the following directories and files from antivirus scanner:
Atmel Studio Installed directory and its sub directories and files
%AppData%\Roaming\Atmel directory and its sub directories, files
%AppData%\Local\Atmel directory and its sub directories, files
Your Atmel project directories
Visual Studio 10 shell requires a lot of swap space. Increase the paging file. Also put the system to
maximize performance. Both options are found in System Properties Performance Settings
menu.
20. Should I install the latest Windows Automation API 3.0?
Yes, if your OS is any of the following
Windows XP
Vista
Server 2003
Server 2008
21. How can I make sure my system has the latest Windows Automation API 3.0?
Your system has the latest Windows Automation API if you have Windows 7 or Windows 8 operating
system. Only Windows XP, Windows Vista, Windows Server 2003 and Windows Server 2008 have the old
version API. Find the UIAutomationCore.dll file in your system (normally found in the windows folder)
and compare the version number of that file. The FileVersion will be 7.X.X.X. for the new API. Latest API
can be found at http://support.microsoft.com/kb/971513.
22. My Project is large and it takes a long time to open. Is there any option to avoid this delay?
Visual Assist X parses all the files when we opening the existing project. You could disable this option:
1. Go to VAssistX Visual Assist X Options Performance.
2. Then uncheck the Parse all files when opening the project.
23. I have the limited RAM size in my system and I work long hours in the same instance of Atmel
Studio. After some time, Atmel Studio becomes slow on my system. What is the reason for this?
Press Ctrl+Shift+Alt+F12 twice to force Atmel Studio to garbage collect.
24. Does Atmel Studio perform better on multi-core processors than on single-core?
Yes, Atmel Studio performs better on a multi-core system.
25. How can I make my projects build faster ?
You can enable parallel build Option from Tools Options Builder GNU Make Make Parallel
Execution Of Build. This option will enable GNU make utility's parallel execution feature. The build output
window log messages may not be in proper order.

42130B-MCU-05/2014
8
3. New and Noteworthy
3.1 Atmel Studio 6.2
Atmel Software Framework 3.17.0
AVR 8 Toolchain 3.4.4 (with upstream GCC 4.8.1)
ARM GCC Toolchain 4.8.3
Support for Atmel-ICE
Support for Xplained Mini
Support for data breakpoints
Read OSCCAL calibration for tinyAVR and megaAVR
Create ELF production files for AVR8 using the programming dialogue
Live Watch
Nonintrusive trace support for SAM3 and SAM4 family of devices including
Interrupt trace / monitoring
Data trace
Free RTOS awareness
Statistical code profiling
Polled Data trace support for Cortex M0+
Default debugger for SAM devices is now GDB. GDB does in some scenarios handle debugging of
optimized code better
Support to create a GCC Board project (Atmel board\User board) for ALL the installed versions of ASF
New ASF Board Wizard, to Add or Remove Board Project Template
Improved loading time of New Example Project dialog, by loading only one ASF version by default
IDR events now gets displayed in a separate pane in the output window
LSS file syntax highlighting
3.2 Atmel Studio 6.1 update 2
Support for SAM D20 devices on the JTAGICE3
3.3 Atmel Studio 6.1 update 1.1
Fix programming of boot section for xmega devices introduced in 6.1 update 1
Fix SAM4LSP32 barebone project setup.
3.4 Atmel Studio 6.1 update 1

42130B-MCU-05/2014
9
Extension Development Kit (XDK). Support for packaging an Embedded Application project into an Atmel
Gallery Extension
Support for SAM D20 and SAM4N devices
ARM GCC Toolchain 4.7.3 with experimental newlib-nano and multilibs
Support for Embedded Debugger platform
Support for Xplained Pro kits
ARM GCC Toolchain 4.7.3
CMSIS 3.20
Updated Visual Assist
Command line utility for firmware upgrade
Stimulus for simulator. Create a stimuli file to write register values while executing simulation.
Support for new devices
Support for Atmel ARM-based MCUs with Atmel SAM-ICE
AVR Toolchain 3.4.0
ARM Toolchain 3.3.1
Atmel Software Framework Explorer
Support for QTouch Composer as extension
Updated Visual Assist
New extension gallery
3.7 AVR Studio 5.1
New version of AVR Software Framework (ASF)
Availability and installation of new ASF versions through extension manager, without having to upgrade
Studio 5
Support for side by side versioning of ASF, with the ability to upgrade projects
Syntax highlighting and better debugging support for C++ projects
Support for importing AVR 32 Studio C++ projects
New version of AVR Toolchain
New command line utility (atprogram) with support for all Atmel AVR tools and devices

42130B-MCU-05/2014
10
Enhancements to programming dialog including support for ELF programming
New version of Visual Assist with several enhancements and bugfixes
Support for 55 new devices

42130B-MCU-05/2014
11
4. Atmel Studio Extensions
Extensions and updates to Atmel Studio are available through the Atmel Gallery. Access it through http://
gallery.atmel.com or use the extension manager in Atmel Studio under the Tools menu.
The set of extensions supporting a given Atmel Studio version may vary. Visit http://gallery.atmel.com to see
which extensions are available for a given version of Atmel Studio. Note that at the time of the release of a new
version of Atmel Studio not all extensions have been ported from the previous version.
Atmel Studio does not automatically reinstall extensions installed on previous versions of Atmel Studio.

42130B-MCU-05/2014
12
5. Bugs and New Features
5.1 New features
Issue #AVRSV-4821:
Add -l and --list option to atfw.exe to list out all connected tools.
Issue #AVRSV-5316:
It is now possible to select newlib-nano for ARM devices from the toolchain configuration page.
Issue #AVRSV-5396:
Stimuli files for the Simulator can now be changed during a debug session.
Issue #AVRSV-5475:
Add support for '#pragma region' to give outlines in the editor similar to Visual Studio.
5.2 Notable bugs fixed
Issue #AVRSV-197:
The breakpoint functionality "break when hit count is equal to" and "break when hit count is greater than or
equal to" doesn't work in Atmel Studio. Both these alternatives behaves as "break when hit count is multiple of".
Issue #AVRSV-4504:
The programming dialog does not remember last used settings.
Issue #AVRSV-4647:
When a compiler symbol is created of the form DEFINE="(ONE | TWO)" Atmel Studio would crash when
attempting to edit the symbol.
Issue #AVRSV-4747:
The programming option "Erase only program area" can only be used on JTAGICE3 and later debuggers. For
JTAGICE mkII , AVR Dragon and AVR One!, the user should select "Erase entire chip".
Issue #AVRSV-4758:
Configure Visual Assist X from menu "VAssistX->Visual Assist X Options->Performance" to reduce the disk
usage and improve the performance.
Issue #AVRSV-4869:
When a linked source file in an Atmel Studio project is deleted/moved from the HDD Atmel Studio refuses to
load the project.
Issue #AVRSV-4896:
Launching (F5) on debugWire does not trigger the "Do you want to use SPI to enable DWEN fuse?" dialog.
Issue #AVRSV-4999:
The Mask Interrupts while stepping feature does not work on SAM D20 devices. The workaround is to disable
interrupts manually in the application code or in the I/O view before stepping through the section of interest.
Issue #AVRSV-5024:
It is not possible to edit bitfield values in the watch window.
Issue #AVRSV-5100:
Using external reset fails for devices where this is forced on, causing programming to fail.
Issue #AVRSV-5111:
Entering debugWire mode may fail if the CKOUT fuse is programmed.
Issue #AVRSV-5117:
Drag and drop a folder onto itself is possible in the Solution Explorer, causing recursive folder creation on disk.

42130B-MCU-05/2014
13
Issue #AVRSV-5132:
The 'info' command in atprogram fails to read fuses for ATxmega devices.
Issue #AVRSV-5142:
Improved error handling in atprogram. Most errors will now provide a message describing the issue.
Issue #AVRSV-5162:
Connecting to SAM devices where the security bit is set gives a generic 'Unable to connect' error message. If
the tool is able to talk to the DAP on the device, the details of the error message will state the DAP identificator
and a text saying that this usually means that the chip is locked.
Issue #AVRSV-5193:
Under options, there is a DSL Tools page. This is not part of Atmel Studio and has been removed.
Issue #AVRSV-5240:
Fixed issue where the Intel Hex file reader crashed when a hex file containing a single byte in a data record
was loaded.
Issue #AVRSV-5281:
Some errors are shown in the output window when reading properties from Xplain Pro kits.
Issue #AVRSV-5286:
During firmware upgrade, the window freezes and does not show any progress. This can also cause the
firmware upgrade to time out and fail, leaving the tool in a unusable state. To restore the firmware in this case,
use 'atfw' from the Atmel Studio command line.
Issue #AVRSV-5318:
Using software breakpoints with a SAM3N might cause the target to enter the Hard Fault handler.
Issue #AVRSV-5330:
The call stack window may not show the full depth of the call hierarchy when debugging AVR32 UC3 devices
with the simulator.
Issue #AVRSV-5331:
The voltage read by Atmel Studio is always 3.3V for SEGGER tools.
Issue #AVRSV-5338:
SEGGER tools has various programming and debugging options that are not controlled by Atmel Studio. The
options can be accessed through the JLINK Control Panel found in the notification area of the Windows task
bar, through the 'JLink Control Panel' button in the Programming Dialog or through the 'panel' command in
atprogram.
Issue #AVRSV-5443:
The 'KeepTimersRunning' choice is now shown for all ATtiny and ATmega devices.
Issue #AVRSV-5455:
For multicore devices, the default programming setting for all but core 0 is to skip programming as this is
usually carried out by core 0.
Issue #AVRSV-5470:
The D20 parts are held in reset by the debugger on the Xplained Pro board, causing them to not start after a
programming or debug session.
Issue #AVRSV-5474:
Rounting cards for the STK600 may be validated wrongly if it contains a revision. This is typically seen on USB
devices.
Issue #AVRSV-5490:
Programming devices with mirrored memory can take excessive time.

42130B-MCU-05/2014
14
Issue #AVRSV-5554:
Programming devices over JTAG using the AVR One! could fail from the Programming Dialog with a "write
memory" error. This was caused by the AVR One! being reset as a consequence of reading the voltage during
programming to avoid memory corruption.
5.3 Known issues
Issue #AVRSV-283:
A message saying "webproperties.tlb could not be located" can be displayed on some systems. A workaround
for this problem is to make a copy of a file named "webproperties???.tlb" in "C:\Program Files (x86)\Common
Files\microsoft shared\MSEnv" (on the same location) and rename it to "webproperties.tlb".
Issue #AVRSV-414:
Power toggle and external reset is not handled gracefully in all situations.
Issue #AVRSV-546:
The .NET Framework installer might not work properly if network connectivity is limited. If connectivity is limited
please disconnect from the network or disable all active network adapters before starting installation of Atmel
Studio.
Issue #AVRSV-628:
Scrolling memory view does not work properly.
It is not possible to use the slider in the memory view to scroll it. Only the up and down arrows works.
Issue #AVRSV-680:
Sometimes breakpoints that are set in the Source Editor are not reflected correctly in the Disassembly Window
while debugging.
Issue #AVRSV-831:
Atmel Studio installation may fail on XP systems if the Microsoft Windows Imaging Component (32-bit) is not
installed. Please install this component, downloadable from http://www.microsoft.com/download/.
Issue #AVRSV-966:
Running the Atmel Studio installer using the "run as" option on Windows XP may crash the installer.
Issue #AVRSV-1192:
Internet Explorer 6 will not render the navigation menu in the user documentation correctly.
Issue #AVRSV-1254:
The asf.h header file is not included in all examples.
Workaround: Include this file manually if you add additional drivers using the
"Select Drivers from AVR Software Framework" dialog.
Issue #AVRSV-1436:
If a command times out during execution on a tool, then the next command can fail with a 'Command Error'.
This is due to desynchronization between the software and hardware, and is fixed by power cycling the tool.
Issue #AVRSV-1533:
Visual Studio 2010 RC/Beta version has conflict with RTM version of Microsoft Visual Studio 2010 Isolated
Shell. The workaround is to uninstall Microsoft Visual Studio 2010 isolated Shell that is installed with Atmel
Studio.
Issue #AVRSV-1557:
Mapped network drives do not appear in the Project Location window when creating a new project.
Issue #AVRSV-1603:
When debugging on ATmega16[A] or ATmega32[A] devices it is not possible to read out the value of UBRRH
using the debugger.

42130B-MCU-05/2014
15
Issue #AVRSV-1675:
If a driver for a tool has not been installed (first time it's plugged in) and the user plugs the tool into the PC
when Atmel Studio is running then the front-end will show the tool in the "Available Tools"-view but the back-
end will not have access to the tool as a OS driver for the tool does not exist. Any operation on the tool initiated
from the front-end will fail as it's not available to the back-end.
Restart Atmel Studio to access the tool.
Issue #AVRSV-1733:
Stepping in the Source View over a software reset may leave the target running on ATxmega devices.
Issue #AVRSV-1758:
Projects which include paths or files with non-Latin characters are not supported.
Issue #AVRSV-1760:
Service Pack 1 of Visual Studio 2010 installed on a PC where Atmel Studio 6 is installed, may initiate a need
for reapplying the SP1 installer. A dialog box will then appear during startup of Atmel Studio, and detail the
steps that must be taken.
Issue #AVRSV-1883:
The IO window does not fully support registers like e.g. DIRSET, DIRTGL and DIRCLR for the XMEGA family
(used to manipulate a corresponding DIR register). Toggling the value of bits in these registers have undefined
result on DIR.
Issue #AVRSV-1888:
Debugging ATmega128 in ATmega103 compatibility mode is not supported.
Issue #AVRSV-1895:
'Alt + G' does not open the file <avr/io.h>. This file is not parsed by Visual Assist.
Issue #AVRSV-1901:
Creating two projects in the same solution which have different devices is not supported. Create two different
solutions instead.
Issue #AVRSV-2022:
Running Folding@home together with Atmel Studio may cause unresponsive user interface. We recommend to
disable the Folding@home when running Atmel Studio.
Issue #AVRSV-2163:
Files/Folders with more than one consequent spaces are not supported as part of AVRStudio 5 projects.
Issue #AVRSV-2558:
HVPP for ATtiny2313A does not work on STK500.
Issue #AVRSV-2601:
During installation of Atmel studio, the Visual Studio 2010 Shell installation will re-register the 'vsjitdebugger'.
This might make Visual Studio 2008 and Visual Studio 2005 unable to debug a crashed application reported by
Windows.
Workaround : Run repair of Visual Studio on top of the Atmel Studio installation. This should re-enable the
capability of visual studio to get a chance to handle crashed applications.
Issue #AVRSV-2884:
Project creation may fail when file/folder name of the project or its sub-items name exceeds 256 characters
limit.
Issue #AVRSV-3313:
If you encounter the error : variable 'xxxx' must be const in order to be put into read-only section by means
of '_attribute_((progmem))', then this description applies. The problem is due to the incompatibility of the
ASF source code with the AVR GCC compiler. The GCC 4.6 Release document (http://gcc.gnu.org/gcc-4.6/
changes.html) mentions that the error is expected and to use the ASF projects created in 5.1 (i.e ASF 2.9.0)

42130B-MCU-05/2014
16
we have to use avr gcc toolchain verison 3.3.1 and for later ASF versions use 3.4.0. Alternatively you could
manually add the const qualifier to the variable(s) that are reported, when compiling ASF 2.9.0 projects with
AVR GCC toolchain 3.4.0 or later.
Issue #AVRSV-3376:
If a custom destination folder is selected in the Atmel Studio installer, some components will still install
themselves in the default location.
Issue #AVRSV-3672:
ASF projects cannot be created in UNC paths. To create the ASF project, map the UNC path to a network
drive.
Issue #AVRSV-3761:
If atprogram is interrupted during programming, the next invocation to the same programming tool may throw
an error. A hardware reset of the tool will resolve the issue.
Issue #AVRSV-3993:
On virtual machines like VirtualBox, the event endpoint may not work properly and no events will be
propagated from the tool to our backend. This mainly impacts debugging.
Issue #AVRSV-4005:
Setting flash region lockbits when using SEGGER may have no effect, as the SEGGER tool may unlock the
flash region before it writes to it at a later stage.
Issue #AVRSV-4037:
Using a SEGGER tool, after a chiperase in the programming dialogue, reading device flash to file does not
reflect the true (erased) state of the device.
Issue #AVRSV-4050:
User signature on RFR parts can only be accessed by JTAG or parallel programming.
Issue #AVRSV-4079:
Launching debug with an ELF file containing non-0xFF lockbits may fail. Lockbits should not be set for
debugging.
Issue #AVRSV-4216:
After installing an extension, some windows, most notably the Memory Windows, can pop up floating on the
screen and leaving a blank memory window docked. If this happens, rearrange the windows as desired.
Issue #AVRSV-4337:
Build abruptly fails in 6.0 Atmel studio without proper error message and the error window shows no error.
Tail of the Build Output:
Task "RunCompilerTask"
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========
Reason: Project file was upgraded from 6.0 to 6.1.
Steps to Restore back the project to working condition:
Scenario 1: (With Backup)
Check whether there is a back up project in the projectfolder with the name ProjectName_6_0 (For Example
the backup project is GccApplication1_6_0.cproj if the actual project name is GccApplication1.cproj)
* Project with the name GccApplication1.cproj is the upgraded project to confirm edit the project file in editor
you should be able to see <ProjectVersion>6.1</ProjectVersion>.
* Open the project GccApplication1_6_0.cproj in Atmel Studio 6.0. It should prompt you to save the solution file.
Save and build it should work fine.
Scenario 2: (Without Backup)

42130B-MCU-05/2014
17
If the backup project is not found in the project folder chances are that you would have upgraded the project
from 6.0 to 6.1 without opting for the backup.
* Edit the project file modify <ProjectVersion> tag and set the version to 6.0 and also modify the
<ToolchainName> tag by removing .C or .CPP from the tag ( For example com.Atmel.AVRGCC32.C must be
renamed as com.Atmel.AVRGCC32) build the project now.
Issue #AVRSV-4380:
When building a project in Atmel Studio, and if you get an error like the one as follows
<some file>.o: No such file or directory
during the linking stage, then it could be because of the number of characters in the command line. Windows
expects that the command line be less than 8192 characters.
To workaround the issue, reduce the name of the folder so that the command line becomes shorter.
Issue #AVRSV-4440:
The SAM header files have been updated, due to this there are breaking changes when upgrading from 6.0
to 6.1. Bare bone SAM projects created with Atmel Studio 6.0 can get compilation errors due to changes in
defines. You can continue to use the old headers by keeping Atmel Studio 6.0 and 6.1 installed in parallel and
use the toolchain from 6.0. ASF projects are not affected.
Issue #AVRSV-4501:
Toolchain libraries "Full Path" property will display the base path of the current toolchain.
Issue #AVRSV-4521:
If a library is removed, the Library list in the solution explorer may not update. Double click the "Libraries" node
to refresh the status of Libraries presence.
Issue #AVRSV-4576:
Modifying EEPROM data values in the memory view during debugging of XMEGAE5 devices causes the
EEPROM data to be corrupted.
Issue #AVRSV-4659:
Programming SAM4L and some UC3 devices may fail when core voltage is raised above 1.9 V.
Issue #AVRSV-4753:
In the information window for Xplained Pro kits, the revision is not the actual chip revision, but the revision
coded into the Xplained Pro itself. Use the Programming Dialog to read the correct revision from the device.
Issue #AVRSV-4953:
All users are asked to log in when downloading extensions from the Extension Manager. If the user for some
reason does not want to log in and closes the log-in dialog, the Extension Manager may crash Atmel Studio.
Issue #AVRSV-5050:
Starting the process by selecting "Start Debugging and Break" / "Start Without Debugging" doesn't perform
flash memory verification.So if BOOTPROT fuse is set in the device, flash memory may not get programmed
correctly and no error-message will be displayed to the User.
Issue #AVRSV-5271:
USB drivers and Atmel Kits Help installation might fail on 32-bit Windows Vista. As a result Atmel Studio may
not work correctly. The issue is usually related to out of date security certificates in Windows Vista. Ensuring
that the Windows version is up to date on security patches usually solves this issue.
Issue #AVRSV-5324:
Modifying SAMD20 port registers like OUTSET, OUTCLR and OUTTGL will not have the expected result
unless the full register value is taken into consideration. The mentioned registers reflects the current value of
OUT when read by the user application and Atmel Studio. Clicking a single bit in one of these registers in the
IO View will write back the full register with only the clicked bit toggled from its existing value, causing a set,
clear or toggle action also on other set bits in that register. These considerations can be avoided by directly
setting and clearing bits in the OUT (or corresponding) register.

42130B-MCU-05/2014
18
Issue #AVRSV-5339:
Variables in Live Watch are not updated when single stepping on UC3 devices.
Issue #AVRSV-5378:
SAM devices: Interrupt flags that are cleared by reading a register, can unexpectedly be cleared by the
debugger if the register is monitored in the IO view or the memory view in Atmel Studio. An example is the
RXRDY flag for USART0 in SAM4LC4C, which might be cleared if the debugger breaks e.g. in an ISR and
reads the RHR register in order to display its value.
Issue #AVRSV-5450:
During trace activation, Atmel Studio can silently fail to enable trace on multi-core devices where the
TRACESWO pin is shared by the cores through a mux that does not switch automatically to the active core.
To be able to get trace on these devices, the mux for the TRACESWO signal needs to be set correctly by the
users application.
Issue #AVRSV-5586:
After programming a SAMD 20, SAM D21 or SAM R21 device, the device will need external reset to be applied
once after programming to operate properly. This is only needed if the user code performs a software reset.

42130B-MCU-05/2014
19
6. Supported Devices
The following tables lists all supported tools and devices.
6.1 AVR UC3
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
AT32UC3A0128 D/P D/P D/P D/P D/P D/P P
AT32UC3A3128 D/P D/P D/P D/P D/P P
AT32UC3A3128S D/P D/P D/P D/P D/P P
AT32UC3B0128 D/P D/P D/P D/P D/P P
AT32UC3C0128C D/P D/P D/P D/P D/P P

42130B-MCU-05/2014
20
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
AT32UC3L0128 D/P D/P D/P D/P D/P P
AT32UC3L016 D/P D/P D/P D/P D/P D/P P
AT32UC3L0256 D/P D/P D/P D/P D/P P
AT32UC3L032 D/P D/P D/P D/P D/P D/P P
AT32UC3L064 D/P D/P D/P D/P D/P P D/P P
ATUC128D3 D/P D/P D/P D/P D/P P
ATUC128L3U D/P D/P D/P D/P D/P P
6.2 AVR Mega
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
AT90CAN128 D/P D/P P D/P D/P D/P P
AT90PWM1 D/P D/P P D/P D/P D/P P
AT90PWM2B D/P D/P P D/P D/P D/P P
AT90PWM3B D/P D/P P D/P D/P D/P P
AT90USB1286 D/P D/P P D/P D/P D/P P
ATA5702M322 D/P D/P P D/P D/P D/P P
ATA5782 D/P D/P P D/P D/P D/P P

42130B-MCU-05/2014
21
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATA5790N D/P D/P P D/P D/P D/P P
ATA6612C D/P D/P P D/P D/P D/P D/P P P
ATA6613C D/P D/P P D/P D/P D/P D/P P P
ATA6614Q D/P D/P P D/P D/P D/P D/P P P
ATA6616C D/P D/P P D/P D/P D/P P
ATA6617C D/P D/P P D/P D/P D/P P
ATmega128 D/P D/P P D/P D/P D/P D/P P
1
P
ATmega1284 D/P D/P P D/P D/P D/P D/P P P
ATmega1284P D/P D/P P D/P D/P D/P D/P P P
ATmega1284RFR2 D/P D/
P
2
P
2
D/
P
2
D/P D/
P
2
P
2
ATmega128A D/P D/P P D/P D/P D/P D/P P
ATmega128RFA1 D/P D/P P D/P D/P D/P P
P
2
P
2
D/
P
2
D/P D/
P
2
P
2
ATmega162 D/P D/P P D/P D/P D/P P P
ATmega164A D/P D/P P D/P D/P D/P D/P P P
ATmega164PA D/P D/P P D/P D/P D/P D/P P P
ATmega165P D/P D/P P D/P D/P D/P D/P P
ATmega165PA D/P D/P P D/P D/P D/P D/P P
ATmega168PA D/P D/P P D/P D/P D/P D/P D/P P P

42130B-MCU-05/2014
22
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATmega16HVA D/P D/P P D/P D/P D/P P
ATmega16HVB D/P D/P P D/P D/P D/P D/P P
ATmega16HVBrevBD/P D/P P D/P D/P D/P P
ATmega16M1 D/P D/P P D/P D/P D/P P
ATmega16U2 D/P D/P P D/P D/P D/P P
P
2
P
2
D/
P
2
D/P D/
P
2
P
2
P
2
P
2
D/
P
2
D/
P
2
D/P D/
P
2
P
2
ATmega324PA D/P D/P P D/P D/P D/P P D/P P P
ATmega328P D/P D/P P D/P D/P D/P D/P D/P P P
ATmega32C1 D/P D/P P D/P D/P D/P P
ATmega32HVB D/P D/P P D/P D/P D/P D/P P
ATmega32HVBrevBD/P D/P P D/P D/P D/P P

42130B-MCU-05/2014
23
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATmega406 D/P
P
2
P
2
D/
P
2
D/P D/
P
2
P
2
ATmega64C1 D/P D/P P D/P D/P D/P P
ATmega64HVE2 D/P D/P P D/P D/P D/P P
ATmega64RFR2 D/P D/
P
2
P
2
D/
P
2
D/P D/
P
2
P
2
ATmega8 P P P P P P D/P P P
ATmega8515 P P P P P P P P
ATmega8535 P P P P P P P
ATmega8A P P P P P P D/P P P
ATmega8HVA D/P D/P P D/P D/P D/P P

42130B-MCU-05/2014
24
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
Notes:
1
The ATmega128 needs the STK501 extension board to connect to the STK500.
2
The user signature pages can only be accessed by JTAG programming or parallel programming, not by ISP programming.
6.3 SAM
Note The JTAGICE3 added SAM support in firmware version 3. Older firmware versions are not able to
program or debug SAM devices.
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATSAM3A4C D/P D/P D/P
ATSAM3A8C D/P D/P D/P
ATSAM3N00A D/P D/P D/P
ATSAM3N00B D/P D/P D/P
ATSAM3N0C D/P D/P D/P
ATSAM3S1A D/P D/P D/P
ATSAM3S1B D/P D/P D/P
ATSAM3S1C D/P D/P D/P
ATSAM3SD8B D/P D/P D/P

42130B-MCU-05/2014
25
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATSAM3SD8C D/P D/P D/P
ATSAM3U1C D/P D/P D/P
ATSAM3U1E D/P D/P D/P
ATSAM3X4C D/P D/P D/P
ATSAM3X4E D/P D/P D/P
ATSAM3X8C D/P D/P D/P
ATSAM3X8E D/P D/P D/P
ATSAM3X8H D/P D/P D/P
ATSAM4C16C D/P
ATSAM4C32C D/P
ATSAM4C32E D/P
ATSAM4C8C D/P
ATSAM4CMP16C D/P
ATSAM4CMP32C D/P
ATSAM4CMP8C D/P
ATSAM4CMS16C D/P
ATSAM4CMS32C D/P
ATSAM4CMS8C D/P
ATSAM4CP16B D/P
ATSAM4E16C D/P D/P D/P
ATSAM4E16E D/P D/P D/P D/P
ATSAM4E8C D/P D/P D/P
ATSAM4E8E D/P D/P D/P
ATSAM4LC2A D/P D/P D/P
ATSAM4LC2B D/P D/P D/P
ATSAM4LC2C D/P D/P D/P
ATSAM4LC4C D/P D/P D/P D/P
ATSAM4LC8C D/P D/P D/P D/P
ATSAM4LS2A D/P D/P D/P
ATSAM4LS2B D/P D/P D/P
ATSAM4LS2C D/P D/P D/P

42130B-MCU-05/2014
26
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATSAM4N16C D/P D/P D/P D/P
ATSAM4SA16B D/P D/P D/P D/P
ATSAM4SA16C D/P D/P D/P D/P
ATSAM4SD16C D/P D/P D/P
ATSAM4SD32C D/P D/P D/P D/P
ATSAM4SP32A D/P D/P D/P
ATSAMD20E14 D/P D/P D/P D/P
ATSAMD20E18 D/P D/P D/P
ATSAMD20G14 D/P D/P D/P D/P
ATSAMD20J14 D/P D/P D/P D/P

42130B-MCU-05/2014
27
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATSAMD21E15A D/P D/P D/P
ATSAMD21G15A D/P D/P D/P
ATSAMD21G18A D/P D/P D/P D/P
ATSAMD21J15A D/P D/P D/P
ATSAMD21J18A D/P D/P D/P D/P
ATSAMG51G18 D/P D/P D/P D/P
ATSAMG51N18 D/P D/P D/P D/P
ATSAMG53G19 D/P D/P D/P D/P
ATSAMG53N19 D/P D/P D/P D/P
ATSAMR21E16A D/P D/P D/P
ATSAMR21G16A D/P D/P D/P
ATSAMR21G17A D/P D/P D/P
ATSAMR21G18A D/P D/P D/P D/P
6.4 AVR Tiny
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATtiny10 P P D/P P
ATtiny13 D/P D/P P D/P D/P D/P D/P P P
ATtiny13A D/P D/P P D/P D/P D/P D/P P P
ATtiny1634 D/P D/P P D/P D/P D/P D/P P
ATtiny167 D/P D/P P D/P D/P D/P P
ATtiny20 P P D/P P
ATtiny24A D/P D/P P D/P D/P D/P D/P P
ATtiny26 P P P P P P D/P P P

42130B-MCU-05/2014
28
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATtiny28 P P
ATtiny4 P P D/P P
ATtiny40 P P D/P P
ATtiny43U D/P D/P P D/P D/P D/P D/P P
ATtiny5 P P D/P P
ATtiny828 D/P D/P P D/P D/P D/P P D/P P
ATtiny87 D/P D/P P D/P D/P D/P P
ATtiny88 D/P D/P P D/P D/P D/P P D/P P P
ATtiny9 P P D/P P
6.5 AVR Xmega
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATxmega128A1 D/P D/
P
1
P D/P D/P D/P P D/P P
ATxmega128A1U D/P D/P P D/P D/P D/P D/P D/P P
ATxmega128A3 D/P D/
P
2
P D/P D/P D/P D/P P
ATxmega128A3U D/P D/P P D/P D/P D/P D/P P
ATxmega128B1 D/P D/P P D/P D/P D/P D/P P
ATxmega128C3 D/P D/P P D/P D/P D/P D/P P

42130B-MCU-05/2014
29
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATxmega128D3 D/P D/
P
3
P D/P D/P D/P D/P P
ATxmega128D4 D/P D/P P D/P D/P D/P D/P P
ATxmega16A4 D/P D/P P D/P D/P D/P D/P P
ATxmega16E5 D/P D/P P D/P D/P D/P D/P P
ATxmega192A3 D/P D/
P
2
P D/P D/P D/P D/P P
ATxmega192D3 D/P D/
P
3
P D/P D/P D/P D/P P
ATxmega256A3 D/P D/
P
2
P D/P D/P D/P D/P P
ATxmega256A3B D/P D/
P
4
P D/P D/P D/P D/P P
ATxmega256A3BU D/P D/P P D/P D/P D/P D/P P
ATxmega256D3 D/P D/
P
3
P D/P D/P D/P D/P P
ATxmega32A4 D/P D/P P D/P D/P D/P D/P P
ATxmega64A1 D/P D/
P
1
P D/P D/P D/P D/P P
ATxmega64A3 D/P D/
P
2
P D/P D/P D/P D/P P

42130B-MCU-05/2014
30
Device
A
t
m
e
l
-
I
C
E
A
V
R

D
r
a
g
o
n
A
V
R
I
S
P

m
k
I
I
A
V
R

O
N
E
!
E
D
B
G
J
T
A
G
I
C
E
3
J
T
A
G
I
C
E
m
k
I
I
m
E
D
B
G
Q
T
6
0
0
S
A
M
-
I
C
E
S
i
m
u
l
a
t
o
r
S
T
K
5
0
0
S
T
K
6
0
0
ATxmega64D3 D/P D/
P
3
P D/P D/P D/P D/P P
Notes:
1
XMEGA PDI mode on AVR Dragon does not work for the ATxmega64A1 and ATxmega128A1, revision A-I.
2
XMEGA PDI mode on AVR Dragon does not work for the ATxmega64A3, ATxmega128A3, ATxmega192A3 and
ATxmega256A3, revision A, B, C and E.
3
XMEGA PDI mode on AVR Dragon does not work for the ATxmega64D3, ATxmega128D3, ATxmega192D3 and
ATxmega256D3, revision A, B, C and E.
4
XMEGA PDI mode on AVR Dragon does not work for the ATxmega256A3B, revision A, B, C and E.

42130B-MCU-05/2014
31
7. Device Notes
The following mature devices are not recommended for new designs:
ATtiny11
ATtiny12
ATtiny15
ATtiny22
AT90S1200
AT90S2313
AT90S2323
AT90S2343
AT90S4433
AT90S8515
AT90S8535
ATmega323
ATmega161
ATmega163
ATmega103
ATmega165
ATmega169
ATmega64HVE
ATmega32U6
AT90PWM2
AT90PWM3
AT90SCR100
AT86RF401
See www.atmel.com for replacements.

42130B-MCU-05/2014
32
8. Contact Information and Disclaimer
For support on Atmel Studio please contact [email protected].
8.1 Disclaimer
Atmel Studio is distributed free of charge for the purpose of developing applications for Atmel ARM and Atmel
AVR processors. Use for other purposes is not permitted; see the software license agreement for details. Atmel
Studio comes without any warranty.

42130B-MCU-05/2014
33
9. Document Revision History
Document
revision
Date Comment
42130B 05/2014 Update for 6.2 final release
42130A 01/2014 First release
Atmel Corporation 1600 Technology Drive, San Jose, CA 95110 USA T: (+1)(408) 441.0311 F: (+1)(408) 436.4200 | www.atmel.com
2014 Atmel Corporation. All rights reserved. / Rev.: 42130B-MCU-05/2014
Atmel
, Atmel logo and combinations thereof, Enabling Unlimited Possibilities
, AVR, tinyAVR, XMEGA, megaAVR, and others are registered

trademarks or trademarks of Atmel Corporation or its subsidiaries. Windows, and others, are registered trademarks of Microsoft Corporation in U.S. and
or other countries. ARM is a registered trademark of ARM Ltd. Other terms and product names may be trademarks of others.
Disclaimer: The information in this document is provided in connection with Atmel products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted
by this document or in connection with the sale of Atmel products. EXCEPT AS SET FORTH IN THE ATMEL TERMS AND CONDITIONS OF SALES LOCATED ON THE ATMEL WEBSITE,
ATMEL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL ATMEL BE LIABLE FOR
ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS AND PROFITS, BUSINESS
INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF ATMEL HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. Atmel makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to
specifications and products descriptions at any time without notice. Atmel does not make any commitment to update the information contained herein. Unless specifically provided otherwise,
Atmel products are not suitable for, and shall not be used in, automotive applications. Atmel products are not intended, authorized, or warranted for use as components in applications intended
to support or sustain life.

AStudio6!2!1153 Readme

Uploaded by

Copyright:

Available Formats

AStudio6!2!1153 Readme

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AStudio6!2!1153 Readme

Uploaded by

Copyright:

Available Formats

42130B-MCU-05/2014

, Atmel logo and combinations thereof, Enabling Unlimited Possibilities

, AVR, tinyAVR, XMEGA, megaAVR, and others are registered

You might also like