Using PMR in C++ Embedded Systems for Functional Safety
summary
Argues C++17 PMR lets safety-critical firmware use stdlib types by enforcing memory partitioning and predictable behavior: uses a 01 Heap allocator that is deliberately memory-inefficient but runs in constant time, maps functions to separate RAM/TCM regions plus a zero-copy DMA driver, demonstrates a string backed by DMA, and shows how partitioning limits out-of-memory interaction so timing and exhaustion become testable properties rather than unknowns.
AI-written summary · about
related talks
50mTwo advanced PMR techniques in C++17/20
55mC++ in the World of Embedded Systems
57mDynamic memory allocation challenges in safety critical systems
57mDeeply Embedded C++
01h 31mUsing C++14 in an Embedded “SuperLoop” Firmware
06mMy least favorite C++ feature
01h 38mEmbedded & C++
01h 01mMemory Safety: Rust vs. C
