Hello Simon, Simon Glass <s...@chromium.org> writes:
[...] > Now that am335x_evm boots OK on the Beaglebone black, drop the latter > and update the docs to cover the change. [...] > diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig > index d243cb16e72..cabc181460a 100644 > --- a/configs/am335x_evm_defconfig > +++ b/configs/am335x_evm_defconfig > @@ -13,6 +13,8 @@ CONFIG_AM335X_USB0_PERIPHERAL=y > CONFIG_AM335X_USB1=y > CONFIG_SPL=y > CONFIG_TIMESTAMP=y > +CONFIG_FIT_SIGNATURE=y > +CONFIG_FIT_VERBOSE=y Your patch drops CONFIG_LEGACY_IMAGE_FORMAT as a side effect of enabling CONFIG_FIT_SIGNATURE. Is that intentional? Debian systems use "legacy" format boot scripts to boot (at least when using the "flash-kernel" package which is probably the most common configuration) so recent U-Boot versions cannot boot Debian systems on BeagleBone Black any more: === Begin === U-Boot 2025.01-3 (Apr 08 2025 - 23:07:41 +0000) CPU : AM335X-GP rev 2.1 Model: TI AM335x BeagleBone Black [...] Scanning mmc 0:3... Found U-Boot script /boot/boot.scr 1625 bytes read in 2 ms (793 KiB/s) ## Executing script at 80000000 Wrong image format for "source" command SCRIPT FAILED: continuing... === End === Sascha
signature.asc
Description: PGP signature
