We've been working on the next version of the Mbed Tools for some time now, and believe now is a fine time to share additional details about why we've been working on new tools, the design goals of the new tools, and how we'll be rolling the new tools out.
Mbed Festival is an annual community event that happens in Japan that bring developers and enthusiasts together to learn about, and share their passion for, Mbed OS.
The Mbed team are pleased to announce the release of Mbed OS 6.1, following fast on the heels of our 6.0 release.
A major feature we have introduced in this release aims to improve your experience with Arm’s Platform Security Architecture when used in conjunction with Mbed OS. Platform Security Architecture, or PSA, is an Arm- led framework for securing IoT devices. Arm has been working in close collaboration with a broader ecosystem to establish both a certification scheme, involving a number of test labs and security consultants, and to provide a reference software implementation of the PSA Root of Trust, via the Trusted Firmware project.
I’m pleased to announce that the 1.0 release of Mbed Studio is now available for macOS, Windows and Linux. You can download Mbed Studio from here: https://os.mbed.com/studio
With the number of developers with an Mbed account growing by 20% since the initial release last year, some of you might be new to Mbed Studio. Here is a summary of the features and some background:
- New: Custom target management
- New: Keil uVision exporter
- New: Better source control workflows for git and mbed.com
- New: Completely overhauled documentation
- New: Mbed OS 6 support with examples
- New: Checkout progress for libraries added to the libraries panel
- Full set of tools dependencies (git, hg, Arm Compiler 6, gdb, pyOCD, Mbed CLI, GreenTea, clangd etc) included with the product along with terminal access from inside Mbed Studio
- Powerful Monaco editor including C++ intellisense for your development board and a source code minimap
- Integration with Pelion Device Management Services
- Preferences support for the editor and IDE
- Workspace management and search capabilities
- Support for Linux (Ubuntu 18)
- Serial output (automatically launched when you connect a board)
- Step debugging
- Custom build profile support
The Arm Mbed team is delighted to announce the release of Mbed OS 6, our first major release in almost four years. We have invested heavily to add the features required for today’s IoT devices, and to back those features up with state of the art tooling to simplify development of IoT and embedded products. You can use Mbed OS 6 now in Mbed Studio, the Mbed Online Compiler, Mbed CLI and directly from the Mbed OS GitHub repository.
This blog covers:
- Stable and mature APIs
- Board support for the most popular boards
- Custom hardware
- Community supported boards
- Bare Metal Profile
- Cloud services support
As initially explained in an earlier post, we’re introducing a few changes in Mbed OS 6 to increase the quality of the platforms that Arm Mbed is officially supporting.
For the reasons we shared in the blog, community-contributed platforms will no longer be maintained in the mainline Mbed OS repository. Fortunately, developers can continue to use community boards in the upcoming version of Mbed OS 6. It simply needs to be done in a slightly different way, through a new concept known as custom board introduced in Mbed OS 5.
We introduced the bare metal profile in Mbed OS 5.12 to offer memory constrained devices a subset of Mbed OS’s rich features. This configuration of Mbed OS excludes the RTOS and several other features and gives developers a higher degree of control over their application.
As announced in previous posts, we’re introducing many changes ahead of the Mbed OS 6 release to improve the quality of the code and user experience. A major focus is making the code base more maintainable and easier to use. We started by removing a large number of deprecated APIs. With this work almost complete, we’re now removing references of unsupported or deprecated tools.
As initially mentioned in an earlier post, we’re introducing a few changes in Mbed OS 6. It’s our priority to continue to improve the developer experience – this depends on the quality of hardware and software support of Mbed platforms and the work we’re doing with our partners on delivering the best support we can.
Back in October 2019 we announced the plan to change the Mbed OS release process and the monthly release cadence has now been running since the beginning of this year. This is just one of the changes being implemented on the run up to the next version of Mbed OS.
A lot of work is currently ongoing to remove deprecated APIs from Mbed OS 6 and to ensure that Mbed OS can provide a stable environment for production devices and, to ensure stability can be maintained, a modification to the API Life Cycle is being introduced.
The need to add a mechanism to introduce experimental APIs was proposed to the mbed partner governance forum along with a proposed solution and the forum granted its approval.
- 1 ...
- next »
You need to log in to post a reply