diff options
| author | Tom Rini <trini@konsulko.com> | 2024-06-18 10:47:10 -0600 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2024-06-18 10:47:10 -0600 |
| commit | 01a5d7547ed3a51a8ac5837c31a150f85bc475f8 (patch) | |
| tree | 326a83a66dad60d2a406c593b775245b3ed764ca /doc/develop | |
| parent | 2c92ec69d162c1ac1a6b6ab25324c0e53b4a6ffe (diff) | |
| parent | 3e6fd29aa88c5c05a3e4057148ff74c7f2d7a3d2 (diff) | |
Merge patch series "EFI: ti: Enable EFI capsule updates"
Jonathan Humphreys <j-humphreys@ti.com> says:
Enable on disk capsule updates, which includes defining the firmware
components (tiboot3, spl, u-boot) and enabling processing of raw capsule
updates.
This is enabled for several TI SoC based platforms: AM64, AM62, AM62p,
AM69, BeaglePlay, J7, and BeagleboneAI. The configs to enable this are in a
single base config file. This will make it more scalable to add additional
EFI capsule features (like authentication) across all TI boards that have
capsules enabled.
This series also includes enabling serial flash DFU for AM62 and MMC DFU
for beagleplay.
Diffstat (limited to 'doc/develop')
| -rw-r--r-- | doc/develop/uefi/uefi.rst | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/develop/uefi/uefi.rst b/doc/develop/uefi/uefi.rst index 0389b269c01..36ac75278fa 100644 --- a/doc/develop/uefi/uefi.rst +++ b/doc/develop/uefi/uefi.rst @@ -631,6 +631,18 @@ where version.dtso looks like:: The properties of image-type-id and image-index must match the value defined in the efi_fw_image array as image_type_id and image_index. +Porting Capsule Updates to new boards +************************************* + +It is important, when using a reference board as a starting point for a custom +board, that certain steps are taken to properly support Capsule Updates. + +Capsule GUIDs need to be unique for each firmware and board. That is, if two +firmwares are built from the same source but result in different binaries +because they are built for different boards, they should have different GUIDs. +Therefore it is important when creating support for a new board, new GUIDs are +defined in the board's header file. *DO NOT* reuse capsule GUIDs. + Executing the boot manager ~~~~~~~~~~~~~~~~~~~~~~~~~~ |