I ran across this really cool project this morning. A guy built a little device that recorded light patterns, i.e. bright/dark, and then replayed them on an LED. He used a tiny Atmel micro controller and programmed it in C using, you guessed it, the CDT, with the WinAVR cross compiler toolchain.
It's projects like this that make working on the CDT so cool. We have this little device with 1K flash and 64 bytes, yes bytes!, of RAM and people can use the CDT to program it. Then we have the big iron supercomputers that the Parallel Tools Project gang work with, and you can use the CDT to program it as well. And, of course everything in between, from mobile multi-media devices, to Linux server applications, to the PC desktop, to gaming consoles. But this little project really made my day!
Thanks for the tip - WinAVR seems to be a great tool, I'll try to propagate it (with Eclipse/CDT) through our company since we still use TurboC and some outdated IDEs/compilers to develop our Atmel-based hardware.
ReplyDeleteHi!
ReplyDeleteMy name is Ivan Muzzolini from Italy and I work for Electrolux as a developer of firmware for ovens and hobs.
Our platforms are usually 8bit microcontrollers from Freescale, ST and recently Renesas; in the next years, we'll propably move to 32 bit platforms.
We are currently using MultiEdit as text editor for writing code and a toolchain composed by the following:
1. OpusMake (which is normally called through a batch file which sets up some environment variables before calling the Opusmake program )
2. several C compilers (usually Cosmic but also Renesas and IAR)
3. several debuggers (Cosmic ZAP, Codewarrior and a debugger from Renesas)
As you can see, every developer of our department uses a different set of tools depending on the microcontroller he is working on.
My intention is to propose the adoption of Eclipse as, first of all, a text editor in order to take advantage of the navigation facilities, code templates and so on. It would be nice to prepare Eclipse in order to do all the things that our current Editor is doing ( editing but also launching OpusMake with a simple keyboard shortcut...) but also the
things that it is not able to do ( having the compiler errors CORRECTLY parsed in order to jump to the corresponding line
in the code, easily browsing to the definition of a function, code completion ).
QUESTION: Which is the most immediate way of doing this first step with the CDT?
Thank you very much!
Best Regards
Ivan Muzzolini