Hardware Podcasts

114: Wild While Loops

Embedded.fm · 19 Aug 2015 · 1h 27m

What this episode covers

Andrei Chichak, a systems developer at CBF Systems Inc., joins hosts Alicia White and Christopher White to discuss error handling strategies in embedded systems. They cover the importance of early logging, checking return codes, using asserts for development, and designing user-facing error messages that account for the end-user's context. The conversation also touches on hardware-software collaboration, watchdog timers, and the social experiment of Hitchbot.

Most relevant to

early-stage companies

Topics

Mentioned

Companies
CBF Systems Inc., Ryerson Polytechnic, McMaster University, Clever Script, JDS Uniphase, Leapfrog
Products
Hitchbot, Windows 10, Making Embedded Systems, Kindness of Strangers, Therac-25, Challenger

Related episodes from other shows

Other shows on the same ground, closest first.

  • The Pragmatic Embedded Podcast · 39m

    Christmas Special

    Hosts Jeff Gable and Luca share war stories from their careers in embedded systems, highlighting the pain of manual testing in helicopter avionics, the chaos of managing requirements with Word and Excel in Dropbox for medical devices, and the technical debt of massive #ifdef blocks in legacy machine tool software. They discuss the industry's slow adoption of modern software practices like version control and CI/CD, contrasting embedded development with web development standards. The episode concludes with book recommendations including 'The Phoenix Project' and 'Team Topologies', and reflections on the future of IoT security and agile adoption in hardware.

    Debugging & failure analysisEmbedded firmware
    6 chapters

  • The Pragmatic Embedded Podcast · 30m

    Testing on the Host vs Target

    Jeff Gable and Luca discuss the strategy of testing embedded software on the host machine versus the target hardware, arguing that host testing catches the majority of bugs while target testing is reserved for hardware-specific interactions. They introduce architectural patterns like the Model-Hardware-Controller (MHC) and the Data Model pattern to decouple business logic from hardware, enabling effective unit testing. The conversation also covers handling resource-constrained systems by optimizing last and using special integration tests to uncover low-level bugs like interrupt priority issues.

    Embedded firmwareDebugging & failure analysis
    6 chapters

  • The Pragmatic Embedded Podcast · 50m

    Agile at Growing Hardware Startups with Matt Cole

    Matt Cole, Director of Embedded Systems at Rise Robotics and formerly of Super Pedestrian, explains how he applied agile principles to embedded software development at a growing hardware startup. He details the challenges of integrating firmware updates for e-scooters, managing parallel hardware and software teams, and navigating supply chain crises that forced reactive engineering. Cole emphasizes the importance of treating the engineering team as a customer to improve tooling and process efficiency while maintaining safety and quality.

    Embedded firmwareScaling production
    7 chapters

  • The Pragmatic Embedded Podcast · 1h 02m

    The Three Ways of DevOps

    Jeff Gable and Luca engineer discuss applying Gene Kim's Three Ways of DevOps to embedded systems development. They cover increasing flow through value stream analysis, amplifying feedback loops via continuous integration and field diagnostics, and fostering a culture of continuous improvement and safe experimentation. The hosts emphasize that these principles help embedded teams avoid silos, reduce cycle times, and build higher quality products by shifting left and learning from failures.

    Leadership, teams & cultureScaling production
    10 chapters

  • The Pragmatic Embedded Podcast · 43m

    Build Pipelines Revisited

    Hosts Jeff Gable and Luca Jani revisit build pipelines for embedded systems, advising teams to start with command-line builds and immediate failure notifications. They recommend adding static analysis and unit tests to enforce coding standards, arguing that automation saves time on trivial debates like brace styles. The discussion extends to tracking metrics via dashboards and integrating target hardware testing to ensure deployment scripts remain valid. Finally, they highlight pitfalls such as ignoring pipeline failures or embedding business logic directly into the CI configuration.

    Embedded firmwareDebugging & failure analysis
    8 chapters

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