I'm (still) new at AVR32s, but I've worked with 8-bit AVRs for nearly a decade. So I thought that a switch to AVR32 would be pretty easy.
Well, to quote the teacher in Pink Floyd, The Wall: "WROOONG! Do it again!"
When compiling my regular 8-bit programs, I simply start the compiler (using make.exe) from my text editor, and get the compiler response in a separate window in the editor. Make.exe uses "makefile" to figure out which device I'm using, which files are part of the project, which file is the main file, and so on.
I find great value in this simple operation, especially when keeping track of firmware versions, copying (parts of) projects, all that kind of stuff. Yes, I actually see a big advantage in not using a huge and complicated GUI when compiling a program that has no graphical interface. A long time ago, I had to use the IAR compiler "“ and hated it.
Now for the AVR32. I put MCU = at32uc3b0256 (and later MCU = __AVR32_UC3B0256__) in a copy of an existing makefile, and I fairly quickly figured out that I had to use avr32-gcc.exe instead of make.exe. But nooo. avr32-gcc.exe apparently doesn't use the makefile, but (possibly) expects to have the whole shebang of options added in the command line. This is where I "crash". I can't even get the compiler to run. :(
Just to try something, I put #define __AVR32_UC3B0256__ in the beginning of my .c file, and the compiler now doesn't complain, but neither does it give me any feedback. I just get - silence.
I've spent hours browsing the AVR32 forums and the GCC manual, without getting anything useful. It seems that everybody else at least know how to compile. But maybe that's because everybody else use AVR Studio 5, 6 or 32. I still feel very reluctant to install such huge software, just to control another command-line based piece of software, but I fear that might be the bitter end. :-/
Anybody else have experience with avr32-gcc.exe? And makefiles for this?