C++ on small micro controllers
summary
Programs target tiny MCUs — 4 KB and even 20 bytes — with constraints driving choices: prefer templates and compile‑time computation to generate only needed code, use static classes and global allocation not globals so RAM is known at link time, avoid heap, exceptions and virtual dispatch to guarantee predictable worst‑case timing, skip heavyweight STL and floating‑point libraries, measure worst‑case not average, consider link‑time sizing checks and permissive licenses (Boost/BSD) for reuse.
AI-written summary · about
chapters (12)
- 0:00Microcontroller programming intro
- 2:52Embedded constraints
- 9:05Desktop vs embedded dev
- 16:15Small MCU programming
- 21:27Standard libraries issues
- 27:21Heap allocation vs real-time
- 30:56Exceptions in real-time
- 36:52Optimizing virtual functions
- 40:12Memory efficiency
- 43:33Licensing and code reuse for small microcontrollers
- 47:34Stack size prediction
- 49:20Summary best practices
related talks
01h 00mModern C++: C++ Patterns to Make Embedded Programming More Productive
55mC++ in the World of Embedded Systems
49mCost of C++ Abstractions in C++ Embedded Systems
01h 30mC++ in Constrained Environments
01h 38mEmbedded & C++
01h 00mBuilding Effective Embedded Systems in C++: Architectural Best Practices
39mErlang on Microcontrollers: The Research Continues
59mHow to understand modern C++ features in practice? Let's create a compiler!