Content originally posted in LPCWare by ktownsend on Sat May 11 06:06:19 MST 2013
I guess having to learn multiple tools is just what feels (for better or worse) normal to me with embedded development, and that will probably never change. Is it a PITA? Sure! ... it's also why I stick with GCC and a good old makefile/linker script, since it's the only relatively constant tool that I'm sure will be here years from now.
For IDEs, though, I guess I've just gotten used to switching between LPCXpresso, Crossworks, Keil and a Makefile. Personally, I prefer to work in Crossworks, but given the cost LPCXpresso is a compelling choice for a lot of people, so I need to support that as well, and I know I'll never have one IDE on my desk since it does change vendor to vendor.
Again ... I see absolutely zero signs that that will change soon, except sticking to VI/nano and make + GDB.
No single IDE does everything I want (at least for the prices I can pay!), and at the end of the day I take what I /can/ afford for debugging, and rely on GCC and the command-line when it really matters and for production builds.
LPCXpresso is far from perfect, but Keil has it's issues as well and the price tag is a lot harder to swallow.
It comes down to personal taste, but I'm only interested in GCC as a viable/safe long term solution, so if you need something that plays well with other MCUs, I'd really recommend taking a look at Crossworks for ARM. If you're looking for an affordable option for LPC chips, though, LPCXpress does represent a pretty good value for your money.
Kevin