Memfault

San Francisco, CA, USA
2018
  |  By Victor Lai
In this article, I walk through how the growth of internal observability tooling for an AOSP device might look like, and the variety of pitfalls one might encounter as they scale from 1s to 10s to 1000s of Android devices in the field, based off my experience talking to AOSP developers and teams, and personally as an Android app developer working on AOSP hardware.
  |  By Blake Hildebrand
One of the core features of the Memfault Linux SDK is the ability to capture and analyze crashes. Since the inception of the SDK, we’ve been slowly expanding our crash capture and analysis capabilities. Starting from the standard ELF coredump, we’ve added support for capturing only the stack memory and even capturing just the stack trace with no registers and locals present.
  |  By Fabian Graf
Monitoring IoT applications is essential due to their operation in dynamic and challenging environments, which makes them susceptible to various operational and connectivity issues. Application Performance Monitoring (APM) is the key to identifying and resolving these issues in real time, ensuring uninterrupted data flow and functionality. Moreover, the insights gained from APM can optimize device performance, ensure reliability, and reduce operational costs.
  |  By JP Hutchins
This guide provides instructions for setting up an environment for developing, debugging, and programming embedded systems firmware in the Windows Subsystem for Linux (WSL2). WSL2 provides a convenient and stable Linux development environment for working on embedded systems firmware. If you’re curious about toolchain performance, check out this comparison of firmware development environments, but the summary is that WSL2 is about 2x the speed of Windows and similar to “bare metal” Linux.
  |  By Gaurav Singh
At Ultrahuman, innovation is at the core of everything we do. Our health devices, powered by the nRF52840 SoC for BLE functionality, rely on Nordic Semiconductor’s renowned wireless technology. For years, the nRF5 SDK was the cornerstone of firmware development for these chipsets, but in 2018, Nordic introduced the nRF-Connect SDK(NCS), built on Zephyr RTOS, signaling a new era for BLE applications.
  |  By Dion Dokter
While using a full-blown filesystem for storing your data in non-volatile memory is common practice, those filesystems are often too big, not to mention annoying to use, for the things I want to do. My solution? I’ve been hard at work creating the sequential-storage crate. In this blog post I’d like to go over what it is, why I created it and what it does.
  |  By Noah Pendleton
In this very Memfault-centric post, I’ll be talking about how we shipped our SDK as an ESP-IDF component. This is a continuation of our efforts to make it easier to integrate Memfault into your projects, specifically targeting ESP32-based projects.
  |  By Gillian Minnehan
Last week, a handful of Memfolks had the opportunity to travel to Austin to attend the first ever Embedded World North America1! Embedded World NA welcomed 3,500 visitors and 180 vendors across 3 days2. While it was surely a smaller showing than Nueremburg’s Embedded World, we still wanted to quickly touch on our takeaways from the event. In this post, we will cover what we learned from the first Embedded World North America.
  |  By JP Hutchins
About a year and a half ago, I decided to take a different approach to setting up a Zephyr environment for a new project at Intercreate. Instead of using my trusty VMWare Workstation Linux VM, I opted for WSL2. I was curious to find out: Would hardware pass-through for debugging work reliably? Would all of the tooling dependencies be supported? What about build system performance?
  |  By Bert Schiettecatte
In this article, we will learn how memory usage patterns can affect the real-time performance of an embedded application, drawing from a recent experience tracing an audio DSP application running on an embedded Linux platform. First, I will introduce the product in question and the real-time audio software I developed for it. Then, I’ll describe the issues I encountered with audio callbacks and the strategy I followed to determine the cause of the issues, ending with my solution and lessons learned.
  |  By Memfault
After years in the field, Pebble watches started failing—resources wouldn’t load, watch faces went blank, and support requests piled up. The culprit? A subtle timing issue with NOR flash wear that only surfaced as devices aged.
  |  By Memfault
Pebble wasn’t built by industry veterans, it was built by hackers figuring it out as they went. Memfault founders François Baldassari and Chris Coleman, alongside Brad Murray of Beeper, dive into how Pebble’s startup culture led to a unique approach in firmware development.
  |  By Memfault
A single unprotected region holding fonts changed everything. Memfault founders François Baldassari and Chris Coleman, along with Brad Murray of Beeper, discuss one of the most clever security bugs discovered through Pebble’s WhiteHat program.
  |  By Memfault
When Pebble launched its SDK in 2012, it started as a pile of Python scripts. That was just the beginning. Memfault founders, François Baldassari and Chris Coleman, along with Brad Murray of Beeper, discuss the evolution of Pebble’s app sandbox, the challenges of early firmware development, and how a passionate developer community helped shape the platform.
  |  By Memfault
Join the Founders of Memfault as they dive into this trend alongside special guest Alexander Samuelsson, CTO and Co-Founder of Imagimob (an Infineon Technologies company). This conversation on The Future of Edge AI and What It Means for Device Makers will explore how advancements in Edge AI are reshaping the embedded landscape, from hardware design to edge AI model development.
  |  By Memfault
IoT margins are already tight—why make it worse? Many companies are throwing away money on preventable costs like unnecessary RMAs, bloated customer support, and costly technician visits. But there’s a better way: Observability and OTA updates can help reduce churn, cut support costs, and eliminate waste. We just watched a customer slash support tickets by 30% and RMAs by 50% using Memfault’s observability data. These are real numbers, real savings, and real impact.
  |  By Memfault
Big tech has the resources, but startups have the real advantage in AI wearables: speed, agility, and the freedom to take risks. Right now, the AI wearable market is in the wildcard phase—no dominant device, no set form factor, and no clear winner. That’s a massive opportunity for smaller teams that can move fast, test in the field, and refine in real time. Unlike big tech, startups don’t need a five-year roadmap. They can launch quickly, experiment aggressively, and pivot without worrying about shareholders.
  |  By Memfault
Meta is making a massive push into AI wearables, with at least six new devices launching in 2025. But here’s the catch—this wasn’t originally about AI. Meta built its hardware for the metaverse, only to find itself at the center of the AI revolution. With over 1 million Ray-Ban smart glasses already sold (and a goal of 5 million in 2025), it’s clear there’s demand. But can Meta actually scale this initiative from within, or will they lean on brand partnerships like Oakley to expand?
  |  By Memfault
How can engineering teams have a bigger impact on the bottom line? By thinking beyond code. Most engineers love to build and solve problems. But in a business, building for the sake of building isn’t enough. Even the cleanest code is just an expensive distraction if it doesn’t move the needle.
  |  By Memfault
Some IoT companies are making money; others are leaking it. Margins in IoT are already tight, but many brands are losing cash in ways that are completely preventable. RMAs, bloated customer support costs, churn, and on-site technician visits all add up. Too many companies default to replacing hardware instead of fixing the code. Without OTA updates and remote diagnostics, budgets get drained by unnecessary shipping and support costs.

Reduce risk, ship products faster, and resolve issues proactively by upgrading your Android and MCU-based devices with Memfault. By integrating Memfault into smart device infrastructure, developers and IoT device manufacturers can monitor and manage the entire device lifecycle, from development to feature updates, with ease and speed.

With Memfault, engineers no longer have to rely on incomplete user crash reports and their local debugger to reproduce and fix device issues in the field. Memfault's cloud-based firmware delivery, monitoring, and analytics tools dramatically reduce engineering and support overhead, enabling you to ship and manage thousands to millions of IoT devices with confidence./p>

One platform for more efficient device operations:

  • Continuously monitor devices: Go beyond application monitoring with device and fleet-level metrics, like battery health and connectivity with crash analytics for firmware.
  • Remotely debug firmware issues: Resolve issues more efficiently with automatic detection, alerts, deduplication, and actionable insights sent via the cloud.
  • Systematically deploy OTA updates: Keep customers happy by fixing bugs quickly and shipping features more frequently with staged rollouts and specific device groups (cohorts).

Cloud Debugging and Observability for Your IoT Devices.