[PATCH v2 2/3] X86: Add support for distro boot

[Simon Glass]

Hi,

On Fri, 5 May 2023 at 02:23, Mittelstaedt Thomas (XC-CT/EBV3)
<Thomas.Mittelstaedt at de.bosch.com> wrote:
>
> Hi Simon,
>
> U-Boot can't start with boot script boot.scr, if BOOTSTD_DEFAULT is set. With this setting "bootflow scan -lb" is not supported.
> Booting with extlinux.conf works somehow.
>
> = Bootlog =======================================================
> U-Boot 2023.04-01135-g4ea415461d-dirty (May 05 2023 - 05:56:36 +0000)
>
> CPU: x86_64, vendor Intel, device a0652h
> DRAM:  8 GiB
> Core:  12 devices, 11 uclasses, devicetree: separate
> MMC:
> Loading Environment from FAT... scanning bus for devices...
> Target spinup took 0 ms.
> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> flags: 64bit ncq stag only ccc
>   Device 0: (0:0) Vendor: ATA Prod.: VBOX HARDDISK Rev: 1.0
>             Type: Hard Disk
>             Capacity: 32768.0 MB = 32.0 GB (67108864 x 512)
> Unable to read "uboot.env" from scsi0:1...
> No video mode configured in EFI!
> No video mode configured in EFI!
> Model: EFI x86 Payload
> Net:   e1000: 08:00:27:1c:36:6f
>
> Warning: e1000#0 failed to set MAC address
> eth0: e1000#0
> Bus xhci_pci: Register e000820 NbrPorts 14
> Starting the controller
> USB XHCI 1.00
> scanning bus xhci_pci for devices... 2 USB Device(s) found
> Hit any key to stop autoboot:  0
> scanning bus for devices...
>   Device 0: (0:0) Vendor: ATA Prod.: VBOX HARDDISK Rev: 1.0
>             Type: Hard Disk
>             Capacity: 32768.0 MB = 32.0 GB (67108864 x 512)
> Bus 0: OK Bus 1: not available
>   Device 0: Model: VBOX Firm: 1.0 Ser#: CD-ROM
>             Type: Removable CD ROM
>             Capacity: 50.5 MB = 0.0 GB (25902 x 2048)
>   Device 1: not available
> Error (no IRQ) dev 0 blk 0: status 0x11
> Error (no IRQ) dev 0 blk 0: status 0x11
> Error (no IRQ) dev 0 blk 10: status 0x11
> Error (no IRQ) dev 0 blk 0: status 0x11
> Bus xhci_pci: scanning bus xhci_pci for devices... Device not responding to set address.
>
>       USB device not accepting new address (error=80000000)
> failed, error -71
>
> => printenv bootcmd
> bootcmd=bootflow scan
> => bootflow scan -lb
> Flags not supported: enable CONFIG_BOOTFLOW_FULL
> bootflow - Boot flows
>
> Usage:
> bootflow scan - boot first available bootflow
>
> ===============================================================
>
> With BOOTSTD_FULL it's so far fine, but I'm missing the handling of U-Boot-Menu compared to U-Boot (2023.01) at Apertis.
> I could not find a real difference but version.
> But also with DISTROBOOT enabled at earlier patch sets I see following differences:
>
> The U-Boot image created with this patch set
> - doesn't provide any output toTTY screen at Virtualbox, only at serial console
> - doesn't provide U-Boot-Menu at screen (U-Boot of Apertis provides it also at serial console)
> But I'll proceed investigating these differences. Perhaps they are caused by Debian patches not upstreamed yet. Atm it's not critical.
>
> = Bootlog =======================================================
> U-Boot 2023.04-01135-g4ea415461d-dirty (May 05 2023 - 05:56:36 +0000)
>
> CPU: x86_64, vendor Intel, device a0652h
> DRAM:  5.6 GiB
> Core:  12 devices, 11 uclasses, devicetree: separate
> MMC:
> Loading Environment from FAT... scanning bus for devices...
> Target spinup took 0 ms.
> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> flags: 64bit ncq stag only ccc
>   Device 0: (0:0) Vendor: ATA Prod.: VBOX HARDDISK Rev: 1.0
>             Type: Hard Disk
>             Capacity: 33792.0 MB = 33.0 GB (69206016 x 512)
> Unable to read "uboot.env" from scsi0:1...
> No video mode configured in EFI!
> No video mode configured in EFI!
> Model: EFI x86 Payload
> Net:   No ethernet found.
> No working controllers found
> Hit any key to stop autoboot:  0
> scanning bus for devices...
>   Device 0: (0:0) Vendor: ATA Prod.: VBOX HARDDISK Rev: 1.0
>             Type: Hard Disk
>             Capacity: 33792.0 MB = 33.0 GB (69206016 x 512)
> ** Booting bootflow 'ahci_scsi.id0lun0.bootdev.part_2' with distro
> 1:      Apertis pro v2022 5.15.0-trunk-amd64
> Retrieving file: /boot/vmlinuz-5.15.0-trunk-amd64
> Retrieving file: /boot/initrd.img-5.15.0-trunk-amd64
> append: root=UUID=8ab7a6d1-a3fa-4fff-8de0-e381551b7cc4 console=tty0 console=ttyS0,115200n8 rootwait ro quiet splash plymouth.ignor e-serial-consoles fsck.mode=auto fsck.repair=yes
> Valid Boot Flag
> ===================================================================
>
> Mit freundlichen Grüßen / Best regards
>
> Thomas Mittelstaedt
>
> Cross-Domain Computing Solutions

Can you please try these four patches?

https://patchwork.ozlabs.org/project/uboot/list/?series=353761
https://patchwork.ozlabs.org/project/uboot/patch/20230506142709.1382495-1-sjg@chromium.org/

Regards,
Simon