Comment # 15 on bug 1207562 from Chester Lin

(In reply to Stefan Seyfried from comment #14)
> updated the second machine today to u-boot-rpiarm64-2023.01-2.1.aarch64 from
> tumbleweed-oss repo, last changelog
> 
> * Fri Jan 27 2023 Guillaume GARDET <guillaume.gardet@opensuse.org>
> Patch queue updated from https://github.com/openSUSE/u-boot.git
> tumbleweed-2023.01
>   Prefer upstream solution to fix boo#1207562
>   * Patches dropped:
>   0017-rpi-fix-boot-from-USB-on-RPi4-boo-1.patch
>   * Patches added:
>   0017-Backport-https-patchwork.ozlabs.org.patch
> 
> 
> And it still fails.
> I only could take a picture of the error message, so typing in here (if this
> continues, I definitely will have to set up a serial-to-syslog-device for my
> raspis ;-))
> -------
> Scanning usb 0:1
> BootOrder not defined

> EFI boot manager: Cannot load any image
> Found EFI removable media binary efi/boot/bootaa64.efi

This log was printed by the u-boot script 'scan_dev_for_efi', and then it ran
the script 'boot_efi_binary' in order to load and execute grub2.

> ** Reading file would overwrite reserved memory **
> Failed to load 'efi/boot/bootaa64.efi'

It seemed that somehow the load address [should be 0x00080000 = kernel_addr_r]
had been *reserved* so that the 'boot_efi_binary' script failed to load the
grub2 from the USB disk.

Could you please check if there's any reserved memory declared in the runtime
FDT?

> No UEFI binary known at 0x00080000

There was no grub2 binary stored in 0x00080000 so the bootefi command just
failed.

> EFI LOAD FILED: continuing...
> BOOTP broadcast 1
> ------
> 
> I'd try to boot the machine simply via bootp/tftp, but these machines are in
> the guest network and thus I cannot easily provide them with tftp ;-)