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)
Section 1: Introduction and RTOS Concepts
Section 2: Toolchain Setup
Section 3: RTOS Application Examples
Section 4: Advanced RTOS Techniques

Understanding generic RTOS APIs

An RTOS API defines the programming interface that the user interacts with when using the RTOS. Native APIs expose all of the RTOS's functionality. So far in this book, we've been using the native FreeRTOS API only. This was done to make it easier to search for help for a given function and to rule out any possibility of a poorly behaving wrapper layer between FreeRTOS and a generic API. However, this is not the only API option for FreeRTOS. There are also generic APIs available that can be used to interface with the RTOS functionality – but instead of being tied to a specific RTOS, they can be used across multiple operating systems.

These generic APIs are usually implemented as a wrapper layer above the native RTOS API (the exception to this is RTX, which has only the CMSIS-RTOS API). Here we can see where a typical API would...