From owner-freebsd-arm@FreeBSD.ORG Wed Dec 26 06:07:53 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CC3308A9 for ; Wed, 26 Dec 2012 06:07:53 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id 65ABA8FC13 for ; Wed, 26 Dec 2012 06:07:53 +0000 (UTC) Received: from [207.6.254.8] (helo=[192.168.1.67]) by id.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1Tnk9a-0006wv-JB; Tue, 25 Dec 2012 22:07:52 -0800 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Raspberry Pi questions From: Oleksandr Tymoshenko In-Reply-To: Date: Tue, 25 Dec 2012 22:07:28 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <2E70584E-598E-4D3A-9B2B-6E5FB19A506C@bluezbox.com> References: <1356466883.1144.8.camel@revolution.hippie.lan> <08125E73-C46A-4DDF-BFD8-59D5B86136B8@bluezbox.com> <1356476778.1144.20.camel@revolution.hippie.lan> <0F630E03-7A0C-4D56-A580-C7A9ABD2CB0C@bluezbox.com> <1356479705.1144.23.camel@revolution.hippie.lan> To: Tim Kientzle X-Mailer: Apple Mail (2.1499) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2012-12-25, at 9:57 PM, Tim Kientzle wrote: > On Dec 25, 2012, at 3:55 PM, Ian Lepore wrote: >>>> >>>> This is so close to working. > > I know what you mean…. > > I've almost got my scripts building bootable RPi images now using > the new boot sequence that Oleksandr's been working on. > > There's clearly been a huge amount of progress: memory config > now works, the HDMI video console works. > > But I am still having a few inexplicable issues: > > 1) Building U-Boot. > > I'm trying to build U-Boot from the sources at > github.com/gonzoua/u-boot-pi.git > They build but the result won't boot. Can anyone > point me to the U-Boot sources that do work? For > now, I'm using the binary blob that Oleksandr built. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -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] Cc: freebsd-arm@freebsd.org 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: Wed, 26 Dec 2012 06:07:53 -0000 On 2012-12-25, at 9:57 PM, Tim Kientzle wrote: > On Dec 25, 2012, at 3:55 PM, Ian Lepore wrote: >>>>=20 >>>> This is so close to working. >=20 > I know what you mean=85. >=20 > I've almost got my scripts building bootable RPi images now using > the new boot sequence that Oleksandr's been working on. >=20 > There's clearly been a huge amount of progress: memory config > now works, the HDMI video console works. >=20 > But I am still having a few inexplicable issues: >=20 > 1) Building U-Boot. >=20 > I'm trying to build U-Boot from the sources at > github.com/gonzoua/u-boot-pi.git > They build but the result won't boot. Can anyone > point me to the U-Boot sources that do work? For > now, I'm using the binary blob that Oleksandr built. u-boot.bin should be post-processed by this tool: https://github.com/raspberrypi/tools/tree/master/mkimage The rest file is proper binary to be booted by Raspberry Pi firmware. >=20 > 2) Random failure to mount root. >=20 > This is weird. If I insert the SD card into my Mac and open > the MSDOS partition, then eject, the card will boot (sort of, > see below). Otherwise, the kernel can't mount root. I'm > entirely baffled. Never heard of it before :( could you provide full dmesg for failed=20= mountroot? >=20 > 3) Doesn't quite make it to multi-user. >=20 > When root does mount, it goes through the init > scripts (generates SSH keys, etc), then prints the > date and time and stops. I know the kernel is running > since I get insert/removal messages if I plug/unplug a > keyboard, but getty never seems to launch on either > HDMI or serial console. Daisuke Aoyama posted patch that I believe should fix this problem. The = root cause for it is that timer setup is interrupted and as a result - timer = never gets fired. So system stuck waiting for interrupt. If you boot with serial = console - pressing any key will generate UART interrupt and system will go out of=20= freeze. I'm planning on merging this patch soon.=20=