From 5dcc0232a54e958f1a9acae5f7394b589cf5fd12 Mon Sep 17 00:00:00 2001 From: Daniel Rossier Date: Tue, 30 Jun 2026 10:05:06 +0200 Subject: [PATCH] config: default SO3 boot chain to bare U-Boot (no ATF/OP-TEE) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The SO3 standalone default on virt64 was left at IB_BOOT_CHAIN = "full", which pulled ATF + OP-TEE + AVZ into the boot chain and assembled a secure- world flash0.img — appropriate for the e1c capsule model but not for the plain SO3-at-EL1 default. The inline documentation already describes the empty value as the SO3 default and prescribes a weak assignment so a capsule layer can override it. Set IB_BOOT_CHAIN ?= "" so the default build is bare U-Boot (no ATF, no OP-TEE, no AVZ) and a downstream capsule layer can still select "full". Verified: a clean bsp-so3 build now produces a 42-task graph with no atf/optee/avz tasks and no flash0.img; st.sh loads U-Boot via -kernel at EL1. --- build/conf/local.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build/conf/local.conf b/build/conf/local.conf index 57dc092993..b06165d030 100644 --- a/build/conf/local.conf +++ b/build/conf/local.conf @@ -161,7 +161,7 @@ IB_CONFIG:avz:verdin-imx8mp ?= "verdin-imx8mp_avz_defconfig" # "full" ATF + OP-TEE (BL32) + U-Boot in flash0.img — secure world. # The flash0.img assembly lives in meta-bsp/.../bsp_virt64.inc # (__do_platform_boot_chain); st.sh picks ATF vs bare from its presence. -IB_BOOT_CHAIN = "full" +IB_BOOT_CHAIN ?= "" # ATF / OP-TEE platform identifiers for QEMU virt (used when IB_BOOT_CHAIN # is "atf+uboot" or "full"). Mirrors edgem1's virt64 settings.