Building a Safe and Open Vehicle Core With Open Source
summary
Safe Open Vehicle Core (S‑Core) builds a safety-certifiable middleware stack for high‑performance ECUs, targeting ISO 26262, ASPICE and ISO 21434 compliance and aiming for a 0.5 release by end of year that covers fixed execution order, IPC and logging. Development uses a docs-as-code with Sphinx-Needs, ReStructuredText, Bazel and PlantUML workflow, provides dev‑container reproducibility, supports C++ and Rust components, currently layers on QNX with POSIX compatibility, runs process audits toward certification evidence, and relies on a distributor model to package artifacts for OEM/tool qualification.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:11Shift left in automotive software
- 8:10Project status and contributions
- 12:27Architectural blocks and components
- 15:34Certification alignment
- 19:09Contribution process and community
- 24:43Q&A on education and infrastructure
- 31:48Rust vs C++ discussion
- 32:51Infotainment integration
- 34:34Closing remarks
related talks
32mDeveloping Open Source for Safety and Security
16mAutomotive Solution Empowered by RISC-V Based Security and Functional Safety Module
36mAligning Automotive Standards with Open Source Excellence
33mU-Boot in the Fast Lane: Developing a Safety Test Framework for Automotive Applicati...
35mOpen Sesame! Why Functional Safety is the Master Key to Open the Door for Linux into Automotive
44mThe Road to Safety Certification: How the Xen Project is Making Progress within the Auto Industry
38mZephyr: Learnings From Working on Safety Certification in the Open
32mDeveloping Open Source for Safety and Security