The Spark Gap - Episode 4

The Spark Gap · 6 Jul 2014 · 26m

What this episode covers

Corey and Carl debate the merits of using Real-Time Operating Systems (RTOS) versus bare-metal firmware for single-core embedded systems. Carl argues that RTOS solutions like ChibiOS and FreeRTOS provide necessary abstraction for changing design requirements, efficient timer management, and interrupt handling, while Corey contends that bare-metal code offers lower latency, no licensing costs, and full control over platform-specific optimizations. They discuss specific RTOS implementations, licensing models like GPL, and the trade-offs between development time and hardware performance.

Mentioned

Products
STM Discovery board
Chips
STM32F4
Also
ChibiOS, FreeRTOS, MP Lab Harmony

Other shows on the same ground, closest first.

  • Embedded.fm · 59m

    307: Big While Loop

    Hosts Elecia White and Christopher White discuss the decision to use a real-time operating system (RTOS) on microcontrollers versus bare-metal programming. They define an RTOS as an application framework that simplifies task management, memory handling, and inter-thread communication, contrasting it with the 'big while loop' approach. The hosts outline specific scenarios where an RTOS is beneficial, such as handling TCP/IP, Bluetooth, complex displays, and file systems, while also addressing common concurrency issues like priority inversion, race conditions, and non-reentrancy.

  • The Amp Hour · 1h 25m

    Real Time Operating Systems with Brian Amos

    Chris Gammell, author of 'Hands-On RTOS with Microcontrollers', explains the practical application of Real-Time Operating Systems (RTOS) to host Brian Amos. They discuss when to use an RTOS versus a simple state machine or super loop, highlighting use cases like UI handling and complex communications. Gammell details how FreeRTOS manages task prioritization, memory segmentation, and inter-task communication using queues and semaphores. The conversation covers debugging strategies using tools like Segger Ozone and SystemView, and contrasts lightweight RTOS with full operating systems like Linux and Zephyr.

  • Oxide and Friends · 1h 06m

    The episode formerly known as ℔

    Bryan Cantrill, Adam Leventhal, and Laura Abbott of Oxide Computer Company discuss the development of Hubris, a microkernel operating system for embedded systems, emphasizing its correctness, lack of dynamic memory allocation, and use of Rust. The group traces the evolution of operating system concepts from the 1990s, including 'personalities' in Windows NT and the microkernel vs. monolithic debate, to modern containerization and embedded design. They detail specific engineering challenges in Hubris, such as stack overflow handling and memory protection, while also engaging in a broad discussion on Unix trivia, open-source maintenance, and accessibility technology.

  • Embedded.fm · 1h 10m

    248: I'm Not in Charge!

    Hosts Christopher White and Elecia White answer listener emails covering career transitions, tool selection, and embedded systems design. They discuss the value of generalist software experience for embedded roles, the importance of using established C++ safety standards like those from NASA and the F-35, and the practical benefits of tools like Beyond Compare and the Teensy Audio Library. The conversation also addresses the STEM vs. STEAM debate, the choice between bare-metal and RTOS for power efficiency, and the use of Tracery for generative art bots.

  • The Amp Hour · 1h 13m

    Focus, Dammit

    Dave Jones and Chris Gammell discuss the debate between being a generalist versus a specialist in engineering, using Zephyr RTOS as a case study for focused expertise. They analyze Jay Carlson's comprehensive guide on building embedded Linux systems and the strategic importance of component obsolescence management, citing Raspberry Pi's eight-year supply guarantees. The conversation also covers the challenges of remote work for hardware teams, the downsizing of commercial real estate, and Dave Jones's personal transition to a new home lab setup.

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.