From owner-freebsd-arm@FreeBSD.ORG Mon Feb 17 19:11:54 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 050DB234; Mon, 17 Feb 2014 19:11:54 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C9C3116BB; Mon, 17 Feb 2014 19:11:53 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WFTbX-000MkI-Az; Mon, 17 Feb 2014 19:11:47 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s1HJBiID027813; Mon, 17 Feb 2014 12:11:44 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/C2xiVIugc5HDNWW+g7Je8 Subject: Re: "No valid device tree blob found" error From: Ian Lepore To: Luiz Otavio O Souza In-Reply-To: References: <20140216213001.GF1667@glenbarber.us> <20140216213152.GG1667@glenbarber.us> Content-Type: text/plain; charset="us-ascii" Date: Mon, 17 Feb 2014 12:11:44 -0700 Message-ID: <1392664304.1145.21.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Glen Barber , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Feb 2014 19:11:54 -0000 On Mon, 2014-02-17 at 16:03 -0300, Luiz Otavio O Souza wrote: > On 16 February 2014 18:31, Glen Barber wrote: > > On Sun, Feb 16, 2014 at 04:30:01PM -0500, Glen Barber 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@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. > >> > > > > Correction: RPI-B fails to boot. BEAGLEBONE boots after pressing 'q' > > when this message is displayed. > > > > Glen > > > > > Yeah, i had noted this difference already (and forgot to ask about it...). > > It works on BEAGLEBONE because the BEAGLEBONE kernel still has the > FDT_DTB_STATIC option. > > I have booted mine without the static dtb blob included in kernel > without any issue (using crochet images - other images which doesn't > use ubldr may be broken by this change). > > If you guys think it is appropriate i can ask to commit the attached patch. > > Luiz I think it's a good idea to leave the static dtb compiled in on platforms where it'll work. The code in initarm() tries to use the dtb passed in by ubldr or by u-boot using the linux boot abi, and only falls back to the static one if those aren't available. -- Ian