Bruce,

I didn't spend much time with the IAR for the ARM as I couldn't get it to work - problemswith the startup code I expect. As for code size comparisons between IAR and others, I can't comment. I doubt if IAR would be substantially better as they might be for the 8051.

As for code memory usage comparison between the 8051 and ARM - this is purely speculative- I would say about twice for the ARM. However, using the THUMB instructions might redress the balance. Also, ints are 32 bits on the gcc compiler so that may cause more code bloat due to initialisers etc. In my reading of various articles on the web, the implication is that ARMs and other RISC cpus tend to be hungrier for code space. As such,this is not too much of an issue as most of the Philips ARMs and the other manufacturers usually have a fair slab of flash on the chip. I dare say for my LPC2103 project it might turn out to be more cost effective to go to a larger part. Once I've got most of the features implemented in the code, I'll be in a better position to compare compilers etc and decide whether I squeeze it into the '2103 or goto to a part with 128k or more flash.

I suppose the next question is comparison between Atmel, Philips and Analog Devices ARM parts. The Philips are reputed to be the fastest due to 128bit wide flash internally. As to who's parts you use will depend on speed,features and cost I expect.

Most of the tools support all these devices, it's mainly a matter of the include files for the peripherals, where the memory is located and the startup code.

Another negative just came to mind - the LPC's don't have a slab of internal eeprom like the AVRs,PICs and some of the 8051's have. Adding the external i2c eeprom is just so 90's!