Resolve and standardize early access to hardware for automotive industry with Linux
summary
Linux cannot meet automotive early-KPI needs so OEMs offload boot-time tasks to MCU firmware; the result is cost, fragmentation and non‑Linux friendly designs. The proposed path is an open, safety‑qualified boot and late‑attach model: make SPL/SBL/U-Boot artifacts certifiable with MISRA/LDRA safety checks, run early DMA/I2C configuration and network bring‑up in a multi-threaded bootloader, and publish tests and requirements via Basil/LAVA. Targets are concrete: 500 msec audio, glass‑to‑glass camera in 500 msec, display needles in 1000 msec, CAN in 100 msec, Ethernet wake 150 msec, then form a consortium (ELISA/Linux groups).
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 7:47Automotive challenges with Linux adoption
- 12:23Bootloader standardization for automotive
- 15:18Early peripheral configuration in bootloader
- 18:32Power management in automotive Linux
- 22:32Network and peripheral early access
- 25:27Safety certification for open source
- 31:47Certification levels and requirements
- 37:13Open source collaboration and next steps
- 40:24Q&A and closing remarks
related talks
42mBooting Automotive ECUs Really Fast with Modern Security Features
49mOpen Source in Every Car with Automotive Grade Linux
36mBoF: Automotive Grade Linux Developer Community
26mLinux in Cars: So What?
49mOpen Source in Every Car with Automotive Grade Linux
35mMake Your System Firmware Faster, More Flexible and Reliable with LinuxBoot
33mUsing Open Source Software to Build an Industrial-grade Embedded Linux Platform...
39m“Early Boot and Late Attach” of Remote Processor...