From owner-freebsd-arm@freebsd.org Tue Jul 14 19:09:14 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C158B9A13CC for ; Tue, 14 Jul 2015 19:09:14 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 945D21439 for ; Tue, 14 Jul 2015 19:09:14 +0000 (UTC) (envelope-from tim@kientzle.com) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t6EJ9MGE093806; Tue, 14 Jul 2015 19:09:22 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.100] (192.168.1.101 [192.168.1.101]) by kientzle.com with SMTP id hziqm5dkfw4pynirh8b2qmqtye; Tue, 14 Jul 2015 19:09:22 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: RPi won't boot 10.2-BETA1 From: Tim Kientzle In-Reply-To: <1436808326.55378.YahooMailBasic@web120802.mail.ne1.yahoo.com> Date: Tue, 14 Jul 2015 12:09:06 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <1436808326.55378.YahooMailBasic@web120802.mail.ne1.yahoo.com> To: Leonardo Fogel X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 19:09:14 -0000 > On Jul 13, 2015, at 10:25 AM, Leonardo Fogel = wrote: >=20 >> Does anybody see what I am missing here? Thanks for any suggestions. >=20 > I've got a similar error trying to boot the BBB image. As I understand = it, the image itself is broken. > On the U-Boot> prompt, you can type the command 'fatls mmc 0' to list = the FAT content. You'll see there isn't any kernel image, FreeBSD images boot ubldr from U-Boot. ubldr then loads the kernel from UFS. It's easier to chain-load through FreeBSD=E2=80=99s loader than to teach U-Boot how to configure the FreeBSD kernel. ubldr is basically just FreeBSD=E2=80=99s loader(8) except that it is designed to boot from a system using U-Boot rather than a system running a PC BIOS. It knows how to read configuration files from UFS that can be used to load modules and otherwise configure the kernel before it boots. ubldr also knows how to read the kernel and FDT from UFS, which simplifies upgrades. (There are variations, of course. On RPi and RPi2, the FDT is actually read from FAT by the RPi firmware before U-Boot loads. The firmware adjusts the FDT which is then accessed at a known position in memory by U-Boot, ubldr, and the kernel.) Yes, this is different from other systems: U-Boot knows how to read e2fs and how to configure a Linux kernel, so an additional boot stage is unnecessary. Other systems forego boot-time configuration entirely. > the filenames are not in the "canonical" form, and I=E2=80=99m not sure what you mean by this. > (BB-)uEnv.txt is empty. An empty uEnv.txt is expected. You can put U-Boot commands there if you need to customize U-Boot operation. Most people don=E2=80=99t. If it=E2=80=99s missing, then U-Boot prints some warnings, so = distributions typically put an empty file there. Tim