WinAVR 20100110's AVR32 toolchain conflict

Log in or register to post comments
Go To Last Post
3 posts / 0 new
Author
Message
lfmorrison
lfmorrison's picture
Level: Raving Lunatic
Joined: Wed. Dec 8, 2004
Posts: 4647 View posts
Location: Nova Scotia, Canada
#1
Posted by lfmorrison: Mon. Nov 29, 2010 - 02:05 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So, up until now I've stuck with WinAVR 20090313. Independently, I've been working on a number of projects using the UC3 line of AVR32 microcontrollers, using the AVR32 toolchain included with AVR32 Stuio. I've had no problems with these pieces of software coexisting.

But I've been handed a project that uses an XMega AVR, so I just upgraded to 20100110. The new version of WinAVR also comes with a copy of the AVR32 toolchain, and it appears that the AVR32 toolchain in WinAVR is conflicting with the toolchain in AVR32 Studio.

It is reporting an inability to locate certain tools, such as avr32program.exe. And whenever I invoke a makefile-managed build, I get Cygwin warnings relating to non-POSIX paths.

Other than using two different computers, is there anything else I can do to continue using WinAVR 20100110 for 8-bit AVR work, but use the default AVR32 Studio toolchain for AVR32 development?

Tags:

Tools, Compilers and General Programming
Top
lfmorrison
lfmorrison's picture
Level: Raving Lunatic
Joined: Wed. Dec 8, 2004
Posts: 4647 View posts
Location: Nova Scotia, Canada
Posted by lfmorrison: Tue. Nov 30, 2010 - 12:57 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Answering my own question:
Atfer installing WinAVR, re-install Atmel's AVR32 GNU Toolchain, and select "Repair". Some important environment variables are reverted back to their correct, pre-WinAVR, values.

Top
gregsmithcts
gregsmithcts's picture
Level: Raving Lunatic
Joined: Thu. Nov 4, 2010
Posts: 2098 View posts
Location: Bristol, UK
Posted by gregsmithcts: Tue. Nov 30, 2010 - 01:36 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Further, you could write some batch files to set environment/paths etc and launch the ide from inside these.

--greg
Still learning, don't shout at me, educate me.
Starting the fire is easy; the hardest part is learning how to keep the flame!

Top