Book Image

Hands-On RTOS with Microcontrollers

By : Brian Amos
Book Image

Hands-On RTOS with Microcontrollers

By: Brian Amos

Overview of this book

A real-time operating system (RTOS) is used to develop systems that respond to events within strict timelines. Real-time embedded systems have applications in various industries, from automotive and aerospace through to laboratory test equipment and consumer electronics. These systems provide consistent and reliable timing and are designed to run without intervention for years. This microcontrollers book starts by introducing you to the concept of RTOS and compares some other alternative methods for achieving real-time performance. Once you've understood the fundamentals, such as tasks, queues, mutexes, and semaphores, you'll learn what to look for when selecting a microcontroller and development environment. By working through examples that use an STM32F7 Nucleo board, the STM32CubeIDE, and SEGGER debug tools, including SEGGER J-Link, Ozone, and SystemView, you'll gain an understanding of preemptive scheduling policies and task communication. The book will then help you develop highly efficient low-level drivers and analyze their real-time performance and CPU utilization. Finally, you'll cover tips for troubleshooting and be able to take your new-found skills to the next level. By the end of this book, you'll have built on your embedded system skills and will be able to create real-time systems using microcontrollers and FreeRTOS.
Table of Contents (24 chapters)
1
Section 1: Introduction and RTOS Concepts
5
Section 2: Toolchain Setup
9
Section 3: RTOS Application Examples
13
Section 4: Advanced RTOS Techniques

Chapter 10

  1. Interrupt-driven drivers are more complex because there are at least three pieces of code involved (setup code, ISR code, and callback code). With a polled driver, all of this happens serially.
  2. False. Only functions ending in FromISR may be called within an ISR.
  3. False. Interrupts take precedence over the scheduler since the scheduler should be configured to run from the lowest priority interrupt.
  4. DMA – it uses hardware to transfer data between peripherals and memory, without any CPU intervention.
  5. Direct Memory Access.
  6. Attempting to receive data at any point in time is very difficult to do well with a raw buffer. Raw buffers can also become a bit complex when receiving data of unknown length.