Bridging Safety and Architecture: Zephyr’s Path To IEC 61508 Complian...
summary
Project pursues IEC 61508 certification for Zephyr by isolating a safety scope of about 15,000 lines of kernel code in scope, establishing a safety committee and working group, and securing budget for TÜV assessment. Concrete work includes a subset of MISRA coding guidelines, static analysis integrations (eclair and cppcheck), and a safety manual with assumptions and traceability mechanisms under development. Build specifics matter: Kconfig and CMake with in-tree code generation create verification and integration challenges and a plan targets SIL3‑level reasoning and audit evidence.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:18Zephyr’s safety gaps
- 6:46Functional safety standards
- 12:44Architecture for safety
- 15:57Hazards to design
- 21:18Compliance scope
- 25:17Open-source certification challenges
- 33:43Documenting safety decisions
- 37:41Progress and outlook
- 43:29Interdependent safety architectures
- 44:40Q&A
related talks
37mTools and Methodologies to Test Compliance with IEC61508 Standard
40mHow I Fell in Love with Zephyr – a System Architect’s Tale
40m9 Years in the Making, the Story of Zephyr, Starting with Commit Nr. 1
41mIs Linux Kernel Development Good Enough to Make Your Life Depend on It?
32mBoF: Quality and Testing Processes for Zephyr + Discussion
32mArchitecting an IoT Product Line: Part 1 - Scoping
20mSafety Processes
01h 05mBoF: Unlocking Software Defined Power Electronics with Zephyr: Concepts...