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.
We know that it’s common to keep Mbed programs in other source control systems, and based on feedback from many of you in the developer survey earlier this year we decided it was high time to allow you to share your code directly from GitHub. We’ve added a new option that allows you to do just this. Your code is hosted in GitHub, but is listed and searchable alongside Mbed-hosted repositories on the Code page and your My repositories page. GitHub-hosted code can be imported directly into the Online Compiler or with Mbed CLI.
We’ve blogged about memory optimization before: Reducing memory usage by tuning RTOS configuration, Optimizing memory usage in Mbed OS 5.2 and Where did my flash go? Visualizing linker statistics. Mbed OS also supports runtime memory tracing and runtime memory statistics.
Both flash memory and RAM are limited on most microcontrollers, so reducing the memory footprint of your application can help you squeeze in more features or reduce cost. In this blog post we'll look at making Mbed OS 5 applications smaller, first by replacing standard I/O calls with a smaller implementation, and then by switching the whole standard library. All numbers in this post are based on Mbed OS 5.6.6 and GCC 6.3.1, and verified on NUCLEO-F401RE.
Having a small and resilient file system is crucial for many IoT devices. But utilizing the file system and pairing it with the correct storage technology such as external flash or SD cards can be difficult. Mbed OS is making it easy to add file system support by providing a wide portfolio of file systems. Mbed OS 5.7 supports both a FAT file system and introduces a new high-integrity embedded file system. This high-integrity file system is small, power-cut resilient and has wear-leveling support for flash chips that do not have their own wear levelling controller.
The Arm Mbed OS 5.7.0 release helps to further simplify the Internet of Things (IoT) and embedded product development with the addition of several new features, such as the high-integrity embedded file system, which provides power loss resilient operation and maximizes the life of the external memory block device by implementing wear leveling techniques. The release also includes an open-source mesh networking stack, which is IPv6, 6LoWPAN and one of the only two open-source certified Thread networking stacks. This release also continues our efforts to add comprehensive documentation for Mbed OS. Our ongoing efforts in this area include adding documentation about contributing and using our platform, drivers, RTOS, connectivity and storage APIs, as well as information about our tools. This release also includes improvements to the user experience of our documentation.
In addition, this release contains many minor fixes and enhancements and brings support for 103 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.7.0 release.
- 1 ...
- next »