Why it exists
Developing all software on an ECU to ASIL D would be extremely expensive. Mixing ASIL D and QM software is only acceptable if the QM part provably cannot corrupt the ASIL part.
What kinds of interference exist
| Kind | Example | Typical mechanism |
|---|---|---|
| Spatial (memory) | QM code overwrites safety data | MPU/MMU, SMMU, separate OS applications |
| Temporal (timing) | QM task blocks the CPU | Timing protection, budgets, separate cores |
| Communication | Corrupted or delayed data between partitions | E2E protection, checked interfaces |
How it is implemented
On MCUs, the AUTOSAR OS separates software into OS applications with memory and timing protection. On HPCs, a hypervisor and the SoC’s SMMU and bandwidth controls isolate VMs; the safety island stays independent.
Best practices
- Minimise shared resources; document every remaining one.
- Verify isolation with fault injection tests.
Common pitfalls
- Forgetting shared caches, interrupts or DMA as interference paths.