Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

These FAQs were 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
?
Do I need an AM62L EVM to follow this Learning Path?
No. You can use QEMU without hardware. If you have an AM62L EVM, follow its target-specific setup and boot-media instructions instead.
Do I need to patch the U-Boot source to add the trusted key?
No. You’ll generate a public-key node in signature.dtsi and include it when you build U-Boot. For the AM62L EVM, use CONFIG_DEVICE_TREE_INCLUDES. For QEMU, add the node to the control device tree supplied with EXT_DTB. You don’t need to change the U-Boot source files.
How can I check the signed FIT before booting the target?
Use the U-Boot fit_check_sign tool with your signed FIT and built u-boot.dtb. This checks the FIT against the public key in the control device tree before you prepare the boot media.
How do I confirm that verification succeeded on the target?
Look for sha256,rsa2048:key-a+ OK in the U-Boot output, followed by the Zephyr image A banner. You can also run the optional wrong-key and tampered-image tests to check that U-Boot refuses to start either image.
Does this setup authenticate U-Boot as well as Zephyr?
No. In QEMU, you’ll run U-Boot without an earlier stage that authenticates it. On the AM62L EVM, you’ll leave the device in High Security, Field Securable (HS-FS) development state, where earlier stages accept boot files signed with any key. To extend trust to U-Boot in production, you need to provision your key, move the device to High Security, Security Enforced (HS-SE), and sign the earlier boot files.

Share

Tell others about this Learning Path.

Back
Return to Embedded and Microcontrollers