hello all!

I'm currently playing with YAGARTO, exlipse, a SAM3N-EK board and a SAM ICE, and find it pretty good - though having a bit of an issue with a disconnect between eclipse code highlighting and the actual compiler.

for instance in the library code all the conditionals are always marked greyed out - even the ones that actually get used to compile the code. Also funny things like #include <stdint.h> in source code is seen as unresolved by eclipse, but of course, the code compiles, and can be debugged on my evaluation board...

I've played with codesourcery lite, but it couldn't even compile its own example code out of the box (problem with make I think?) so I'm not sure if it's worth my while to chase that problem down or not.

So, I was wondering if there's a consensus on which option is best (there's winarm, sourcery codebench lite, and anglia.. any more? )

I'm wanting to be able to use atmel's ASF library code for their ARM models, and also the bitcloud zigbee pro stack library. Plus my SAM-ICE to program and debug.

I'm not really interested in time or code size limited tools, I want a toolset I can use for free at home as long as I want, to the limits of the silicon.

I'm also interested in atmel studio 6, but have decided to leave it alone until I get a new computer (my poor old 7 year old laptop really struggles, plus I'm having major issues with the program that nobody else has ever reported...)

Any pointers you could give to help speed my search would be greatly appreciated.

thanks!

The compiler is not the problem in 90% of the cases. For proper code-highlighting in eclipse, the indexer refers to the include paths that gets set for the project.

Right click on your project, click on properties, Expand C/C++ General, Select Paths and Symbols.

Under the includes tab Add all the directories containing .h files "basically the same as the makefile -I direction". Also add your compilers include directory for <stdlib.h> etc. Directories can be added as absolute, or workspace relative. It should be done for Assembly, GNU C, and GNU C++ depending on which gets used by the project.

In the C/C++ Build tab under properties, select settings, and make sure the GNU Elf parser is selected under the Binary parsers tab. Under the Error parsers tab you can select which error parsers are used.

Eclipse basically takes the output from the console window after a compile, and parses it to get its error and warning highlighting

For Codesourcery lite compiler, use cs-make with a custom makefile(no auto makefile generators). I use it every day on SAM3s.

hey there incognito! thanks for the reply.

I'll have a poke about later tonight and see what I can see with the code highlighting vs. actual compiler output. It's not really a problem right now if the code compiles and basically does what I expect, just something that looks a little weird and I'll have to nail down sooner or later for my peace of mind.

Good to know you use codesourcery every day. I think I'll give that one a bit more of a look next. I didn't think it was a good sign that a demo project for codesourcery didn't work from a default codesourcery install, but maybe it was just having a bad day.

Just wondering - do you use either ASF or bitcloud (or both?) with codesourcery? are you happy with how they work?

thanks again!

Was the demo project from Atmel, or codesourcery? I'm not very fond of the way the example sources are structured in the Atmel example projects. I usually take these, and create my own project with custom makefile and linker script.