The Interrupt community comprises engineers, hobbyists, and enthusiasts with a shared passion for hardware and firmware development. We come together to share best practices, problem-solve, collaborate on projects, advance the embedded community, and elevate device reliability engineering (DRE).
The Interrupt Community was created and is moderated today by the founders of Memfault.
Latest Blog Posts
-
Linux Coredumps (Part 3) － On Device Unwinding
In this post, we’ll go over a method of coredump collection that does the stack unwinding on-device. This approach allows devices that may be sensitive to leaking PII (Personally Identifiable Information) that may be stored in memory on the stack or heap to safely collect coredumps in addition to greatly reducing the size needed to store them.
-
Smart Ring Development (Part 1) － Research and Prototype
This series of articles discusses the development of a SOTA Open Smart Ring － a tiny wearable packed with electronics that fits on your (even the smallest) finger. We dive deep into what it means to develop such a product, its challenges, and ultimately, how to make it a manufacturable and usable piece.
-
What we've been reading in May (2025)
Here are the articles, videos, and tools that we’ve been excited about this May.
-
Gophyr: Building a Gopher Client for Zephyr with Claude
by Jon SharpThis article chronicles my unexpected 3-hour adventure using Claude to create Gophyr: a fully functional Gopher client for Zephyr, complete with a Zephyr shell command set.
-
What we've been reading in April (2025)
Here are the articles, videos, and tools that we’ve been excited about this April.
About Memfault
Memfault is the first cloud-based observability platform for connected device debugging, monitoring, and updating, which brings the efficiencies and innovation of software development to hardware processes. Recognizing that any connected device team could benefit from what they were building, François Baldassari, Chris Coleman, and Tyler Hoffman founded Memfault in 2018 with the help of colleagues from Pebble. Try Memfault