Insights Into the Safe Open Source Vehicle Core Project for SDV
summary
Code-first middleware for software-defined vehicles that targets ISO 26262, ASPICE and ISO 21434 compliance for upper layers rather than the OS, developed by 30+ contributors from 8+ companies. Uses a docs-as-code workflow with sphinx-needs, Bazel, PlantUML, CI pipelines, VS Code dev containers, C++ and Rust. Current artifacts (FO model, IPC, logging, persistency) populate a ~43-repo monorepo and are staged for a 0.5 certifiable component release by year end; tooling builds are reproducible though some repos still need stabilizing.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:04Speaker and project
- 3:09Motivation for Eclipse SDV
- 5:19Shift left approach
- 8:13Eclipse SDV stack
- 9:16Timeline and releases
- 11:43Progress and transparency
- 13:27Contributors and community
- 15:35Process and maturity
- 17:20V-model integration
- 21:10Contribution process
- 22:54Project structure
- 24:18Build tooling challenges
- 25:43Resources and channels
- 27:07Getting started
- 29:14Integration with existing automotive stacks
- 33:17Safety analysis
- 35:01Collaboration with Automotive Grade Linux
- 39:13Future scope and MCUs
- 42:05Virtual ECUs
- 43:09Q&A
related talks
22mSteering into Tomorrow: Embracing Software-Defined Vehicle in an Open-Source Appro...
18mSoftware Defined Vehicle - from Hype to Reality
34mSDV What's Happened since Last Year?
17mperspective on automotive software and Eclipse SDV
19mDriving Automotive with Open Source: From Compliance to Collaboration
30mSoftware-Defined Vehicles and FOSS
17mKeynote: AGL SoDeV: Leading the Software Defined Vehicles Revolution
10mSoftware Defined Vehicle WG Introduction