WinAVR or AVR Toolchain (8-bit)?

Go To Last Post
19 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

With AVR Studio 4.18 SP3 installed, I get a warning on startup if I don't have both WinAVR and the new AVR 8-bit Toolchain installed. ("gcc plug-in: No WinAVR installation found. Using AVR Toolchain instead if installed. The AVR GCC plug-in can still be used if you set up your own build tools.") Is the best practice to have both of these installed? Or is it best to just install the AVR 8-bit Toolchain and ignore the warning about WinAVR not being installed? I don't really have any significant projects completed yet, so I'm not worried about backward compatibility with WinAVR, if there is even any difference.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

what happens if you re-install winavr after you have installed the avr studio?

the two should bond automatically and should not give you any problems.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I get that warning in SP3 even though I have WinAVR installed. It seems to be benign (and just plain wrong)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meslomp wrote:
what happens if you re-install winavr after you have installed the avr studio?

the two should bond automatically and should not give you any problems.

I'm not really having any problems, just trying to figure out what is the best practice given the warnings that come up. Here are the behaviors I have observed:

WinAVR and AVR Toolchain installed: no warnings

WinAVR or AVR Toolchain installed: one warning

Neither WinAVR nor AVR Toolchain installed: two warnings (obviously this is not a practical scenario)

It just seems odd that warnings appear unless both toolchains are installed. That made me wonder if the best practice is to have both installed.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What do you mean by "AVR Toolchain"?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"AVR Toolchain" is the name that Atmel is calling the new incarnation of WinAVR. At least, that's my impression.

Stu

Engineering seems to boil down to: Cheap. Fast. Good. Choose two. Sometimes choose only one.

Newbie? Be sure to read the thread Newbie? Start here!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
What do you mean by "AVR Toolchain"?

See http://www.atmel.com/dyn/product...

It's right above the download for AVR Studio 4.18 SP3. It says it is "for use with AVR Studio 4.18 SP3". I know what it is. I'm just trying to figure out why AVR Studio squawks unless WinAVR is installed along with it.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

I know what it is.

I didn't. Thanks.

As I say I use WinAVR+Studio all the time and apart from this rather stupid warning that seems to have appeared when I applied SP3 to AVR studio it works the same way it always has.

It is curious that Atmel have even been working on a way to hook the new WinAVR replacement into AVR Studio. Popular myth suggests we get Eclips-Studio-8/32 (or whatever) at the same time as "Phoenix"-WinAVR. So why would they have botherd with a mechanism to bolt this into the supposedly "dead" AVR Studio 4? Maybe it's suffering from Mark Twain Syndrome?

BTW I just noticed that to get this "AVR Toolchain" you have to register. So when the Phoenix was reborn the notion of "open software" went South then? I don't ever remember having to give my details to download anything from SourceForge! :evil:

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
went South
Is South good or bad? :roll:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
BTW I just noticed that to get this "AVR Toolchain" you have to register. So when the Phoenix was reborn the notion of "open software" went South then? I don't ever remember having to give my details to download anything from SourceForge!

Not if you catch it at http://www.atmel.no/beta_ware/ - stuff usually resides there for 30 days before falling off.

Stan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Stan,

Thanks, I know that, but the majority of beginners wanting to use GCC for the AVR won't. It just seems to go against the spirit of open source software. How many people want to be spammed for downloading a C compiler?

Cliff

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Not if you catch it at http://www.atmel.no/beta_ware/

Or you could fight the Atmel registering-for-each-download stupidity by a little subversive activity. Read this: https://www.avrfreaks.net/index.p... .

If enough of us do it, then there are four possible outcomes:
- Atmel will be stubborn, keep the registration, but leave the back door open. OK for us.
- Atmel will be stubborn and sore, keep the registration and close the backdoor. Bad for us, but at least we've stirred the pot a bit.
- Atmel will see reason and drop the registration. Good for us.
- Atmel will redesign the registration so that you can use a simple login when needing to download. OK for us.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

For what it's worth, it seems to be working fine with just the AVR Toolchain installed. I don't know if there are any major differences. I just like it better because it installs to the Program Files directory instead of the root. I don't like having a lot of stuff cluttering the root of the C drive.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I also wonder if there's a main difference between winavr and AVR toolchain...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

I also wonder if there's a main difference between winavr and AVR toolchain...

The first works, the jury is still out on the second.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

microcontrollerguy wrote:
For what it's worth, it seems to be working fine with just the AVR Toolchain installed. I don't know if there are any major differences. I just like it better because it installs to the Program Files directory instead of the root. I don't like having a lot of stuff cluttering the root of the C drive.

Most versions of WinAVR, including the current version, don't have to be installed in c:\. (Although I don't use "Program Files", since older open source stuff can't handle spaces in the file path). I install all open source stuff, including WinAVR, to c:\apps

Actually, I install WinAVR to c:\apps\WinAVR (without the version number), so that I can easily switch versions of WinAVR without changing the PATH or the registry.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

I can easily switch versions of WinAVR without changing the PATH or the registry

Did you know about WinDOS' mklink command? It's just like symlinks in Unix. It's easy to make a C:\WINAVR point to any directory you choose in a single command.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
It's easy to make a C:\WINAVR point to any directory you choose in a single command.

Yes, to make that useful, you have to first (or last) install WinAVR to C:\WinAVR, so that the registry settings and path point to C:\WinAVR.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Tested for a few days AVRStudio + AVR Toolchain.
Annoyed by the stupid registration request so i used mailinator.
Looks like the AVR toolchain is just an WinAVR installed in another subfolder, under Program Files.
It works OK even if it complains for missing WinAVR installation.
In the end I switched to Source Insight (IDE) + WinAVR + AVRstudio (Debugger).