Zephyr Functional Safety BOF
summary
Zephyr narrows certification to a kernel-only scope plus unavoidable kernel-adjacent code and aims to deliver a safety element with a safety manual and traceable evidence for IEC 61508 SIL3 (optionally ISO 26262 ASIL D via a contracted agency); work includes writing requirements in a GitHub requirements repo, CI-integrated static analyzers, a concept approval from TUS suit, a safety FAQ, biweekly calls and Discord, compiler support tied to a GCC12 SDK with GCC14/LLVM coming, and an end-to-end process target toward certificate by 2026.
AI-written summary · about
chapters (21)
- 0:00Zephyr Safety BOF intro
- 1:04Safety certification scope
- 3:14Safety element out of context
- 4:37Compliance process progress
- 6:24Safety working group setup
- 7:30Coding standards & static analysis
- 8:12Certification status & next steps
- 9:36Q&A
- 10:18Compiler & MCDC concerns
- 15:13Scope clarity & extensions
- 16:40Sustainability & maintainers
- 20:13Kernel impact on apps
- 21:58Coverage for simple app
- 26:13Tools qualification limits
- 27:14User space integration
- 29:43User space & mixed criticality
- 32:35Automotive tool alignment
- 34:21Compiler qualification
- 37:14Call for contributions
- 38:59Integrator needs & timeline
- 40:46Community involvement
related talks
55mZephyr: An Ideal Platform for Introducing Processes of Safety-Critical Embedded Systems
48mDeveloping Open-Source Software RTOS with Functional Safety in Mind
48mDeveloping Open-Source Software RTOS with Functional Safety in Mind
41mTurning the Ignition on Safety: Zephyr RTOS in Automotive Compliance
14mWhat is Zephyr and Where Is It Heading To?
32mDeveloping Open Source for Safety and Security
20mOpen Source Safety Elements - Out of Context?
09mInto & Kick-off