mbed OS Migration Plan
Migration to mbed OS will be a process that happens over several phases.
Along with the new OS, migration will involve transitioning to new development workflows. You can learn about these on the Getting Started pages.
When an mbed Classic platform is converted to an mbed OS board, we will no longer update and support this platform in the mbed SDK. This means you can continue to use any previously released version, but no bug fixes will be accepted or released as part of the mbed SDK.
For an mbed Classic platform to be added to mbed OS, it must go through the mbed Enabled program and meet all technical criteria.
What is the migration schedule?
Technology preview: "mbed-drivers" API and "mbed-hal" allow board porting by ecosystem partners and developers. This will be a good time to start component porting. mbed will have API and usability documentation and examples of the solidified APIs.
Phase 1: A few new boards. Keil MDK and online IDE support.
Phase 2: The mbed team, its partners and the developer community port the mbed libraries. This will be an open and collaborative process using the mbed OS primitives and driver APIs.
Phase 2.1: This will include more boards, specifically ones that rely on a library that has already been ported. Example: NetworkSocketAPI, HTTPClient, Websockets and MQTT.
Phase 2.2: This will include more boards, specifically ones that rely on a library that has already been ported. Examples: SDFileSystem, FileSystem (for external media) and FlashIAP.
Phase 2.3: This will include more boards, specifically ones that rely on a library that has already been ported. Examples: USBDevice, RPC, LWM2M and sub-GHz 6LoWPAN.
Phase 3: We're now quite confident that porting an existing application should be clearly documented and APIs hardened. FOTA using mbed Device Server, Thread stack certified and BLIP.
Stable: Boards and components are constantly running in under a hardware based continuous integration environment. There may be bugs but you can contribute tests and deploy them on hardware in the test farm.
When mbed, together with partners and developers, have fininshed porting all compatible platforms to mbed OS, we will deprecate and eventually make http://developer.mbed.org read-only. If you're an education institution and have course material built around these tools, please contact us at firstname.lastname@example.org. You'll have a period of time to continue using the site and services but will need to start planning the migration for course material.
If you have questions about the mbed SDK or development for platforms listed on http://developer.mbed.org please continue to ask them on the classic developer website and forum https://developer.mbed.org/forum.
If you are migrating to mbed OS, have questions or want to contribute please use http://forums.mbed.com.
We're excited about what's been done and what's coming. We hope you are too!