1
0
mirror of https://git.yoctoproject.org/poky synced 2026-06-01 13:09:50 +00:00

ref-manual: uboot-sign: Add how to enable ATF, TEE and User defined snippet ITS for U-Boot FIT image

Add how to enable ATF, TEE and User defined ITS for U-Boot FIT image generation.

(From yocto-docs rev: ee6b3698da044e290dbc4fbb852f3cc37638e689)

Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Jamin Lin
2025-03-18 11:10:40 +08:00
committed by Richard Purdie
parent 869c4f3adb
commit 3bc048c01a
2 changed files with 151 additions and 0 deletions
+13
View File
@@ -3401,6 +3401,19 @@ The variables used by this class are:
- :term:`UBOOT_FITIMAGE_ENABLE`: enable the generation of a U-Boot FIT image. - :term:`UBOOT_FITIMAGE_ENABLE`: enable the generation of a U-Boot FIT image.
- :term:`UBOOT_MKIMAGE_DTCOPTS`: DTC options for U-Boot ``mkimage`` when - :term:`UBOOT_MKIMAGE_DTCOPTS`: DTC options for U-Boot ``mkimage`` when
rebuilding the FIT image containing the kernel. rebuilding the FIT image containing the kernel.
- :term:`UBOOT_FIT_ARM_TRUSTED_FIRMWARE`: include the Trusted Firmware-A
(TF-A) binary in the U-Boot FIT image.
- :term:`UBOOT_FIT_ARM_TRUSTED_FIRMWARE_IMAGE`: specifies the path to the
Trusted Firmware-A (TF-A) binary.
- :term:`UBOOT_FIT_TEE`: include the Trusted Execution Environment (TEE)
binary in the U-Boot FIT image.
- :term:`UBOOT_FIT_TEE_IMAGE`: specifies the path to the Trusted Execution
Environment (TEE) binary.
- :term:`UBOOT_FIT_USER_SETTINGS`: adds a user-specific snippet to the U-Boot
Image Tree Source (ITS). Users can include their custom U-Boot Image Tree
Source (ITS) snippet in this variable.
- :term:`UBOOT_FIT_CONF_USER_LOADABLES`: adds one or more user-defined images
to the ``loadables`` property of the configuration node.
See U-Boot's documentation for details about `verified boot See U-Boot's documentation for details about `verified boot
<https://source.denx.de/u-boot/u-boot/-/blob/master/doc/uImage.FIT/verified-boot.txt>`__ <https://source.denx.de/u-boot/u-boot/-/blob/master/doc/uImage.FIT/verified-boot.txt>`__
+138
View File
@@ -9971,6 +9971,45 @@ system and gives an overview of their function and contents.
See `more details about #address-cells <https://elinux.org/Device_Tree_Usage#How_Addressing_Works>`__. See `more details about #address-cells <https://elinux.org/Device_Tree_Usage#How_Addressing_Works>`__.
:term:`UBOOT_FIT_ARM_TRUSTED_FIRMWARE`
`Trusted Firmware-A (TF-A) <https://www.trustedfirmware.org/projects/tf-a>`__
is a reference implementation of secure world software for Arm A-Profile
architectures (Armv8-A and Armv7-A), including an Exception Level 3 (EL3)
Secure Monitor. This variable enables the generation of a U-Boot FIT
image with a Trusted Firmware-A (TF-A) binary.
Its default value is "0", so set it to "1" to enable this functionality::
UBOOT_FIT_ARM_TRUSTED_FIRMWARE = "1"
:term:`UBOOT_FIT_ARM_TRUSTED_FIRMWARE_IMAGE`
Specifies the path to the Trusted Firmware-A (TF-A) binary. Its default
value is "bl31.bin"::
UBOOT_FIT_ARM_TRUSTED_FIRMWARE_IMAGE ?= "bl31.bin"
If a relative path is provided, the file is expected to be relative to
U-Boot's :term:`B` directory. An absolute path can be provided too,
e.g.::
UBOOT_FIT_ARM_TRUSTED_FIRMWARE_IMAGE ?= "${DEPLOY_DIR_IMAGE}/bl31.bin"
If the Trusted Firmware-A (TF-A) binary is built in a separate recipe,
you must add the necessary dependency in a U-Boot ``.bbappend`` file. The
recipe name for Trusted Firmware-A (TF-A) binary is
``trusted-firmware-a``, which comes from the
:yocto_git:`meta-arm </meta-arm>` layer::
do_compile[depends] += "trusted-firmware-a:do_deploy"
:term:`UBOOT_FIT_CONF_USER_LOADABLES`
Adds one or more user-defined images to the ``loadables`` property of the
configuration node of the U-Boot Image Tree Source (ITS). This variable
is handled by the local shell in the recipe so appropriate escaping
should be done, e.g. escaping quotes.::
UBOOT_FIT_CONF_USER_LOADABLES = '\"fwa\", \"fwb\"'
:term:`UBOOT_FIT_DESC` :term:`UBOOT_FIT_DESC`
Specifies the description string encoded into a U-Boot fitImage. The default Specifies the description string encoded into a U-Boot fitImage. The default
value is set by the :ref:`ref-classes-uboot-sign` class as follows:: value is set by the :ref:`ref-classes-uboot-sign` class as follows::
@@ -10019,6 +10058,105 @@ system and gives an overview of their function and contents.
of bits. The default value for this variable is set to "2048" of bits. The default value for this variable is set to "2048"
by the :ref:`ref-classes-uboot-sign` class. by the :ref:`ref-classes-uboot-sign` class.
:term:`UBOOT_FIT_TEE`
A Trusted Execution Environment (TEE) is a secure environment for
executing code, ensuring high levels of trust in asset management within
the surrounding system. This variable enables the generation of a U-Boot
FIT image with a Trusted Execution Environment (TEE) binary.
Its default value is "0", so set it to "1" to enable this functionality::
UBOOT_FIT_TEE = "1"
:term:`UBOOT_FIT_TEE_IMAGE`
Specifies the path to the Trusted Execution Environment (TEE) binary. Its
default value is "tee-raw.bin"::
UBOOT_FIT_TEE_IMAGE ?= "tee-raw.bin"
If a relative path is provided, the file is expected to be relative to
U-Boot's :term:`B` directory. An absolute path can be provided too,
e.g.::
UBOOT_FIT_TEE_IMAGE ?= "${DEPLOY_DIR_IMAGE}/tee-raw.bin"
If the Trusted Execution Environment (TEE) binary is built in a separate
recipe, you must add the necessary dependency in a U-Boot ``.bbappend``
file. The recipe name for Trusted Execution Environment (TEE) binary is
``optee-os``, which comes from the :yocto_git:`meta-arm </meta-arm>`
layer::
do_compile[depends] += "optee-os:do_deploy"
:term:`UBOOT_FIT_USER_SETTINGS`
Add a user-specific snippet to the U-Boot Image Tree Source (ITS). This
variable allows the user to add one or more user-defined ``/images`` node
to the U-Boot Image Tree Source (ITS). For more details, please refer to
https://fitspec.osfw.foundation/\ .
The original content of the U-Boot Image Tree Source (ITS) is as
follows::
images {
uboot {
description = "U-Boot image";
data = /incbin/("u-boot-nodtb.bin");
type = "standalone";
os = "u-boot";
arch = "";
compression = "none";
load = <0x80000000>;
entry = <0x80000000>;
};
};
Users can include their custom ITS snippet in this variable, e.g.::
UBOOT_FIT_FWA_ITS = '\
fwa {\n\
description = \"FW A\";\n\
data = /incbin/(\"fwa.bin\");\n\
type = \"firmware\";\n\
arch = \"\";\n\
os = \"\";\n\
load = <0xb2000000>;\n\
entry = <0xb2000000>;\n\
compression = \"none\";\n\
};\n\
'
UBOOT_FIT_USER_SETTINGS = "${UBOOT_FIT_FWA_ITS}"
This variable is handled by the local shell in the recipe so appropriate
escaping should be done, e.g. escaping quotes and adding newlines with
``\n``.
The generated content of the U-Boot Image Tree Source (ITS) is as
follows::
images {
uboot {
description = "U-Boot image";
data = /incbin/("u-boot-nodtb.bin");
type = "standalone";
os = "u-boot";
arch = "";
compression = "none";
load = <0x80000000>;
entry = <0x80000000>;
};
fwa {
description = "FW A";
data = /incbin/("fwa.bin");
type = "firmware";
arch = "";
os = "";
load = <0xb2000000>;
entry = <0xb2000000>;
compression = "none";
};
};
:term:`UBOOT_FITIMAGE_ENABLE` :term:`UBOOT_FITIMAGE_ENABLE`
This variable allows to generate a FIT image for U-Boot, which is one This variable allows to generate a FIT image for U-Boot, which is one
of the ways to implement a verified boot process. of the ways to implement a verified boot process.