Zephyr and Trusted Execution Environments
summary
Describes concrete Zephyr work: adds ARMv8-M and ARMv7-M trusted execution support by integrating ARM Trusted Firmware (TFM), generating paired secure and non‑secure images, and using a single DTS with device tree ranges to emit coherent address maps. Notes tool gaps — Zephyr SDK lacks an M-Profile SE compiler so external toolchains are required — and runtime issues: SVC-style transitions use secure/non-secure callable region stubs that are blocking synchronous calls (seconds-long on slow boards). Targets multi-core via OpenAMP and aims for a seamless make-based build that packages Zephyr + TFM.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:43Agenda and trusted execution basics
- 2:31Core goals of TEEs
- 4:18ARM TrustZone requirements
- 6:27Zephyr and TrustZone
- 9:22Secure image creation
- 10:29PSA levels and separation
- 13:17Context switch mechanics
- 15:23Multi-core IPC
- 16:33Bootloader challenges
- 19:46Device tree secure mapping
- 20:51Work items and plans
- 23:38PSA docs and threat modeling
- 25:00Q&A
related talks
27mZephyr Porting Efforts in High Performance SoCs
33mZephyr Support for Heterogeneous SoCs
49mThe Zephyr™ Project – An Updated Overview
27mvTZ: Virtualizing ARM TrustZone
41mTrusted Firmware M: Introduction
16mTrusted RV: Trusted Execution Environment, Secure Coprocessor, and their Program...
55mZephyr: An Ideal Platform for Introducing Processes of Safety-Critical Embedded Systems
10mLightning Talk: Using Zephyr to Power the Sustainable Cloud