Who is this for?

This is an advanced topic for embedded developers who boot Zephyr from U-Boot on an Arm Cortex-A processor and want U-Boot to verify the Zephyr image before starting it.

What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

  • Identify where U-Boot verifies Zephyr in the Arm Cortex-A boot chain.
  • Build and sign a Flattened Image Tree (FIT) containing Zephyr, and embed the public key in U-Boot without changing its source.
  • Configure U-Boot to verify Zephyr before booting, and optionally test rejection of wrong-key and tampered images.
  • Identify the verification boundary in QEMU and on a development board, and how fusing your key extends trust in production.

Prerequisites

Before starting, you'll need the following prerequisites:

  • One of two targets - QEMU, which needs no hardware, or a Texas Instruments (TI) AM62L EVM with accessories to power it, write an SD card, and attach a serial console
  • A Linux host running Ubuntu 22.04 or 24.04, with about 20 GB of free disk space; QEMU runs on x86_64 or arm64, while the AM62L EVM needs x86_64 for the TI SDK
  • Visual Studio Code with the Workbench for Zephyr extension installed
  • Basic knowledge of U-Boot and the Linux command line

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll build a Zephyr image for Arm Cortex-A and configure U-Boot to verify its signed FIT before booting. After choosing QEMU or a TI AM62L evaluation module (EVM), you’ll set up the host tools, build Zephyr, sign the FIT, and embed the trusted public key in U-Boot. You’ll then boot the image, optionally test rejection of untrusted or tampered images, and examine what remains outside the verification boundary.
Next