"No valid device tree blob found" error

[Ian Lepore]

On Mon, 2014-02-17 at 10:08 -0300, Luiz Otavio O Souza wrote:
> On 16 February 2014 18:30, Glen Barber <gjb at freebsd.org> wrote:
> > Images for RPI-B and BEAGLEBONE (and I suspect PANDABOARD) are failing
> > to boot this week.
> >
> > The images are built against r261948.  Console messages during boot:
> >
> >   ## Starting application at 0x88000054 ...
> >   Consoles: U-Boot console
> >   Compatible API signature found @9f242240
> >   MMC Device 2 not found
> >   MMC Device 3 not found
> >   Number of U-Boot devices: 2
> >
> >   FreeBSD/armv6 U-Boot loader, Revision 1.2
> >   (root at grind.freebsd.org, Sun Feb 16 18:10:43 UTC 2014)
> >   DRAM:    512MB
> >
> >   Device: disk
> >   Loading /boot/defaults/loader.conf
> >   /boot/kernel/kernel data=0x460bc8+0x2c7438
> >   syms=[0x4+0x85a60+0x4+0x50c89]
> >
> >   Hit [Enter] to boot immediately, or any other key for command prompt.
> >   Booting [/boot/kernel/kernel]...
> >   Using DTB provided by U-Boot.
> >   No valid device tree blob found!WARNING! Trying to fire up the kernel,
> >   but no device tree blob found!
> >
> > Any ideas if this is error on my part, or a problem in head/ ?  The
> > stable/10/ images boot fine, so I do not suspect any code changes in the
> > build process.
> >
> 
> 
> Glen,
> 
> I think it is related to r261819. Looking at the code it looks like
> the attached patch may fix it (i'm still updating my images to the
> latest -head and would probably need a few hours before i can test it
> myself).
> 
> Can you check if it works for you ?
> 
> Thanks,
> 
> Luiz

I believe your patch is correct; when I copied the code to do the header
check it came from a context where the header variable was the struct
itself, not a pointer to it.  Odd that the error message doesn't seem to
match, though.

-- Ian