How To Accelerate Software Defined Vehicle(SDV) With OSS
summary
Honda builds an in‑house IVI team that begins with two people and scales into regional software centers, uses AOSP and OSS plus SPDX Lite and achieves OpenChain self‑certification to raise the starting point. Architecture consolidates many functions into a central ECU (supports 32+ speakers) and targets a Type‑1 hypervisor stack with a Zen hypervisor POC on GitHub. Integration pain points include lifecycle mismatches (Linux kernel EOLs vs AOSP timelines) and over 2000+ repos modified for BOMs and updates.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:09Honda’s software culture
- 9:07What is SDV
- 11:54SDV system components
- 14:27SDV architecture challenges
- 25:55SDV challenges with OSS
- 30:55Critical OSS for SDV
- 37:32Linux kernel and SDV security
- 40:08OSS BOM and collaboration
- 43:00SDV future with OSS
- 45:36Q&A: Third-party apps
related talks
05mKeynote: Honda’s OSPO Challenge: Accelerating Strategic Collaboration for Softwar...
22mSteering into Tomorrow: Embracing Software-Defined Vehicle in an Open-Source Appro...
42mAccelerating Software Defined Vehicles Through Open Source Software
41mHow Did You Cook It? About Honda’s AOSP-Based IVI (in-Vehicle Infotainment) System
35mAccelerating Software Defined Vehicles Through Open Source Software
30mSoftware-Defined Vehicles and FOSS
39mPanel Discussion: Open Source as a Path for a Competitive Automotive Industry
19mKeynote: Accelerating Software Defined Vehicles through Open Source