Hi Heinrich, On Tue, 21 Nov 2023 at 10:20, Heinrich Schuchardt <xypron.g...@gmx.de> wrote: > > On 11/21/23 12:35, Simon Glass wrote: > > This works when run outside a test: > > > > good: > > > > /tmp/b/sandbox/u-boot -T > > -c "bootfl scan mmc; bootfl sel 1; bootfl list; bootfl b" > > > > ** Booting bootflow 'mmc7.bootdev.part_1' with efi > > desc = 0000000018c86ee0 > > dev=mmc, devnr=7:1, path=efi/boot/bootsbox.efi, buffer=0000000011001000, > > size=1600 > > - boot device > > /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,0000000000000000)/SD(7)/SD(3)/HD(1,MBR,0x2f7d9756,0x800,0x9000) > > - image /efi\boot\bootsbox.efi > > No EFI system partition > > No EFI system partition > > Failed to persist EFI variables > > EFI using ACPI tables at 8ef8000 > > WARNING: Can't have ACPI table and device tree - ignoring DT. > > Loaded from disk > > Booting /efi\boot\bootsbox.efi > > EFI: Call: efi_load_image(false, efi_root, file_path, source_buffer, > > source_size, &handle) > > info->device_handle = 0000000018f180e0 > > loaded_image info for 0000000018f184e0: 0000000018f18470 > > > > EFI: 0 returned by efi_load_image(false, efi_root, file_path, > > source_buffer, source_size, &handle) > > EFI: Call: efi_start_image(handle, &exit_data_size, &exit_data) > > Hello, world! > > Running on UEFI 2.10 > > Have ACPI 2.0 table > > Have SMBIOS table > > 18f18470 > > Load options: <none> > > finding > > - search 0000000018c931a0 ret=0 > > File path: /efi\boot\bootsbox.efi > > Vendor: Das U-Boot > > Boot device: > > /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,0000000000000000)/SD(7)/SD(3)/HD(1,MBR,0x2f7d9756,0x800,0x9000) > > Exiting boot sevices > > EFI: 5 returned by efi_start_image(handle, &exit_data_size, &exit_data) > > Boot failed (err=-22) > > > > bad: > > > > rtv bootflow_efi > > > > ** Booting bootflow 'mmc7.bootdev.part_1' with efi > > Should we have an ESP on the MMC image to persist UEFI variables?
That would be a good enhancement, but I would like to get the basics going first. Regards, Simon
