Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Apr 2013 10:03:46 -0700
From:      Tim Kientzle <tim@kientzle.com>
To:        Iain Young <iain@g7iii.net>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: BeagleBone Black
Message-ID:  <BE864289-8FDA-4223-BB5E-33EFC31AA0A0@kientzle.com>
In-Reply-To: <517CEDBF.3090102@g7iii.net>
References:  <CANuCnH9XP3Jn30EWCuZ0AmQF6MA4q4U9GUB7LU=XXZEdp7ZJ8g@mail.gmail.com> <D74DF146-7E72-4A2A-B74B-A20758010166@kientzle.com> <26A08C89-95EA-463D-98C5-A471F8D15C90@freebsd.org> <BCB14F16-203D-4C9A-8318-4E7DF1F88E17@kientzle.com> <54A0884D-31D0-4FC6-BBB5-58E3D11050E6@freebsd.org> <F01F0BC9-8464-469C-B1FE-D0E6AC217164@freebsd.org> <77E91A57-7880-4908-8999-6115333F5002@kientzle.com> <517CEDBF.3090102@g7iii.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BE864289-8FDA-4223-BB5E-33EFC31AA0A0>