Using Zephyr for Embedded Controllers
summary
Zephyr replaces the legacy EC across Chromebook designs with concrete results: functional ports on Intel, Qualcomm and Mediatek chipsets, board bring-up completed on four projects, and power and image-size targets met. Qualification uses hardware-free driver emulators, integration suites and public GitLab runs; USB‑C PD stack and a state‑machine library go upstream. Configuration moves to kconfig/device tree and build uses west/zmake; migration uses a shim layer translating APIs so existing tooling keeps working; hardware needs remain 512 kilobytes flash 64 kilobytes SRAM 48 MHz core and power <10 mW sleep.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:52Chromebook block diagram (simplified)
- 2:36Embedded Controller Overview
- 16:24Hardware Based Qualification
- 23:07Questions?
related talks
27mZephyr and Trusted Execution Environments
23mKeynote: Zephyr & IoT Security
27mZephyr and Trusted Execution Environments
33mZephyr‑Based VIRTIO Backend on Xen: Toward Open Source Functional Safety
05mZephyr
16mDesigning Secure Systems for CRA Compliance leveraging Zephyr
18mZVM: Zephyr-based Virtual Machine
40mZephyr Project Security Status