On 8/19/26 5:19 AM, Gokul Praveen wrote:
This fragment enables a boot mode for K3 platforms where the R5 SPL
directly loads U-Boot proper, bypassing the A Core SPL stage
The R5 config modifies the payload filename to load tinospl.bin
instead of tispl.bin. The A Core config updates the U-Boot load
address to match the A Core SPL load address, allowing R5 SPL to
load U-Boot directly from that location since A Core SPL is not
present in this boot flow.
This reduces boot time by eliminating the A Core SPL stage.
Is there any downside to this approach to look out for? If this
is strictly better, then why not make this the default and not
add yet another boot flow combination (to the already long list
of combinations..)?
Andrew
Signed-off-by: Gokul Praveen <[email protected]>
Reviewed-by Neha Malcom Francis <[email protected]>
---
configs/k3_a72_nospl.config | 1 +
configs/k3_r5_nospl.config | 1 +
2 files changed, 2 insertions(+)
create mode 100644 configs/k3_a72_nospl.config
create mode 100644 configs/k3_r5_nospl.config
diff --git a/configs/k3_a72_nospl.config b/configs/k3_a72_nospl.config
new file mode 100644
index 00000000000..7522acab950
--- /dev/null
+++ b/configs/k3_a72_nospl.config
@@ -0,0 +1 @@
+CONFIG_TEXT_BASE=0x80080000
diff --git a/configs/k3_r5_nospl.config b/configs/k3_r5_nospl.config
new file mode 100644
index 00000000000..94931bf8798
--- /dev/null
+++ b/configs/k3_r5_nospl.config
@@ -0,0 +1 @@
+CONFIG_SPL_FS_LOAD_PAYLOAD_NAME="tinospl.bin"
