Release Notes 2.0.2

Product name
AVR32 Studio
Release version
2.0.2
Release date
2008-05-15

Contents

Overview

AVR®32 Studio is an integrated development environment for writing, debugging and deploying AVR32 applications. AVR32 Studio is distributed by Atmel® free of charge, and runs on both Windows® and Linux®. AVR32 Studio is Built on Eclipse™, enabling integration with third party plugins for increased functionality.

News

AVR32 Studio 2.0.2 is a maintenance upgrade from 2.0.1 addressing a few critical issues. If upgrading from 2.0, please also read the release notes for 2.0.1 for important information about upgrading projects.

New Features

There are no new features in AVR32 Studio 2.0.2.

Notable Bugs Fixed

Fixed missing conf_isp.h for EVK1100 template projects (bug #7982)
In AVR32 Studio 2.0.1 projects created by selecting AVR32 C Project From Template > Executable > Start EVK1100 application (ES) would not compile due to a misplaced conf_isp.h.
Added UC3B1256 and UC3A1128 to "Any board" (bug #6877)
When using the "Any board" in a target, it was not possible to select the UC3B1256 or UC3A1128 devices.

Known Issues

Bug #5867
The contents of addresses near a memory boundary, such as the end of SRAM, will not render properly in the memory view.
Bug #6986
The GPIO registers are incorrectly displayed in the AVR32 Registers view for some devices. Some devices may show too many GPIO ports while some show only a single GPIO port.
Bug #5716
Stepping over a line of source code that results in a large amount of machine instructions to be executed (typically empty for or while loops used for delays) will cause AVR32 Studio to be unresponsive. To regain control, terminate the launch. To step over such code line, use breakpoints and the resume (F8) function.
Bug #6427
When a UC3 device is programmed with a bootloader that is protected with the BOOTPROT fuse, the device must be erase with the chip erase command to be able to reprogram it.
Bug #7099
The launch configuration setting "Verify memory after programming" will not be effective for debug launches.
Bug #7658
It is not possible to stop the debugger at the reset vector (usually the location of the _start() function) by entering the reset vector address in the 'Stop on startup at' field in the launch configuration's Debugger page. A workaround is to stop on the next instruction or function being called, for instance _stext().
Bug #5813
The dynamic help for the AVR32 specific views is incomplete or in some cases missing.
Bug #7370
The Includes folder for projects will only display includes for the Debug configuration.
Bug #7596
The contents of the Disassembly view may be displayed non-sequential depending on the output of the compiler. Typically, the presentation of for-loops or optimized code may be unfamiliar to some users.
Bug #7707
It is not possible to use redirection in Pre-build or Post-build steps. A workaround is to create an external command (i.e a .bat file) that performs the necessary redirection.
Bug #7820
When building projects that use make, the Problems view will contain a warning about not being able to launch the external scanner info generator. A workaround is to change the Discovery profile in the project properties dialog's C/C++ Make Project > Discovery Options page from "GCC per project scanner info profile" to "AVR32/GNU C per project scanner info profile".
Bug #7538
It is not possible to access voltages or frequencies in a target's Adapter tab before the Board tab has been configured properly.
Bug #7280
If a breakpoint and a tracepoint is located on the same source line it is not possible to open the breakpoint's properties from the context (right-click) menu. In such cases, access the breakpoint from the Breakpoints view.
Bug #7560
The NanoTrace option Break on application buffer access does not work.
Bug #7621
The "Use NANOTRACE segment" trace option in the launch configuration does not work. The buffer location and size must be specified explicitly or by using the NANOTRACE variable.
Bug #7756
The source code presented in the Trace Data view may be incorrect in some cases. Use the Disassembly or Mixed formats instead.

System Requirements

AVR32 Studio is supported under the following configurations.

Hardware requirements

  • Minimum processor Pentium 4, 1GHz
  • Minimum 512 MB RAM
  • Minimum 500 MB free disk space
  • Minimum screen resolution of 1024x768

AVR32 Studio has not been tested on computers with less resources, but may run satisfactorily depending on the number and size of projects and the user's patience.

Software requirements

  • Windows 2000 or Windows XP
  • Fedora™ 7 or 8, Ubuntu Linux 6.06 (Dapper) or SUSE® Linux 10.1, 10.2 or 10.3
  • Sun Java 2 Platform version 1.5 or later
  • Internet Explorer®, Mozilla®, or Firefox®

Limited testing has been made on Windows Vista™ and 64-bit operating systems. AVR32 Studio does not support Windows 98, NT or ME.

Downloading and Installing

The software can be found on the AVR32 Technical Library DVD, or downloaded from Atmel's website at http://www.atmel.com/products/avr32/ under the "Tools & Software" menu.

Upgrading from previous versions

AVR32 Studio 2.0 has enabled automatic searching for updates when it is started. When the updates are found AVR32 Studio will display a dialog indicating that new updates are available. To upgrade, click the Yes button. Due to an error in AVR32 Studio 2.0, the UC3A and UC3B software frameworks will not be upgraded using this method. To ensure AVR32 Studio is fully upgraded to 2.0.2, perform a manual update as described below.

If the automatic update feature has been disabled, a manual search can be executed from the menu Help > Software Updates > Search for Updates.

IMPORTANT: Due to changes in the project types used in 2.0.1, projects created with 2.0 must be converted in order to modify the toolchain settings. To convert a project, right-click the project in the Navigator view and select 'Convert To...'.

No upgrade of the AVR32 GNU Toolchain is required to upgrade from 2.0 to 2.0.1.

It is not possible to upgrade to 2.0.1 from AVR32 Studio 1.x. Workspaces with projects built with earlier versions should not be used directly with AVR32 Studio 2.0. It is recommended that a new workspace is created for 2.0/2.0.1, and that any projects from earlier workspaces are imported using the File > Import function.

After successfully installing AVR32 Studio 2.0.1 (see below) and migrating to the new workspace, earlier versions (1.0 or older) can be uninstalled using the "Add or Remove Programs" (Windows) or by deleting the installation directory (Linux). It is also recommended that the old AVR32 GNU Toolchain is uninstalled using "Add or Remove Programs" on Windows.

Different major versions of AVR32 Studio can co-exist without interference.

Please read the What's New section for more information about changes since previous versions.

Windows

The DevelopmentTools installer which was distributed with 1.0 is no longer supported. AVR32 Studio and the AVR32 Toolchain must be installed separately.

The AVR32 Studio installer can be downloaded from the website as noted above. After downloading, double-click the AVR32Studio-2.0.1-Setup.exe file to install. If you wish to specify the location where the AVR32 Studio software is installed, choose "Custom Installation". The installation software will install a Sun Java Runtime Environment on your computer if it is missing.

Linux

On Linux, the AVR32 Studio IDE is distributed separately from the AVR32 GNU Toolchain which can be installed as RPM or Debian packages depending on the distribution. AVR32 Studio is available as a ZIP archive which can be extracted using the unzip utility.

IMPORTANT! The Java runtime environments shipped with many Linux distributions are not compatible with AVR32 Studio. A Java Runtime (or JDK) 1.5 or 1.6 is required. Consult your Linux distribution's documentation for instructions on installing Sun Java, or download it from Sun's website at http://java.sun.com/. Specifically, any reference to a Java version 1.7 indicates that an incompatible version is being used.

We recommend installing AVR32 Studio into a directory which is writable for the user(s). This simplifies the process of adding or updating the product using the update manager. On a single-user machine, you can typically extract the AVR32 Studio ZIP file into your home directory. This creates an avr32studio directory containing the product files.

To run AVR32 Studio, execute the avr32studio program from the avr32studio directory. If you experience problems, make sure the correct java is being used by running java -version which should give output similarly to this:

java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing)

RedHat Enterprise Linux 4

Note that you may need to set the environment variable MOZILLA_FIVE_HOME to the folder containing your Firefox install. e.g.

export MOZILLA_FIVE_HOME=/usr/lib/firefox-1.0.4

or, if using a tcsh:

setenv MOZILLA_FIVE_HOME /usr/lib/firefox-1.0.4

in order for the welcome page to work.

Contact Information

For support on AVR32 Studio please contact mailto:avr32@atmel.com.

Users of AVR32 Studio are also welcome to discuss on the AVRFreaks website forum for AVR32 Software Tools.

Disclaimer and Credits

AVR32 Studio is distributed free of charge for the purpose of developing applications for AVR32 processors. Use for other purposes are not permitted; see the software license agreement for details. AVR32 Studio comes without any warranty.

© 2008 Atmel Corporation. All rights reserved. ATMEL, logo and combinations thereof, Everywhere You Are, AVR, AVR32, and others, are the registered trademarks or trademarks of Atmel Corporation or its subsidiaries. Windows, Internet Explorer and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Built on Eclipse is a trademark of Eclipse Foundation, Inc. Sun and Java are registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. Fedora is a trademark of Red Hat, Inc. SUSE is a trademark of Novell, Inc. Other terms and product names may be the trademarks of others.