Trusted Firmware M : Trusted Boot
summary
TF‑M ships as a PSA-aligned prototype that boots via MCUboot used as BL2 bootloader and produces a single signed secure+nonsecure blob (ECDSA/RSA signatures, SHA/CMAC support). It implements dual-slot swapping with a scratch area and a two-phase, power-fail‑recoverable copy+swap; a post-boot self-test gates a rollback/fallback window. Experiments show position‑independent builds inflate MCUboot by ~9 KB; current release lacks a serial recovery console and key‑revocation is planned but not implemented; crypto accelerator offload is supported as a future build option.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:45Agenda
- 1:50Trusted Environment
- 4:01Trusted Boot
- 7:51High Level Requirement
- 8:45Boost Bootloader
- 18:34Memory Map
- 29:13Crash
- 31:58Threat Model
- 35:56Device Constraint
- 39:23Threads
- 43:09Image Swapping
- 46:13Alternative Solutions
- 48:56Position Independent Code
- 51:31Optional Config
- 53:56Hardware Accelerator
- 55:09Plans
- 56:38Questions
related talks
23mTrusted Firmware M – what’s cooking?
41mTrusted Firmware Project update
39mSecuring firmware: Secure and Trusted boot in OpenBMC
24mIntroduction to MCUboot: Secure Bootloader and Easy Firmware Updates
39mMCUboot: Multi-Image Support
39mTrusted Firmware M, Secure Partitioning – Compartmentalization in IoT
46mEnhancing System Security by Integrating Zephyr Bootloader and MCUboot
26mKeynote: Trusted Firmware – Build Security Collaboratively