Booting FreeBSD from eMMC on BeagleBone Black

Rui Paulo rpaulo at FreeBSD.org
Mon Mar 17 01:33:15 UTC 2014


On 16 Mar 2014, at 14:59, Patrick Kelsey <kelsey at ieee.org> wrote:

> - Improved disk probing support that will now by default find and use the
> first suitable partition among the available storage devices.

I think this introduced a bug where, if you have a non-responsive boot device, ubldr will stop and won't try network booting:

## Starting application at 0x01000054 ...
Consoles: U-Boot console  
Compatible API signature found @1d800a8
Number of U-Boot devices: 2

FreeBSD/armv6 U-Boot loader, Revision 1.2
(rpaulo at zedfs.local, Fri Mar 14 22:35:47 PDT 2014)
DRAM:	 256MB
Unknown device type ''   <------------ this is new
Found U-Boot device: disk
Probing all storage devices...
Checking unit=0 slice=0 partition=-1...disk0: read failed, error=1

Checking unit=1 slice=0 partition=-1...
Checking unit=2 slice=0 partition=-1...
Checking unit=3 slice=0 partition=-1...
Checking unit=4 slice=0 partition=-1...
Checking unit=5 slice=0 partition=-1...

can't load 'kernel'

Type '?' for a list of commands, 'help' for more detailed help.
loader> 

It stops here and doesn't try net0 booting.

--
Rui Paulo





More information about the freebsd-arm mailing list