From owner-freebsd-arm@FreeBSD.ORG Tue Feb 19 11:24:02 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 198B9112 for ; Tue, 19 Feb 2013 11:24:02 +0000 (UTC) (envelope-from werner@thieprojects.ch) Received: from newton.metanet.ch (newton.metanet.ch [80.74.158.130]) by mx1.freebsd.org (Postfix) with ESMTP id 83EE26E9 for ; Tue, 19 Feb 2013 11:24:00 +0000 (UTC) Received: (qmail 15812 invoked from network); 19 Feb 2013 12:23:59 +0100 Received: from 217-071-083-008.ip-tech.ch (HELO ?192.168.11.88?) (217.71.83.8) by newton.metanet.ch with (DHE-RSA-AES256-SHA encrypted) SMTP; 19 Feb 2013 12:23:59 +0100 Message-ID: <512360D0.6020709@thieprojects.ch> Date: Tue, 19 Feb 2013 12:24:00 +0100 From: Werner Thie User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: Re: RPi hangs in bootloader References: <51227033.3070304@thieprojects.ch> <5123427E.4030607@thieprojects.ch> In-Reply-To: <5123427E.4030607@thieprojects.ch> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2013 11:24:02 -0000 Hi top posting in this case: The error is not in the log file, its spelled out on the console when building the image: : Partitioning the raw disk image at Tue Feb 19 07:35:07 CET 2013 md2 created Setting up boot partition Creating the FAT partition at Tue Feb 19 07:35:07 CET 2013 md2s1 added active set on md2s1 Mounting the virtual FAT partition beaglebsd.sh: dtc: not found Installing ubldr : After cloning anew from https://github.com/kientzle/freebsd-beaglebone.git It seems that in the case of the RPi build the dtc is not compiled anymore. My suspicion was right then, it all ends with a file amiss. With two places in the scripts which supposedly should/will build the devtree.dat file (one in board/RaspberryPi/setup.sh and the other in lib/freebsd.sh) it should now be possible to find out what's going wrong. Thxs for listening, Werner On 2/19/13 10:14 AM, Werner Thie wrote: > Hi > > now retracing the generated configuration which was autogenerated from > Tim Kientzle's scripts: > > Content of the FAT boot partition: > > 20 -rwxr-xr-x 1 root wheel 17764 Feb 18 17:57 bootcode.bin > 4 -rwxr-xr-x 1 root wheel 105 Feb 18 17:57 config.txt > 8 -rwxr-xr-x 1 root wheel 5284 Feb 18 17:57 fixup.dat > 4 -rwxr-xr-x 1 root wheel 2018 Feb 18 17:57 fixup_cd.dat > 16 -rwxr-xr-x 1 root wheel 16032 Feb 18 17:57 loader.hel > 2300 -rwxr-xr-x 1 root wheel 2353656 Feb 18 17:57 start.elf > 516 -rwxr-xr-x 1 root wheel 526828 Feb 18 17:57 start_cd.elf > 240 -rwxr-xr-x 1 root wheel 242830 Feb 18 17:57 ubldr > 308 -rwxr-xr-x 1 root wheel 312848 Feb 18 17:57 uboot.img > 4 -rwxr-xr-x 1 root wheel 170 Feb 18 17:57 uenv.txt > > Content of uEnv.txt: > > loadbootscript=fatload mmc 0 0x2000000 ubldr > bootscript=bootelf 0x2000000 > > Content of config.txt: > > device_tree=devtree.dat > device_tree_address=0x100 > > Content of /boot partition: > > 4 drwxr-xr-x 7 root wthie 512 Feb 18 18:03 . > 4 drwxr-xr-x 18 wthie wthie 1024 Feb 18 17:58 .. > 4 drwxr-xr-x 2 root wheel 512 Feb 18 17:57 defaults > 4 drwxr-xr-x 2 root wheel 512 Feb 18 17:57 firmware > 4 drwxr-xr-x 2 root wheel 512 Feb 18 17:57 kernel > 16 -r--r--r-- 1 root wheel 16032 Feb 18 17:58 loader.help > 4 -rw-r--r-- 1 root wthie 15 Feb 18 18:03 loader.rc > 4 drwxr-xr-x 2 root wheel 512 Feb 18 17:57 modules > 192 -r-xr-xr-x 1 root wheel 195172 Feb 18 17:58 ubldr > 4 drwxr-xr-x 2 root wheel 512 Feb 18 17:57 zfs > > Content of /boot/loader.rc: > > fdt addr 0x100 > > The only thing which does not seem to fit is the mentioning of the file > devtree.dat, which is nowhere to be found. Also, no log file in the work > directory is referring to devtree.dat, which seems quite fishy to me. > > I cloned a fresh version of uboot as advised by Tim's script, according > to git the u-boot-rpi is up to date, no changes made on my side. > > In freebsd-beaglebone/u-boot-rpi > git describe --tags > > loadb_works-2174-g6709570 > > That's about the end of my analysis, I'm stumped again. > > Werner > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"