From owner-freebsd-arm@freebsd.org Fri Jan 27 02:27:48 2017 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 B94AFCC3290 for ; Fri, 27 Jan 2017 02:27:48 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 88034F7B for ; Fri, 27 Jan 2017 02:27:47 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from [127.0.0.1] (helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cWwGQ-0000tt-My; Thu, 26 Jan 2017 18:27:47 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id v0R2Rk6u003464; Thu, 26 Jan 2017 18:27:46 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Thu, 26 Jan 2017 18:27:46 -0800 From: Oleksandr Tymoshenko To: =?iso-8859-1?Q?Otac=EDlio?= Cc: "freebsd-arm@freebsd.org" Subject: Re: FreeBSD 12 r312227 dont boots on Beaglebone black Message-ID: <20170127022746.GA3433@bluezbox.com> References: <51d197a2-1332-617a-32a8-9901f474afa2@bsd.com.br> <20170125221350.GA92571@bluezbox.com> <3ad9c97c-e40c-0a37-f603-a08b5a72ebd3@bsd.com.br> <20170127013142.GA2921@bluezbox.com> <13aa921f-b65f-8bf6-f298-ccb286c7ed6e@bsd.com.br> <20170127020035.GA3187@bluezbox.com> <55637733-f4f5-6bcc-1d00-4c4b7d1b1b3d@bsd.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <55637733-f4f5-6bcc-1d00-4c4b7d1b1b3d@bsd.com.br> X-Operating-System: FreeBSD/11.0-RELEASE-p2 (amd64) User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Otacílio (otacilio.neto@bsd.com.br) wrote: > Em 26/01/2017 23:00, Oleksandr Tymoshenko escreveu: > > Otacílio (otacilio.neto@bsd.com.br) wrote: > >> Em 26/01/2017 22:31, Oleksandr Tymoshenko escreveu: > >>> Otacílio (otacilio.neto@bsd.com.br) wrote: > >>>> Em 25/01/2017 19:13, Oleksandr Tymoshenko escreveu: > >>>>> Otacílio (otacilio.neto@bsd.com.br) wrote: > >>>>>> Dears > >>>>>> > >>>>>> I'm trying boot a FreeBSD12-armv6-r312227 > >>>>>> (u-boot-beaglebone-2017.01.00.1) on a beaglebone black. The snapshot > >>>>>> FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170105-r311461.img that I > >>>>>> downloaded from > >>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/12.0/ > >>>>>> works fine, but when I try boot the image that I build on my machine > >>>>>> using crouchet I get: > >>>>>> > >>>>>> U-Boot SPL 2017.01-rc3 (Jan 22 2017 - 23:17:18) > >>>>>> Trying to boot from MMC1MMC partition switch failed > >>>>>> *** Warning - MMC partition switch failed, using default environment > >>>>>> > >>>>>> reading u-boot.img > >>>>>> reading u-boot.img > >>>>>> > >>>>>> And boot stops. Someone can confirm that the revision 312227 is working > >>>>>> fine? > >>>>> I did some digging at the breakage is caused by this commit in U-Boot: > >>>>> https://www.mail-archive.com/u-boot@lists.denx.de/msg234317.html > >>>>> > >>>>> Crochet is using FAT12 for Beaglebone Black. Switching to FAT16 fixes > >>>>> the problem. Try applying this patch to crochet and re-build image: > >>>>> > >>>>> https://people.freebsd.org/~gonzo/patches/crochet-bbb-fat16.diff > >>>>> > >>>> I have applied the patch and now I'm getting this error. Some hints? > >>> FreeBSD uses dtb names that do not match upstream ones. After updating > >>> to 2017.01 that change was lost in progress. Possible workaround (HACK > >>> ALERT!!!) would be to do something like this: > >>> > >>> => setenv findfdt 'setenv fdtfile beaglebone-black.dtb' > >>> => saveenv > >>> > >>> Copy-paste to U-Boot serial console does not work for me on BBB, so > >>> you'll have [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: mail-archive.com] -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 02:27:48 -0000 Otacílio (otacilio.neto@bsd.com.br) wrote: > Em 26/01/2017 23:00, Oleksandr Tymoshenko escreveu: > > Otacílio (otacilio.neto@bsd.com.br) wrote: > >> Em 26/01/2017 22:31, Oleksandr Tymoshenko escreveu: > >>> Otacílio (otacilio.neto@bsd.com.br) wrote: > >>>> Em 25/01/2017 19:13, Oleksandr Tymoshenko escreveu: > >>>>> Otacílio (otacilio.neto@bsd.com.br) wrote: > >>>>>> Dears > >>>>>> > >>>>>> I'm trying boot a FreeBSD12-armv6-r312227 > >>>>>> (u-boot-beaglebone-2017.01.00.1) on a beaglebone black. The snapshot > >>>>>> FreeBSD-12.0-CURRENT-arm-armv6-BEAGLEBONE-20170105-r311461.img that I > >>>>>> downloaded from > >>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/12.0/ > >>>>>> works fine, but when I try boot the image that I build on my machine > >>>>>> using crouchet I get: > >>>>>> > >>>>>> U-Boot SPL 2017.01-rc3 (Jan 22 2017 - 23:17:18) > >>>>>> Trying to boot from MMC1MMC partition switch failed > >>>>>> *** Warning - MMC partition switch failed, using default environment > >>>>>> > >>>>>> reading u-boot.img > >>>>>> reading u-boot.img > >>>>>> > >>>>>> And boot stops. Someone can confirm that the revision 312227 is working > >>>>>> fine? > >>>>> I did some digging at the breakage is caused by this commit in U-Boot: > >>>>> https://www.mail-archive.com/u-boot@lists.denx.de/msg234317.html > >>>>> > >>>>> Crochet is using FAT12 for Beaglebone Black. Switching to FAT16 fixes > >>>>> the problem. Try applying this patch to crochet and re-build image: > >>>>> > >>>>> https://people.freebsd.org/~gonzo/patches/crochet-bbb-fat16.diff > >>>>> > >>>> I have applied the patch and now I'm getting this error. Some hints? > >>> FreeBSD uses dtb names that do not match upstream ones. After updating > >>> to 2017.01 that change was lost in progress. Possible workaround (HACK > >>> ALERT!!!) would be to do something like this: > >>> > >>> => setenv findfdt 'setenv fdtfile beaglebone-black.dtb' > >>> => saveenv > >>> > >>> Copy-paste to U-Boot serial console does not work for me on BBB, so > >>> you'll have have to enter these commands > >>> > >>> I will submit update to u-boot ports so all these workarounds will > >>> not be required. > >>> > >> I'm getting this: > >> > >> Type '?' for a list of commands, 'help' for more detailed help. > >> loader> setenv findfdt 'setenv fdtfile beaglebone-black.dtb' > >> Error: stack underflow > >> loader> > > No, setenv/saveenv should be done in u-boot. But this gave me > > an idea. You can also mount root partition on SD card and > > add following line to /boot/loader.conf: > > > > fdt_file="beaglebone-black.dtb" > > > > That should do the trick as well > > > I have added > > fdt_file="bboneblk.dtb" > > (because this is the name that I found on fat partition) to > /boot/loader.conf but still getting No, in this case it's not about what's on FAT it's what in /boot/dtb/ on root partition. That's where loader looks for DTB files. I don't have crochet setup handy right now so can't check end-to-end procedure, but I'll do it tomorrow. > > DRAM: 512MB > Number of U-Boot devices: 3 > U-Boot env: loaderdev not set, will probe all devices. > Found U-Boot device: disk > Probing all disk devices... > Checking unit=0 slice= partition=... good. > Booting from disk0s2a: > /boot/kernel/kernel data=0x609624+0x1a29dc syms=[0x4+0x89070+0x4+0x9d363] > /boot/kernel/geom_label.ko text=0x4de8 data=0x870+0x4 > syms=[0x4+0x12c0+0x4+0x1061] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > No valid device tree blob found! -- gonzo