Atmel releases AVR Studio 5 beta

Atmel has released the beta version of their Atmel® AVR Studio® 5, the Integrated Development Environment (IDE) for developing and debugging embedded Atmel AVR® applications. Version 5 provides one development environment for all 8-bit and 32-bit AVR microcontrollers.

Features include an integrated C compiler, new project wizard, and an improved editor displaying code suggestions, shortcuts and snippets. Also included is the AVR Software Framework, a collection of production-ready source code including peripheral drivers, communication stacks and application-specific libraries. This release includes the familiar application builder and compatibility with a wide range of in-system programmers.

Download your copy today!

Join the Conversation


  1. as much as I love this, the 500 MB download is a tad big, the total time from start of download to installation actually took just under an hour.

    and I love this blog, none of the other blogs I read have mentioned this yet, keep up the good work

    1. The 500 MB contains
      > .NET Framework – 48 MB
      > Visual Studio Isolated Shell – 168 MB
      > AVR Software Framework for 8-bit XMega and 32-bit devices
      > Lots of Example projects and Stater kit templates
      > AVR Toolchain 8-bit and 32-bit
      > Help documents
      > AVR Assembler

      Once you have the initial platform in your PC, subsequent downloads might be smaller :)

  2. I read somewhere that awhile back ATMEL hired-away the fellow behind WinAVR. Then WinAVR when stale and has since been declared dead. As a result, many speculated ATMEL was going to release an AVR Studio with an integrated C/C++-compiler. Voila – AVR Studio 5 with a compiler appears.

    The good stuff…

    * It still seems to be uncrippled freeware (registration required)

    * It still works with WinXP SP3+ as a minimum.

    * AVR Dragon is still supported (the fake 32kB limit on the AVR Dragon was removed awhile back).

    * Looks like it is easy to update, that wasn’t the case with AVR Studio 4.

    The bad stuff…

    * Still in Beta.

    * Proprietary, not open-source.

    * Windows only (dunno about Wine etc.).

    * Requires Micro$oft’s bloated .NET framework.

    * Bloated 500+ MB download, probably eats up more than 1GB HDD space after install.

    * Stull needs the Jungo USB driver nonsense for your USB programmer (like the Dragon).


    It still looks like free and uncrippled AVR Studio in conjunction with the highly capable and now uncrippled $49 USD AVR Dragon programmer/debugger remains when it comes to proprietary microcontroller development suites. Yes it is boated, single platform, and now drags the .NET ball and chain along. But the positives make AVR Studio 5 a welcome sight in my opinion. The first real results will be when we compare compiler performance with GCC/AVRlibc combo.

    When will the marketing goons at competing microcontroller houses learn that trying to extract a pound of flesh from potential customers via crippled development environments only costs them hugely in the long term?

    1. .NET Framework 4.0 is not supported by WINE. SO i guess the chances of AVR Studio 5.0 running under Mac is a ?. atleast for now….

      I cannot comment on your situation, but in our neighbourhood i buy a 2TB harddisk @ ~80 USD.

      May be ATMEL can release a flavour of installer with the prerequisites stripped down (.NET Framework, Isolated Shell)

  3. So if this is the new winAVR basically, is there any documentation on how the libc might have changed or how they implemented everything?

    Seems like all the examples & ‘software framework’ stuff is AVR32 or xmega only.

    I actually kinda LIKE the big VS2010 interface, but this really feels like the regular megas/tinys are getting left behind and this is still making me look harder at MPLABX & pic.

  4. Yikes. I have always been torn between PICs for cheap debuggers that work with all chips and a ton of devices for all occasions. And on the other hand AVR’s open source compiler full of open source sweetness, but lack of cheap debuggers (clones…). If they torpedo the open source compiler, and nobody picks up the project, it seems like AVR is killing the golden goose that secured their (current hobby) dominance in projects like Arduino.

    1. Adding… I mentioned PICs, but I’m willing to use any uC in any project (not a flame). This was just one of the big features of the AVR that I liked a lot, and I’m really disappointed to see it tossed.

      Interestingly, they seem to be headed to Windows only, while Microchip is making a huge push to be multiplatform (finally) with MPLABX. Are the tables turning?

      1. The toolchain is still open and free; atmel provides the patches they apply to the toolchain, and there is a discussion in the avr-gcc mailinglist about making them compatible with crosstools-ng. The patches to the toolchain in AS5 is not yet released, but according to a poster on avrfreaks this is just because of the still beta stage of the toolchain. They will have to provide these no matter what to stay in accordance with the GPL, In addition it is mentioned in the studio 5 thread by multiple atmel employees they do cross compilation of the toolchain internally, but they are not being released at the time. There is also hinting at the debug and programming backend being cross-platform; in my opinion a much more important part than the IDE.

        In summary: as long as Atmel uses the gcc compiler they will have to release the source and patches they do to the toolchain to comply with the GPL. In addition if they release the cross-platform backend (debug, simulator, programming) they are taking a huge step forward.

      2. I think Microchip similarly uses GCC and releases the source for their compiler, but there is a bunch of other important stuff (device headers, etc) that they still won’t release under an open source/distributable license. Hopefully they don’t go that way.

        A shared problem with both platforms now is the closed development process (as far as I know this applies to MPLABX and studio 5, willing to be wrong). We have to divine how things are going from forum posts, leaks, rumors, etc instead of getting a good look at the code and project tracker.

  5. Well, compared to AVR Studio 4.18 and WinAVR it’s a God sent! No more piddle farting around with avr-strip -g commands, compile time is lightning compared with WinAVR and it looks and feels good, it has excellent search capabilities… I haven’t found anything to complain about yet.. and its free… I use the JTAGICE mkII and it has worked a absolute treat for ATMEGA and XMEGA!! Not to mention this is still the first BETA! Way to go Atmel, (although it was about time!!)

  6. Hmm just installed AVR Studio 5 beta today, and it immediately asked to upgrade my AVR Dragon programmer, which i did.

    Now the programmer cannot recognize any Atmel uC i plug in. Tried both ISP and parallel, but it just times out with this message in the AVR Studio 5 console (it keeps mentioning jtagicemkii eventhough i have a dragon):

    # Error occurred in jtagice mkII event and response thread: Attempted read from detached USB device.
    # jtagicemkii: Invalid size of received packet.
    # Error occurred in jtagice mkII event and response thread: jtagicemkii: Invalid size of received packet.
    # Error occurred in jtagice mkII event and response thread: Attempted read from detached USB device.
    # Failed to execute command with ID 0x01.
    # Failed to stop JTAGICE mkII event polling thread.
    # Failed to sign on to mkii: Bad signon response: premature packet end (size=0).
    # Failed to sign on to mkii: Bad signon response: premature packet end (size=0).
    15:43:18.034: [ERROR] TCF command: Tool:connect failed: Code:131103 ,Service: ,Message from peer:Failed to sign on to mkii: Bad signon response: premature packet end (size=0).
    15:45:11.506: [ERROR] Unable to connect to tool context: ”.

    The sad thing is that AVR Studio 4 cant connect to my AVR Dragon now eather! :-((

    1. Just to follow up since yesterday:

      I used AVR Studio 4’s firmware upgrade feature (Tools -> AVR Dragon upgrade) to reflash my Dragon to firmware revision 6.b which AVR Studio 4 comes with, and expects.

      After that everything was fine in AVR Studio 4, so i tried my luck again in Studio 5 and was again prompted to upgrade to 7.2 which i did.
      Now things seems to work fine in Studio 5 and Studio4 politely asks me to downgrade to the Dragon when i start the connect dialog.

  7. I’d recommend sending a mail to explaining the failure. You could also add a post in the studio 5 forum, but there appears to be some of these already regarding this problem without any solutions. If you contact atmel directly they will at least know that there is a problem.

  8. Windows only; no C++ (has a beta, but don’t supports “new” and “delete”). It’s a practical joke. Then go to the MAC API… the horror… the horror.

Leave a comment

Leave a Reply to Ondrej Galbavý Cancel reply

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail. You can also subscribe without commenting.