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 memory allocation

Memory allocation isn't necessarily at the top of a developer's list of favorite topics to consider when developing an application—it just isn't all that glamorous. Dynamic allocation of memory—that is, allocating memory as it is needed rather than at the beginning of the program—is the norm. With desktop-oriented development, memory is generally available whenever it is needed, so it isn't given a second thought; it is simply a malloc call away. When it is finished, it will be unallocated with free.

Unlike the carefree dynamic memory allocation schemes in a desktop environment, programmers of deeply embedded systems that use MCUs will often need to be more careful about how (and if) memory is dynamically allocated. In an embedded system, regulatory, RAM, and timing constraints can all play a role in whether...