The Spark Gap - Episode 19

The Spark Gap · 22 Oct 2014 · 34m

What this episode covers

Hosts Carl and Corey discuss the architectural trade-offs of placing intelligence in embedded firmware versus host software. They analyze factors such as performance determinism, development speed, security risks, and the user experience of updates, citing Tesla's over-the-air updates as a key example of successful software-driven functionality changes.

Most relevant to

makers and hobbyists

Topics

Mentioned

Companies
Tesla, Hackaday, Kickstarter
Products
Arduino Fermata, Google Chrome, Steam Greenlight

Other shows on the same ground, closest first.

  • Coredump Sessions · 55m

    #019: END-OF-YEAR CELEBRATION: Moments You Loved, Stories You Missed, and 2026 Predictions You Need

    François Baldassari and Chris Coleman, co-founders of Memfault, reflect on the 20th episode of Coredump Sessions, highlighting lessons from guests like Nick Sinas of Oval, Dan Mangum of Golioth, and Chad from Gabb. They discuss the critical importance of Over-the-Air (OTA) updates, the rise of AI-assisted firmware development using tools like Claude and Cursor, and the evolving security landscape for devices from Pebble to modern smart rings. The hosts predict that 2026 will see OTA become a regulatory requirement and AI offload processing to the edge, while emphasizing the need for engineers to adapt to higher-level abstractions.

  • The Pragmatic Embedded Podcast · 40m

    Does DevOps Make Sense for Embedded Systems?

    Jeff Gable and Luca Engeni discuss why DevOps and Agile principles are essential for embedded systems, particularly in safety-critical industries like medical devices and aerospace. They argue that while hardware iteration is slower than software, fixed cadences for PCB releases can still accelerate feedback loops. The conversation highlights the shift toward over-the-air updates, using Tesla as a case study for the new safety challenges introduced by connected vehicles.

  • Embedded.fm · 1h 12m

    390: Irresponsible At the Time

    Tyler Hoffman, co-founder of Memfault, discusses the challenges of managing firmware updates, device diagnostics, and remote monitoring for millions of IoT devices. He draws on his experience at Pebble and Fitbit to explain why existing cloud platforms are often unsuitable for resource-constrained embedded systems, highlighting the need for secure boot, staged rollouts, and efficient heartbeat reporting. Hoffman details how Memfault’s platform helps engineers detect crashes, track battery life trends, and prioritize bugs by aggregating data from large device fleets. The conversation emphasizes the importance of defensive programming and building robust OTA systems to prevent bricking devices at scale.

  • The Amp Hour · 1h 15m

    The Endless Y2K

    Dave Jones of EEVblog discusses the final stages of his 121 GW multimeter, specifically the decision to use an SD card for firmware updates instead of Bluetooth due to reliability and bootloader complexity. Chris Gammell of Contextual Electronics shares his experience hand-assembling 0402 components and advocates for KiCad's OpenGL rendering mode for PCB design. The hosts also debate the industry's reliance on always-connected IoT devices, citing the WPA2 vulnerability and Tesla's Powerwall, before touching on CircuitPython and the future of embedded development.

  • Coredump Sessions · 57m

    #002: The secrets to building secure & scalable OTA infrastructure with Nick Sinas

    Nick Sinas, CTO at Oval, and Chris Coleman, CTO at Memfault, discuss the critical importance of Over-the-Air (OTA) updates for connected devices, emphasizing that OTA must be designed into the hardware architecture from day one. They detail the technical requirements for secure, scalable OTA systems, including bootloader design, memory management, and cloud-side cohort rollouts to mitigate fleet-wide risks. The conversation highlights real-world failures, such as breaking future update capabilities due to stack overflow fixes, and stresses the need for rigorous testing, security best practices like signing keys, and fallback mechanisms like dual-bank architectures.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by The Spark Gap. The episode itself belongs to its publisher.