Real Time Operating Systems with Brian Amos

The Amp Hour · 14 Mar 2022 · 1h 25m · Episode 581

What this episode covers

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.

Mentioned

Companies
Mouser, Digi-Key
Products
Hands-On RTOS with Microcontrollers, Nucleo F7
Chips
STM32
Tools
Segger Ozone, SystemView, Persefio Tracelizer, J-Link, ST-Link
Also
FreeRTOS, Zephyr, TinyOS, Contiki, Nessie

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 Spark Gap · 26m

    The Spark Gap - Episode 4

    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.

  • Embedded.fm · 1h 09m

    401: Oil and Water

    Miro Samek, founder of Quantum Leaps, discusses his 'Modern Embedded Systems Programming' YouTube series and the QP framework, explaining why event-driven state machines and active objects are superior to traditional RTOS usage for hard real-time systems. He details the architectural pitfalls of mixing blocking and non-blocking paradigms, advocating for strict separation to avoid race conditions and priority inversion. Samek also explains the business model of selling commercial licenses for QP to companies that cannot use its GPL open-source version, while providing free educational content to build trust and community.

  • Embedded.fm · 1h 15m

    175: How Hard Could It Be?

    Jean Labrosse, founder of Micrium (now part of Silicon Labs) and author of the uC/OS real-time operating system, explains the origins of his software, which began after his team encountered a bug in a commercial RTOS that the vendor refused to fix. He details the technical challenges of building a robust kernel, including handling race conditions, priority inversion, and stack overflows, and discusses the importance of clean code and certification for medical and avionics applications. Labrosse also advocates for using commercial RTOS support over free alternatives like FreeRTOS, arguing that the 'free puppy' analogy highlights the hidden costs of maintenance and debugging time.

  • The Pragmatic Embedded Podcast · 56m

    Modern Embedded Systems Programming with Miro Samek

    Miro Samek, founder and CEO of Quantum Leaps, explains why traditional embedded architectures like superloops and RTOS lead to 'spaghetti code' and concurrency bugs, advocating instead for event-driven active objects and hierarchical state machines. He details how this approach eliminates race conditions and mutexes by enforcing a 'no sharing' principle, thereby improving testability and development velocity. Samek also discusses the importance of using lightweight modeling tools to generate code from state diagrams, ensuring the model remains the source of truth in an agile workflow.

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