English-language podcasts

Podcasts

The Embedded Frontier

An episode can be the start of a conversation. Explore recent releases, share your thoughts, and meet through a ThinkMatch Roundtable.

Ask friends about this

Episodes to discuss

The Embedded Frontier

#029 - How to Write Fast RTOS Code

35 min

Jacob Beningo talks with RTOS pioneer Bill Lamie, creator of Nucleus, ThreadX, and PX5 RTOS, about how to write efficient, high-performance real-time code. They cover POSIX pthreads, keeping software simple, RTOS benchmarking, test-driven development, using AI as a development teammate, and practical tips for structuring RTOS applications. Key Takeaways: • Keep it simple: complexity is the biggest enemy of embedded software, and a complex solution is probably not the right one. • Minimize nested function calls in critical paths, since pushing and popping registers and return addresses is expensive. • Design for performance from the start. Every comparison and data reference matters in the real-time path, and performance can't be bolted on at the end. • Use an error-checking veneer selectively. Enable it for new or untrusted code and call the direct API for proven code to save cycles. • Standardizing on the POSIX pthreads API makes it easier to share code between Linux and RTOS-based pr

Discuss this episode

The Embedded Frontier

#028 - From Coding Assistants to Autonomous Engineering

26 min

Jacob Beningo explores the shift from using AI as a coding assistant to agentic firmware development, where AI agents autonomously build, debug, test, and verify embedded systems. He shares a real experiment using an NXP MCX N947 board and an AI-written I2C driver. He also covers hardware safety guardrails, simulation, and how embedded engineers can evolve into systems engineers. Key Takeaways: • Most teams use AI only as a coding assistant. The bigger gains come from agentic workflows where AI builds, debugs, tests, and verifies firmware. • AI doesn't get firmware right on the first try, and neither do human engineers. It needs the ability to iterate, as with test-driven development. • Connecting an AI agent to real hardware or a simulator lets it observe results, find root causes, and fix problems instead of guessing. • In the I2C experiment, the agent correctly diagnosed a hardware problem (a backwards click board) that the engineer had wrongly blamed on the software. • Once the boa

Discuss this episode