From owner-freebsd-arm@FreeBSD.ORG Sun Apr 28 17:03:49 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E060F219 for ; Sun, 28 Apr 2013 17:03:49 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id A708F1D6A for ; Sun, 28 Apr 2013 17:03:48 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r3SH3lVY065841; Sun, 28 Apr 2013 17:03:47 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.123] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id e4mhyj7k7uxfwd89rf9agqp4ta; Sun, 28 Apr 2013 17:03:47 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: BeagleBone Black Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <517CEDBF.3090102@g7iii.net> Date: Sun, 28 Apr 2013 10:03:46 -0700 Content-Transfer-Encoding: 7bit Message-Id: References: <26A08C89-95EA-463D-98C5-A471F8D15C90@freebsd.org> <54A0884D-31D0-4FC6-BBB5-58E3D11050E6@freebsd.org> <77E91A57-7880-4908-8999-6115333F5002@kientzle.com> <517CEDBF.3090102@g7iii.net> To: Iain Young X-Mailer: Apple Mail (2.1283) 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: Sun, 28 Apr 2013 17:03:49 -0000 On Apr 28, 2013, at 2:37 AM, Iain Young wrote: > On 28/04/13 08:13, Tim Kientzle wrote: > >> The 4-pin adapter I got from Adafruit for use with Raspberry Pi seems >> to work just fine, though the CircuitCo documentation has the instructions >> wrong. It should be: >> Black => Pin 1 >> Green => Pin 4 >> White => Pin 5 > > Hurm, I wonder what the other 3 pins are used for. They seem to be > undocumented in the SRM I believe they're unconnected. They're only there for compatibility with the common FTDI TTL-232R-3v3 USB-to-serial adapter that has a 6-pin connector. >> Harumph. Looks like it always boots initially from the eMMC and >> U-Boot then looks at the boot switch to decide whether to continue >> from eMMC or uSD. > > This would appear to be the default behaviour, but can be over-ridden > if I read the SRM correctly. For a one off force to uSD boot, hold down > the "boot" button". See Page 57 of the SRM Tried that, but from watching the serial console, it's still loading U-Boot from the eMMC. It's U-Boot that actually looks at that pin (there are some messages on the serial console about U-Boot inspecting a GPIO pin). >> This sucks: the U-Boot on the eMMC doesn't have ELF support >> nor API support so can't load and boot ubldr. >> >> Short version: The existing FreeBSD images for BeagleBone >> won't work as-is. At a minimum, we'll have to replace the U-Boot >> on the eMMC with one that has ELF and API enabled. I guess >> I'll be spending more quality time with U-Boot. :-/ > > Or wipe the eMMC. In that case, then it appears it boots off > the uSD card next. Yep. Or replace U-Boot on the eMMC, which is what I was hoping to look into today. The model that the BeagleBone seems to use for "installing a new OS" is basically a two-drive model (in essence, the micro-SD is drive 0 and the eMMC is drive 1): * Download an "installer image" to micro-SD. * Boot from that micro-SD/drive 0. * That "installer" copies the OS onto drive 1/eMMC * Reboot from eMMC. Tim