Hardware Podcasts

211: 4 weeks, 3 days (Repeat)

Embedded.fm · 31 Jan 2020 · 1h 19m · Episode 211

What this episode covers

Dennis Jackson, Director of Firmware at Element Science, discusses the career path from software to embedded systems, emphasizing that practical projects and understanding core software principles are more valuable than specific hardware knowledge for entry-level roles. He advises aspiring engineers to start with cheap development boards like STM32 Discovery boards to write simple drivers, rather than relying on high-level abstractions like Arduino. Jackson also stresses the importance of adopting professional software engineering practices, such as command-line builds with Make, continuous integration, and unit testing, to ensure code quality and reliability in production environments.

Most relevant to

early-stage companies

Topics

Mentioned

Companies
Element Science, Airware
Products
STM32 Discovery Board, Arduino, Test Driven Development in Embedded C, Making Embedded Systems
Tools
Jenkins, Make, Lint

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 · 36m

    How to Get Started

    Jeff Gable and Luca Ingianni discuss how engineering teams can transition from traditional methods to agile development in embedded systems. They outline a three-layered approach starting with tactical technical practices like version control and continuous integration to establish reliable feedback loops. The conversation emphasizes using these quick wins to build trust and demonstrate value before expanding into project management practices like sprints and user stories, ultimately aiming to improve team culture and product quality.

    Embedded firmwareCareers & education
    5 chapters

  • The Amp Hour · 2h 13m

    Embedded Linux with Jay Carlson

    Jay Carlson, an embedded Linux expert and PhD student, discusses his comprehensive guide to building embedded Linux systems, detailing the process of designing and testing 10 different boards to demonstrate the steps. He explains the transition from bare-metal microcontroller development to embedded Linux, emphasizing that Linux development involves reading and configuring source code rather than writing it from scratch, and highlights the importance of using build systems like Buildroot. Carlson advises engineers to start with simple, low-cost processors like the Allwinner A33 or V3S, arguing that modern embedded Linux is accessible to hobbyists and small teams if they leverage existing mainline kernel support and dev configs.

    Embedded firmwareMicrocontrollers & dev platforms
    13 chapters

  • The Pragmatic Embedded Podcast · 36m

    Development is Better when it's Test-Driven

    Jeff Gable, an embedded software consultant, explains his practice of Test-Driven Development (TDD) to host Luca Ingianni, arguing that writing failing unit tests before application code forces good architecture and high coverage. Gable details how this discipline decouples embedded application logic from hardware-specific drivers, allowing tests to run on the host machine for rapid feedback rather than slow target flashing. He addresses the common industry resistance to TDD in embedded systems, citing the initial learning curve and the need for coaching, while recommending resources like the 'Throw the Switch' video courses and tools such as Unity, CMock, and Ceedling. The conversation concludes by framing TDD as an artistic craft of storytelling through code, emphasizing that the practice builds confidence and prevents regressions in production-quality software.

    Embedded firmwareDebugging & failure analysis
    9 chapters

  • The Amp Hour · 1h 18m

    Why isn't this working?

    Chris Gammell, founder of Contextual Electronics, explains his transition from hardware consulting to learning embedded firmware to stabilize his income. He details his personal project involving an STM32F030 and a 433MHz transmitter, highlighting the steep learning curve of moving from Arduino to bare-metal C development. Gammell and guests Elecia White and Dave Jones discuss the importance of hiring tutors, using build logs for debugging, and the specific frustrations of dealing with obscure Chinese components and complex microcontroller peripherals like SPI displays and I2S audio.

    Embedded firmwareDebugging & failure analysis
    10 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.