Re: git: 1dec3639fd0c - main - sysutils/u-boot: Update to 2021.07

Emmanuel Vadot <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On Mon, 12 Jul 2021 13:44:43 +0200
"Herbert J. Skuhra" <[email protected]> wrote:

> Hi Emmanuel,
> 
> thanks for your feedback.
> 
> On Mon, Jul 12, 2021 at 11:50:10AM +0200, Emmanuel Vadot wrote:
> > 
> >  So I took the latest snapshot image available on the ftp
> > (FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20210701-c5f4772c66d-247671.img)
> >  and dd u-boot for the nanopi_m1plus on it.
> >  The snapshot already have the u-boot for BeagleBone and RPI*
> > 
> >  No problems on the BBB
> >  No problems on the NanoPi M1Plus
> >  I do see the hang on the RPI2 though (RPI2 v1.1)
> > 
> >  Commit 60a376b09332a0cf061b3 in u-boot removes
> > CONFIG_EFI_GRUB_ARM32_WORKAROUND from the RPI2 defconfig but we do
> > re-add it in the ports tree (see
> > https://cgit.freebsd.org/ports/tree/sysutils/u-boot-master/Makefile#n215
> > and
> > https://cgit.freebsd.org/ports/tree/sysutils/u-boot-master/files/FreeBSD_Fragment#n2)
> > 
> >  So if you bisected from u-boot tree directly and didn't use a fragment
> > that's normal to get this commit as the first bad one.
> 
> I was lazy and built the port (created a *.tar.bz2 archive from
> the git checkout or rcX downloads and modified distinfo). 
> 
> >  Note that the images don't have a boot.scr (u-boot script) for a long
> > time now, we rely on EFI. (See commit
> > https://cgit.freebsd.org/src/commit/?id=33bec6889a0957d1c06c36378157a46a95fcb004)
> 
> Yes, my RPi2 only boots without this change (a361eabce3cf). Maybe it
> should be reverted until we have a proper fix? Or create images with
> older U-Boot (2021.01)?

 Damn, I missed that u-boot-rpi2 used its own fragment.
 Can you try adding CONFIG_EFI_GRUB_ARM32_WORKAROUND=y to
sysutils/u-boot-rpi2/files/rpi2_fragment and see if that fixes the
issue for you ?

> >  For your mmc problem this can be that you are not using the dtoverlay
> > that switches between the sdhost controller and the sdhci. Using this
> > rewrite the mmc number for u-boot.
> 
> This happens even with the official builds!
> 
> FreeBSD-13.0-STABLE-arm64-aarch64-RPI-20210701-6aee7855180-246143.img.xz
> ==> OK (U-Boot 2021.04)
> FreeBSD-13.0-STABLE-arm64-aarch64-RPI-20210708-f6d448caf69-246212.img.xz
> ==> Not OK. (U-Boot 2021.07)
> 
> I am using U-Boot 2021.04 again because I still don't know how to boot
> from mmc device 2 automatically.
> 
> -- 
> Herbert
> 


-- 
Emmanuel Vadot <[email protected]> <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.