Initial experiences with mbed M0
Steve Crozier.
1 reply
Well I signed up as a beta-tester for the latest M0 version of the mbed. The main project I intend to use this for is a data logger (more on that later) but this post is to document my first experiences with the LPC11U24 M0 device.
The beta part was recieved quickly but was unfortunately dead (enumerated as a USB disk, but contained no files and could not be written to - sounds like the flash failed). Thankfully the support guys were quick off the mark sending out a replacement part which works just fine.
The intial setup and registration of the device was simple enough (same process as for the LPC1768). First app (blinky lights) compiled and loaded okay, but the mbed library for your apps needs to be updated to the latest to avoid the error:
"#error directive: "CMSIS Target not recognised"" in file "lib/mbed/cmsis.h", Line: 16, Col: 1
... so most basic app now working, on to the datalogger.
1 comment on Initial experiences with mbed M0:
Please log in to post comments.
Initial experiences with mbed M0
Page owner: Steve Crozier
Created 17 Dec 2011.
Last updated 17 Dec 2011
Additional info from product support (after noticing the LED's were dimly lit):
...the LEDs glowing dimmly is an interesting point. We wire the GPIO to the anode of the LED, so that the pin sources current to the pin, and writing a '1' switches it on. When LPC parts are held in reset, their GPIOs are set to inputs, and have weak pull ups. On the LPC1768 mbed, the blue LEDs have a high Vf (about 3.1v) and a characteristic that means the tiny current from the pull ups isn't enough to light them. On the LPC11U24 mbed, we're using yellow LEDs, which can be lit dimmly by the pull up. Any time the LPC11U24 is in reset (including when the interface doesn't find a binary file) you'll see the feint glow!
so, tip/info: dimly lit LED's indicates the ports are in a HI-Z state.