[PATCH V6 07/20] configs: am62x_evm_a53_defconfig: Switch to bootstd
Jan Kiszka
jan.kiszka at siemens.com
Sat Feb 17 09:42:07 CET 2024
On 17.02.24 04:11, Alexander Sverdlin wrote:
> Hello Nishanth,
>
> On Fri, 2023-08-25 at 13:02 -0500, Nishanth Menon wrote:
>> Switch to using bootstd. Note with this change, we will stop using
>> distro_bootcmd and instead depend entirely on bootflow method of
>> starting the system up.
>>
>> Suggested-by: Tom Rini <trini at konsulko.com>
>> Suggested-by: Simon Glass <sjg at chromium.org>
>> Reviewed-by: Tom Rini <trini at konsulko.com>
>> Tested-by: Mattijs Korpershoek <mkorpershoek at baylibre.com>
>> Signed-off-by: Nishanth Menon <nm at ti.com>
>> Reviewed-by: Tom Rini <trini at konsulko.com>
>> Reviewed-by: Mattijs Korpershoek <mkorpershoek at baylibre.com>
>> ---
>> No change other than picking up reviews, tested tags along the way.
>> V5: https://lore.kernel.org/r/20230824031101.3460411-6-nm@ti.com
>> configs/am62x_evm_a53_defconfig | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/configs/am62x_evm_a53_defconfig b/configs/am62x_evm_a53_defconfig
>> index d55caabe22c9..1807df8bbee9 100644
>> --- a/configs/am62x_evm_a53_defconfig
>> +++ b/configs/am62x_evm_a53_defconfig
>> @@ -28,8 +28,9 @@ CONFIG_SPL_SPI=y
>> # CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set
>> CONFIG_SPL_LOAD_FIT=y
>> CONFIG_SPL_LOAD_FIT_ADDRESS=0x81000000
>> -CONFIG_DISTRO_DEFAULTS=y
>> -CONFIG_BOOTCOMMAND="run envboot; run distro_bootcmd;"
>> +CONFIG_BOOTSTD_FULL=y
>> +CONFIG_BOOTSTD_DEFAULTS=y
>> +CONFIG_BOOTCOMMAND="run envboot; bootflow scan -lb"
>> CONFIG_SPL_MAX_SIZE=0x58000
>> CONFIG_SPL_HAS_BSS_LINKER_SECTION=y
>> CONFIG_SPL_BSS_START_ADDR=0x80c80000
>
> could you please suggest which distro have you used for testing?
>
> After U-Boot update to v2024.01 Buildroot is not booting any more:
>
> ---
> U-Boot 2024.01 (Feb 15 2024 - 01:43:17 +0100)
>
> SoC: AM62X SR1.0 HS-FS
> Model: Texas Instruments AM625 SK
> DRAM: 2 GiB
> Core: 56 devices, 23 uclasses, devicetree: separate
> MMC: mmc at fa10000: 0, mmc at fa00000: 1
> Loading Environment from nowhere... OK
> In: serial at 2800000
> Out: serial at 2800000
> Err: serial at 2800000
> Net: eth0: ethernet at 8000000port@1
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc1 is current device
> SD/MMC found on device 1
> Failed to load 'uEnv.txt'
> Scanning for bootflows in all bootdevs
> Seq Method State Uclass Part Name Filename
> --- ----------- ------ -------- ---- ------------------------ ----------------
> Scanning global bootmeth 'efi_mgr':
> No EFI system partition
> No EFI system partition
> Failed to persist EFI variables
> Scanning bootdev 'mmc at fa00000.bootdev':
> Scanning bootdev 'mmc at fa10000.bootdev':
> Unknown uclass 'usb' in label
> link up on port 1, speed 100, full duplex
> BOOTP broadcast 1
> BOOTP broadcast 2
> BOOTP broadcast 3
> ...
> ---
>
> I suppose TI's BSP has older U-Boot... So it's not providing necessary
> script for BOOTSTD, I suppose?
>
You can make the BeagleBone boot via EFI, but it requires a hybrid
partition table (ROM loader want DOS, EFI needs GPT). A Debian
integration with this can be found for Isar [1] in this series [2]. It's
only using upstream sources (plus still one u-boot patch to get wifi
working).
If you want legacy script booting, I suspect you need to flip some extra
switches explicitly by now.
Jan
[1] https://github.com/ilbers/isar/
[2] https://patchwork.isar-build.org/project/isar/list/?series=1049
--
Siemens AG, Technology
Linux Expert Center
More information about the U-Boot
mailing list