F3 · Mission-Critical & Auto
Open AD Kit 2.0: Safety Isolation
Overview
Across two Arm Neoverse instances, this guide deploys an Open AD Kit simulation environment and connects safety-critical and non-safety-critical workloads via DDS/ROS 2, building a safety-island software-isolation prototype. The workflow separates services of different criticality into independent execution environments and validates an architectural approach to cross-instance communication, interface boundaries and fault isolation. This reference architecture chains ISO 26262-oriented design thinking, cloud simulation and open in-vehicle middleware, letting teams discuss and track the safety boundary before production hardware.
Scope of verification
- It is an automotive safety-isolation reference workflow on two Arm-based Linux instances, validating software partitioning, DDS/ROS 2 communication and the safety-island architecture concept.
- Dependencies include two interoperable Arm64 Linux environments, Open AD Kit, a matching ROS 2/DDS configuration and networking that supports cross-instance simulation and data exchange.
- Scope centers on architecture and a software-isolation prototype; it does not cover a hardware safety island, fault injection, real-time guarantees, ASIL decomposition, ISO 26262 certification or a production in-vehicle safety case.
Canonical source: https://learn.arm.com/learning-paths/automotive/openadkit2_safetyisolation/
This page is a guided summary with boundary notes, not an official reproduction.
This page is a guided summary with boundary notes, not an official reproduction.