Go ahead with AVR Toolchain version 3.4.0


Update! There was a mistake in the designation of Atmel Studio 6. Since version 6, Atmel AVR Studio is called as Atmel Studio.

Atmel released a new version of its AVR Toolchain (3.4.0) with AVR Studio 6 a week or two ago. However, the standalone installer of this toolchain has not been released yet. This post shows how to go ahead with the new version that is included in the Studio 6. First let's check what version of the toolchain we have already installed. This can be done via command line. Assuming that you are on Windows, press Win-R and type cmd, then press enter.

Heads up! Unfortunaltely, Linux users have to wait standalone package, because Studio 6 is only for Windows.

In command line type

avr32-gcc --version

so you should see something similar

Checking the AVR Toolchain version

Seems like I have the latest standalone version that's 3.3.2 at the moment of writing. Now let's update this to the latest version, so download and install AVR Studio 6. If you installed it into the default folder, you can find the toolchain from the C:\Program Files (x86)\Atmel\Atmel Studio 6.0\extensions\Atmel\AVRGCC\\AVRToolchain.

Go back to the command line and reset the PATH so that it overrides the current version (3.3.2) of the AVR Toolchain. That's prepending the PATH variable with the installation dir that includes the binaries of the latest toolchain version

set PATH=C:\Program Files (x86)\Atmel\Atmel Studio 6.0\extensions\Atmel\AVRGCC\\AVRToolchain\bin;%PATH%

AVR Toolchain version 3.4.0

If you recheck the toolchain version now, you can see that it's updated to 3.4.0. The drawback with this method is that you have to always remember to reset the PATH or otherwise the old version of the toolchain is reverted. Thus open the Control Panel » System and Security » System, then select Advanced system settings. From the window shown below press Environment Variables.... Then you can change the PATH variable in the way that's persistent.

System Properties window in Windows 7

blog comments powered by Disqus