- Product name
- AVR32 Studio
- Release version
- 1.0
- Release date
- 2007-06-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.
This is the first full release of AVR32 Studio. A beta version has been available for a couple of months; the list of changes since the beta version is available later in this document.
Known Issues
The following issues are known at the time of release.
- Bug #4948
- Files with '.S' suffix will not be run through the preprocessor before assembling. This causes problem when using preprocessor directives such as #include in the assembly file. A workaround is to use '.s' as suffix, and specify the assembler flag "-x assembler-with-cpp" in the file's C/C++ Build properties.
- 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 #5452
- Referencing external folders in managed make projects when using GNU make 3.81 causes build failures. This is caused by GNU make no longer supporting Windows-style path names. GNU make 3.80 works as expected.
- Bug #5502
- When pressing the Alt key for the first time in the fuse editor, the BODEN radio buttons and corresponding texts disappear. Pressing the Alt key and moving the mouse over the editor location will cause them to reappear.
- 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 #5767
- Upgrading GNU Toolchain or installing over an existing cygwin setup can sometimes cause problems with compiling projects, resulting in an "error 57" from make. A workaround is to uninstall GNU Toolchain and possibly also cygwin, then reinstall.
- Bug #5813
- The dynamic help for the AVR32 specific views is incomplete or in some cases missing.
- 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 #5964
- If the Target properties view is open, the Binary date field does not update when programming the target.
System Requirements
AVR32 Studio is supported under the following configurations.
Hardware requirements
- Minimum processor Pentium 4, 1GHz
- Minimum 512 MB RAM
- Minimum 200 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.1
- Sun Java 2 Platform version 1.5 or later
AVR32 Studio has not been tested on Windows Vista or 64-bit operating systems. AVR32 Studio does not support Windows 98, NT or ME. It has been tested and reported to work on SUSE Linux 10.2 in addition to the above.
Downloading and Installing
The software can be found on the AVR32 Technical Library CD, or downloaded from Atmel's website at http://www.atmel.com/products/AVR32/ under the "Tools & Software" menu.
Windows
There are two installers for AVR32 Studio available, one which installs the AVR32 Studio IDE only, which is called AVR32StudioSetup-1.0.exe, and one which incorporates the latest AVR32 GNU Toolchain called AVR32DevelopmentTools-1.0.exe. We recommend the latter even if you have the AVR32 GNU Toolchain already installed, since AVR32 Studio requires the latest versions of some of the utilities such as avr32program.exe and avr23gdbproxy.exe.
Double-click the AVR32DevelopmentTools-1.0.exe icon to start the installer. This will install the AVR32 GNU Toolchain and the AVR32 Studio IDE. The AVR32 GNU Toolchain installation will check for an existing cygwin installation and install itself on top of it. If no cygwin can be found, a minimal environment will be installed by executing the cygwin setup. For more information on the AVR32 Studio IDE installation, see below.
Installing AVR32StudioSetup-1.0.exe
Double-click the AVR32StudioSetup-1.0.exe icon to start the installer. 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.
AVR32 Studio requires Sun Java (JRE or JDK) 1.5 or newer. 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.
News
This section describes the changes between the 0.9 beta and the final 1.0 release. The only difference between the 1.0 RC1 released in May 2007 and the 1.0 released in June 2007 is the list of known issues in the release notes.
New Features
- Added support for EVK1101
- The EVK1101 evaluation board for the AT32UC3B has been added.
- Additional UC3A and UC3B parts
- Support for the following parts have been added: UC3A0512, UC3A1512, UC3A0256, UC3A1256, UC3A1128, UC3B0256, UC3B0128, UC3B1128, UC3B064, UC3B164.
- New board type added
- A target may now use the "AnyBoard" which supports all devices.
- Easier updates
- It is now easier to update AVR32 Studio by selecting the menu Help -> Software Updates -> Search for Updates. This function is also available from the AVR32 Studio section in the Welcome page.
- Easier access to tutorials
- All tutorials are now available from the menu Help -> Tutorials...
- Reorganized perspectives
- The "AVR32 C/C++" and the C/C++ perspectives have been reorganized. The latter now also contains AVR32 specific views.
- Utilize external clock for UC3
- It is now possible to speed up programming of UC3 devices by specifying the clock source to use.
- Fuse editor improvements
- Modified values are now indicated with an asterisk (*) in section title. Tooltips show both new and old fuse values.
- Configurable avr32gdbproxy ports
- The ports used for communicating with avr32gdbproxy can now be specified in the launch configuration.
Notable Bugs Fixed
- Remove all files when uninstalling (bug #5086)
- When uninstalling AVR32 Studio the user is asked whether to remove the user settings (Windows only).
- Apply disabled for read-only properties (bug #5666)
- The Apply button is now disabled for read-only target properties.
- AVR32 properties from C/C++ Project view (bug #5677)
- The AVR32 Settings are now available in the Project Properties when opened from C/C++ Project view.
- Renamed perspective (bug #5680)
- AVR32 perspective renamed to AVR32 C/C++. NOTE: You may need to manually switch to the renamed perspective.
- Removed "Entire file" from Read target action (bug #5708)
- The "Entire file" checkbox has been removed from the "Read..." target action.
- Improved Target action dialogs (bugs #5709, #5726)
- Values in target action dialogs now defaults to the previous state. The OK button is disabled until values are legal.
- Improved environment check (bug #5713)
- Friendlier and more verbose text when environment check succeeds.
- Fixed STK1000 tutorial (bug #5714)
- STK1000 tutorial "Create an AVR32 Application" (later renamed to "Rainbow Lights for STK1000") update: target stops at main().
- Improved job handling (bug #5722)
- Queued target jobs are now woken up.
- Easier to leave Welcome page (bug #5739)
- Welcome page now has a button to enter the workspace.
- Java Runtime checks (bug #5749)
- Stricter checking of which Java Runtime is used. For instance GIJ is not supported.
- Use cygwin registry instead of PATH variable (bugs #5753, #5872)
- When executing avr32program, make etc, we now use the registry setting from cygwin to determine the location of the program instead of relying on the PATH variable.
- Use decimal format in Program dialog (bug #5780)
- The target Program dialog now uses decimal format for "Number of bytes".
- Windows 2000 fix for Welcome page (bug #5781)
- Welcome page now paints properly in Windows 2000.
- Launching from Linux tutorial (bug #5786)
- The Linux cheatsheet would launch application as standalone using JTAGICE mkII.
- Quiet environment check (bug #5796)
- The Environment check is now silent when AVR32 Studio is started unless there are errors.
- Relocated project types category (bug #5802)
- Moved AVR32 project types from AVR32 category to C/C++ category.
- Fixed dialog for Read target action (bug #5818)
- The "Read..." target action now opens a "Save file" dialog instead of "Open file".
- Debug perspective cleanup (bug #5837)
- The Modules view is removed, and the AVR32 Registers and Expressions views are added to the Debug perspective.
- Terminate debug session (bug #5845)
- The debug session is now terminated if suspending fails.
- Added AVR32 perspective shortcut (bug #5846)
- The AVR32 C/C++ perspective is now available from the Perspective shortcut when in the Debug perspective.
- Use arguments specified in preferences (bug #5860)
- The "Default GDB Proxy" field in Preferences -> AVR32 -> AVR32Program now accepts parameters to be specified.
- Improved progress indication (bug #5528)
- A new option to avr32program is used to improve the reporting of progress during programming of standalone targets.
- Simplified EVK1100 tutorial (bug #5799)
- The EVK1100 tutorial has now been changed to include fewer steps.
- Disable automatic build by default (bug #5803)
- Projects are no longer automatically built (e.g when a file is saved). This would cause spurious builds and temporary failures while executing tutorials.
- Failed launch no longer updates last binary (bug #5804)
- When a launch fails, the target's last binary will no longer be updated.
- Moved console and progress views (bug #5805)
- The default location of these views is now in the bottom.
- Fixed problems connecting to avr32gdbproxy (bug #5807)
- The default ports used by avr32gdbproxy has been changed to avoid conflict with other services running on port 1024/1025 in Windows.
- Open file dialog remembers last location (bug #5816)
- All Open file dialogs now defaults to their previous location or the user's workspace.
- Assembler uses -g for debug targets (bug #5832)
- Assembly files will now include debug information when building a debug target configuration.
- Improved handling of avr32gdbproxy failures (bug #5859)
- If communication with avr32gdbproxy fails during a debug session, it will now be automatically terminated.
- Fixed batchisp arguments (bug #5875)
- When launching via BatchISP, the arguments are now properly separated.
- Fixed Welcome page links (bug #5880)
- The broken AVR32 Studio Known Issues link in the Welcome page has been replaced with a link to the Release Notes.
- Failed target actions now display error message (bug #5884)
- When a target action is executed (e.g when right-clicking in the target view), it will now display an error message when it fails.
- Fixed options for program action (bug #5910)
- The program target action sometimes wouldn't apply options such as erase before the option was toggled.
- Improved responsiveness when typing target hostname (bug #5920)
- When entering a target hostname for debugging Linux applications, the host is no longer resolved using DNS for each key pressed.
- Fixed AVR32 Settings error when using standard make projects (bug #5927)
- Projects created before AVR32 Studio 1.0 must have one of
<entry key="AVR32_PROJECT_TYPE">avr32.managedbuild.target.gnu.exe</entry>
or <entry key="AVR32_PROJECT_TYPE">avr32linux.managedbuild.target.gnu.exe</entry>
added to its .avr32project file in order to change MCU.
- Renamed tutorials (bug #5937)
- All tutorials now have unique names.
In addition to these fixes, the tutorials have been improved, and more documentation has been added.
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.
© 2007 Atmel Corporation. All rights reserved. ATMEL®, logo and combinations thereof, Everywhere You Are®, AVR®, and others, are the registered trademarks or trademarks of Atmel Corporation or its subsidiaries. Windows® is a registered trademark 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. Other terms and product names may be the trademarks of others.