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

 Hi Herbert,

 Took the last mail of the thread, it was easier.

On Sun, 11 Jul 2021 20:47:13 +0200
"Herbert J. Skuhra" <herbert@gojira.at> wrote:

> On Sun, 11 Jul 2021 20:28:36 +0200, "Herbert J. Skuhra" wrote:
> > 
> > On Fri, 09 Jul 2021 15:35:17 +0200, "Herbert J. Skuhra" wrote:
> > >  
> > > With u-boot 2021.07 two of my RPis no longer boot:
> > > 
> > > Raspberry Pi 3 Model B V1.2: mmc not detected; tries to boot over the network.
> > 
> > With u-boot 2021.04 I get:
> > 
> > > mmc list 
> > mmc@7e300000: 0 (SD)
> > 
> > > mmc part
> > 
> > Partition Map for MMC device 0  --   Partition Type: DOS
> > 
> > Part    Start Sector    Num Sectors     UUID            Type
> >   1     2048            102400          5fd0f4e4-01     0c Boot
> >   2     104448          124631040       5fd0f4e4-02     a5
> > 
> > > mmcinfo 
> > Device: mmc@7e300000
> > Manufacturer ID: 3
> > OEM: 5344
> > Name: SC64G 
> > Bus Speed: 25000000
> > Mode: MMC legacy
> > Rd Block Len: 512
> > SD version 3.0
> > High Capacity: Yes
> > Capacity: 59.5 GiB
> > Bus Width: 4-bit
> > Erase Group Size: 512 Bytes
> > 
> > But with u-boot 2021.07 (starting with rc1) I get:
> > 
> > > mmc list
> > mmc@7e300000: 2 (SD)
> > 
> > > mmc part
> > MMC Device 0 not found
> > no mmc device at slot 0
> > 
> > > mmc info
> > MMC Device 0 not found
> > no mmc device at slot 0
> > 
> > I have to run
> > 
> > > mmc dev 2
> > 
> > Afterwards 'mmc part' and 'mmc info' show the above output.
> > But how do I boot from mmc dev 2? And how can I change this
> > permanently?
> 
> My RPi3 boots if I run:
> 
> U-Boot> setenv boot_targets 'mmc2'
> U-Boot> setenv bootcmd_mmc2 'devnum=2; run mmc_boot'
> U-Boot> boot
> 
> --
> Herbert
> 

 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.

 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)

 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.

 Cheers,

-- 
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>