Date: Sat, 4 Mar 2023 08:21:22 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Karl Denninger <karl@denninger.net> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: uBoot broken on RPI2 Model B? Message-ID: <20230304082122.aa28fdf4e18f53fa58618329@bidouilliste.com> In-Reply-To: <a1ce1685-4d82-566e-ec35-a878592ebd0c@denninger.net> References: <a1ce1685-4d82-566e-ec35-a878592ebd0c@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 3 Mar 2023 16:12:48 -0500 Karl Denninger <karl@denninger.net> wrote: > Just tried to build -13STABLE for the RPi2 and ran into this (I'm using=20 > Crochet and have had to make some changes to the board-specific files,=20 > but it appears the problem that results in it not working is in uboot;=20 > I've made a number of changes since it looks like the system now wants=20 > to boot off EFI as opposed to what worked in -12, which would be ok if=20 > it can find the boot device -- I think (may be wrong here) >=20 > U-Boot 2023.01 (Jan 26 2023 - 04:25:18 +0000) >=20 > DRAM:=A0 948 MiB > RPI 2 Model B (0xa21041) > Core:=A0 70 devices, 13 uclasses, devicetree: board > MMC:=A0=A0 mmc@7e300000: 1 > Loading Environment from FAT... ** Bad device specification mmc 0 ** > In:=A0=A0=A0 serial > Out:=A0=A0 vidconsole > Err:=A0=A0 vidconsole > Net:=A0=A0 No ethernet found. > starting USB... > Bus usb@7e980000: USB DWC2 > scanning bus usb@7e980000 for devices... 3 USB Device(s) found > =A0=A0=A0=A0=A0=A0 scanning usb for storage devices... 0 Storage Device(= s) found > Hit any key to stop autoboot:=A0 0 > U-Boot> >=20 > Needless to say if I let it try to continue it fails as it can't find=20 > the SD card and "mmc dev" shows nothing present. >=20 > Obviously going to dig into this further myself but I recalled something= =20 > about this uBoot version being broken on older Pis... >=20 > The layout of the disk on the boot partition is thus: >=20 > root@NewFS:/mnt # ls -la > total 12679 > drwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0 16384 Dec 31=A0 1979 . > drwxr-xr-x=A0 35 root=A0 wheel=A0=A0=A0=A0=A0=A0 42 Jan 20 10:16 .. > drwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0=A0 4096 Feb 13 11:09 EFI > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0=A0=A0 709 Feb 13 11:09 README > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0 26745 Feb 13 11:09 bcm2709-rpi-= 2-b.dtb > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0 52456 Feb 13 11:09 bootcode.bin > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0=A0=A0 141 Feb 13 11:09 config.t= xt > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0=A0 7314 Feb 13 11:09 fixup.dat > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0=A0 3187 Feb 13 11:09 fixup_cd.d= at > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0 10298 Feb 13 11:09 fixup_db.dat > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0 10298 Feb 13 11:09 fixup_x.dat > drwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0 20480 Feb 13 11:09 overlays > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0=A0 21169 Feb 13 11:09 rpi2.dtb > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0 2952960 Feb 13 11:09 start.elf > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0 793116 Feb 13 11:09 start_cd.elf > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0 4794472 Feb 13 11:09 start_db.elf > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0 3704808 Feb 13 11:09 start_x.elf > -rwxr-xr-x=A0=A0 1 root=A0 wheel=A0=A0 521916 Feb 13 11:09 u-boot.bin >=20 > root@NewFS:/mnt # ls -laR EFI > total 24 > drwxr-xr-x=A0 1 root=A0 wheel=A0=A0 4096 Feb 13 11:09 . > drwxr-xr-x=A0 1 root=A0 wheel=A0 16384 Dec 31=A0 1979 .. > drwxr-xr-x=A0 1 root=A0 wheel=A0=A0 4096 Feb 13 11:09 BOOT >=20 > EFI/BOOT: > total 140 > drwxr-xr-x=A0 1 root=A0 wheel=A0=A0=A0 4096 Feb 13 11:09 . > drwxr-xr-x=A0 1 root=A0 wheel=A0=A0=A0 4096 Feb 13 11:09 .. > -rwxr-xr-x=A0 1 root=A0 wheel=A0 133812 Feb 13 11:09 bootarm.efi >=20 > root@NewFS:/mnt # more config.txt > init_uart_clock=3D3000000 > enable_uart=3D1 > kernel=3Du-boot.bin > kernel7=3Du-boot.bin > dtoverlay=3Dmmc > audio_pwm_mode=3D2 > dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don >=20 > root@NewFS:/mnt # ls -la overlays | grep mmc > -rwxr-xr-x=A0 1 root=A0 wheel=A0=A0=A0 1221 Feb 13 11:09 mmc.dtbo >=20 > Which I BELIEVE should work -- assuming that I can get "see" the SD card= =20 > from u-boot that is.... >=20 > Installed rpi-related packages: >=20 > root@NewFS:/mnt # pkg info|grep rpi > rpi-firmware-1.20210303.g20210303 Firmware for RaspberryPi Single Board=20 > Computer > u-boot-rpi2-2023.01=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Cross-build das u-bo= ot for model rpi2 > u-boot-rpi3-2023.01=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Cross-build das u-bo= ot for model rpi3 > u-boot-rpi4-2023.01=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Cross-build das u-bo= ot for model rpi4 >=20 > --=20 > Karl Denninger > karl@denninger.net > /The Market Ticker/ > /[S/MIME encrypted email preferred]/ I would not be the first time that a u-boot update break booting on a board. I didn't test on RPI* the last two (or three) update. Just to be sure could you test the official image ? Latest armv7 14-CURRENT snapshot should have the last u-boot. Cheers, --=20 Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230304082122.aa28fdf4e18f53fa58618329>