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.
"If it's not documented, it didn't happen," is a mantra often heard in the Arm office these days. That's because documentation is important to us at Arm. Because documentation is so important, the Mbed OS 5.6 release included dramatic improvements to our Mbed OS documentation to better serve our users. These improvements include a new documentation site and engine, a new documentation structure and new content.
A big gray box on a desk. A bulky display next to it, gray text on a blue background. A child in front of it, frantically typing commands on the keyboard. Then the wonderful sense of excitement when the computer responds… "Hello world". For many of us, this was not only how we started programming, but also how we became developers. Naturally, we'd want to instill this feeling into the next generation.
Visual Studio Code, Microsoft's new cross-platform IDE, is gaining a lot of momentum. In the 2017 Stack Overflow Developer Survey it ranked in the top five for most popular developer environment for both web and desktop developers. Unfortunately, the survey did not have numbers on embedded developers - but its popularity is definitely on the rise in the Mbed offices, thanks to the excellent C/C++ support and the built-in support for visual debugging through GDB.
On November 29th, Arm and The Things Network hosted two webinars on getting started with LoRa and LoRaWAN. More than 700 people joined the webinar, but if you missed it, the recording is available here.
That LoRa is a popular subject was much reflected in the Q&A; we received far more questions than we could handle during the webinar. So in this blog post, Jan Jongboom and Johan Stokking are answering as many as possible.
Where can I find the presentation?
Seventy people, fifteen teams, and thirty-six hours of little to no sleep — those were the main ingredients to the final weekend of the Seoul IoT Hackathon. This year’s theme was "Better City Life," so we had the teams throw themselves at projects to make Seoul a better city, such as, reducing the time getting in and out of metro stations, detecting impacts on workers’ helmets, and building smarter electric car chargers — all using Mbed!
Arm Mbed DAPLink is an open-source software project that enables programming and debugging application software running on Arm Cortex CPUs . Commonly referred to as interface firmware, DAPLink runs on a secondary MCU that is attached to the SWD or JTAG port of the application MCU. This configuration is found on nearly all development boards. It creates a bridge between your development computer and the CPU debug access port. DAPLink enables developers with drag-and-drop programming, a serial port and CMSIS-DAP based debugging.
Over the years, DAPLink has been widely adopted and embedded into microcontroller development boards. We've been making many improvements to DAPLink from the kernel to the USB stack and the implementation of a virtual filesystem. This includes robust protections in the bootloader to prevent the MCU from getting corrupted by unexpected SCSI command sequences in mass storage class data transfers. We've now made it possible to get these updates on all development boards that run DAPLink interface firmware or have a DAPLink compatible MCU circuit.