AStudio6 2sp2 1563

RELEASE NOTES

Atmel Studio 6.2 Service Pack 2

Welcome to Atmel Studio

Atmel Studio is the integrated development platform from Atmel

®

. It provides 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 such as Atmel Video Lounge

1

, Atmel Store and datasheets to keep you updated and help you to design your solutions.

With strong extension possibilities and best use and productivity.

online gallery

3

, it is possible for both designers and 3rd party to provide plug-ins and customize the environment for

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 see “Supported

Devices” on page 19 .

1

http://atmel.com/video/

2

http://store.atmel.com

3

http://gallery.atmel.com

42399A-MCU-02/2015

Table of Contents

Welcome to Atmel Studio ............................................................. 1

1. New and Noteworthy .............................................................. 3

1.1.

Atmel Studio 6.2 Service Pack 2 .............................................. 3

1.2.

Atmel Studio 6.2 Service Pack 1 .............................................. 3

1.3.

Atmel Studio 6.2 ................................................................... 3

1.4.

Atmel Studio 6.1 Update 2 ...................................................... 4

1.5.

Atmel Studio 6.1 Update 1.1 ................................................... 4

1.6.

Atmel Studio 6.1 Update 1 ...................................................... 4

1.7.

Atmel Studio 6.1 ................................................................... 4

1.8.

Atmel Studio 6.0 ................................................................... 5

1.9.

AVR Studio 5.1 ..................................................................... 5

2. FAQ ......................................................................................... 6

3. Installation Instructions .......................................................... 10

3.1.

System Requirements .......................................................... 10

3.1.1.

Supported Operating Systems ................................... 10

3.1.2.

Supported Architectures ............................................ 10

3.1.3.

Hardware Requirements ........................................... 10

3.2.

Downloading and Installing .................................................... 10

4. Atmel Studio Extensions ....................................................... 12

5. Bugs and New Features ....................................................... 13

5.1.

Notable bugs fixed ............................................................... 13

5.2.

Known issues ..................................................................... 13

6. Supported Devices ................................................................ 19

6.1.

AVR UC3 ........................................................................... 19

6.2.

AVR Mega .......................................................................... 20

6.3.

SAM .................................................................................. 24

6.4.

AVR Tiny ........................................................................... 29

6.5.

AVR Xmega ........................................................................ 30

7. Device Notes ......................................................................... 32

8. Contact Information and Disclaimer ...................................... 33

8.1.

Disclaimer .......................................................................... 33

9. Document Revision History ................................................... 34

Atmel Studio 6.2 Service Pack 2 [RELEASE NOTES]

42399A-MCU-02/2015

2

1.

1.1

1.2

1.3

New and Noteworthy


● Atmel Software Framework 3.21.0

● Added support for the ATSAML21 device family

● Added support for the ATSAMV7 device family, based on the ARM Cortex-M7 core



● AVR 8 Toolchain 3.4.5 with upstream versions

1

:

● GCC 4.8.1

● Binutils 2.41

● avr-libc 1.8.0svn

● gdb 7.8

● AVR 32 Toolchain 3.4.2 with upstream versions

1

:

● GCC 4.4.7

● Binutils 2.23.1

● ARM GCC Toolchain 4.8.4 with upstream versions

1

:

● GCC 4.8.4

● Binutils 2.23.1

● gdb 7.8

● Support for trace buffers for ARM (MTB) and AVR32 UC3 (NanoTrace)

● Support for attaching to targets

Atmel Studio 6.2


● 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

1

For more information, see the readme that is installed as part of the toolchain.


42399A-MCU-02/2015

3

1.4

1.5

1.6

1.7

● Nonintrusive trace support for SAM3 and SAM4 family of devices including

● Interrupt trace and 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

Atmel Studio 6.1 Update 2

● Support for SAM D20 devices on the JTAGICE3


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

Atmel Studio 6.1 Update 1


● 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


42399A-MCU-02/2015

4

1.8

1.9

● Command line utility for firmware upgrade

● Stimulus for simulator. Create a stimuli file to write register values while executing simulation.


● 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

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

● Enhancements to programming dialog including support for ELF programming

● New version of Visual Assist with several enhancements and bugfixes


42399A-MCU-02/2015

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.

I get an error during installation of the Atmel USB Driver Package

During installation of the Atmel USB Driver Package, you might get the error 0x800b010a - A certificate

chain could not be built to a trusted root authority. This means that the certificate that signs the installer could not be validated using the certificate authority built in to Windows.

The reason for not being able to validate the certificate is because the certificate chain needs to be updated through Windows Update. Make sure that you have received all updates, so that Windows is able to validate the certificate.

If you are not able to update your computer due to the computer being offline or restricted in some way, then the root certificate update can be downloaded from http://support2.microsoft.com/kb/931125 .

3.

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. If you are uninstalling AVR Studio 4.0 or AVR32 Studio 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 the Atmel folder and registry paths.

4.

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.

5.

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), 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.

6.

The Atmel Studio installer crashes when installing using the run as option in Windows XP (any

architecture) with the Protect my computer... option enabled..

Do not use the run as option with the Protect my computer... option enabled. The installer will have read-only access to parts of the registry 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.

7.

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.

8.

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. Download the Atmel USB Driver installer from the Atmel web and install it.

9.

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.


42399A-MCU-02/2015

6

10.

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.

11.

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."

This probably means that your PC does not have Service Pack 3 for Windows XP installed. Install SP3 and then install Atmel Studio again.

12.

Atmel Studio takes a very long time to start, but runs well in a VM environment.

The Visual Studio shell (and thus Atmel Studio) does a considerable amount of processing during startup. 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.

13.

Verification and programming often fails 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. A workaround which works for most systems is to use an USB to serial adapter.

14.

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. 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.

15.

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. Clean up this location and try running the installer again.

16.

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.

17.

Can 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.

18.

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 inside the start page.

● Disable the startup page (alternative 2)

1. Go to Tools → Options → Environment → Startup → At Startup.

2. Select Show empty environment option.


42399A-MCU-02/2015

7

19.

How to improve studio performance on Windows XP or single core systems?

● 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.

● 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.

20.

How to improve studio performance for any supported version of Windows?

● 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.

21.

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

22.

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. 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 version should be 7.X.X.X. for the new API. The latest API can be found at http://support.microsoft.com/kb/971513 .

23.

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. Uncheck the Parse all files when opening the project.

24.

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.

Press Ctrl+Shift+Alt+F12 twice to force Atmel Studio to garbage collect.

25.

Does Atmel Studio perform better on multi-core processors than on single-core systems?

Yes, Atmel Studio performs better on a multi-core system.


42399A-MCU-02/2015

8

26.

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 the parallel execution feature in the GNU make utility. This option may cause the build log to be displayed unordered.


42399A-MCU-02/2015

9

3.

3.1

3.1.1

3.1.2

3.1.3

3.2

Installation Instructions

System Requirements

Supported Operating Systems

● Windows XP (x86) with Service Pack 3 - all editions except Starter Edition

● Windows Vista (x86 and 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 and 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)

Supported Architectures

● 32-Bit (x86)

● 64-Bit (x64)

Hardware Requirements

● Computer that has a 1.6 GHz 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

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

● Save all your work before starting, because the installation might prompt you for a restart if required

● 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 the

FAQ

for more information.

● Double click the installer executable file. Note that this might take some time to extract depending on H/W configuration.


42399A-MCU-02/2015

10

● Atmel Studio Prerequisites installation will start. If you have all the prerequisites already installed then this dialog will not be shown.

● If the .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 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 or upgrade the existing Jungo USB driver

● Accept the license agreement and proceed through the installation

● If you have previous versions of Jungo USB driver then the installer will update them. The Atmel

USB driver (Jungo USB Driver and SAM USB Driver) is fully compatible with its previous versions.

AVR Studio 4, Studio 32 and AVR Studio 5.0 and 5.1 should continue to work with the updated driver without any issues.

● After this the 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 Atmel Studio. Choose this 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 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).


42399A-MCU-02/2015

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.


42399A-MCU-02/2015

12

5.

5.1

5.2

Bugs and New Features

Notable bugs fixed

Issue #AVRSV-5685:

The first flash page can be corrupted by re-connecting with a SAM-ICE after a programming session. Problem is seen in relation to reading the CoreSight ROM table, which is done during the connect sequence.


Debugging and stepping in code can lead to interrupts being disabled.


Support links in Atmel Studio points to the old support site.


Error message pops up during programming using JTAGICEmkII, saying that the device id is wrong. This is due to an error during the programming session, which caused Atmel Studio to start a new programming session inside the already ongoing session.


Compile time in Atmel Studio is many times greater then building directly from the command line. This has been traced to a issue in how Atmel Studio parses warning information and presents it to the user.


Locking region may fail in few scenarios. If it fails import the user page fuse settings from a file through memories page in "Device programming" dialog


Programming files that have non-ascii charaters in the path fails. This is now fixed by doing a UTF-8 to UTF-16 conversion if the path is not found.

Known issues


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".


Power toggle and external reset is not handled gracefully in all situations.


The .NET Framework installer might not work properly if network connectivity is limited. If connectivity is limited disconnect from the network or disable all active network adapters before starting installation of Atmel Studio.


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.


Sometimes breakpoints that are set in the Source Editor are not reflected correctly in the Disassembly Window while debugging.


Atmel Studio installation may fail on XP systems if the Microsoft Windows Imaging Component (32-bit) is not installed. Install this component, downloadable from Microsoft.


Running the Atmel Studio installer using the "run as" option on Windows XP may crash the installer.


42399A-MCU-02/2015

13


Internet Explorer 6 will not render the navigation menu in the user documentation correctly.


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.


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.


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.


Mapped network drives do not appear in the Project Location window when creating a new project.


When debugging on ATmega16[A] or ATmega32[A] devices it is not possible to read out the value of UBRRH using the debugger.


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 it will be shown in the "Available Tools" view but not have access to the tool as a OS driver for the tool does not exist. Any operation on the tool initiated will fail.

Restart Atmel Studio to access the tool.


Stepping in the source view over a software reset may leave the target running on ATxmega devices.


Projects which include paths or files with non-Latin characters are not supported.


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.


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.


Debugging ATmega128 in ATmega103 compatibility mode is not supported.


'Alt + G' does not open the file <avr/io.h>. This file is not parsed by Visual Assist.


Creating two projects in the same solution which have different devices is not supported. Create two different solutions instead.


Running Folding@home together with Atmel Studio may cause unresponsive user interface. We recommend to disable the Folding@home when running Atmel Studio.


42399A-MCU-02/2015

14


Files or folders with more than one consequent spaces are not supported as part of AVRStudio 5 projects.


Reading target voltage with the TPI interface enabled might cause all further actions to fail.


HVPP for ATtiny2313A does not work on STK500.


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.


Project creation may fail when file/folder name of the project or its sub-items name exceeds 256 characters limit.


Autocompletion and snippets provided by Visual Assist can generate invalid embedded C++, and it might also try to insert C++ in a C project.

This includes exceptions, classes and namespace declarations.


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) 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.


If a custom destination folder is selected in the Atmel Studio installer, some components will still install themselves in the default location.


ASF projects cannot be created in UNC paths. To create the ASF project, map the UNC path to a network drive.


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.


On virtual machines like VirtualBox, the event endpoint may not work properly and no events will be propagated from the tool to Atmel Studio. This mainly impacts debugging.


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.


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.


42399A-MCU-02/2015

15


User signature on RFR parts can only be accessed by JTAG or parallel programming.


Launching debug with an ELF file containing non-0xFF lockbits may fail. Lockbits should not be set for debugging.


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.


Build abruptly fails in 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)

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.


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.


The SAM header files have been updated and 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.


Toolchain libraries "Full Path" property will display the base path of the current toolchain.


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.


42399A-MCU-02/2015

16


Modifying EEPROM data values in the memory view during debugging of XMEGAE5 devices causes the

EEPROM data to be corrupted.


Programming SAM4L and some UC3 devices may fail when core voltage is raised above 1.9 V.


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.


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.


Starting the process by selecting "Start Debugging and Break" or "Start Without Debugging" does not perform flash memory verification. If the BOOTPROT fuse is set in the device, flash memory may not get programmed correctly and no error will be displayed.


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.


Variables in Live Watch are not updated when single stepping on UC3 devices.


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 and reads the RHR register in order to display its value.


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.


The Live Watch feature in Atmel Studio does not work well with expressions as the variable. Since the watch in this case is on a memory address, the Live Watch implicitly adds a ampersand (&) before the variable being watched to extract the address of the variable. This means that expressions will be evaluated to the wrong value.


Relocating the .text segment may cause the debugger to fail in certain conditions. This results in 'Start debugging and break' to stop at a high address in the disassembly view.

To make the debugger break the application entry, tick the 'Override VTOR' option in the project properties, and ensure that the text box contains the address of the interrupt vector. This is usually 'exception_table' or '&exception_table', depending on the startup code in the project. The difference between these is that

'&exception_table' is a struct, while 'exception_table' is a function pointer array.


Installation of Atmel Studio 6.2.1153 after Atmel Studio 6.2 Service Pack 1 corrupts the installation of Atmel

Studio 6.2 Service Pack. The installations cannot co-exist so always uninstall Atmel Studio 6.2 Service Pack 1 before installing Atmel Studio 6.2.1153.


42399A-MCU-02/2015

17


Trying to enable GDB for AVR32 projects will probably fail in even the simplest debugging, such as Halt, Step, and Go. It is not recommended to ignore the warning shown when this option is enabled for a project.


The Atmel USB Driver Package may fail during installation with error '0x800b010a - A certificate chain could not be built to a trusted root authority'. The reason for this is that the built in certificate in Windows is out of date and needs to be updated through Windows Update. If you are unable to perform a update, then the update can be manually downloaded from KB931125 from Microsoft.


Atmel Studio would not be able to erase a SAM4L part if the part was put into a sleep mode immediately after startup. Note that a POR may be required after programming to be able to establish contact.


42399A-MCU-02/2015

18

6.

6.1

Supported Devices

The following tables lists all supported tools and devices.

AVR UC3

Device

AT32UC3A0128 D/P D/P







AT32UC3A3128S D/P D/P



AT32UC3A364 D/P D/P






AT32UC3A464 D/P D/P


AT32UC3B0128 D/P D/P



AT32UC3B064 D/P D/P




AT32UC3B164 D/P D/P

AT32UC3C0128C D/P D/P











D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P


42399A-MCU-02/2015

19

6.2

Device


AT32UC3L0128

AT32UC3L016

D/P

D/P

D/P

D/P

AT32UC3L0256

AT32UC3L032

AT32UC3L064

D/P D/P

D/P D/P

D/P D/P

ATUC128D3

ATUC128D4

ATUC128L3U

ATUC128L4U

ATUC256L3U

ATUC256L4U

ATUC64D3

ATUC64D4

ATUC64L3U

ATUC64L4U

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

AVR Mega

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

D/P

D/P

D/P

Device

AT90CAN128

AT90CAN32

AT90CAN64

AT90PWM1

AT90PWM161

AT90PWM216

AT90PWM2B

AT90PWM316

AT90PWM3B

AT90PWM81

AT90USB1286

AT90USB1287

AT90USB162

AT90USB646

AT90USB647

AT90USB82

ATA5272

ATA5505

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P


42399A-MCU-02/2015

20

Device

ATA5702M322

ATA5781

ATA5782

ATA5783

ATA5790

ATA5790N

ATA5791

ATA5795

ATA5831

ATA5832

ATA5833

ATA6285

ATA6286

ATA6612C

ATA6613C

ATA6614Q

ATA6616C

ATA6617C

ATA664251

ATA8210

ATA8215

ATA8510

ATA8515

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

ATmega128

ATmega1280

ATmega1281

D/P D/P P

D/P D/P P

D/P D/P P

ATmega1284 D/P D/P P

ATmega1284P D/P D/P P

ATmega1284RFR2 D/P D/

P

2

P

2

ATmega128A D/P D/P P

ATmega128RFA1 D/P D/P P


P

2

P

2

ATmega16

ATmega162

D/P

D/P

D/P

D/P

P

P

ATmega164A

ATmega164P

ATmega164PA

ATmega165A

ATmega165P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

P

P

P

P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P

D/P

D/

P

2

D/P

D/P

D/

P

2

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/

P

2

D/P D/P

D/P D/P

D/P D/

P

2

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P

P

P

P

P

P

P

P

P

P

2

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

2

P

P

P

P

D/P

D/P P

P

D/P P

D/P P

D/P P

D/P

D/P

D/P P

D/P P

D/P P

D/P P

1

D/P

D/P

D/P P

D/P P


42399A-MCU-02/2015

21

Device

ATmega165PA

ATmega168

ATmega168A

ATmega168P

ATmega168PA

ATmega168PB

ATmega169A

ATmega169P

ATmega169PA

ATmega16A

ATmega16HVA

ATmega16HVB

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

P

P

P

P

P

ATmega16HVBrevBD/P D/P P

ATmega16M1 D/P D/P P

ATmega16U2

ATmega16U4

D/P

D/P

D/P

D/P

P

P




P

2

P

2


P

2

P

2

ATmega32

ATmega324A

ATmega324P

ATmega324PA

ATmega325

ATmega3250

ATmega3250A

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

P

P

P

P

D/P D/P P

D/P D/P P

ATmega3250P D/P D/P P

ATmega3250PA D/P D/P P

ATmega325A

ATmega325P

D/P

D/P

D/P

D/P

P

P

ATmega325PA

ATmega328

ATmega328P

D/P D/P P

D/P D/P P

D/P D/P P

ATmega329

ATmega3290

ATmega3290A

ATmega3290P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

P

P

P


D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/

P

2

D/

P

2

D/

P

2

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P D/P

D/P D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/

P

2

D/P D/

P

2

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P

D/P

D/P

D/P

D/P P

D/P P

D/P P

D/P P

D/P P

D/P P

D/P P

D/P P

D/P P

D/P

D/P P

D/P P

D/P P

D/P P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P P

D/P P

D/P

D/P

D/P

D/P

D/P

P

P

P

P

P

P

P

2

P

P

P

P

P

P

P

P

P

P

P

P

P

2

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P


42399A-MCU-02/2015

22

Device

ATmega329A

ATmega329P

ATmega329PA

ATmega32A

ATmega32C1

ATmega32HVB

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

ATmega32HVBrevBD/P D/P P


ATmega32U2

ATmega32U4

ATmega406

ATmega48

D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

P

P

ATmega48A

ATmega48P

ATmega48PA

ATmega48PB

ATmega64

ATmega640

ATmega644

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

P

P

P

P

D/P D/P P

D/P D/P P

ATmega644A

ATmega644P

D/P D/P P

D/P D/P P



P

2

P

2

ATmega645 D/P D/P P

ATmega6450

ATmega6450A

ATmega6450P

ATmega645A

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

ATmega645P

ATmega649

ATmega6490

ATmega6490A

ATmega6490P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

ATmega649A

ATmega649P

ATmega64A

ATmega64C1

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

P

P

P

ATmega64HVE2 D/P D/P P


D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/

P

2

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/

P

2

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

2

P

P

P

P

P

P

P

P

P

P

P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P P

D/P

D/P P

D/P P

D/P P

D/P P

D/P P

D/P

D/P

D/P P

D/P P

D/P

D/P P


42399A-MCU-02/2015

23

6.3

Note

Device

ATmega64RFR2 D/P D/

P

2

ATmega8

ATmega8515

ATmega8535

ATmega88

ATmega88A

P

P

P

P

P

P P P

D/P D/P P

D/P D/P P

P

P

2

ATmega88P

ATmega88PA

ATmega88PB

ATmega8A

ATmega8HVA

ATmega8U2

D/P

D/P

D/P

P

D/P

D/P

D/P

D/P

D/P

P

D/P

D/P

P

P

P

P

P

P

Notes:

D/

P

P

P

P

2

D/P

D/P

D/P

D/P

D/P

P

D/P

D/P

D/P

P

P

D/

P

P

P

P P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P P

D/P D/P

D/P D/P

D/P

D/P P

D/P P

D/P P

D/P P

D/P P

D/P P

P

P

P

2

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.

P

P

P

P

P

P

P

P

P

P

P

SAM

The JTAGICE3 added SAM support in firmware version 3. Older firmware versions are not able to program or debug SAM devices.

Device

ATSAM3A4C

ATSAM3A8C

ATSAM3N00A

ATSAM3N00B

ATSAM3N0A

ATSAM3N0B

ATSAM3N0C

ATSAM3N1A

ATSAM3N1B

ATSAM3N1C

ATSAM3N2A

ATSAM3N2B

ATSAM3N2C

ATSAM3N4A

ATSAM3N4B

ATSAM3N4C

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P


42399A-MCU-02/2015

24

Device

ATSAM3S1A

ATSAM3S1B

ATSAM3S1C

ATSAM3S2A

ATSAM3S2B

ATSAM3S2C

ATSAM3S4A

ATSAM3S4B

ATSAM3S4C

ATSAM3S8B

ATSAM3S8C

ATSAM3SD8B

ATSAM3SD8C

ATSAM3U1C

ATSAM3U1E

ATSAM3U2C

ATSAM3U2E

ATSAM3U4C

ATSAM3U4E

ATSAM3X4C

ATSAM3X4E

ATSAM3X8C

ATSAM3X8E

ATSAM3X8H

ATSAM4C16C

ATSAM4C32C

ATSAM4C32E

ATSAM4C8C

ATSAM4CMP16C

ATSAM4CMP32C

ATSAM4CMP8C

ATSAM4CMS16C

ATSAM4CMS32C

ATSAM4CMS8C

ATSAM4CP16B

ATSAM4CP16C

ATSAM4E16C

ATSAM4E16E

ATSAM4E8C

ATSAM4E8E

ATSAM4LC2A

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P


42399A-MCU-02/2015

25

Device

ATSAM4LC2B

ATSAM4LC2C

ATSAM4LC4A

ATSAM4LC4B

ATSAM4LC4C

ATSAM4LC8A

ATSAM4LC8B

ATSAM4LC8C

ATSAM4LS2A

ATSAM4LS2B

ATSAM4LS2C

ATSAM4LS4A

ATSAM4LS4B

ATSAM4LS4C

ATSAM4LS8A

ATSAM4LS8B

ATSAM4LS8C

ATSAM4N16B

ATSAM4N16C

ATSAM4N8A

ATSAM4N8B

ATSAM4N8C

ATSAM4S16B

ATSAM4S16C

ATSAM4S2A

ATSAM4S2B

ATSAM4S2C

ATSAM4S4A

ATSAM4S4B

ATSAM4S4C

ATSAM4S8B

ATSAM4S8C

D/P

D/P

D/P

D/P

D/P

D/P

ATSAM4SA16B

ATSAM4SA16C

D/P

D/P

ATSAM4SD16B D/P

ATSAM4SD16C D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

ATSAM4SD32B D/P

ATSAM4SD32C D/P

ATSAM4SP32A D/P

ATSAMD09C13A D/P

ATSAMD10C13A D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P

D/P D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P

D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P


42399A-MCU-02/2015

26

Device

ATSAMD10C14A D/P

ATSAMD10D13AM D/P

ATSAMD10D13AS D/P

ATSAMD10D14AM D/P

ATSAMD10D14AS D/P

ATSAMD11C14A D/P

ATSAMD11D14AM D/P

ATSAMD11D14AS D/P

ATSAMD20E14

ATSAMD20E15

ATSAMD20E16

ATSAMD20E17

D/P

D/P

D/P

D/P

ATSAMD20E18

ATSAMD20G14

ATSAMD20G15

ATSAMD20G16

D/P

D/P

D/P

D/P

ATSAMD20G17 D/P

ATSAMD20G17U D/P

ATSAMD20G18 D/P

ATSAMD20G18U D/P

ATSAMD20J14 D/P

ATSAMD20J15

ATSAMD20J16

D/P

D/P

ATSAMD20J17 D/P

ATSAMD20J18 D/P

ATSAMD21E15A D/P

ATSAMD21E16A D/P

ATSAMD21E17A D/P

ATSAMD21E18A D/P

ATSAMD21G15A D/P

ATSAMD21G16A D/P

ATSAMD21G17A D/P

ATSAMD21G18A D/P

ATSAMD21J15A D/P

ATSAMD21J16A D/P

ATSAMD21J17A D/P

ATSAMD21J18A D/P

ATSAME70J19

ATSAME70J20

D/P

D/P

ATSAME70J21

ATSAME70N19

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P


42399A-MCU-02/2015

27

Device

ATSAME70N20

ATSAME70N21

ATSAME70Q19

ATSAME70Q20

D/P

D/P

D/P

D/P

ATSAME70Q21 D/P

ATSAMG51G18 D/P

ATSAMG51N18 D/P

ATSAMG53G19 D/P

ATSAMG53N19 D/P

ATSAMG54G19 D/P

ATSAMG54J19

ATSAMG54N19

D/P

D/P

ATSAMG55G19 D/P

ATSAMG55J19 D/P

ATSAML21E15A D/P

ATSAML21E16A D/P

ATSAML21E17A D/P

ATSAML21G16A D/P

ATSAML21G17A D/P

ATSAML21G18A D/P

ATSAML21J16A D/P

ATSAML21J17A D/P

ATSAML21J18A D/P

ATSAMR21E16A D/P

ATSAMR21E17A D/P

ATSAMR21E18A D/P

ATSAMR21G16A D/P

ATSAMR21G17A D/P

ATSAMR21G18A D/P

ATSAMS70J19 D/P

ATSAMS70J20

ATSAMS70J21

D/P

D/P

ATSAMS70N19

ATSAMS70N20

ATSAMS70N21

ATSAMS70Q19

D/P

D/P

D/P

D/P

ATSAMS70Q20

ATSAMS70Q21

ATSAMV70J19

ATSAMV70J20

ATSAMV70N19

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P


42399A-MCU-02/2015

28

6.4

Device

ATSAMV70N20

ATSAMV70Q19

ATSAMV70Q20

ATSAMV71J19

ATSAMV71J20

ATSAMV71J21

ATSAMV71N19

ATSAMV71N20

ATSAMV71N21

ATSAMV71Q19

ATSAMV71Q20

ATSAMV71Q21

AVR Tiny

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

Device

ATtiny10

ATtiny13

ATtiny13A

ATtiny1634

ATtiny167

ATtiny20

ATtiny2313

ATtiny2313A

ATtiny24

ATtiny24A

ATtiny25

ATtiny26

ATtiny261

ATtiny261A

ATtiny28

ATtiny4

ATtiny40

ATtiny4313

ATtiny43U

ATtiny44

ATtiny441

ATtiny44A

P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

P P P

D/P D/P P

P

P

D/P D/P P

D/P D/P P

D/P D/P P

P

P

D/P D/P P

D/P D/P P

D/P D/P P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

D/P P

P

D/P

D/P

D/P P

D/P

D/P

D/P

D/P

D/P

D/P P

D/P P

D/P

D/P

D/P P

D/P P

D/P

D/P

D/P P

D/P P

D/P P


42399A-MCU-02/2015

29

6.5

Device

ATtiny45

ATtiny461

ATtiny461A

ATtiny48

ATtiny5

ATtiny828

ATtiny84

ATtiny841

ATtiny84A

ATtiny85

ATtiny861

ATtiny861A

ATtiny87

ATtiny88

ATtiny9

AVR Xmega

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

D/P D/P P

P P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

D/P P

D/P P

D/P P

D/P P

D/P

D/P

D/P

D/P

D/P

D/P P

D/P P

D/P P

D/P P

D/P

Device

ATxmega128A1 D/P D/

P

1

P

ATxmega128A1U D/P D/P P

ATxmega128A3 D/P D/

P

2

P



ATxmega128B1

ATxmega128B3

D/P D/P P

D/P D/P P

ATxmega128C3 D/P D/P P

ATxmega128D3 D/P D/

P

3

P

ATxmega128D4 D/P D/P P

ATxmega16A4 D/P D/P P



ATxmega16D4

ATxmega16E5

ATxmega192A3

D/P

D/P

D/P

D/P

D/P D/

P

2

P

P

P

D/P D/P D/P

D/P D/P D/P D/P

D/P D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

D/P D/P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P


42399A-MCU-02/2015

30

Device



ATxmega192D3 D/P D/

P

3

P

ATxmega256A3 D/P D/

P

2

ATxmega256A3B D/P D/

P

4

P

P

ATxmega256A3BU D/P D/P P



ATxmega256D3 D/P D/

P

3

P

ATxmega32A4 D/P D/P P


ATxmega32C3

ATxmega32C4

ATxmega32D3

ATxmega32D4

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

P

P

P

P

ATxmega32E5 D/P D/P P


ATxmega384D3 D/P D/P P

ATxmega64A1 D/P D/

P

1

P


ATxmega64A3 D/P D/

P

2

P



ATxmega64B1

ATxmega64B3

ATxmega64C3

ATxmega64D3

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/

P

3

P

P

P

P

ATxmega64D4

ATxmega8E5

D/P D/P P

D/P D/P P

Notes:

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P D/P

D/P D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

D/P

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.

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P

P


42399A-MCU-02/2015

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.


42399A-MCU-02/2015

32

8.

8.1

Contact Information and Disclaimer

For support on Atmel Studio browse throught the Knowledge Base or open a support case at the

Support

1

page.

Atmel Design

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.

1

http://www.atmel.com/design-support/


42399A-MCU-02/2015

33

9.

Document Revision History

Document revision

42399A

Date

01/2015

Comment

Initial Release


42399A-MCU-02/2015

34

Atmel Corporation

1600 Technology Drive, San Jose, CA 95110 USA

© 2015 Atmel Corporation. / Rev.: 42399A-MCU-02/2015

T: (+1)(408) 441.0311

F: (+1)(408) 436.4200

| www.atmel.com

Atmel

®

, Atmel logo and combinations thereof, Enabling Unlimited Possibilities

®

, AVR

®

, tinyAVR

®

, XMEGA

®

, megaAVR

®

, and others are registered trademarks or trademarks of Atmel Corporation in U.S. and other countries. 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.

SAFETY-CRITICAL, MILITARY, AND AUTOMOTIVE APPLICATIONS DISCLAIMER: Atmel products are not designed for and will not be used in connection with any applications where the failure of such products would reasonably be expected to result in significant personal injury or death (“Safety-Critical Applications”) without an Atmel officer's specific written consent. Safety-Critical

Applications include, without limitation, life support devices and systems, equipment or systems for the operation of nuclear facilities and weapons systems. Atmel products are not designed nor intended for use in military or aerospace applications or environments unless specifically designated by Atmel as military- grade. Atmel products are not designed nor intended for use in automotive applications unless specifically designated by Atmel as automotive-grade.

AStudio6 2sp2 1563

RELEASE NOTES

Atmel Studio 6.2 Service Pack 2

Welcome to Atmel Studio

Table of Contents

1.

New and Noteworthy

2.

FAQ

3.

Installation Instructions

4.

Atmel Studio Extensions

5.

Bugs and New Features

6.

Supported Devices

7.

Device Notes

8.

Contact Information and Disclaimer

9.

Document Revision History

Related manuals

Table of contents

AStudio6 2sp2 1563

RELEASE NOTES

Atmel Studio 6.2 Service Pack 2

Welcome to Atmel Studio

Table of Contents

1.

New and Noteworthy

2.

FAQ

3.

Installation Instructions

4.

Atmel Studio Extensions

5.

Bugs and New Features

6.

Supported Devices

7.

Device Notes

8.

Contact Information and Disclaimer

9.

Document Revision History

Related manuals

MICROCHIP

ATAVRDRAGON

Atmel

AVR2052

Atmel

STK600-RC064SAM-72

Table of contents