Coredump Sessions

Spotify DetailsIn today's Coredump Session, François Baldassari and Chris Coleman sit down with Ross Yeager, VP of Device Platform Software at Skydio, to explore how autonomy is reshaping modern robotics and what it takes to build drones that can truly think for themselves. Ross shares his journey from Boosted Boards to Skydio, unpacking how the company pioneered fully autonomous flight, built a vertically integrated manufacturing operation in California, and created a foundation that blends cutting-edge software and hardware. It’s a conversation about leadership, innovation, and the engineering mindset behind one of the most advanced drone platforms in the world.Key Takeaways:Ross Yeager's journey into embedded engineering began with a passion for electronics and product development.Kickstarter projects provided valuable lessons in scaling production and managing customer expectations.Working at Boosted Boards allowed Ross to experience the challenges of building products from scratch.Safety is a critical concern in drone technology, with high stakes for reliability and performance.Skydio's unique approach involves vertical integration, manufacturing drones in the U.S. for quality control.The embedded engineering landscape has evolved, with new tools and technologies simplifying development.Testing and quality assurance are paramount, with innovative methods to ensure reliability in drone operations.Ross emphasizes the importance of curiosity and problem-solving in engineering roles.Chapters:00:00 Intro & Teasers03:30 Ross's Path to Embedded Engineering07:52 Lessons from Kickstarter and Early Projects12:35 Transitioning to Boosted Boards and Micro-Mobility17:52 Challenges in Embedded Systems and Hardware Development22:45 Skydio's Unique Approach to Drone Technology30:06 Manufacturing Drones in the U.S.35:01 Embedded Engineering Challenges and Safety Considerations39:29 Testing and Quality Assurance in Drone Development46:47 Future of Skydio and Career Opportunities56:18 Closing Thoughts & ReflectionsJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTube [ADD Playlist YT Link from here)⁠⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

SummaryIn today’s Coredump Session, François and Chris wrap up the year with a special milestone celebration for the 20th episode of the series. They take listeners behind the mic to reflect on how Coredump began, the moments that defined 2025, and the lessons learned along the way. Expect highlights from the year’s most talked-about discussions, bold predictions for what’s ahead in 2026, and the biggest live Q&A yet—where nothing is off the table.Key Takeaways:Why Coredump Sessions started and how the show has evolved over 20 episodesThe biggest engineering lessons guests shared throughout 2025The most surprising device failures and field behaviors teams faced this yearHow firmware teams adapted to fast-changing toolchains and new requirementsThe rise of AI-assisted debugging, testing, and development in embedded workHow security mandates tightened and reshaped device developmentThe recurring theme that real-world conditions rarely match lab assumptionsWhat François and Chris learned from producing the series behind the scenesWhat the hosts expect to define embedded systems development in 2026The expanded live Q&A format and how the community is shaping future episodesChapters:00:00 Teasers01:30 Intro/ Welcome03:35 The Genesis of Core Dump06:54 Favorite Moments and Lessons Learned08:45 Clip Reaction: Nick Sinas's OTA Nightmare in the Snow12:19 Clip Reaction: Lack of Security at Pebble16:45 Clip Reaction: Dan Mangum on AI & Engineering21:50 Clip Reaction: Vatsal at Ultrahuman Talks Always-On Devices25:29 Clip Reaction: Chad from Gabb Talks Security30:12 Looking Ahead: Predictions for 202635:59 The Rise of AI and Edge Computing42:24 Evolving Skills for Firmware Engineers47:01 Security in Embedded Systems49:01 The Future of Testing in Embedded Development53:15 Conclusions & Thank Yous⁠Join the Interrupt Slack⁠ ⁠⁠⁠⁠⁠⁠⁠Watch this episode on YouTube ⁠Follow Memfault⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠Bluesky⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠Other ways to listen:⁠⁠⁠⁠⁠Apple Podcasts⁠⁠iHeartRadio⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Amazon Music⁠⁠GoodPods⁠⁠Castbox⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Visit our website

In today’s Coredump Session, François and Chris from Memfault sit down with Charles Taylor, co-founder of Ozlo Sleep, to explore the journey from Bose’s original Sleepbuds to the rebirth of a product designed to help people truly rest. The conversation traces how Ozlo revived this beloved idea, balancing power management, all-night comfort, and reliability in one of the most demanding consumer tech categories. Along the way, Charles shares lessons from bringing a hardware product back to life, testing technology people use in their sleep, and building a community that believes better rest starts with better engineering.Key Takeaways:Charlie's journey from engineering to entrepreneurship was accidental but rewarding.The emotional connection users have with physical products is significant.Sleep tech addresses the problem of noise disruption during sleep.Kickstarter was used not just for funding but to build a community.Firmware updates are crucial for improving user experience and product functionality.Designing sleep earbuds involves unique challenges related to comfort and size.Battery life and efficiency are critical in hardware development.Sensing technology in sleep tech can provide valuable health data.Testing and quality assurance are essential in product development.Navigating FDA regulations is complex but necessary for medical-related devices.Chapters:00:00 Intro and Teasers02:02 Meet Charlie Taylor and the Ozlo Sleep Story06:13 Why Sleepbuds Exist and Why Noise Matters07:07 Rebuilding Bose’s Discontinued Sleepbuds09:15 The Hardest Parts of Hardware: Timelines and Vendors10:39 Kickstarter as Validation and Community Building15:57 Designing for Sleep: Comfort, Power, and Miniaturization23:16 The Ear as the USB to the Body: Sensing and Health Insights26:18 Testing Sleep Tech in the Real World33:34 Firmware as the Real Product and Ozlo’s Update Strategy45:38 Moving Toward Medical: FDA and Software Therapies55:17 Customer Feedback at Scale and Prioritizing What MattersJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTube [ADD Playlist YT Link from here)⁠⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today's Coredump Session, François Baldassari and Chris Coleman sit down with Ultrahuman co-founder Vatsal Singhal to unpack what it takes to build and scale a hardware startup in the fiercely competitive health wearable market. From transitioning from software to hardware to building responsibly with AI and machine learning, Vatsal shares what it means to blend deep engineering rigor with a mission to improve human performance. This conversation explores the challenges, surprises, and future of health-tech innovation at the edge.Key TakeawaysHow Ultrahuman transitioned from a software-first mindset to mastering complex hardware development.Lessons learned moving from large-scale software systems to building precision-focused health wearables.Why building hardware for health requires a fundamentally different level of accountability and rigor.The role of machine learning at the edge and how it enables better, faster insights while managing battery and compute tradeoffs.How responsible use of AI in health applications shapes product design and user trust.The importance of rapid iteration cycles and adopting software methodologies in hardware innovation.Insights into how Ultrahuman’s internal teams use AI not just in engineering, but across all business functions.A look at what’s next for health-tech — and where innovation is heading in wearables and bio-sensing.Chapters:00:00 Intro & Teasers03:43 From Software to Hardware: The Leap of Faith07:49 The Harsh Realities of Hardware10:40 Iterating Fast Without Breaking People15:17 Redefining A/B Testing in Hardware21:40 Why Ultrahuman Built Its Own Factory26:56 Scaling Production Across Continents29:48 Managing Complexity: 20 Hardware Revisions in a Year35:08 Firmware Velocity & Observability with Memfault43:42 Health Tech Meets Regulation47:55 Shared Codebases & Fast Iteration Across Products50:39 Building the Machines That Build the Rings54:34 Responsible AI & The Future of Health Wearables56:35 Closing Reflections & Key TakeawaysJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTube Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today’s Coredump Session, we sit down with Nico Comier, CTO of reMarkable, to explore the journey from early-stage startup to global brand. Nico shares insights on scaling engineering teams, balancing technical credibility with leadership responsibilities, and what it really takes to bring a hardware product to market. From the pressures of product launches to the importance of customer connection, this conversation dives into the realities of building impactful technology.Key Takeaways:Nico Comier emphasizes the importance of customer impact in engineering roles.reMarkable's journey from startup to global brand involved scaling engineering teams.Cross-functional collaboration is key to successful product launches.Understanding customer needs is crucial for product development.reMarkable focuses on creating tools that help people think better.The Paper Pro Move was developed in response to user feedback.reMarkable values a hacker culture and allows device jailbreaking.Telemetry and customer feedback are vital for product improvement.reMarkable's leadership believes in maintaining technical credibility.Cross-functional teams enhance empathy and collaboration within organizations.Chapters:00:00 Introduction to reMarkable and Nico's Journey04:21 The Path to CTO: Insights and Experiences07:21 Technical Leadership and Staying Relevant10:03 Understanding Customer Needs in Tech Leadership13:00 The Launch of Paper Pro Move: A Major Achievement15:17 Preparing for Product Launch: Challenges and Strategies18:07 Balancing Agile and Waterfall in Product Development21:04 Product Decision-Making: Insights from the Paper Pro Move23:39 Navigating Challenges in Hardware Development26:30 Final Thoughts on Product Launch and Future Directions29:30 The Importance of Hypercare Post-Launch35:44 Scaling a Startup: Lessons Learned39:41 Building Cross-Functional Teams47:13 The Role of Firmware in Product Development50:48 Integrating Accessibility and Customer Feedback57:02 Leadership and Team Dynamics01:00:00 OutroJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTube Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today’s Coredump Session, we explore the rise of kids safe tech with leaders from the GABB team, creators of connected devices designed specifically for children. From designing products that prioritize child safety to integrating AI in ways that support families, this conversation unpacks the complexities of building secure, intuitive technology for the next generation. The team also shares real-world lessons on hardware partnerships, customer trust, and what it takes to innovate responsibly in the IoT space.Key Takeaways:Kids safe tech is an emerging category centered on digital safety for children.IoT connectivity is essential for building trust between parents and kids.Gabb’s mission is rooted in protecting families through intentional technology.Strong partnerships are critical to scaling hardware, firmware, and software development.AI enhances product safety by filtering content and flagging risks in real time.Security and data privacy are foundational to Gabb’s product design philosophy.Product development requires aligning launch timing, market needs, and platform strategy.Managing multiple product lines demands balance between innovation and sustainment.Kids often outpace parents in tech fluency—celebrating young users can inspire product direction.Efficient QA processes are necessary to uphold product quality and customer trust.Customer feedback and word of mouth are vital inputs for roadmap decisions.Data minimization is a core principle when designing for young users.Cross-functional collaboration drives more effective and family-first product development.Chapters:00:00 Episode Teasers & Intro04:46 Understanding Kids Safe Tech10:25 The Role of Partnerships in Product Development14:59 Navigating AI in Product Design20:20 Balancing Needs of Kids and Parents28:14 Ensuring Security in Kids Tech32:31 Celebrating Advocacy and Security Solutions33:45 Navigating Privacy in Child Analytics37:30 Product Development Cycle and Timelines41:31 Balancing Current and Future Product Development45:53 Sustaining Products Amid New Launches48:37 Customer-Centric Approach in Product Maintenance52:42 Firmware Versioning Challenges and StrategiesJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTube ⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠

In today’s Coredump Session, the team takes a hard look at why some IoT projects stall before they ever hit scale. From organizational missteps to product-market fit challenges, they explore the hidden forces that derail even technically sound products. You’ll hear candid insights on why being “connected” isn’t enough—and what it really takes to succeed in IoT today.Key TakeawaysThe biggest blockers for IoT teams aren’t always technical—they’re organizational, strategic, and systemic.Shipping a connected device doesn't guarantee product-market fit, especially if it's missing the right workflows or visibility.Engineers often build what's technically possible instead of what's valuable for the business.Collecting data from devices is table stakes—but what matters is how you use that data to drive action.Many teams lack a clear owner for post-deployment success, leading to blind spots in field performance.“Observability” should go beyond crash logs and include signals that help prioritize engineering work.Product-market fit isn’t static—it has to be reevaluated and maintained across the device lifecycle.Chapters:00:00 Introduction to IoT Challenges01:54 Afzal’s Journey in IoT & Early Expectations04:11 The 500K SIM Card Mirage08:10 Why IoT Projects Stall: Internal Resistance & Misaligned Incentives14:25 Rethinking the “IoT” Label: Lessons from Pebble17:28 When Good Tech Still Fails: The Organizational Blindspot20:43 Field Reality Check: Why Real-World Feedback is Critical26:00 Who Owns It? Accountability After Launch29:07 Designing for Fault Tolerance in Connected Devices32:52 Fragmentation in IoT: Meeting Diverse Customer Needs37:27 Niche Focus as a Winning Strategy39:57 What IoT Can Learn from AI’s Go-to-Market Playbook44:42 Drivers for Success in the IoT Space47:14 The Future of IoT: Regulation, Trust & E-Waste50:32 Final Reflections on Long-Term Ownership & Customer ImpactJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTube Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today's Coredump Session, we dive into the fascinating world of building Edge AI models that truly work in real-world environments. Joined by David Tischler, Developer Program Manager, and Alessandro Grande, Head of Product at Edge Impulse (A Qualcomm Company), we unpack what it takes to deploy AI on tiny devices, explore practical applications from wearables to industrial use cases, and discuss why customization, hardware choices, and continuous monitoring are critical for success. Tune in to explore how Edge AI is transforming device development and enabling smarter solutions.Key Takeaways:Edge AI empowers devices to process data locally, significantly reducing latency, bandwidth usage, and improving privacy.The best use cases for Edge AI today often involve video and audio analytics, wearables, and industrial sensor applications.Customization is the key value of AI, making it easy to fine-tune models for specific tasks or customer needs without extensive traditional coding.Effective Edge AI requires thoughtful pre-processing (DSP), not just AI models—this combination significantly improves model performance.Hardware selection is crucial; developers must balance model complexity with device constraints, such as available RAM and compute power.Many AI co-processors marketed for embedded systems today are essentially DSP units rebranded as AI accelerators, and usability matters more than raw performance.Observability and OTA (over-the-air) updates are critical components in Edge AI deployment, enabling continuous monitoring, data-driven refinements, and quick responses to issues in the field.Production readiness in Edge AI involves not only initial deployment but ongoing data collection, model retraining, and continuous improvement cycles.Chapters:00:00 Intro & Teasers: Edge AI's Real-World Promise01:57 Meet Our Guests: David Tischler & Alessandro Grande from Edge Impulse05:19 How Edge AI Took Off: From Hyped to Essential09:21 Beyond Voice Commands: Emerging AI Use Cases12:02 Defining the Edge: Wearables to Factories19:09 AI's Hidden Superpower: Customization and Fine-Tuning26:15 Why AI Belongs at the Edge: Latency, Privacy, and Power28:38 Building the Software Stack: Edge AI for Embedded Engineers34:17 Choosing Your Hardware: Constraints and AI Accelerators45:42 Observability and OTA Updates: Essential for Edge AI52:28 Audience Q&A: Fine-Tuning, TinyML, and the FutureJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTubeFollow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today's Coredump Session, we delve into the evolving landscape of cellular connectivity, particularly focusing on eSIM technology and its implications for IoT devices. The discussion features insights from industry experts on the challenges and opportunities presented by cellular connectivity, the cost considerations for device makers, and the technological advancements that are shaping the future of connectivity. Key themes include the vision behind Kigen, the role of SIM technology, emerging business models, and best practices for managing device connectivity and profiles. Key TakeawaysCellular connectivity is essential for modern IoT devices.Kigen aims to secure trillions of connected devices.Cost reduction in cellular modules opens new opportunities.Device makers must consider the total cost of ownership.Emerging business models include rental and subscription services.iSIM technology is gaining traction in the market.Device management and profile updates are critical for success.Security by design is a priority for device manufacturers.Interoperability between eSIM products is improving.Chapters00:00 Intro & Teasers03:54 The Vision Behind Kigen06:36 Challenges and Opportunities in Connectivity09:09 Cost Considerations in Cellular Technology12:01 Innovative Business Models for Device Makers14:46 Understanding SIM Technology17:22 The Future of iSIM and SoftSIM20:19 Global Considerations for Cellular Products30:25 Navigating IoT Network Choices33:41 Choosing the Right Cellular Technology36:56 Understanding eSIM and Network Management42:05 Optimizing Device Connectivity and Provisioning47:43 Key Considerations for New Device Makers54:42 OutroJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTubeFollow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today's Coredump Session, François and Chris share a major milestone in Memfault’s journey: Memfault is joining forces with Nordic Semiconductor. They’re joined by Kjetil Holstad from Nordic to explore Nordic’s history, how the acquisition came to be, and the exciting future they envision together. Along the way, they dive into the evolution of Bluetooth, the challenges of building complex embedded systems, and why developer experience is at the heart of it all.Key Takeaways:Nordic Semiconductor’s journey from design services to global Bluetooth leadership hinged on bold bets and developer-centric decisions.The inclusion of Bluetooth Low Energy in the iPhone was a pivotal moment that accelerated Nordic’s growth.Building robust embedded systems today requires deep attention to software complexity, which has significantly increased over time.Decisions that prioritize developer experience—like open documentation and accessible SDKs—have been instrumental to Nordic’s success.Memfault’s partnership with Nordic was driven by a shared vision to make embedded observability easy, accessible, and deeply integrated.Memfault’s pre-integration with Nordic’s SDKs and their collaborative engineering work have helped reduce barriers for developers.The vision for a “chip-to-cloud” platform is about delivering seamless device management, monitoring, and OTA updates with a scalable, unified solution.Both Memfault and Nordic are committed to supporting non-Nordic hardware, focusing on building solutions that serve the broader embedded ecosystem.Chapters:00:00 Episode Teasers & Intro02:59 The Origin Story of Nordic Semiconductor06:11 The Evolution of Bluetooth Technology at Nordic09:40 Bold Decisions and Learning from the Market14:24 Nordic's Commitment to Developers and Software17:32 The Shift Towards Software in IoT20:04 Embracing Complexity: The Future of Nordic's SDKs20:55 Understanding Trust Zone and Embedded Systems21:46 The Importance of Strategic Partnerships22:30 Building Relationships in the Tech Industry25:09 The Value of Collaboration and Integration27:38 Enhancing Developer Experience through Integration32:24 Announcing the Partnership and Future Vision33:07 Creating a Chip to Cloud Platform36:05 Supporting Non-Nordic Devices and Ecosystem Expansion39:10 Reactions to the Acquisition Announcement44:58 Q&AJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTubeFollow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today's Coredump Session, we explore the wild early days of Pebble and what it takes to scale a hardware startup against industry giants. From scrappy hackathons to 100+ person engineering teams, Kean Wong, former VP of Software at Pebble and now CTO at Igor, joins Memfault’s François and Chris to unpack how startups can outpace Big Tech by staying nimble, hiring wisely, and embracing constant change.Key Takeaways:Early-stage hardware startups benefit from direct engagement with developer communities for recruiting.Transparency and shared business context can create stronger, more motivated engineering teams.Scaling a hardware company requires embracing organizational change—not resisting it.“Trial by fire” can be an effective onboarding path for technical leaders in fast-moving environments.Engineering leadership should balance short-term firefighting with long-term vision setting.Hackathons and passion projects can be powerful hiring channels in embedded tech.Growth requires thoughtful infrastructure investments—even when it's tempting to keep things scrappy.A good leader earns respect by doing the hard work, not just delegating it.Chapters:00:00 Welcome and Introduction to Today’s Topic06:00 Lessons from Scaling Teams at Pebble12:00 Chaos, Structure, and Growing as a Startup18:00 Building Process Without Killing Agility24:00 Hiring Smart in Fast-Growth Environments30:00 From Product Complexity to Organizational Change36:00 Staying Productive Through Engineering Transitions42:00 Applying Startup Lessons in Larger Organizations48:00 What Kean’s Building Now at Eagor54:00 Live Q&A and Closing ThoughtsJoin the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTube ⁠⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today’s Coredump Session, we dive into the origins and evolution of Zephyr RTOS with Kate Stewart, VP of Dependable Embedded Systems at the Linux Foundation. From Intel’s early ambitions to a thriving global community, Kate unpacks how Zephyr grew into a leading open-source RTOS and what makes it uniquely resilient and developer-friendly. This conversation also explores the technical shifts shaping embedded development and how governance, safety, and collaboration continue to steer Zephyr’s trajectory.Speakers:Kate Stewart: Vice President of Dependable Embedded Systems, The Linux FoundationFrançois Baldassari: CEO & Founder, MemfaultThomas Sarlandie: Field CTO, MemfaultKey Takeaways:Zephyr was born from Intel’s desire for a scalable, secure, and open RTOS, evolving from Wind River roots.Early adoption of Linux-inspired practices, like Kconfig and "signed-off-by" contributions, lowered friction and encouraged community participation.The project’s governance model, emphasizing multi-vendor participation and elected leadership, prevents corporate capture and boosts resilience.Zephyr’s pragmatic reuse of tools like MCUboot accelerated development and expanded capabilities.Long-term support (LTS) releases—now extended to five years—make Zephyr production-friendly and aligned with regulatory demands like the CRA.Innovations like the Twister test framework and open testing infrastructure set Zephyr apart for visibility and maintainability.Zephyr thrives as complexity in embedded systems increases, filling the gap left by simpler RTOSes ill-suited for modern MCU workloads.Not every project is a fit for Zephyr—especially ultra-low-end 8-bit systems—but it excels in growing, connected device classes.Chapters:00:00 Introduction and Guest Introduction04:12 Building Zephyr: Intel’s Open RTOS Bet06:39 Governance That Guards Against Capture08:10 Borrowing From Linux, Avoiding Its Baggage09:41 What Makes Zephyr Different13:55 Zephyr in Production: LTS and Real-World Adoption16:15 Scaling with Twister and QEMU18:15 Taming Complexity Without Losing Performance35:45 SBOMs and the Future of Compliance38:20 A Head Start on Security Standards43:02 Inside Zephyr's Safety Certification Journey46:44 Real-World Use Cases and Industry Uptake50:25 What's Next for Zephyr and the RTOS Landscape53:12 Final Reflections and Closing Thoughts⁠⁠Join the Interrupt SlackWatch this episode on YouTube ⁠Suggest a Guest⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today's Coredump Session, we dive into the evolving landscape of IoT security regulations with Giovanni Alberto Falcione, CTO at Exine. From the impact of the EU's CRA to the complexities of OTA updates, Giovanni, François, and Thomas unpack what these new requirements mean for product engineers and how to navigate the increasingly stringent security landscape.Speakers:François Baldassari: CEO & Founder, MemfaultThomas Sarlandie: Field CTO, MemfaultGiovanni Alberto Falcione: CTO, ExeinKey Takeaways:The EU's Cyber Resilience Act (CRA) mandates stringent security measures for all connected devices marketed after December 2027, with a particular focus on runtime security monitoring.OTA updates are essential for mitigating vulnerabilities in the field but can also introduce challenges in regulatory compliance.Giovanni highlights that less than 1% of IoT device manufacturers actively monitor cybersecurity state awareness, a critical area of compliance under CRA.Implementing a Software Bill of Materials (SBOM) and tracking Common Vulnerabilities and Exposures (CVEs) are low-hanging fruit for product teams to start bolstering security.eBPF technology offers powerful, low-impact monitoring capabilities that can detect unauthorized activities at the syscall level without kernel-level intervention.Companies need to plan for at least five years of security updates under CRA, with potential for longer support based on device lifecycles.Even seemingly innocuous devices, like coffee makers, can pose significant cybersecurity risks as entry points for broader attacks.Giovanni emphasizes that while regulation can stifle innovation, it also raises the bar for security practices across the board.Chapters:00:00 Introduction and Guest Introduction02:30 The Unseen Costs of Cybersecurity Regulation04:40 OTA Updates: Security Savior or Hidden Risk07:21 CRA vs. Other Regulations: What Matters Most10:30 The Rise of Runtime Security Monitoring12:23 Why Manufacturers Are Freaking Out About CRA15:09 The Hidden Cost of Legacy Firmware17:30 Inside the Automotive Cybersecurity Playbook21:22 eBPF: The Next Frontier in IoT Security55:38 Coffee Machines, Coffee Attacks, and Unexpected Entry Points⁠⁠Join the Interrupt SlackWatch this episode on YouTube⁠Suggest a Guest⁠⁠⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today's Coredump Session, we dive into a wide-ranging conversation about the intersection of AI, open source, and embedded systems with the teams from Memfault and Goliath. From the evolution of AI at the edge to the emerging role of large language models (LLMs) in firmware development, the panel explores where innovation is happening today — and where expectations still outpace reality. Listen in as they untangle the practical, the possible, and the hype shaping the future of IoT devices. Speakers:François Baldassari: CEO & Founder, MemfaultThomas Sarlandie: Field CTO, MemfaultJonathan Beri: CEO & Founder, GoliothDan Mangum: CTO, GoliothKey Takeaways:AI has been quietly powering embedded devices for years, especially in edge applications like voice recognition and computer vision.The biggest gains in IoT today often come from cloud-based AI analytics, not necessarily from AI models running directly on devices.LLMs are reshaping firmware development workflows but are not yet widely adopted for production-grade embedded codebases.Use cases like audio and video processing have seen the fastest real-world adoption of AI at the edge.Caution is warranted when integrating AI into safety-critical systems, where determinism is crucial.Cloud-to-device AI models are becoming the go-to for fleet operations, anomaly detection, and predictive maintenance.Many promising LLM-based consumer products struggle because hardware constraints and cloud dependence create friction.The future of embedded AI may lie in hybrid architectures that balance on-device intelligence with cloud support.Chapters:00:00 Episode Teasers & Welcome01:10 Meet the Panel: Memfault x Golioth02:56 Why AI at the Edge Isn’t Actually New05:33 The Real Use Cases for AI in Embedded Devices08:07 How Much Chaos Are You Willing to Introduce?11:19 Edge AI vs. Cloud AI: Where It’s Working Today13:50 LLMs in Embedded: Promise vs. Reality17:16 Why Hardware Can’t Keep Up with AI’s Pace20:15 Building Unique Models When Public Datasets Fail36:14 Open Source’s Big Moment (and What Comes Next)42:49 Will AI Kill Open Source Contributions?49:30 How AI Could Change Software Supply Chains52:24 How to Stay Relevant as an Engineer in the AI Era⁠⁠Join the Interrupt SlackWatch this episode on YouTube⁠Suggest a Guest⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today’s Coredump Session, the team reunites to unpack the behind-the-scenes lessons from their time building firmware at Pebble. This episode dives into the risks, decisions, and sheer grit behind a near-disastrous OTA update—and the ingenious hack that saved a million smartwatches. It’s a candid look at the intersection of rapid development, firmware stability, and real-world consequences.Key Takeaways:Pebble’s open approach to developer access often came at the cost of security best practices, reflecting early startup trade-offs.A critical OTA update bug almost bricked Pebble devices—but the team recovered using a clever BLE-based stack hack.Lack of formal security measures at the time (e.g., unsigned firmware) unintentionally enabled recovery from a serious update failure.Static analysis and test automation became top priorities following the OTA scare to prevent repeat incidents.The story reveals how firmware constraints (like code size and inline functions) can lead to high-stakes bugs.Investing in robust release processes—including version-to-version OTA testing—proved vital.Real security risks included impersonation on e-commerce platforms and potential ransom via malicious OTA compromise.The importance of "hiring your hackers" was humorously noted as a de facto security strategy.Chapters:00:00 Episode Teasers & Welcome01:22 Why Pebble’s Firmware Was Open (and Unsigned)05:01 The Security Tradeoffs That Enabled Speed11:00 The OTA Bug That Could Have Bricked Everything15:26 Hacking Our Way Out with BLE Stack Overflow17:47 Lessons Learned: Test Automation & Static Analysis26:30 How Pebble Built a Developer Ecosystem29:56 CloudPebble, Watchface Generator & Developer Tools42:55 Backporting Pebble 3.0 to Legacy Hardware49:02 The Bootloader Rewrite & Other Wild Optimizations53:31 Simulators, Robot Arms & Debugging in CI56:40 Firmware Signing, Anti-Rollback & Secure Update1:06:10 Coding in Rust? What We’d Do Differently Today1:08:28 Where to Start with Open Source Pebble Development⁠⁠Join the Interrupt SlackWatch this episode on YouTube⁠Suggest a Guest⁠⁠⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today’s Coredump Session, we zoom in on the rapidly evolving world of cellular IoT—what’s working, what’s changing, and what developers should know. With expert insight from Fabien Korheim of ONES, the conversation breaks down MVNOs vs MNOs, dives into certification hurdles, explores connectivity trade-offs like NB-IoT vs LTE-M, and unpacks why cellular is quietly powering more devices than you think. Whether you're building metering devices or baby monitors, this one hits the full stack—from tech to business models.Key Takeaways:MVNOs simplify global IoT deployments by abstracting regional carrier relationships and reducing SKU complexity.LTE-M is currently the safest bet for low-power cellular applications, with 5G RedCap positioned as a future alternative.Certification processes are lighter with MVNOs, especially when using pre-approved modules.Cellular IoT is ideal where Wi-Fi isn’t guaranteed, like basements, forests, and mobile tracking.Consumer IoT has huge untapped potential—cellular can dramatically improve usability and reduce returns.Battery life and data costs are major design considerations, especially when scaling fleets globally.Multiradio devices and smart fallback strategies (e.g. BLE/Wi-Fi + Cellular) are becoming more common.Debugging tools and observability platforms are essential for maintaining reliability across networks, devices, and regions.Chapters:00:00 Episode Teasers & Intro02:34 MVNO vs MNO: What’s the Difference?06:28 Certifications, SIMs & Simplifying Deployment12:31 NB-IoT, LTE-M, LoRaWAN & Satellite—Explained23:43 5G for IoT: Hype or Here?27:14 Top Use Cases: Meters, Trackers & Wildlife33:28 The Big Opportunity: Cellular in Consumer Devices36:33 Business Models: Who Pays for Cellular?37:49 Getting Started: Kits, SIMs & Copy-Paste Firmware41:59 Common Mistakes & What to Watch in the Field47:15 What to Measure: Observability That Scales49:13 Q&A: Prioritization, Firmware Updates, RedCap & More⁠⁠Join the Interrupt SlackWatch this episode on YouTube ⁠Suggest a Guest⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today’s Coredump Session, we dive into the fast-evolving world of Edge AI and its real implications for device makers. From robots that detect humans to welding machines that hear errors, we explore the rise of intelligent features at the hardware level. The conversation spans practical tools, common developer traps, and why on-device AI might be the most underrated revolution in embedded systems today.Key Takeaways:Edge AI means real-time inference on embedded devices, not just “AI at the edge of the network.”Privacy, latency, and power efficiency are core reasons to use Edge AI over cloud processing.Hardware accelerators like the Cortex-M55 + U55 combo have unlocked GPU-like performance in microcontrollers.Battery-powered AI devices are not only possible—they're already shipping.Data collection and labeling are major bottlenecks, especially in real-world form factors.Start projects with data acquisition firmware and plan ahead for memory, power, and future use cases.Edge AI applications are expanding in healthcare, wearables, and consumer robotics.Business models are shifting, with AI driving recurring revenue and service-based offerings for hardware products.Chapters:00:00 Episode Teasers & Intro02:57 What Is Edge AI Anyway?06:42 Tiny Models, Tiny Devices, Big Impact10:15 The Hardware Leap: From M4 to M55 + U5515:21 Real-World Use Cases: From ECGs to Welding Bots17:47 Spec’ing Your Hardware for AI24:15 Firmware + Inference Frameworks: How It Actually Works26:07 Why Data Is the Hard Part34:21 Where Edge AI Will—and Won’t—Take Off First37:40 Hybrid Edge + Cloud Models40:38 Business Model Shifts: AI as a Service44:20 Live Q&A: Compatibility, Labeling, On-Device Training56:48 Final Advice: Think of AI as Part of the ProductJoin the Interrupt Slack⁠⁠⁠Watch this episode on YouTube⁠⁠Suggest a Guest⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

REGISTER FOR PART 2 OF THE PEBBLE CONVERSATION ON APRIL 15THIn this episode of Coredump, three former Pebble engineers reunite to dive deep into the technical quirks, philosophies, and brilliant hacks behind Pebble OS. From crashing on purpose to building a single codebase that powered every watch, they share war stories, bugs, and what made Pebble’s firmware both rare and remarkable. If you love embedded systems, software-forward thinking, or startup grit— this one’s for you.Key topics:Pebble intentionally crashed devices to collect core dumps and improve reliability.All Pebble devices ran on a single codebase, which simplified development and updates.The open-sourcing of Pebble OS is a rare opportunity to study real, commercial firmware.A platform mindset—supporting all devices and apps consistently—shaped major engineering decisions.Pebble’s app sandbox isolated bad code without crashing the OS, improving developer experience.The team built a custom NOR flash file system to overcome constraints in size and endurance.Core dumps and analytics were essential for tracking bugs, deadlocks, and field issues.Collaborations between hardware and firmware engineers led to better debugging tools and smoother development.Chapters:00:00 Episode Teasers & Intro01:10 Meet the Team: Pebble Engineers Reunite01:13 Meet the Hosts + Why Pebble Still Matters03:47 Why Open-Sourcing Pebble OS Is a Big Deal06:20 The Startup Firmware Mentality08:44 One OS, All Devices: Pebble’s Platform Bet12:30 App Compatibility and the KEMU Emulator14:51 Sandboxing, Syscalls, and Crashing with Grace20:25 Pebble File System: Built from Scratch (and Why)23:32 From Dumb to Smart: The Iterative Codebase Ethos26:09 Core Dumps: Crashing Is a Feature30:45 How Firmware Shaped Hardware Decisions33:56 Rust, Easter Eggs, and Favorite Bugs36:09 Wear-Level Failures, Security Exploits & Font Hacks39:42 Why We Chose WAF (and Regret Nothing?)42:41 What We’d Do Differently Next Time47:00 Final Q&A: Open Hardware, Protocols, and Part Two?Join the Interrupt Slack ⁠⁠⁠⁠Watch this episode on YouTube⁠Suggest a Guest⁠⁠⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today’s Coredump Session, the team dives deep into the world of over-the-air (OTA) updates—why they matter, how they break, and what it takes to get them right. From horror stories involving IR updates in a snowstorm to best practices for deploying secure firmware across medical devices, this conversation covers the full stack of OTA: device, cloud, process, and people. It's equal parts cautionary tale and technical masterclass.Key Takeaways:OTA is essential for modern hardware—without it, even small bugs can require massive field operations.Good OTA starts early, ideally at the product design and architecture phase.Bootloaders, memory maps, and security keys must be carefully planned to avoid long-term issues.Staged rollouts and cohorts help mitigate fleet-wide disasters.Signing keys and root certificates should be treated like firmware—versioned, updatable, and secure.Real-world constraints (medical, smart home, etc.) make OTA more complex—but not optional.Testing both the update and the update mechanism itself is critical before going live.When OTA fails, fallback plans (like dual banks or A/B slots) can be the difference between a patch and a catastrophe.Chapters:00:00 Episode Teasers & Intro03:29 Meet the Guests + OTA Gut Reactions05:33 Why OTA Is Non-Negotiable03:29 The OTA Wake-Up Call: Why You Need It09:31 Building OTA into Hardware from Day One16:49 Cloud-Side OTA: Cohorts, Load, and Timing21:53 OTA in Regulated Industries30:10 When OTA Breaks Itself34:44 Minimizing OTA Risk: The Defensive Playbook41:18 OTA and the Matter Standard47:17 Networking Stacks, Constraints, and Reliability51:11 Security, Scale, and the OTA Future⁠⁠⁠⁠Join the Interrupt SlackWatch this episode on YouTube ⁠Suggest a Guest⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website

In today’s Coredump Session, we unpack the full story of Bluetooth—from its PDA-era beginnings to its rising role in cloud-connected devices. With insights from Memfault’s Chris Coleman and François Baldassari, along with Blecon’s Simon Ford, this wide-ranging conversation explores how Bluetooth Low Energy has evolved, where it thrives (and doesn’t), and why it’s often the right tool, even if it’s not a perfect one. Expect history, hot takes, and practical guidance for building better Bluetooth-powered products.Key Takeaways:Bluetooth Low Energy (BLE) and Bluetooth Classic are fundamentally different—and BLE was never just a “lite” version.BLE's strength lies in its low power consumption and quick connection setup, making it ideal for peripheral devices that sleep most of the time.Use cases like audio, asset tracking, and cloud sync continue to shape BLE’s evolution, and new specs like LE Audio and PAwR are expanding its reach.Bluetooth wins not because it’s perfect—but because it’s practical: globally adopted, low-cost, and well-supported.Debugging Bluetooth at scale requires collecting connection parameters, analyzing retries, and understanding phone ecosystem quirks.BLE Mesh adoption has been underwhelming, with real-world complexity often outweighing its theoretical benefits.Expect to see BLE turn up in more places, including MEMS sensors and energy-harvesting devices, not just consumer gadgets.Designers should understand trade-offs in connection intervals, latency, and power draw when choosing Bluetooth for cloud or local connectivity.Chapters:00:00 Episode Teasers & Intro01:10 Meet the Guests: Bluetooth Roots at Pebble, Fitbit, and Blecon06:51 BLE’s Breakthrough: The iPhone 4S Moment10:22 BLE vs Classic: Why It Took Off14:39 Specs That Shifted Everything: Packet Length, Coded PHY & LE Audio21:41 Is BLE Still Interoperable? And Does It Matter?28:22 The BLE Cloud Puzzle: Gateways, Phones & Golden Gate38:40 BLE’s Sweet Spot: Power, Latency & When It Just Works47:12 Operating BLE Devices in the Wild: What to Track & Why57:40 Mesh Ambitions vs Reality⁠⁠Join the Interrupt SlackWatch this episode on YouTube⁠Suggest a Guest⁠Follow Memfault⁠⁠LinkedIn⁠⁠⁠⁠Bluesky⁠⁠⁠⁠Twitter⁠⁠Other ways to listen:⁠⁠Apple PodcastsiHeartRadio⁠⁠⁠⁠Amazon MusicGoodPodsCastbox⁠⁠⁠⁠Visit our website