A Maintainable, Scalable, and Verifiable SW Qualification Approach for Automotive in Linux
summary
Proposes a hybrid qualification approach that treats drivers or subsystems as ISO 26262 pre‑existing components (part 8.12) and verifies their integration with runtime verification monitors. Demonstrates on a telltale watchdog timeout use case: spec in enhanced kernel-doc + UML sequence diagram → automata → automata‑generated kernel monitors; a prototype runtime monitor generator and kernel interface is upstream‑patched, runs with low overhead, and detected mismatches live. Uses static analysis (CoreTree) and tracepoint baselines to build models.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:36Agenda
- 4:02Qualification of Pre-Existing Software Component
- 7:48Black Box Approach
- 12:05Implementation
- 22:31Telltale Use Case
- 25:50Communication Diagram
- 27:43Block Specification
- 29:50Integration Testing
- 30:46Runtime Verification
- 36:07Why Automata
- 42:34Communication Diagrams
- 45:30Question and Answer
related talks
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
45mLooking at Linux as a SEooC
42mNVIDIA's Approach for Achieving ASIL B Qualified Linux
08mWIP: QKSAN: Towards Multiple Sanitizers for In-vehicle COTS OS Kernels
38mSafe Systems with Linux
35mValidating Freedom From Interference in Automotive Linux