‘Team mbed’ is back again at the AT&T Developer Summit Hackathon in Las Vegas, NV, Jan 3-4.
After a very inspiring and sleepless weekend at the AT&T Hackathon – Code for Car and Home in September, we have gathered Freescale Semiconductor, Multi-Tech Systems, Nordic Semiconductor, ST Microelectronics, u-blox and ARM back together again to form ‘Team mbed.’ We will be offering a ‘smorgasbord’ of sensors and actuators to go along with a variety of hardware platforms to choose from based on your I/O and connectivity needs (Bluetooth®, cellular, Ethernet, and Wi-Fi®). This event is a great place for developers to explore new hardware, experiment with innovative ideas and get guidance from the experts…not to mention the great food and grand prizes! This year the first place winner will be taking home $25,000 USD, second place with $10,000 USD and third place with $5,000 USD!
We are giving first priority to our sensor and actuator collection to those whom complete our form to help identify the best hardware and components for your project. Fill out the form here!
All the information you need from ‘Team mbed’ can also be found here: https://developer.mbed.org/teams/ATT-Hackathon/
If plan on being one of the winning teams, you may also want to start thinking about how you will deliver your winning pitch to the panel of judges, check out some helpful tips at the bottom of this post.
We are looking forward to seeing everyone there and good luck!
It has been a while since the last activity roundup and the mbed team has been pretty busy! So we thought we would share some highlights from the last few months.
First off, if you haven’t already heard, we made a major announcement at ARM TechCon in October about the new ARM® mbed™ IoT Device Platform. This platform sets out to provide a new software platform and free operating system to simplify and speed up the creation and deployment of the Internet of Things (IoT) products. What that really means is we are making it easier for developers to get access to the tools they need to build internet connected devices and to focus on their value-add features and differentiation.
- Announcing a New IoT Device Platform - ARM mbed by Zach Shelby, Director of Technical Marketing - IoT, ARM
- Announcing our plans for mbed v3.0 by Simon Ford, Director of Platforms - mbed, ARM
Using the RETRO game console that Outrageous Circuits designed around the mBuino platform on mbed, they are calling on all gaming enthusiast to create games for this console. The top 3 games will be selected to win: 1st Place - $1000 USD, 2nd Place - $500 USD, 3rd Place - $250 USD. To find out more about how to get started check out their page, here.
New Sparkfun mbed Starter Kit
Hackster.io is a pretty cool new(ish) platform that lets you easily display projects and include all the source links you would want. We have started collecting some mbed projects, here. We would love to see more of what the mbed community is working on, so add your projects here!
Michael Shimniok made his Jeep into an autonomous vehicle with an mbed in control and it won first place at the 2014 Sparkfun Autonomous Vehicle Competition (AVC).
Is a "SAD" lamp hacked to become a color changing lamp that can be controlled by placing an NFC-enabled smartphone near it. In this case they used an Android Samsung Galaxy Nexus.
The interns at Nordic have created an internet of things platform for mbed. They are making it easy to rapidly prototype and develop Bluetooth LE enabled devices - get up and running in under 10 lines of code.
20 shields are now fully supported and tested across 10 ST Nucleo platforms on mbed. If you would like to help expand this list of shields and add support for more components on mbed then join the teams: components and shields!
Also the team has been working on creating an easier way for the mbed community to use the pyOCD library for programming and debugging the ARM Cortex®-M microcontrollers using CMSIS-DAP. Check out the update on the work, here.
This last August in Tokyo we had the 10th annual mbed Fest! With about 100 attendees and over 470 unique users viewing the live stream, the group showed off some great demos and presentations.
At the AT&T Hackathon @ Super Mobility Week – Code for Car & Home in Las Vegas in September, after a very sleepless night of coding teams Car Bon, Avben Jr, and RideSafe took home the top prizes with their mbed solutions.
- 1st Place in the Home Automation Challenge & Best use of mbed Award- Car Bon
- 2nd Place in the Home Automation Challenge - Avben Jr
- 3rd Place in the Connected Car Challenge - RideSafe
Join us at the AT&T Developer Summit Hackathon just before CES (Jan 3-4) in Las Vegas! 'Team mbed' will be there in full force again with partners from Freescale, MultiTech, Nordic, ST Microelectronics & u-blox. First place takes home $25,000 USD!
Recently added Platforms
- Freescale FRDM-20D50M
- Freescale FRDM-K22F
- NXP LPCXpresso 11U68
- LPC Xpreso 824-MAX
- mbed HRM1017
- Nordic nRF51-Dongle
- Nordic nRF51-DK
- Outrageous Circuits mBuino
- Red Bear Labs BLE Nano
- Red Bear Labs BLE nRF51822
- Renesas GR-PEACH
- Seeed Arch BLE
- Seeed Xadow-M0
- ST Nucleo F411RE
- Switch Science mbed LPC824
There is a lot more to look forward to in 2015, so stay tuned!
When STMicroelectronics joined mbed, they were very interested in code quality, shield form factor components and cross target compatibility. This lined up quite well with the development of the mbed automated test suite and our component database initiative - one solid library and example program for all platforms being developed by groups of people all around the world with similar interests.
In fact, ST was the first to pioneer the use of the mbed automated test suite for platform support development on mbed and through it set a quality acceptance criteria for a target support in the mbed SDK.
Some months later, together with the ST team, we are happy to announce that 20 shields are now fully supported and tested across 10 ST Nucleo platforms on mbed. Here is a picture of the hardware used:
While working our way to support these, we noticed that some of the existing libraries have static pin definitions, supposedly from the original hardware they were developed on. Others contain leftover code from a non-mbed software kits/platforms that they were ported from. Also not all of them were well documented and some would have no documentation at all.
We tracked how many of the existing component libraries are regularly maintained and what's the average time for a pull requests to be accepted for component libraries hosted under user (non-team) accounts. We have noticed that in some cases it would take weeks for a pull request to be accepted if the component library author is not around and this makes it hard to contribute and collaborate.
On the hardware side, a small number of shields use a dedicated 6 pin SPI connector, which is not implemented on most of the platforms on mbed and these shields require bridging between the 6 pin SPI connector and D10-D13. Also other shields require similar bridging for PWM connectivity. Once identified these incompatibilities should be explained on the component pages, so everyone can implement the provided workaround (if any).
This lead us to believe we have to set some ground rules to make it work for everyone:
- References - component libraries should contain no static peripheral code/references
- Routines - libraries should use the mbed SDK library methods/routines whenever possible
- Defines - hardware specific defines should be reduced to minimum and parameters should be used instead
- Documentation - a well documented code is mandatory, not optional
- Pin naming - example programs should refer to pins using the Arduino pin naming standard, e.g. A0-A5, D0-D15
- Teams - the code should be published in teams, not in user accounts, so team of developers would manage and accept new contributions
- Workarounds - any deviation from the shield connectivity standard should be documented on the component page and a workaround provided
To enable a team-managed collaboration workflow, we forked the component libraries and examples into two new teams that everyone can join in - components and shields teams. The components team is focused around any component libraries - either in shield or non-shield form factor, grove, etc. The shields team contains only example programs for shield components and does not contain/support any libraries.
Here's a list of all shields with cross-platform support on mbed:
|Shield name||Shield type||Product page||Support status|
|mbed Application Shield||Display, Sensors||Click to view||Supported|
|Freetronics 16x2 LCD||Display||Click to view||Supported|
|Seeed 2.8" TFT Touch V2||Display||Click to view||Supported|
|Seeed SDCard V4b||Storage||Click to view||Supported|
|W5200 Ethernet||Connectivity||Click to view||Supported|
|Seeed Wifi||Connectivity||Click to view||Supported|
|Seeed Bluetooth||Connectivity||Click to view||Supported|
|Seeed NFC V2||Connectivity||Click to view||Supported|
|Seeed XBee V2||Connectivity||Click to view||Supported|
|Seeed GPRS V2||Connectivity||Click to view||Supported|
|Ciseco SRF||Connectivity||Click to view||Supported|
|Sparkfun GPS||Sensors||Click to view||Supported|
|Freescale Multi-Sensor||Sensors||Click to view||Supported|
|Seeed Motor V2||Drivers||Click to view||Supported|
|Seeed Bot||Drivers||Click to view||Supported|
|Seeed EL||Drivers||Click to view||Supported|
|Seeed Relay V2||Actuators||Click to view||Supported|
|Seeed Energy||Power supply||Click to view||Supported|
|Seeed Charger V2||Power supply||Click to view||Supported|
|Seeed Grove V2||Hook-up||Click to view||Supported|
Next week we'll be in San Francisco at Dreamforce '14! We're hosting a workshop and teaching how to use mbed and the Force.com REST API. In the workshop attendees will use RFID tokens to create Cases in Salesforce. The RFID token is identifies a service technician on-site fixing an intelligent street light. Case data is recorded and sent when the technician presents his/her RFID token. The example scenario and associated project code serve as an introduction to mbed and mbed device programming. Additionally, the project shows how an mbed device can easily connect to the Salesforce.com cloud directly.
For those of you unable to attend here is the complete workshop code. For those wanting to create integration between their own mbed projects and Salesforce.com, please have a look at the mbed Salesforce Interface API.
Come join us at DreamForce 2014 for an awesome learning experience on the bleeding edge of IoT.
We are really pleased to announce our plans for the next generation of mbed!
As you are all aware, we have been working hard on pushing the boundaries of abstraction, productivity and collaboration in the embedded space for a while. Last year it became obvious to us that 1) with the right investment, we could take our thinking even further and also make it applicable to production-grade software development, 2) the disruptive jump in complexity brought on by Internet of Things (IoT) devices was going to be a huge catalyst for a new industry that would expect the levels of productivity we aspire to deliver, and 3) there were a lot of people that agreed with us.
The revolutions in web 2.0 and smartphones were enabled by the creation of platforms and ecosystems, and the widespread innovation they made possible. The complexity and requirements for IoT development at scale means classic embedded development as is just won't meet the needs, so embedded must enter the platform era too!
So we have been working on investing in mbed to deliver a proper full-stack platform that could be used for production software development. That means the technology, the team, the partners and ecosystem to make it possible. Today, we finally get to share our plans!
Here are some of the fundamental highlights for mbed v3.0:
We are working on command-line tools for mbed! To put simply, that means you'll be able to download our SDK tools package to create, work with and build mbed programs on your own machine.
But it goes a bit deeper than that. The underlying build tool we are creating (yotta) is very much inspired by the very successful NPM, and deals not only with building code, but also managing and working with software components and dependencies properly using Semantic Versioning rules. This will give us a path to well managed software component releases for our core libraries and across the whole community, and an easy and powerful way to build and manage your projects with no fuss.
That doesn't mean the Web IDE is going away; it'll be using these same tools hosted behind the scenes on our servers, so will continue to be a great way to get instant access to a latest and greatest development environment. It just wont be the only way :)
You may have seen we started working on a more advanced test framework earlier in the year. Well that'll be a key integrated part of v3.0 such that we can move to unit and regression testing being the standard, for us and the whole community.
The biggest fundamental investment we are making in v3.0 is a full-stack platform you can rely upon to build an application, that brings connectivity, OS primitives, power management and security in to the core. This is mbed OS.
Here is the high level view:
Things like the peripheral APIs and components of the Application Framework have always been part of our core SDK, and grown incrementally. This has worked very well for providing portability across different target microcontrollers and toolchains, and also in terms of management of the code itself. We will be making investments at in these areas for improving power and event management.
But on top of this, we have had a huge number of contributed libraries and components that have enabled all sorts of things, some of which have become near essential components. We have an optional RTOS (among other contributed RTOSes) that can included, but doesn't need to be. We have various networking libraries and various versions of each people have provided, but it is sometimes not clear which to use or where to feed back bugs. At the same time, we have identified some holes in functionality we think are important, so we have worked out how to make them available.
So it is time to pull some of this functionality in to the core so we chose one way of doing it that can become stable, well integrated and relied upon by all users. Here is some more on what we are doing for each of those features:
Wireless connectivity can be really complex, but generally abstracted to some very simple common interfaces. We are building those transports and interfaces in to the core.
The really key standards for wireless connectivity that we are working on are:
- Bluetooth Smart - Ideal for ultra-low power connections to Smartphones, Tablets and Laptops for things like wearables and smartphone accessories
- Wi-Fi - The standard home and office IP backhaul found almost everywhere, with Wi-Fi modules getting exceptionally cheap
- Thread - The new low-power wireless mesh IP network for home applications
- 6LoWPAN - Sub-GHz IP based mesh-networking for industrial and outdoor applications
- Cellular - IP connectivity away from WLAN infrastructure
Each of these can be made accessible to users in a consistent way, and with Wi-Fi, Thread, 6LoWPAN and Cellular, the IP abstraction works transparently.
Power management can't be an afterthought as it has implications down to how drivers are written and how you construct code. When you are running from a coin-cell, these things matter.
We are starting with extending our HAL to support non-blocking drivers and callbacks by default, and then building on that the hooks and intelligence in to our Application Framework to allow programming patterns that are conducive to energy efficiency and enable the processor and peripherals to go to sleep automatically when they are not in use.
When you are building connected devices, security is not an optional feature. Yet, without access to the trusted libraries you need or the standard security patterns you should use, it is hard to know how to get it right. Using IP helps us a lot as the models of end-to-end security of the web are well understood.
To avoid the various half-ports and implementation mistakes that mean you haven't really got the security you thought you had, we are going to be providing pre-integrated implementations of TLS and DTLS (a.k.a SSL) and how to use them so you can get your devices securely connected in a standard and trusted way.
We are also working on implementing the security schemes needed to securely bootstrap devices on to the network, and some really interesting technology to provide protection of things like keys and certificates within the device so they can't be leaked - something that will quickly become an essential requirement for connected devices.
mbed Device Server
This is a new thing we are working on to help make connected devices connected. We are building a scalable, industry strength Device Server that we can license to cloud and service providers to help them get IoT devices connected in to their platforms.
It is basically analogous to a Web Server that accepts connections from mobile phones or web browsers, but in this case, handles the connections from IoT devices and all the differences in protocols and behaviours they have.
It makes the devices accessible through standard REST APIs so they can be accessed by enterprise software, web applications and cloud stacks. So properly bringing the devices in to the world of the web.
To be clear, this is not something we are releasing now. We have been preparing the groundwork to start rolling this out since we really pressed go one year ago, but there is still a lot of work to do. We decided it was now the right time to share our plans, as our approach is an ecosystem one. This is something we are working on with a lot of partners, and a lot more still are aligning with what we are doing, so it is important to provide the visibility to allow the success and impact we want to achieve.
Our aim is to release a first proper version of mbed OS in a year, and we will be introducing early versions of components and functionality at alpha release milestones. You can find the mbed OS release schedule here:
More information on the releases themselves as we go, but for the first one, expect some focus on Bluetooth Smart, 6LoWPAN mesh networking and our HAL!
Team and Partners
We have come a long way! You may not realise, but we have now setup as a totally new business unit in ARM, have whole floors to ourselves and locations around the world. And most importantly, been hiring some really smart people!
Some of us together for a Summer Team Week in Cambridge
We are still growing fast, so if you think you should be part of the team, helping us on our mission, check out some of our latest job postings.
But to be clear, it hasn't been just our team working on this for a long time. This is something we're building in partnership with many other of the top tech companies. Yesterday, we held our invite-only mbed Connect event to go in to more details with some of these top companies; this year we had to make space for over 150! It was also very rewarding to be able to share the list of launch partners who are signed up to work with us to make mbed a success for everyone:
I hope you are as excited about what I've laid out here as I am, and we are looking forward to start rolling this out. Look out for more information later this year!
And if you didn't notice already, we have moved our developer site to a dedicated developer domain, and made way for a front end site to lay out our plans and partners for pushing mbed even further at the root http://mbed.org. Everything should still work fine, but please tell us if you find things broken!
Thanks to everyone who has been part of the journey so far, and we looking forward to working with everyone to continue to take mbed further than we could have ever imagined!