Lpc2000

> 1. What are the GNU-based tools that developers use with the LPC210X,
> and how do they compare?

My preference is for generic gcc run in Linux. Where necessary (e.g.
when using a Macraigor Wiggler...) I use Cygwin.

However, for political reasons, in working on the LPC21xx parts I have
allowed myself to be persuaded to use Keil's version of GNUpro inside
Windows. I do not particularly enjoy cumbersome Windows IDEs, but I'll
allow myself to be persuaded that they accelerate the development
process for engineers who are accustomed to them. Since I'm used to vi
and makefiles, I find an IDE slows me down rather.

I have used ADS, and it's nice enough - and it generates slightly
smaller, often quantifiably faster code than gcc (though I have the same
gripe about ADS as I do about Keil - too much sugar!). The main downside
to ADS is that most of the OSes and other IP I use are open-source, and
they're intended for building with the GNU tools. This means that
serious massaging can be necessary to get things playing nicely inside
the IDEs.

I am currently trying to work out how to coerce the Keil-supplied
toolchain to build eCos.

> 2. (slightly OT) Does anyone use these same tools with other ARM parts
> -- namely, the Sharp LH75410 and the Atmel AT91RM9200.  Are the tools
> plug'n'play across all ARM7/9 cores or is there more to it than that?

Not really OT, many people need to support multiple projects with
different microcontrollers. I have written a book around the "generic"
gcc and the AT91R40807, and using the exact same toolchain I have
written many lines of code for the Cirrus CL-EP7212, 7312, and also the
LH79520. The *compiler* is plug-n-play, it's the default linking options
you need to tinker with (and of course hardware-specific libraries and
POI code!).

-- Lewin A.R.W. Edwards (http://www.zws.com/)
Learn how to develop high-end embedded systems on a tight budget!
http://www.amazon.com/exec/obidos/ASIN/0750676094/zws-20