[PATCH v5 11/15] configs: sc5xx: Set default bootcmd to SPI boot

[Simon Glass]

Hi Caleb,

On 2026-04-23T14:24:50, Caleb Ethridge <jcethrid at gmail.com> wrote:
> configs: sc5xx: Set default bootcmd to SPI boot
>
> Align configs to use the same default bootcommand.
>
> Signed-off-by: Caleb Ethridge <caleb.ethridge at analog.com>
>
> configs/sc589-ezkit_defconfig          | 2 +-
>  configs/sc589-mini_defconfig           | 2 +-
>  configs/sc594-som-ezkit-spl_defconfig  | 2 +-
>  configs/sc594-som-ezlite-spl_defconfig | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)

> diff --git a/configs/sc589-ezkit_defconfig b/configs/sc589-ezkit_defconfig
> @@ -22,7 +22,7 @@ CONFIG_FIT=y
> -CONFIG_BOOTCOMMAND="run ramboot"
> +CONFIG_BOOTCOMMAND="run spiboot"

The commit message says "Align configs to use the same default
bootcommand", but after this patch sc573-ezlite and sc584-ezkit still
have CONFIG_BOOTCOMMAND="run ramboot". Both define USE_SPI, so spiboot
is available there too. Please update those defconfigs as well, or
mention this in the commit message.

Also worth noting the motivation, that with the environment no longer
stored in SPI (patch 1) and the new SPI partitioning from patch 3, SPI
is now the intended default boot medium.

> diff --git a/configs/sc594-som-ezkit-spl_defconfig b/configs/sc594-som-ezkit-spl_defconfig
> @@ -15,7 +15,7 @@ CONFIG_FIT=y
> -CONFIG_BOOTCOMMAND="run ospiboot"
> +CONFIG_BOOTCOMMAND="run spiboot"

Just to check - patch 3 keeps a distinct ospiboot target (with its own
ospiargs setting sfdev to the OSPI bus/SSEL), so switching the sc594
SOM boards from ospiboot to spiboot now points them at the SPI bus
instead of OSPI. Is that intentional on these OSPI-equipped SOMs, or
should the bootcmd remain "run ospiboot"? Please spell this out in the
commit message.

Reviewed-by: Simon Glass <sjg at chromium.org>

Regards,
Simon