
On Sat, 8 Jun 2024 at 01:39, Jonathan Humphreys j-humphreys@ti.com wrote:
Define the firmware components updatable via EFI capsule update, including defining capsule GUIDs for the various firmware components for the AM62x SK.
Signed-off-by: Jonathan Humphreys j-humphreys@ti.com
board/ti/am62x/evm.c | 34 ++++++++++++++++++++++++++++++++++ include/configs/am62x_evm.h | 24 ++++++++++++++++++++++++ 2 files changed, 58 insertions(+)
diff --git a/board/ti/am62x/evm.c b/board/ti/am62x/evm.c index b3e8680dfab..9bdd0223cdb 100644 --- a/board/ti/am62x/evm.c +++ b/board/ti/am62x/evm.c @@ -7,6 +7,7 @@
*/
+#include <efi_loader.h> #include <env.h> #include <spl.h> #include <init.h> @@ -46,6 +47,39 @@ int splash_screen_prepare(void) } #endif
+struct efi_fw_image fw_images[] = {
{
.image_type_id = AM62X_SK_TIBOOT3_IMAGE_GUID,
.fw_name = u"AM62X_SK_TIBOOT3",
.image_index = 1,
},
{
.image_type_id = AM62X_SK_SPL_IMAGE_GUID,
.fw_name = u"AM62X_SK_SPL",
.image_index = 2,
},
{
.image_type_id = AM62X_SK_UBOOT_IMAGE_GUID,
.fw_name = u"AM62X_SK_UBOOT",
.image_index = 3,
}
+};
+struct efi_capsule_update_info update_info = {
.dfu_string = "sf 0:0=tiboot3.bin raw 0 80000;"
"tispl.bin raw 80000 200000;u-boot.img raw 280000 400000",
.num_images = ARRAY_SIZE(fw_images),
.images = fw_images,
+};
+#if IS_ENABLED(CONFIG_SET_DFU_ALT_INFO) +void set_dfu_alt_info(char *interface, char *devstr) +{
if (IS_ENABLED(CONFIG_EFI_HAVE_CAPSULE_SUPPORT))
env_set("dfu_alt_info", update_info.dfu_string);
+} +#endif
int board_init(void) { return 0; diff --git a/include/configs/am62x_evm.h b/include/configs/am62x_evm.h index c8fe59b7531..0d98f14a4bc 100644 --- a/include/configs/am62x_evm.h +++ b/include/configs/am62x_evm.h @@ -9,6 +9,30 @@ #ifndef __CONFIG_AM625_EVM_H #define __CONFIG_AM625_EVM_H
+/**
- define AM62X_SK_TIBOOT3_IMAGE_GUID - firmware GUID for AM62X sk tiboot3.bin
- define AM62X_SK_SPL_IMAGE_GUID - firmware GUID for AM62X sk SPL
- define AM62X_SK_UBOOT_IMAGE_GUID - firmware GUID for AM62X sk UBOOT
- These GUIDs are used in capsules updates to identify the corresponding
- firmware object.
- Board developers using this as a starting reference should
- define their own GUIDs to ensure that firmware repositories (like
- LVFS) do not confuse them.
- */
+#define AM62X_SK_TIBOOT3_IMAGE_GUID \
EFI_GUID(0xabcb83d2, 0x9cb6, 0x4351, 0xb8, 0xf1, \
0x64, 0x94, 0xbb, 0xe3, 0x70, 0x0a)
+#define AM62X_SK_SPL_IMAGE_GUID \
EFI_GUID(0xaee355fc, 0xbf97, 0x4264, 0x8c, 0x82, \
0x43, 0x72, 0x55, 0xef, 0xdc, 0x1d)
+#define AM62X_SK_UBOOT_IMAGE_GUID \
EFI_GUID(0x28ab8c6c, 0xfca8, 0x41d3, 0x8e, 0xa1, \
0x5f, 0x17, 0x1b, 0x7d, 0x29, 0x29)
/* Now for the remaining common defines */ #include <configs/ti_armv7_common.h>
-- 2.34.1
Acked-by: Ilias Apalodimas ilias.apalodimas@linaro.org