Book Image

Embedded Programming with Modern C++ Cookbook

By : Igor Viarheichyk
Book Image

Embedded Programming with Modern C++ Cookbook

By: Igor Viarheichyk

Overview of this book

Developing applications for embedded systems may seem like a daunting task as developers face challenges related to limited memory, high power consumption, and maintaining real-time responses. This book is a collection of practical examples to explain how to develop applications for embedded boards and overcome the challenges that you may encounter while developing. The book will start with an introduction to embedded systems and how to set up the development environment. By teaching you to build your first embedded application, the book will help you progress from the basics to more complex concepts, such as debugging, logging, and profiling. Moving ahead, you will learn how to use specialized memory and custom allocators. From here, you will delve into recipes that will teach you how to work with the C++ memory model, atomic variables, and synchronization. The book will then take you through recipes on inter-process communication, data serialization, and timers. Finally, you will cover topics such as error handling and guidelines for real-time systems and safety-critical systems. By the end of this book, you will have become proficient in building robust and secure embedded applications with C++.
Table of Contents (17 chapters)

Guidelines for Real-Time Systems

Real-time systems are a class of embedded systems where the time of reaction is critical. The consequences of not reacting in time vary between different applications. Based on severity, real-time systems are classified as follows:

  • Hard real time: Missing a deadline is not acceptable and considered a system failure. These are usually mission-critical systems in airplanes, cars, and power plants.
  • Firm real time: Missing a deadline is acceptable in rare cases. The usefulness of the result is zero after the deadline. Think about a live streaming service. A video frame delivered too late can only be discarded. This is tolerable provided it happens infrequently.
  • Soft real time: Missing a deadline is acceptable. The usefulness of results degrades after the deadline, causing degradation of the overall quality, and should be avoided. Such an example is...