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

The importance of MCU selection

After reading the title of this section, you might be asking yourself:

"Hey! I thought this was a book about how to program a microcontroller using an RTOS—what's all this about MCU selection? I'm a software developer!"

FreeRTOS is almost exclusively targeted at MCUs. It is primarily a scheduling kernel with a stable API, which makes it very well-suited to extremely low-level design. Unlike a full-blown CPU system with practically unlimited virtual addressing space and more clock cycles than you know what to do with, you're going to be working with a resource-constrained system. If you're developing firmware on this type of system, it means you're going to be much closer to the hardware than if you were writing software—which, in turn, means you're very likely going to be getting your hands very...