- Product name
- AVR32 Studio
- Release version
- 2.0
- Release date
- 2008-03-14
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 represents a major upgrade from 1.0, with support for new tools and parts as well as overall improvements. It is not possible to upgrade from version 1.0 to 2.0; the new version has to be installed from scratch.
AVR32 Studio 2.0 depends on AVR32 GNU Toolchain 2.0 which uses a MinGW environment instead of Cygwin. Use of the Cygwin shell is discouraged.
AVR32 Studio 2.0 is based on Eclipse platform 3.3.2, the C/C++ Development Tooling (CDT) 4.0.2, Target Management 2.0.2, and Remote Systems Explorer (RSE) 2.0.2.
New Features
- Software Framework for UC3AxxxxES and UC3BxxxxES incorporated with wizard for easy application development.
- Support for the new AVR ONE! emulator for programming and debugging including buffered and streaming AUX trace.
- Support for NanoTrace using the AVR ONE! or the JTAGICE mkII emulators.
- A technology preview of the AVR32 instruction set simulator is included and can be used for getting acquainted with the AVR32 architecture and the development tools.
- Firmware upgrade support for JTAGICE mkII and AVR ONE!.
- A new internal builder removes the dependency on an external make utility to compile applications.
- It is now possible to build static or shared libraries for AVR32 Linux.
- The New Project wizards have been renamed and rearranged. The AVR32 C Project and AVR32 C++ Project are prominently placed and will create projects using the new internal build mechanism. The AVR32 C Project (Make) and AVR32 C++ Project (Make) can be found in the wizards list and will create projects using standard makefiles.
- UC3Axxxx and UC3Bxxxx engineering samples are now supported with the following target names: UC3AxxxxES (revision E) and UC3BxxxxES (revision B). UC3Axxxx refers to revision H and later. UC3Bxxxx refers to revision F and later.
- Part description files, i.e the information in the AVR32 Registers view, has been updated. Registers in the interrupt controller are now displayed.
- Launching a debug is now much faster.
- Several improvements for the fuse related functionality. Note that the .fuses suffix will be forced when saving fuse files.
- Full STK600 documentation is included.
Notable Bugs Fixed
The following is a list of bug fixes which are not obviously visible to the user. Other bug fixes are not explicitly described.
- Support for assembler with preprocessor (bug #4948)
- Files with suffix .x will now be run through the preprocessor and assembler, as a workaround for not being able to use .S on filesystems which are case-insensitive.
- AVR32 Registers view now remembers last selected part (bug #6159)
- When starting AVR32 Studio, the AVR32 Registers view now displays registers for the part that was shown before exiting last time.
- Programming target via a target action updates Binary date field (bug #6552)
- When programming via the Target view the target is now updated, so it is possible to avoid duplicate programming in a succeeding launch.
- Last programmed executable on target now correct (bug #5964)
- When the Target properties view was open, the Binary date field is now updated.
- Less strict project/target matching (bug #6987)
- A launch may now be performed even if the project's MCU is not equal to the one defined for the target.
- Can now ctrl-click or use F3 to go to a macro's definition (bug #6409)
- Note that the file which #defines the macro has to be open for the link to work.
- Less dependent on external browser (bug #6565)
- The Welcome page no longer depends on an external browser to render, which on some hosts would not work properly.
- Can delete targets by pressing Delete key (bug #6009)
- Targets can now be deleted by pressing the Delete key, not just via the context menu.
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 #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 #5013
- After changing the MCU in the Project properties' AVR32 Settings tab, the properties dialog must be closed in order to store the setting before visiting the C/C++ Build tab.
- 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 #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 #7559
- When importing a project from AVR32 Studio 1.0, the project settings will not be updated until AVR32 Studio 2.0 is restarted.
- 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 #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 300 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™ Core 4, 5 or 6, Ubuntu Linux 6.06 (Dapper) or SUSE® Linux 10.2
- Sun Java 2 Platform version 1.5 or later
- Internet Explorer®, Mozilla®, or Firefox®
AVR32 Studio has not been tested on Windows Vista or 64-bit operating systems and is thus not supported on these. 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
It is not possible to upgrade to 2.0 from previous versions of AVR32 Studio. 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, and that any projects from earlier workspaces are imported using the File -> Import function.
After successfully installing AVR32 Studio 2.0 (see below) and migrating to the new workspace, earlier versions 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.
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-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 distribution's documentation for instructions on installing Sun Java, or download it from Sun's website at http://java.sun.com/.
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.
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 and Internet Explorer are registered trademarks of Microsoft Corporation in the United States and 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.