Zephyr and Trusted Execution Environments
summary
Zephyr implements ARMv8-M and v7-M trusted execution by integrating ARM Trusted Firmware (TF‑M) for secure/non‑secure partitions, using newer GCC with -mcmse (GCC 2017q4+) and a Zephyr SDK update, and generating matched secure and non‑secure layouts from a single device tree ranges file. Single‑core transitions are synchronous stubs that can block for seconds on slow boards; multi‑core uses OpenAMP IPC. Building requires a bootloader and a packaged dual‑image workflow that Zephyr aims to automate.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:41Agenda
- 1:39TEE for Microcontrollers
- 2:29Hardware Requirements
- 4:23ARMv8M Specific Hardware
- 6:20Zephyr Support for ARMVBM
- 10:06Zephyr and TFM Separation
- 13:12Single Core Implementation
- 15:06Multicore Implementation
- 16:09Multiple Image Complications
- 20:45Current Work Items
- 23:39Links to Resources
related talks
35mZephyr OS Memory Protection
16mTrusted RV: Trusted Execution Environment, Secure Coprocessor, and their Program...
18mZVM: Zephyr-based Virtual Machine
31mUsing Zephyr for Embedded Controllers- 35mZephyr OS Memory Protection
23mKeynote: Zephyr & IoT Security
27mvTZ: Virtualizing ARM TrustZone
41mTrusted Firmware M: Introduction