RPI2 boot failure with recent changes to u-boot

[Ian Lepore]

On Mon, 2017-12-18 at 10:24 -0600, Karl Denninger wrote:
> I recently upgraded my "u-boot" package for RPI2 to the current
> version
> (and grabbed the "rpi-firmware" package it said it needed) and now I
> have no-start on the RPI2....
> 
> U-Boot 2017.09 (Dec 12 2017 - 18:48:47 +0000)
> 
> DRAM:  948 MiB
> RPI 2 Model B (0xa21041)
> MMC:   sdhci at 7e300000: 0
> reading uboot.env
> 
> ** Unable to read "uboot.env" from mmc0:1 **
> Using default environment
> 
> In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   No ethernet found.
> starting USB...
> USB0:   Core Release: 2.80a
> scanning bus 0 for devices... 3 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> Found FreeBSD U-Boot Loader (bin)
> reading ubldr.bin
> 227704 bytes read in 34 ms (6.4 MiB/s)
> ## Starting application at 0x01000000 ...
> 
> And that be all I get.
> 
> This is what I have in board/RaspberryPi2/setup.sh related to that
> (which I had to change since the firmware files have been split
> between
> the two packages)
> 
> raspberry_pi_populate_boot_partition ( ) {
>     # Copy RaspberryPi 2 boot files to FAT partition
>     cp ${FIRMWARE_PATH}/LICENCE.broadcom .
>     cp ${FIRMWARE_PATH}/bootcode.bin .
>     cp ${FIRMWARE_PATH}/config.txt .
>     cp ${FIRMWARE_PATH}/fixup.dat .
>     cp ${FIRMWARE_PATH}/fixup_cd.dat .
>     cp ${FIRMWARE_PATH}/fixup_x.dat .
>     cp ${FIRMWARE_PATH}/start.elf .
>     cp ${FIRMWARE_PATH}/start_cd.elf .
>     cp ${FIRMWARE_PATH}/start_x.elf .
>     cp ${UBOOT_PATH}/u-boot.bin .
>     cp ${UBOOT_PATH}/fixup_db.dat .
>     cp ${UBOOT_PATH}/start_db.elf .
>     cp ${UBOOT_PATH}/README .
> 
>     # RPi firmware loads and modify the DTB before pass it to kernel.
>     freebsd_install_fdt rpi2.dts rpi2.dtb
> 
>     # Install ubldr to FAT partition
>     freebsd_ubldr_copy_ubldr .
> }
> 
> Any ideas on tracking this down?
> 

How recent is your ubldr.bin?  About a week ago in r326752 I committed
the patches from PR 224008, which affects the startup code for
ubldr.bin, so it could possibly be a fix for the problem you're seeing.

(I don't have an rpi2 to test so I can't say for sure.)

-- Ian