Aligning Automotive Standards with Open Source Excellence
summary
Electrobit presents a practical path to qualify Linux for automotive: a QM Linux distro (about 70% feature reduction) running in three qualified VMs on the ID.3, produced with Canonical and verified via layered testing (Canonical CI, Electrobit reference tests, LTP, fuzzing). ASPICE is treated as an integration assessment (skipping unit-level SW design/testing) using ADRs and ISO 15288 decision flow, IEC 61508 mapping to SIL1, a frozen-kernel product model with occasional backports and a 15-year maintenance promise.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:04Automotive standards and open source
- 4:19Automotive architecture and Linux
- 10:02ASPice challenges with open source
- 12:30ASPice deviations and justification
- 17:25Solution approach and measures
- 19:56Future of mobility and open source
- 22:11Q&A: Kernel updates and vulnerabilities
- 24:23Q&A: ASPice tailoring and ISO 26262
- 28:17Q&A: Legacy OEMs and Linux
- 33:52Q&A: Open source collaboration
related talks
36mAligning Automotive Standards with Open Source Excellence
42mAccelerating Software Defined Vehicles Through Open Source Software
49mOpen Source in Every Car with Automotive Grade Linux
19mDriving Automotive with Open Source: From Compliance to Collaboration
37mBoF: Automotive Grade Linux Developer Community
39mPanel Discussion: Open Source as a Path for a Competitive Automotive Industry
15mLightning Talk: Lessons Learned From 10 Years of Automotive Grade Linux
35mAccelerating Software Defined Vehicles Through Open Source Software