Hi Ivan,
On Thu, 19 Oct 2023 at 08:29, Ivan Ivanov ivan.ivanov@suse.com wrote:
On Thu, 2023-10-19 at 08:00 -0600, Simon Glass wrote:
[2] https://patchwork.ozlabs.org/project/uboot/patch/20230923205017.1754340-1-sj...
[1] https://lists.denx.de/pipermail/u-boot/2023-October/533158.html
> 'git bisect' points to: > ********** > commit c771e5b8c2a186fb072b6c6f571d4a3cc86efba9 > Author: Simon Glass sjg@chromium.org > Date: Thu Jul 27 15:54:28 2023 -0600 > > arm: rpi: Switch to standard boot > > Drop use of the distro scripts and use standard boot instead. > > We don't need to specify the mmc devices individually, since they are > used in order from 0 to 2, and standard boot uses that order anyway. > > Signed-off-by: Simon Glass sjg@chromium.org > ********** > > The following patch fixes the boot from uSD on RPi4 (not tested on RPi3 nor RPi Zero 2 W): > ********** > diff --git a/board/raspberrypi/rpi/rpi.env > b/board/raspberrypi/rpi/rpi.env index 30228285ed..02210b97b5 100644 > --- a/board/raspberrypi/rpi/rpi.env > +++ b/board/raspberrypi/rpi/rpi.env > @@ -74,4 +74,4 @@ pxefile_addr_r=0x02500000 > fdt_addr_r=0x02600000 > ramdisk_addr_r=0x02700000 > > -boot_targets=mmc usb pxe dhcp > +boot_targets=mmc0 mmc1 mmc2 usb pxe dhcp > ********** > > So, the comment from Simon " We don't need to specify the mmc devices individually, since they are used in order from 0 to 2, and standard boot uses that order anyway" seems wrong for the RPi4 case. >
I am afraid we still have a boot issue. This time device can not boot from USB. Device boot order was changed to USB first then uSD. uSD card is removed.
Please see [1] attachment #870321 for boot log details.
I have not invested time to debug this, still.
Thanks for the info. Is this using 'boot_targets=mmc usb pxe dhcp'?
Yes. "boot_targets=mmc usb pxe dhcp". Full environment added to the bug.
OK thank you, I will take a look.
I wonder if there is a way of testing pending patches, or do they need to be applied before they can be tested in your systems?
Regards, Simon