A while back on the 43oh! forums, bluehash posted a link to a contest for the mbed microcontroller platform, including an application for a free evaluation mbed module. I applied, thinking that I wouldn't receive one, but it appears that NXP and Circuit Cellar are very generous and handed one out to me even though I specifically stated that I was a student (not a company), did this as a hobby (not a job), and had no idea what I would end up doing with it. They shipped one out to me, no questions asked. Unfortunately, free boards are no longer available, but I have to say, with the specs it has, it is a very nice kit for the price (~$60US).
Anyway, all that niceness comes with a hitch. The mbed platform was designed around a "cloud compiler", a web-based IDE which operates in the cloud, compiling your code and handing you a downloadable binary file to drop onto the mbed's storage module. This works well, and the API that the mbed organization has developed is very easy to use and rather thorough (even compared to the offering from the Arduino team), and with an online compiler, you never have to download new versions of software... everyone will be using the same version, pushed out to the server whenever there's an update.
But this approach has several drawbacks. Firstly, your code is stored on the cloud. This is fine for most home tinkerers like myself, but for someone using the mbed to simply have an easy to access LPC1768 while prototyping a product or something could have issues with this. Secondly, the mbed API is closed source. I am a major proponent of free libre open source software. Yes, I use TI's CCS, but that's because at the moment I don't have the time to delve into setting up mspgcc4. Thirdly, and this is the biggie for me, if you don't have an active or reliable internet connection, you are left out in the cold. The device, as presented by mbed, is unprogrammable without the internet. This point to me seems a bit ridiculous.
So, upon receiving my mbed and confirming that it works by burning the "hello world" blinky program to it, I decided to find a reliable, easy way to compile code for it offline, with free libre open source software if possible. After a bit of digging and a few dead ends, I found a dead-simple solution.
The mbed is nothing more than a (slightly neutered, slightly enhanced) LPC1768 platform. There is nothing stopping this thing from running any ARM Cortex-M3 code you throw at it. So, I simply looked around for a solution using gcc-arm. Turns out, there is a similar product called the LPCXpresso (which I am considering purchasing), and there is a free version of the Code Red Suite IDE available for it called (uncreatively enough) the LPCXpresso IDE. This IDE is Eclipse based, so it is familiar to a lot of people (including those who use TI's CCS, which is also Eclipse based), and also very powerful. This one also has the advantage of using gcc-arm for the backend. The IDE is limited when using the LPCXpresso boards, as the free version (once registered) has a flash download limit of 128k. But because it uses arm-gcc as the backend, it has an unlimited compile size. And, as the mbed cannot be flashed in the traditional way thanks to it's "innovative" drag2flash magic-chip (their terms, not mine), this effectively renders the LPCXpresso IDE limitless when it comes to compiling code for the mbed.
So, enough of my bantering, on to how to do it. I'll list steps in an ordered list here to simplify the process as much as possible. Note, all of my instruction comes from working with a Windows machine. I do not know how the Linux version of the LPCXpresso IDE differs from the Windows version other than the obvious path names and such.
- Get an mbed.
- Go to the LPCXpresso IDE page, and register an account. Once that is done, download the appropriate version of the IDE for your platform.
- Install the IDE. During setup, you might be asked if you want to install the Debug drivers and the NXP-link drivers. These are completely un-necessary if you are going to be using this IDE strictly for the mbed. The mbed unfortunately cannot be debugged, nor can the chip be completely reflashed, as the mbed module lacks the JTAG breakouts.
- Once installed, run the IDE. To stop the annoying nag message, you should activate your product (it's free). To do this, go to Help>Product Activation>Create Serial number and Activate. This will give you a serial number. On the LPCXpresso IDE site, you can click My Registrations, and enter this serial number. Once you do that, check your email. You will have received an activation code. Go to Help>Product Activation>Enter Activation Code and paste in the code emailed to you. This will register your IDE. Again, this step is optional, but it prevents a nag-box from appearing every time you open the IDE.
And that's all you need to get the IDE.
Now on to some code. The IDE comes with several examples to get you started. To import these examples, go to the button at the top of the IDE that looks like a blue circle with a lightbulb in it. From there, click browse, then go to NXP>LPC1000>LPC17xx>RDB1768cmsis.zip. On the next screen, deselect all, then choose the first one (CMSIS) and the one called LEDflash. This will help us get a simple hello-world up and going. These projects will import, and be ready to compile.
Well, almost. This project (LEDflash, the CMSIS one is a low-level interface library between the C code and the registers in assembly which the LEDflash project depends upon) was designed for Code Red's LPC1768 board, which has LEDs on different pins than the mbed. So a few small changes to the code are in order. Open up "leds.h" and replace the first chunk with the correct pin numbers of the LEDs (change LED_5 to LED_1 wherever it appears in this file). According to the mbed schematic, The user LEDs are connected to P1.18 (LED1), P1.20 (LED2), P1.21 (LED3), and P1.23 (LED4). Change the values of the #defines accordingly. Save, now open up "main_ledflash.c". Wherever LED_5 appears, replace it with LED_1. Save, and you're ready to compile.
Go to Project>Build Project. The project will build. There's one last step to getting it mbed-ready. Over in the left hand panel, click on binaries (under LEDflash), then right click on the .axf file, go to Binary Utilities>Create binary. This will take almost no time at all, and the status bar at the bottom of the IDE will display "Successful". Now find the folder where your workspace is located (right click>properties on the .axf file, and look under Location). In that folder will be a .bin file (created in the last step). Copy that .bin file to your mbed, hit the reset button, and enjoy your (extended) hello-world blinky example!
This has been a long post, but an enlightening one, I hope. I may end up developing an LPChere framework similar to my MSPhere framework, but not at this moment in time. For now, I'm just happy that I was able to find a solution, and I hope this has helped anyone who actually took time out of their day to read it. Thanks for reading, and comments are always appreciated :)
EDIT (21 May 2011): Daniel Marks just emailed me the following information that might be helpful for others:
I just read your blog entry from Oct 17 and I wanted to let you know that you can just use Codesourcery G++ lite (http://www.codesourcery.com/sgpp/lite/arm) or just compile arm-non-eabi-gcc toolchain yourself to use with the mbed. I did this for use with my open source project Jumentum (http://jumentum.sourceforge.net/). My project is an open source BASIC language for LPC microcontrollers that resides on the microcontroller.
If you download the source code for Jumentum you will find ported CMSIS and other sample source code for LPC1768, or you could just try the mbed port of Jumentum directly.