Developing Open-Source Software RTOS with Functional Safety in Mind
summary
Zephyr is being prepared for functional safety by producing a long‑term branch and a separate auditable, certifiable codebase that freezes a small, well‑scoped feature set (kernel scheduler + core services) for certification rather than certifying tens of thousands of lines. CI already runs checkpatch and blocks violations, commercial MISRA/DRA scanners are used for analysis, and automation ties requirements to tests (examples: LDRA demos, Oxygen scripts). Targets include IEC 61508 and Common Criteria, seven architectures supported, and a few thousand PRs show current review cadence.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:50Open Source Software
- 4:23Safety Standards
- 5:51The Problem
- 6:58The Model
- 8:13Quality
- 9:59Requirements
- 11:00LDRA
- 13:18Misra
- 15:33Challenges with Misra
- 18:45Single point of exit
- 20:18No accountability
- 22:07How to approach certification
- 25:13Ideal project
- 27:19Regulating the bazaar
- 28:36How long does it take to merge
- 30:14Review burden
- 31:17Safe Artists
- 32:28The Zephyr Project
- 35:40Features for next year
- 36:07Limiting the scope
- 36:56Candidates targets
- 38:27Architecture
- 38:48Summary
- 41:02Questions
- 42:09Possible Solution
related talks
42mZephyr Functional Safety BOF
32mDeveloping Open Source for Safety and Security
53mBridging Safety and Architecture: Zephyr’s Path To IEC 61508 Complian...
41mTurning the Ignition on Safety: Zephyr RTOS in Automotive Compliance
55mZephyr: An Ideal Platform for Introducing Processes of Safety-Critical Embedded Systems
14mWhat is Zephyr and Where Is It Heading To?
50mZephyr Project: An RTOS to Change the Face of IoT
37mImplement Safety with a RTOS Running as a Linux Companion Within...