Content originally posted in LPCWare by ktownsend on Thu Jun 30 08:30:49 MST 2011
Quote: kmmankad
1.Which Codebase(drivers) to use:
The NXP one is Ok,but its not documented,and frankly,not my style.Also quite tedious to use at places.
I saw the one over at microbuilder.eu,but its not CMSIS...There may be more out there,I dont know yet.Should I write my own? .. would be quite a project to do so though...
I suspect you will find a lot more support with the LPCXpresso library, particularly on the forum here. The library at microbuilder.eu has a handful of additional drivers and code that may be useful, but it's really aimed at a specific set of boards and assumes certain things about pin availability, etc., and also assumes a certain familiarity with make files and building from the command line.
Quote: kmmankad
2.Which Toolchain to use:
The CodeRed's Eclipse based IDE is cool and all,but this question is born from 1. above.Can I use a custom codebase with the provided IDE?
You can definately use LPCXpresso with any code base or library, not just CMSIS. The only caveat is that you will possibly need to setup the makefile and linker script yourself since by default LPCXpresso creates these for you (which is a good thing if you're just getting started with ARM or GCC, etc.). The fact that you have a decent HW debugger is a huge plus, and it can be cut off and used with any other support MCU as well.
The only thing I don't like about LPCXpresso is the way that projects are imported and I haven't found a way to have the Eclipse/LPCXpresso project files a couple levels higher than the source code the way this is done in the microbuilder code base for the LPC1343 or LPC1114 ... the source files start in root and the IDE specific project files (for Crossworks for ARM and CodeLite) are in /build/[IDEName]/* ... maybe I'm just dense, but I could only get LPCXpresso to build and work properly with the project files in the root folder as well, which I really don't like since I wanted to support other IDEs as well.
