About this release
Mbed OS 5.8 focuses on Mbed Enabled modules to reduce development cost, time and risk and provide go-to market value compared to traditional chip down designs. We are continuing our focus on low power with our sleep/deep sleep profiling tool, with which you can identify objects that are stopping entry into low power modes. The 5.8 release continues to strengthen Arm's connectivity portfolio with an updated LPWAN stack and updated Cellular stack with support for IoT-ready NB-IoT and CAT-M1 technologies. We have also launched the closed alpha developer trial of Mbed Studio, a free desktop IDE designed specifically for Mbed OS.
In addition, this release contains many minor fixes and enhancements and brings support for 121 target development boards. In the release note below, we summarize some of the key updates to Mbed OS that are part of the Mbed OS 5.8.0 release.
This is a guest blog, written by James Flynn from Avnet.
When implementing a network driver, you must verify the APIs are all used correctly. To make that possible, Arm provides a suite of network socket tests within Mbed OS called Greentea. The Greentea test suite runs on the test automation environment. This test suite exercises all of the fundamental APIs to ensure the driver will function correctly when integrated. It is a Pass/Fail verification of compliance, not a benchmark.
On March 13th, Jan Jongboom (Developer Evangelist at Arm) and Marko Hietala (Project Manager at Etteplan) will host the "Exploring LoRa with Mbed" webinar.
This is a guest post from STMicroelectronics.
As we celebrate our fourth year on the Mbed IoT platform, we are proud that nine Discovery kits, 29 Nucleo boards, and 24 expansion boards are now part of the ecosystem, making ST one of its most active contributors. In 2014, we started with only four compatible STM32 Nucleo boards, but we continued to increase our portfolio of Mbed Enabled™ solutions, while also porting many application examples and features.
The rapid expansion of the IoT market is being driven by companies who are either augmenting existing product lines with IoT functionality, or building innovative solutions for new market segments. In many instances these companies have neither the time or resources available to design on-board solutions from the ground up utilizing the full capabilities of a particular communications protocol, nor the expertise to obtain the necessary RF certification required in different geographies. To resolve this, they are turning to module manufacturers to provide the pre-verified functionality needed to give their products a solid technical foundation.
You need to log in to post a reply