Unlocking the Power of POSIX Support in Zephyr RTOS
summary
Zephyr RTOS implements POSIX support since version 1.9 (2017) but not complete PSE profiles; expect supported APIs, gaps, and implementation quirks. Examples: POSIX since 1.9 and a previously integrated civetweb removed in 3.2 show real-world adoption and churn. Tooling and limits matter: use of native_posix host mode for testing, C library mismatches (newlib/neolib choices), tradeoffs between static allocation and optional dynamic allocation, and a CoreMark port that uses pthreads for SMP scaling to demonstrate performance impact.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:15Features overview
- 3:48Architecture
- 4:49Basic facts about POSIX
- 7:58POSIX in the context of embedded systems
- 10:53POSIX.13 Realtime and Embedded Application Support
- 14:59History of POSIX support in Zephyr RTOS
- 16:44POSIX in Zephyr RTOS
- 20:23Limitations and differences from traditional POSIX
- 28:50Civet Web: Complex application on top of Zephyr RTOS
- 34:00CoreMark Pro: Integrate with Zephyr build system
- 36:33CoreMark Pro: execute "core" benchmark
related talks
35mMulti-core Application Development with Zephyr RTOS- 35mMulti-core Application Development with Zephyr RTOS
36mLTSv3 POSIX Roadmap Update
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
40mOptimizing Zephyr for Peak Performance
48mPower Management Challenges in IoT and How Zephyr RTOS Meets Them
05mZephyr
27mZephyr RTOS as a role model in the operating systems theory education