Short notes, links worth your time, and the occasional event. Longer pieces live on the blog. Subscribe by RSS.
No signals of this type yet.
A webinar worth a look: taking a Zephyr device from a crash all the way to fixed firmware by debugging it remotely, in real time. Two sessions to pick from.
It’s a joint webinar by Spotflow, where I work, and MAB Labs, with Mohammed Billoo presenting for MAB Labs.
The Linux Foundation’s Open Source Summit Europe comes to Prague this year, and a good part of it is embedded. The Embedded Linux Conference, the Zephyr Developer Summit, the PX4 Dev Summit, and a safety-critical software track all run inside the main summit.
Come a day early for the embedded side events on 6 October: the Yocto Project Developer Day, the Real-Time Linux User Forum, and the Zephyr Maintainers Forum, where maintainers and regular contributors set the project’s direction for the coming year. Each needs its own registration.
Spotflow, where I work, will be there as part of the Texas Instruments booth, right in front of the keynote room, with a firmware observability demo. It is a battery-powered Bluetooth LE asset tracker built on TI’s CC2340R5, a Cortex-M0+ with 36 KB of RAM and no internet connection of its own. It runs Zephyr and sends its logs, metrics, and crash dumps out over Bluetooth through a nearby gateway.
The firmware has a memory bug left in on purpose. Shake the tracker and it crashes, and about ten seconds later the coredump is in the cloud, decoded down to the function and line. If you’re attending, stop by the booth and ask for a walkthrough.
Embedded world’s North American edition returns for 2026: three days of silicon, RTOS, tooling, and firmware under one roof in Anaheim. It’s a chance to put new boards in your hands, ask vendors the questions a datasheet won’t answer, and see what other teams are actually shipping.
As of today, the CRA’s first reporting obligation is live. If a vulnerability in a product you shipped is being actively exploited, the clock is now measured in hours, not weeks.
Once you become aware, the timeline is an early warning within 24 hours, a full notification within 72 hours, and a final report 14 days after a fix is available (one month after the 72-hour mark for a severe incident). Notifications go through ENISA’s Single Reporting Platform, which delivers them to the national CSIRT acting as coordinator and to ENISA at the same time.
Hitting those windows is not a paperwork problem. It means knowing which firmware versions include the affected component, and which of your deployed devices last reported running them. For most fleets, that is not a question you can answer by hand in a day.