Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Jul 2015 09:56:59 -0700
From:      Tim Kientzle <tim@kientzle.com>
To:        Hans Petter Selasky <hps@selasky.org>
Cc:        Glen Barber <gjb@freebsd.org>, Carl Johnson <carlj@peak.org>, freebsd-arm@freebsd.org
Subject:   Re: RPi won't boot 10.2-BETA1 -- SOLVED
Message-ID:  <81706BBF-04D6-4F5D-8EA3-C6E737ECE72E@kientzle.com>
In-Reply-To: <55A6D121.6000403@selasky.org>
References:  <87wpy41zjt.fsf@elk.localnet> <87y4iiyt29.fsf@elk.localnet> <20150715040109.GV15828@FreeBSD.org> <55A6D121.6000403@selasky.org>

next in thread | previous in thread | raw e-mail | index | archive | help

> On Jul 15, 2015, at 2:31 PM, Hans Petter Selasky <hps@selasky.org> =
wrote:
>=20
> I'm seeing the same problem with RPI-B:
>=20
> U-Boot 2013.01-rc1 (Jul 05 2015 - 05:09:50)
>=20
> DRAM:  224 MiB
> WARNING: Caches not enabled
> MMC:   bcm2835_sdhci: 0
> ** Partition 1 not valid on device 0 **
> Failed to register mmc0:1
> Using default environment
>=20
> In:    serial
> Out:   lcd
> Err:   lcd
> mbox: Timeout waiting for response
> bcm2835: Could not set USB power state
> Net:   Net Initialization Skipped
> No ethernet found.
> ** Unrecognized filesystem type **
> Hit any key to stop autoboot:  0
> Booting from: mmc 0 ubldr
> ** Unrecognized filesystem type **
> U-Boot>
>=20
> With multiple SD cards. How can this be solved?

This is coming from U-Boot:

  * AFTER the RPi firmware has loaded from the SD card.
So the SD card is working in some sense and the format
and partitioning is sufficient for the firmware to load.

  * BEFORE any part of FreeBSD proper is involved.

This suggests one of the following:

  * A partitioning problem that is causing U-Boot to not recognize the =
filesystem.  Note this would cause the image to fail on all SD cards, =
not just some.

  * A U-Boot bug or other problem with the U-Boot port.  This could lead =
to erratic behavior depending on the nature of the bug.

  * A hardware problem of some sort.  In particular, RPi is known to be =
sensitive to power supply issues, especially during the boot sequence.

Debugging U-Boot is rather tedious.  Best bet is to put lots of print =
statements in the section of U-Boot code leading up to the =
=E2=80=9Cunrecognized filesystem type=E2=80=9D to try to dig out more =
information.

Tim




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?81706BBF-04D6-4F5D-8EA3-C6E737ECE72E>