Using FOSS as Part of a System Safety Mechanism
summary
Integrates ARM’s software test library via Trusted Firmware so tests run STL at EL3 rather than inside the kernel, invoked from Linux through a character device and SMC, with per-core user‑space test processes scheduled to meet a fault‑tolerance time interval. Uses STPA and the RAFIA workflow (risk analysis, fault injection, automation) to derive tests and evidence, and a deterministic construction service for reproducible builds and ISO 26262 tool qualification. Prototype runs on a Raspberry Pi 4 and highlights GPL vs commercial license friction, qualified‑tool issues, and pathways for system‑level certification.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:54Pauls background
- 3:19What is safety
- 3:43Safety mechanism
- 4:28What is safe
- 6:41Additional perceived challenges
- 7:44raffia
- 9:31Overview
- 10:29What is a Safety Test Library
- 12:10Technical Challenges
- 14:02Software License Restrictions
- 15:31Integrate STL with Linux
- 20:39Integrate into a reference system
- 22:32Safety related system
- 26:43Conclusion
related talks
25mBad Behaviour: Automating System-level Safety Testing Using Open Source Tools
40mBOF: Open Source Projects in Safety Critical Applications
13mJust how far can you go with FOSS?
32mDeveloping Open Source for Safety and Security
26mKeynote: Trusted Firmware – Build Security Collaboratively
22mFOSS as a lifestyle choice | Philosophical ideas
45mSafety Certifying an Open Source Project: The Example of Xen
34mOpen Source in Safety Critical Applications: the Next Frontier