Hi,
A trawl through the forums didn't yield anything clear on this, though I may have missed it...
I note that the Sourceforge project for WinAVR is now marked as "inactive".
Is there a single location for status information about WinAVR and/or avr-libc? Is it "dead" or is there something in the pipeline going forward?
Thanks
Nick
There's lots of threads of speculation - Eric has confirmed that there will be future Windows based avr-gcc tool releases but cannot say much more.
Speculation is that it's going to form part of "Studio 5"
You may have noticed in the last few days that the CVS for AVR-LibC has just stepped from 1.6.x to 1.7.0 which rather suggests that some form of release is imminent.
If you Google for:
"studio 5" site:avrfreaks.net
you will probably hit most of threads with pertinent discussion - sadly you cannot easily do "Studio 5" with the search engine on this site, you can only effectively do "Studio" AND "5" which is a bit too general.
Eric is no longer maintaining a third party WinAVR project for Windows builds of the GNU toolchain. Instead, future toolchain releases will be offered directly from Atmel, still overseen by Eric (but with an official Atmel stamp). Nothing to worry about.
- Dean :twisted:
A new release of the AVR32 tool chain (based on eclipse) was announced today. On downloading and investigation it shows that the AVR tool chain - compiler and library is included in it. So, it seems that the new tool chain for AVR will be based on Eclipse - which in my eyes is excellent news. Linux support out of the box by Atmel on one software platform for AVR, AVR32 through ARM9. It seems I am the first one to let the cat out of the bag - or find the cat in the bag.
Johan Hartman
It seems I am the first one to let the cat out of the bag
This is not Schrödinger's cat (for a start, that one was in a box, not a bag...)
So, if it is now within Atmel, where does that leave the other communities using the toolchain & avr-libc, e.g. the Arduino lot...
Cheers
So, if it is now within Atmel, where does that leave the other communities using the toolchain & avr-libc, e.g. the Arduino lot...
A new release of the AVR32 tool chain (based on eclipse) was announced today. On downloading and investigation it shows that the AVR tool chain - compiler and library is included in it. So, it seems that the new tool chain for AVR will be based on Eclipse - which in my eyes is excellent news. Linux support out of the box by Atmel on one software platform for AVR, AVR32 through ARM9. It seems I am the first one to let the cat out of the bag - or find the cat in the bag.Johan Hartman
What gcc version is it ?
/Bingo
Nothing to worry about.
That won't stop us! :D
If you don't know my whole story, keep your mouth shut.
If you know my whole story, you're an accomplice. Keep your mouth shut. 
So, if it is now within Atmel, where does that leave the other communities using the toolchain & avr-libc, e.g. the Arduino lot...
EDIT: Oh dear it does look like Arduino just picks up a complete WinAVR build:
D:\arduino-0015\hardware\tools\avr\bin>avr-objdump.exe -v GNU objdump (WinAVR 20081205) 2.19 Copyright 2007 Free Software Foundation, Inc.
So Arduino-0015 was based on WinAVR20081205. If they continue to just pick up WinAVRs then they could have a problem. If anyone knows the Arduino folks you might want to point this out to them as they will need to do what Arnold says above and learn to extract the new form of the toolchain or build their own Windows toolchain (maybe Eric could provide them with guidance on how to do that)
Cliff
It seems I am the first one to let the cat out of the bag - or find the cat in the bag.
It's just that we've not talked about it that much. Cut the Atmel folks some slack now, so that we can get Studio 5 this year.
Personally, I am quite happy with the direction things seems to take. Not that the specific super-IDE is all golden w/o flaws etc, but we can hope for a AVR(8) IDE that can run on GNU/Linux, and that has an open specification for add-ons (eg a Subversion plug-in).
My worst fear is that FLIP will be the programming software module...
Linux support out of the box by Atmel
What does "Linux support" mean in this case?
- Windows
- Ubuntu
- Suse Core
- RedHat Enterprise
- Fedora Core (RPM)
but there is also something referred to as "AVR32 GNU Toolchain Linux Source code" and that might be what you're looking for.
Personally I have been tempted to download and install Studio32 for quite some time. While I do not delve into AVR32 matters, I am curious to get a look at if/how Atmel has adopted the Eclipse platform. I've managed to keep the temptation off, though - my backlog of other things I'd like to do is long enough as it is - but the up-coming weekend might just be ruined... :D
Personally I have been tempted to download and install Studio32 for quite some time
https://www.avrfreaks.net/index.p...
So it looks like the train has started to pull out of the station ;-)
I think this information of that other thread is a definitive answer to the original question.
JW
Maybe, several of us has peeked down the bag (read the clues here at AVRfreaks), and seen the outline of a cat-like animal.
It still doesn't mean that it's a cat. ;)
There are still some issues to be worked out, folks. Growing pains. Sometimes the bleeding edge hurts.
What gcc version is it ?
AVR GCC 4.4.3.
I finally feel confident in the amount of testing that AVR GCC has had in the 4.4.x series to move up to it. However, there could always be lurking issues. Remember, this series of GCC includes the new Integrated Register Allocator (IRA) which is valid for all GCC ports.
There hasn't been enough testing on 4.5.x yet to move up to that version, but I know that it's out. I'm thinking that maybe at the beginning of 2011. There are a lot of backlog issues that need to get addressed.
Eric is no longer maintaining a third party WinAVR project for Windows builds of the GNU toolchain. Instead, future toolchain releases will be offered directly from Atmel, still overseen by Eric (but with an official Atmel stamp). Nothing to worry about.- Dean :twisted:
Spot on. And the reason is simply to do with the amount of time it would take to manage and implement two identical projects. :shock: It really doesn't make much sense.
