Requirements of Embedded Programming

Bjarne Stroustrup’s FAQ makes it crystal clear. One of the design goals for C++11 was to make C++ even better for the embedded world.

Or to say it in the words of Bjarne Stroustrup, inventor of C++: “Improve performance and ability to work directly with hardware — make C++ even better for embedded systems programming and high-performance computation.”

I reasoned a lot about this sentence because I changed from software development in the middleware area into the embedded world. I was responsible for the software on defibrillators. So I started my search for the kind of features in C++11 that are particularly well suited for embedded programming. I presented my search results at conferences in Berlin, Munich, and Sindelfingen.

In the meantime, my perception of the new features as user-defined literals, the type-traits library, or constant expressions has changed a lot. They are such great features that they belong in the toolbox of each professional C++ developer. This statement is even more true for the embedded world because they have to deal with stronger requirements. Therefore, the posts about “Embedded programming with C++” are particularly valuable in embedded programming.

What’s the reason for my perception? The answer is simple. There is no typical embedded system. The diversity is large. There is RFID transponder about the size of a few millimeters, pacemakers that should work reliably for a longer period, defibrillators consisting of a few boards and even more CPUs that wait years for their application, or cars having more the 100 electronic control units (ECUs). The borders between the embedded systems and other systems as game development or low-level systems, are blurred.

Modernes C++ Mentoring

"Fundamentals for C++ Professionals" (open)

"Design Patterns and Architectural Patterns with C++" (open)

"C++20: Get the Details" (open)

"Concurrency with Modern C++" (open)

"Generic Programming (Templates) with C++": October 2024

"Embedded Programming with Modern C++": October 2024

"Clean Code: Best Practices for Modern C++": March 2025

Do you want to stay informed: Subscribe.

What makes embedded programming unique? Embedded programming is the more intensive programming. More intensive because it has to deal with strong requirements:

High-performance requirements up to real-time requirements
Safety-critical systems
Reduced resources such as memory and CPU power
More Tasks that should be accomplished in parallel

I had a long fight on how to present the features in a structured way. In addition, the features are often dependent on the C++ standard. Here is my plan. The features are the answers to typical requirements in embedded programming. The requirements are the key points of my structure.

High safety requirements
Performance matters
Careful handling of resources

Additionally, I will provide information on which C++ standard you can use for this feature.

What’s next?

Before I start with the posts about embedded programming, I have to make a short detour. In my profession as a software developer, I heard a lot of myths about C++. I will present them in the next post and provide the facts.

Post Views: 3,945

Thanks a lot to my Patreon Supporters: Matt Braun, Roman Postanciuc, Tobias Zindl, G Prvulovic, Reinhold Dröge, Abernitzke, Frank Grimm, Sakib, Broeserl, António Pina, Sergey Agafyin, Андрей Бурмистров, Jake, GS, Lawton Shoemake, Jozo Leko, John Breland, Venkat Nandam, Jose Francisco, Douglas Tinkham, Kuchlong Kuchlong, Robert Blanch, Truels Wissneth, Mario Luoni, Friedrich Huber, lennonli, Pramod Tikare Muralidhara, Peter Ware, Daniel Hufschläger, Alessandro Pezzato, Bob Perry, Satish Vangipuram, Andi Ireland, Richard Ohnemus, Michael Dunsky, Leo Goodstadt, John Wiederhirn, Yacob Cohen-Arazi, Florian Tischler, Robin Furness, Michael Young, Holger Detering, Bernd Mühlhaus, Stephen Kelley, Kyle Dean, Tusar Palauri, Juan Dent, George Liao, Daniel Ceperley, Jon T Hess, Stephen Totten, Wolfgang Fütterer, Matthias Grün, Phillip Diekmann, Ben Atakora, Ann Shatoff, Rob North, Bhavith C Achar, Marco Parri Empoli, Philipp Lenk, Charles-Jianye Chen, Keith Jeffery, Matt Godbolt, and Honey Sukesan.

Thanks, in particular, to Jon Hess, Lakshman, Christian Wittenhorst, Sherhy Pyton, Dendi Suhubdy, Sudhakar Belagurusamy, Richard Sargeant, Rusty Fleming, John Nebel, Mipko, Alicja Kaminska, Slavko Radman, and David Poole.

My special thanks to Embarcadero
My special thanks to PVS-Studio
My special thanks to Tipi.build
My special thanks to Take Up Code
My special thanks to SHAVEDYAKS