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

Chapter 5

  1. False. The ideal IDE will reflect personal/organizational preferences. A particular IDE that fits well into one team or workflow may not be suitable somewhere else.
  1. False. Many of the freely available IDEs are well suited for professional embedded system development.
  2. False. Vendor-supplied IDEs will often vary widely in their quality. Be careful of getting too tightly bound to a vendor's IDE, especially if you prefer to use MCUs from other vendors.
  3. False. At a minimum, we would expect software-generated code to be syntactically correct the first time. Beyond this, the code generation is only as good as the frontend supplying it, which tends to evolve more slowly than the underlying code bases (so you'll still need to write in customizations later on).
  4. False. The IDE for this book was selected based on cost and only considered compatibility with STM32 devices...