| AVRSV-283: webproperties.tlb file missing.
| 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".
|
| AVRSV-414: Handle Power toggle and external reset for all emulators and architectures/families.
| Power toggle and external reset is not handled gracefully in all situations.
|
| AVRSV-546: .NET Framework install might not work if there is limited network connectivity.
| 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.
|
| AVRSV-628: Scrolling memory view does not work properly.
| 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.
|
| AVRSV-680: Breakpoint is not updating in the Disassembly and Code view.
| Sometimes breakpoints that are set in the Source Editor are not reflected correctly in the Disassembly Window while debugging.
|
| AVRSV-831: .NET install fail because Windows Imaging Component WIC is not installed.
| 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.
|
| AVRSV-966: Installer crashes when trying to install from "runas" option.
| Running the Atmel Studio installer using the "run as" option on Windows XP may crash the installer.
|
| AVRSV-1192: Internet Explorer 6 does not show user documentation correctly.
| Internet Explorer 6 will not render the navigation menu in the user documentation correctly.
|
| AVRSV-1254: The asf.h header file is not included in all examples.
| 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.
|
| AVRSV-1533: Microsoft Visual Studio 2010 Shell --> Error: Cannot publish because a project failed to build.
| 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.
|
| AVRSV-1557: Mapped network drives do not appear in Project Location window.
| Mapped network drives do not appear in the Project Location window when creating a new project.
|
| AVRSV-1603: shared register access not possible?.
| When debugging on ATmega16[A] or ATmega32[A] devices it is not possible to read out the value of UBRRH using the debugger.
|
| AVRSV-1675: Tool marked as available even though OS driver is not installed.
| 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.
|
| AVRSV-1733: Single step over SW reset on Xmega does not work.
| Stepping in the source view over a software reset may leave the target running on ATxmega devices.
|
| AVRSV-1758: Non-Latin characters in project paths are not supported.
| Projects which include paths or files with non-Latin characters are not supported.
|
| AVRSV-1760: Issues with AVR Studio 5 installed alongside Visual Studio 2010 SP1.
| 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.
|
| AVRSV-1883: PORT registers in IO view behaves incorrectly.
| 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.
|
| AVRSV-1888: Detect m103c compatibility fuse setting on atmega128.
| Debugging ATmega128 in ATmega103 compatibility mode is not supported.
|
| AVRSV-1895: VAssistX: Alt + G does not open file <avr/io.h>.
| 'Alt + G' does not open the file <avr/io.h>. This file is not parsed by Visual Assist.
|
| AVRSV-1901: Solution with two projects does not work.
| Creating two projects in the same solution which have different devices is not supported. Create two different solutions instead.
|
| AVRSV-2022: Conflicts with Folding@Home.
| Running Folding@home together with Atmel Studio may cause unresponsive user interface. We recommend to disable the Folding@home when running Atmel Studio.
|
| AVRSV-2163: File/Folder names with spaces are not built property.
| Files or folders with more than one consequent spaces are not supported as part of AVRStudio 5 projects.
|
| AVRSV-2558: HVPP for ATtiny2313A does not work on STK500.
| HVPP for ATtiny2313A does not work on STK500.
|
| AVRSV-2601: VS6 incompatibillity with AS5.
| 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.
|
| AVRSV-2884: AVR Studio cannot create a project from template with a deep file architecture.
| Project creation may fail when file/folder name of the project or its sub-items name exceeds 256 characters limit.
|
| AVRSV-3296: Visual assist inserts the c++ keywords, functions in C project.
| 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.
|
| AVRSV-3313: In Atmel Studio 6.1 compilation fails for ASF Projects created with AVR Studio 5.1.
| 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.
|
| AVRSV-3672: Can't use network path in "New Example Project from ASF"- dialog.
| ASF projects cannot be created in UNC paths. To create the ASF project, map the UNC path to a network drive.
|
| AVRSV-3993: JTAGICE3 event endpoint is not registered on virtual machines.
| 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.
|
| AVRSV-4005: Setting lockbits for SAM4LC4C have no effect.
| 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.
|
| AVRSV-4050: User signature on RFR parts can only be accessed by JTAG or parallel programming.
| User signature on RFR parts can only be accessed by JTAG or parallel programming.
|
| AVRSV-4079: Unable to launch using an ELF file containing LOCKBITS.
| Launching debug with an ELF file containing non-0xFF lockbits may fail. Lockbits should not be set for debugging.
|
| AVRSV-4337: After Installing AtmelStudio 6.1, the old projects does not build in earlier versions of AtmelStudio.
| 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.
|
| AVRSV-4380: No error or warning is displayed when number of characters in command line arguments exceeds microsoft limitation. .
| 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.
|
| AVRSV-4440: Breaking changes in SAM header files going from 6.0 to 6.1.
| 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.
|
| AVRSV-4501: Path of toolchain's native libraries are wrong.
| Toolchain libraries "Full Path" property will display the base path of the current toolchain.
|
| AVRSV-4521: Expanding /collapsing node does not refresh the files in solution explorer.
| 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.
|
| AVRSV-4576: Modifying EEPROM contents in the memory view causes data corruption on XMEGA E5.
| Modifying EEPROM data values in the memory view during debugging of XMEGAE5 devices causes the EEPROM data to be corrupted.
|
| AVRSV-4659: SAM4L and UC3-kilogram programming fails with core voltage at >1.9V.
| Programming SAM4L and some UC3 devices may fail when core voltage is raised above 1.9 V.
|
| AVRSV-4693: Struct type is not displayed correctly for composite types in a COFF project.
| For COFF object file debugging, elements in the "type" field of a watch on a composite data type might contain the object/variable name instead of the type name.
|
| AVRSV-4753: SAM D20 Xplained Pro shows incorrect chip ID.
| 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.
|
| AVRSV-4899: In External Interrupt controller example, stepping through NMI debugging is not working.
| Debugging inside the NMI handler on UC3 does not work. This is probably due to the fact that the NMI interrupt has a higher interrupt priority than breakpoints.
|
| AVRSV-5029: Not able to set CLKPR bits while debugging in Xplained Pro Mega256rfr2.
| Writing bitfields that needs to be written in a timed sequence from the I/O view will not work. This is the case for CLKPR, IVSEL and WDTEN, to mention some bitfields.
|
| AVRSV-5050: Studio should warn if BOOTPROT is set when programming target.
| If the BOOTPROT fuse is set in the device, flash memory may not get programmed correctly and no error will be displayed. If debugging, the program will not get uploaded, but debug will proceed with the wrong image.
|
| AVRSV-5324: SAM D20 - IO View - OUTSET / OUTCLR improperly updated.
| 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.
|
| AVRSV-5339: Live Watch is not updated when single stepping on UC3.
| Variables in Live Watch are not updated when single stepping on UC3 devices.
|
| AVRSV-5378: Debugger on SAM4L-EK is clearing the interrupt flags.
| 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.
|
| AVRSV-5450: It is not possible to get trace from multicore device.
| 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.
|
| AVRSV-5527: Live Watch : Value of complex expression not computed.
| 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.
|
| AVRSV-5635: Unable to debug when assigning fuse bits through .elf.
| Care should be taken when debugging a project with embedded fuse information. The debugging session might misbehave if the fuses overwrites settings that Atmel Studio assumes to have control over.
|
| AVRSV-5711: Cannot debug SAM D code with Atmel Studio if .text section is relocated.
| 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.
|
| AVRSV-5792: Installing 6.2 public after 6.2 ServicePack1 corrupts the Service pack installation.
| 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.
|
| AVRSV-5837: Backend times out if ''USE GDB'' is selected for UC3 devices.
| 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.
|
| AVRSV-5854: Installation of USB Driver package fails on clean Win 7 (64-bit) machine.
| 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.
|
| AVRSV-5952: Firmware upgrade fails from jtagice3v2.15 to jtagice3+.
| Upgrading JTAGICE3 from major version 1 or 2 to major version 3 can fail. The first firmware upgrade attempt will only put the JTAGICE3 into boot mode, and not do an actual upgrade. Running a second firmware upgrade without toggling power to the tool should work. The simplest workaround is to use atfw found in '<Atmel Studio installation folder>\atbackend\'. From a command prompt (inside Atmel Studio, go to Tools|Command Prompt) run"atfw.exe -t jtagice3 -a "<Atmel Studio installation folder>\tools\jtagice3\jtagice3_fw.zip", which would normally be atfw -t jtagice3 -a "C:\Program Files (x86)\Atmel\Atmel Studio 6.2\tools\jtagice3\jtagice3_fw.zip". The first attempt will fail, but when running the command again without toggling power on the JTAGICE3 it should pass. Note that as soon as the JTAGICE3 has been upgraded to a firmware with major version 3 or higher, firmware upgrade should work on first attempt also from Atmel Studio 6.2 SP1.
|
| AVRSV-5987: Cannot chip erase SAM4L in backup mode on SAMICE.
| 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.
|
| AVRSV-6364: ARP entry added into the control panel even if one of the packages get installed by the bootstrapper.
| Atmel Studio 7.0 entry will be visible in Add Remove programs even if the installation is unsuccessful or partial. Please remove the entry and try installing again.
|
| AVRSV-6372: Installing Atmel Studio Extensions does not seem to detect Atmel Studio 7.0.
| If VSIX (Atmel Studio extensions) are installed manually, there might be conflicts between Atmel Studio and Visual Studio due to issues in the Microsoft Visual Studio Version Selector (VSLauncher.exe) executable. To fix this, change the file association for VSIX files from VSLauncher.exe to C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\VSIXInstaller.exe (D:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\VSIXInstaller.exe on 32-bit systems). Changing the file association is done by Shift-Right Click the VSIX, choose 'Open With...' and browse to the VSIXInstaller.exe in the path shown above.
|
| AVRSV-6405: Device disconnected error comes after updating firmware. But allows to debug program.
| Tools may fail to re-enumerate after a firmware upgrade, causing the tool to be listed as disconnected. If this happens, reconnect the tool and it should re-enumerate and become connected again.
|
| AVRSV-6427: Abort of Uninstall sequence leaves the system in intermediate state.
| If the system goes into an intermediate state after abort of uninstall sequence (forceful exit of installation process) the state could be recovered by repairing Atmel Studio 7.0 from control panel.
|
| AVRSV-6664: Atmel Studio crashes when I search in the options dialog.
| Atmel Studio may crash when searching in the Options page. The issue lies in the Visual Studio shell, and is fixed in version 2013.4 and newer. To apply the fix, download Visual Studio 2014 Update 4 or newer from https://www.visualstudio.com/news/vs2013-update4-rtm-vs or from https://www.microsoft.com/en-us/download/details.aspx?id=44921 .
|
| AVRSV-6677: Issues with graphics driver can cause rendering glitches.
| Atmel Studio tries to offload as much of the graphics rendering of the user interfaces as possible to the graphics card to free up CPU resources. If the graphics driver does not support hardware rendering, Atmel Studio will fall back to using software rendering. However, in some cases, this fallback does not work for some reasons, causing rendering glitches in the user interface. The best way to solve this issue is to make sure that the latest graphics driver is installed from your graphics card vendor.
|
| AVRSV-6848: Upgrading JTAGICE3v1 and v2 to v3 works, but studio needs to be restarted.
| Atmel Studio fails to connect to JTAGICE3 after upgrading from firmware version 1 or version 2. To be able to connect, Atmel Studio needs to be restarted.
|
| AVRSV-7003: Current measurements does not work when running debugging or programming at low baud.
| Running current measurements in Data Visualizer while programming or debugging at low interface frequencies/baud rates might result in Data Visualizer disconnecting from the Power Debugger. The lower limit of the interface speed varies depending on target type, flash size and interface type but is typically in the range 100-300kHz.
|
| AVRSV-7154: Studio upgrade breaks functionality for other users on the same computer.
| If a USER is using an Atmel Studio installed by another user ADMIN (USER!=ADMIN), and Atmel Studio is updated by ADMIN, Atmel Studio will still be using the old extensions that were copied to the %appdata% folders. To correct, the USER must delete the %appdata%/Atmel (roaming and local) folders so that they are reinitialized by the new version of Atmel Studio on the next start.
|
| AVRSV-7163: Installing AVR8 Toolchain 7.0: 'An error occured: The specified account already exists'.
| Run 'Microsoft Fix' it and uninstall 'AVR8 Toolchain 7.0'. After this, run the Atmel Studio installer and choose repair.
|
| AVRSV-7235: Atmel Studio crashes when searching in the Solution Explorer.
| On some machines, Atmel Studio can crash when searching for files in the Solution Explorer. Currently, only workaround is to install Visual Studio 2015 Update 2 or newer on the machine.
|
| AVRSV-7309: Multiple Windows security dialog boxes during driver install on Windows 7.
| Some Windows 7 machines can experience multiple security dialog boxes during the driver installation. Clicking the Trust this publisher checkbox does not work. This is related to KB2921916, this hotfix can be downloaded from https://support.microsoft.com/en-us/kb/2921916.
|
| AVRSV-7828: Error during driver installation on Windows 7 32-bit.
| The drivers may fail during upgrade on Windows 7 32-bit. A workaround is to unistall Atmel Studio and the Atmel Driver from Add/Remove programs before installing again.
|
| AVRSV-7931: Arduino sketch project with custom libraries fails to compile in studio.
| To fix this compilation error, After project creation, navigate to ArduinoCore/Src/Libraries/Adafruit-GFX-Library-master/fontconvert/fontconvert.c Exclude fconvert.c from compilation by setting Build Action for this file to None
|