This is the third post in a series about doing device firmware updates (DFU) over the air (OTA) and continuous deployment of firmware for embedded devices. We'll explore the different parts of a complete end-to-end system with this capability.

This post is about how the firmware is delivered to devices and how you can build the firmware using Drogue IoT.

For this release, we had a focus on improving existing functionality. Mostly extending what was already there, but lacked a few features, knobs to tweak, or as postponed in previous releases. And yes, we fixed a few bugs too.

This is the second post in a series about doing device firmware updates (DFU) over the air (OTA) and continuous deployment of firmware for embedded devices. We'll explore the different parts of a complete end-to-end system with this capability.

This post will be about the different networks and how you can manage firmware updates using them.

This is the first post in a series about doing device firmware updates (DFU) over the air (OTA) and continuous delivery of firmware for embedded devices. We'll explore the different parts of a complete end-to-end system with this capability.

This post will be about a fundamental component in such a system: the bootloader.

Producing 1 PCB is very different from producing many PCBs, especially considering the logistics of assembling and testing. In this blog post, we'll continue the story from last time and look at the revised versions and how to scale up the production with PCB assembly and a test jig.

A lot has happened since the last release of Drogue Cloud. Unfortunately, the only thing that seems to stick out is the ongoing war in Ukraine. And whatever you think might have led to this, there is never, ever a justification for bombing the civilian population of a country. So, in a situation like that, can we simply celebrate what we achieved in Drogue IoT, like we usually do? I believe the answer to that must be "yes". Do what you think is right, but also focus on the positive! Because otherwise the terrorists have won!

For some time now, we've wanted to have a Printed Circuit Board (PCB) that we could use to demonstrate Drogue Device and Drogue Cloud. This is the first post in a series of post telling the tale of this journey.

Bluetooth Mesh is a brokerless system for devices to communicate within a local area. We've implemented a Bluetooth Mesh stack, in Rust, on top of Drogue-Device, our async framework for embedded development.

This is our "end of the year" release, and we did want to focus on improving what we already have, rather than introducing a bunch of new functionality, before leaving for the holiday season/Christmas. So we put a lot of effort into cleaning up, filling some gaps that we identified, and polish the current functionality.

We love Kubernetes and the standardized API it brings to deploying applications in the cloud. For running a local instance of Drogue Cloud, minikube is already a great alternative. But sometimes, you just want to have an easy getting started experience, to reduce turnaround time when testing changes to Drogue Cloud itself, or for running in environments where Kubernetes is not available.

Read on to learn how you can run Drogue Cloud standalone.