Exploring the Potential of Zephyr in Automotive and Software Defined Vehicles
summary
More than 100 ECUs per car push Zephyr onto many Cortex‑M devices and standard peripherals (GPIO, I2C, UART) are already supported; POSIX on microcontrollers surprises automotive engineers and eases porting. CAN remains primary with 20 megabit single‑twisted‑pair links; Autosar compatibility, safety certification and process compliance are the real blockers. An Eclipse effort tries gRPC integration and hits limits, while an AVB (IEEE 1722) prototype with NXP hardware successfully demonstrates streaming between zone controllers, so low‑level drivers work but full Autosar app ports fail.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:50Zephyr in automotive
- 2:55Drivers for Zephyr
- 4:40Industry standards and challenges
- 6:25Benefits of Zephyr
- 7:07Zephyr capabilities and use cases
- 9:38Automotive interfaces in Zephyr
- 10:43Safety standards
- 11:26Comparison with AUTOSAR
- 13:58Migration to microprocessor
- 15:00Demo with Eclipse KUKSA
- 16:04Conclusion
related talks
31mOverview of CAN Subsystem in Zephyr
36mConnecting Zephyr Devices at Scale Using Open Source Solutions
40mZephyr Off-Chip Peripheral Emulation
01h 05mBoF: Unlocking Software Defined Power Electronics with Zephyr: Concepts...
30mZephyr Accelerates Tools for Testing External Display Support
35mEnd-to-end IoT Development with Zephyr
45mBluetooth Low Energy Controller in Zephyr OS
41mWhy Rust and Zephyr Are a Good Fit