Developing Open-Source Software RTOS with Functional Safety in Mind
summary
Zephyr adopts a dual-track: keep an open bazaar for innovation while creating an LTS auditable branch that freezes a small kernel + core services and goes through certification. CI already runs checkpatch and static scans, documentation and traceability with Doxygen link requirements → tests → results, and the plan targets IEC 61508 and Common Criteria. Challenges include MISRA rule deviations, reviewer bottlenecks, and a rough industry estimate of $150–200 per line of certified code.
AI-written summary · about
chapters (11)
- 0:00Zephyr and functional safety
- 4:34Open-source in safety-critical
- 9:37Quality for functional safety
- 13:11MISRA C rules implications
- 18:46MISRA C controversies and reviews
- 22:01Adoption barriers and accountability
- 26:24Certification development models
- 32:03Zephyr’s current goals
- 35:39Zephyr’s safety and security 2024
- 39:12Adoption via quality and governance
- 41:23Q&A
related talks
32mDeveloping Open Source for Safety and Security
42mZephyr Functional Safety BOF
50mZephyr Project: An RTOS to Change the Face of IoT
53mBridging Safety and Architecture: Zephyr’s Path To IEC 61508 Complian...
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
14mWhat is Zephyr and Where Is It Heading To?
41mTurning the Ignition on Safety: Zephyr RTOS in Automotive Compliance
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS