Re: [PATCH v3 08/11] configs: am62lx_evm: add initial defconfig
Anshul Dalal <[email protected]> Tue, 4 Aug 2026 17:26:46 +0530
| Newsgroups | gmane.comp.boot-loaders.u-boot |
|---|---|
| Message-ID | <[email protected]> |
On Tue Aug 4, 2026 at 5:39 AM IST, Bryan Brattlof wrote: > Add the initial minimum configuration needed to boot the AM62L3-SK > reference boards. > > Tested-by: Anshul Dalal <[email protected]> > Signed-off-by: Bryan Brattlof <[email protected]> > --- > Changes in v2: > - removed options used for fit image signing > - Link to v1: https://lore.kernel.org/r/20260717-am62lx-v1-0-b9830633afb8= @ti.com > --- > configs/am62lx_evm_defconfig | 139 +++++++++++++++++++++++++++++++++++++= ++++++ > 1 file changed, 139 insertions(+) > > diff --git a/configs/am62lx_evm_defconfig b/configs/am62lx_evm_defconfig > new file mode 100644 > index 000000000000..2db07b508c2a > --- /dev/null > +++ b/configs/am62lx_evm_defconfig > @@ -0,0 +1,139 @@ > +CONFIG_ARM=3Dy > +CONFIG_ARCH_K3=3Dy > +CONFIG_TEXT_BASE=3D0x84000000 > +CONFIG_SYS_MALLOC_F_LEN=3D0x8000 > +CONFIG_TI_COMMON_CMD_OPTIONS=3Dy > +CONFIG_SPL_GPIO=3Dy > +CONFIG_SPL_LIBCOMMON_SUPPORT=3Dy > +CONFIG_SOC_K3_AM62L3=3Dy > +CONFIG_TARGET_AM62L3_EVM=3Dy > +CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=3Dy > +CONFIG_CUSTOM_SYS_INIT_SP_ADDR=3D0x82b80000 > +CONFIG_SF_DEFAULT_SPEED=3D25000000 > +CONFIG_DM_GPIO=3Dy > +CONFIG_DEFAULT_DEVICE_TREE=3D"ti/k3-am62l3-evm" > +CONFIG_OF_LIBFDT_OVERLAY=3Dy > +CONFIG_DM_RESET=3Dy > +CONFIG_SPL_MMC=3Dy > +CONFIG_SPL_SERIAL=3Dy > +CONFIG_SPL_STACK_R_ADDR=3D0x85000000 > +CONFIG_SPL_TEXT_BASE=3D0x82000000 > +CONFIG_SPL_HAS_BSS_LINKER_SECTION=3Dy > +CONFIG_SPL_BSS_START_ADDR=3D0x82c80000 > +CONFIG_SPL_BSS_MAX_SIZE=3D0x80000 > +CONFIG_SPL_STACK_R=3Dy > +CONFIG_SYS_BOOTM_LEN=3D0x800000 Currently using the command 'spl export' throws a "Image too large: increase CONFIG_SYS_BOOTM_LEN" warning. Steps to reproduce: =3D> load mmc 1:2 $loadaddr boot/fitImage =3D> spl export fdt $loadaddr Is there any reason we are keeping it this low? I think the default of 0x8000000 should be fine for us. Rest of the patch looks good to me, - Anshul