On 1/16/26 4:30 AM, Paresh Bhagat wrote:
Reference the tiboot3 binary labels from k3-am62a-sk-binman.dtsi and
override their filenames to use AM62D-specific names:
- tiboot3-am62dx-hs-evm.bin
- tiboot3-am62dx-hs-fs-evm.bin
Signed-off-by: Paresh Bhagat <[email protected]>
---
arch/arm/dts/k3-am62d-evm-binman.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/dts/k3-am62d-evm-binman.dtsi
b/arch/arm/dts/k3-am62d-evm-binman.dtsi
index 41c8746cf08..430bf8ccb79 100644
--- a/arch/arm/dts/k3-am62d-evm-binman.dtsi
+++ b/arch/arm/dts/k3-am62d-evm-binman.dtsi
@@ -63,6 +63,14 @@
config = "board/ti/am62ax/rm-cfg.yaml";
};
+&tiboot3_am62ax_hs_evm {
+ filename = "tiboot3-am62dx-hs-evm.bin";
+};
NAK
We have discussed this before, the name of the file is based on the TIFS
binary used. This file uses "ti-fs-firmware-am62ax-hs-enc.bin" so its
name must match. The name has nothing to do with which board or SoC the
SPL was built for, we have *never* named the SPL image after the board or
SoC, if you believe otherwise then tell me what specific board or SoC the
file "tiboot3.bin" or "MLO" is for?
You also give no "why" you need to change the name in your commit message
nor cover-letter, simply stating it is the "correct" name. I do know the
reason, and it isn't a good one, go fix your yocto/test scripts.
Andrew
+
+&tiboot3_am62ax_hs_fs_evm {
+ filename = "tiboot3-am62dx-hs-fs-evm.bin";
+};
+
#endif
#ifdef CONFIG_TARGET_AM62D2_A53_EVM
