Certifying OxidOS for ISO26262 ASIL-D
summary
OxidOS aims for ISO 26262 ASIL‑D out‑of‑context certification but starts with QM; the team certifies one frozen Tock version, builds an OxidOS simulator for testing, and uses Sphinx‑needs plus custom scripts and carod to extract requirements from Rust code into documentation. Major constraints are legacy ASPICE expectations, no off‑the‑shelf Rust certification tools, vendoring crypto and avoiding crates, and a troubling reality that any safety stamp binds to a specific version — the plan is automated change detection that maps code diffs to impacted requirements.
AI-written summary · about
chapters (8)
- 0:00Introduction and overview
- 1:11OxidOS platform overview
- 2:42ISO 26262 and ASIL standards
- 6:30Overcoming legacy challenges
- 8:20Tools and workflow innovation
- 9:42Team culture and motivation
- 10:50Future plans and automation
- 12:28Q&A and closing remarks
related talks
31mValidating Rust for industry: Certification meets formal analysis
26mFerrocene - qualifying the Rust compiler using a fully open source tool stack
10mSponsored Talk
56mRust for Foundation Software
56mRust for Safe and Scalable Automotive: Insights from
46mPanel: Rust in Safety Critical
07mLightning Talk: “How Rust Is Steering Automotive Software Toward Safety”
51mPete LeVasseur, Lead, Safety-Critical Rust Consortium [Rust Project Content