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.
Come and join us for a talk with Morgan Du, Principle Engineer, Nuvoton to discuss various solutions that Nuvoton is providing for the IoT industry. Nuvoton is a leading provider of semiconductor solutions and platforms leveraging Arm technologies and their products are used in a number of devices satisfying a variety of use cases across industry verticals.
During this session, we will be discussing the Nuvoton NuMaker IoT Platforms and development kits that are using Arm Mbed OS and support Pelion Device Management services. We will also be showcasing how you can use these reference designs to build and manage your smart IoT devices and applications.
As some of you probably noticed, since Mbed OS 5.15 release we started removing deprecated APIs from the codebase. That's part of our cleanup efforts that will culminate in the next major Mbed release later this year.
We recently introduced a new issue template for issues raised in the mbed-os GitHub repository.
This blog post will provide guidance on how we would like to see it filled in. Adhering to the guidance is important for a number of reasons:
- The information requested is required in order for an engineer to be able to reproduce an issue and attempt a fix
- The quality of information provided gives guidance to other mbed-os users and allows them to determine if perhaps an issue they are also seeing, is either the same or related.
- The better the information the easier it is for the triaging engineers to determine the severity of the issue and thus correctly plan the resources and time frame required to fix it
- Some basic validation of the fields will be automated and polite requests added to the comments if anything is deemed to be missing or of insufficient detail. Issues will not be mirrored to our internal defect handling flow (and thus planned) until they are deemed to contain sufficient information. Unmirrored issues are unlikely to be investigated.
Some of the more curious amongst you may have noticed a new external Mbed OS release a couple of weeks ago on GitHub and we thought we’d give an update on what we’re doing in the Mbed OS team currently.
We are pleased to announce the release of Mbed OS 5.15 today.
One of our primary focus areas over the past three months has been updating the underlying compiler infrastructure that we support in order to benefit from the performance optimizations and language enhancements those compilers bring to the Mbed ecosystem. Further, work continues to improve our support for Python 3 and many of our basic tools have been updated to support this version. For Mbed itself, we have added support in a backward compatible way for “static pin map tables” to further reduce memory consumption in scenarios where runtime modification is not needed and not required.
The Mbed ecosystem relies on its community to support others, identify bugs and share its experience. We want to help that community thrive and provide answers and help as quickly as possible. You've told us that the existing forum experience is confusing so to improve the community experience we're merging our various forums in to one at forums.mbed.com.
You need to log in to post a reply