Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Oct 2019 17:53:37 +0000
From:      Glen Barber <gjb@freebsd.org>
To:        Emmanuel Vadot <manu@bidouilliste.com>
Cc:        Mike Karels <mike@karels.net>, freebsd-arm@freebsd.org
Subject:   Re: FreeBSD 12.1-BETA3 won't boot on Beaglebone Black
Message-ID:  <20191008175337.GX27491@FreeBSD.org>
In-Reply-To: <20191008192123.f62ef00d8760a68cfc4006a6@bidouilliste.com>
References:  <20191007093947.69ae5d772ebedfc1e1c98328@bidouilliste.com> <201910080102.x98127Jk048407@mail.karels.net> <20191008153417.GQ27491@FreeBSD.org> <20191008155404.GU27491@FreeBSD.org> <20191008192123.f62ef00d8760a68cfc4006a6@bidouilliste.com>

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

--u4YTXYx8N/vaYnQM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 08, 2019 at 07:21:23PM +0200, Emmanuel Vadot wrote:
> On Tue, 8 Oct 2019 15:54:04 +0000
> Glen Barber <gjb@freebsd.org> wrote:
>=20
> > On Tue, Oct 08, 2019 at 03:34:17PM +0000, Glen Barber wrote:
> > > On Mon, Oct 07, 2019 at 08:02:07PM -0500, Mike Karels wrote:
> > > > >  Hi,
> > > >=20
> > > > > On Sun, 06 Oct 2019 10:02:32 -0500
> > > > > Mike Karels <mike@karels.net> wrote:
> > > >=20
> > > > > > [bcc to freebsd-stable; followups to freebsd-arm]
> > > > > > I am not subscribed to freebsd-arm, please cc me on responses.
> > > > > >=20
> > > > > > My Beaglebone Black does not boot FreeBSD 12.1-BETA3.  It previ=
ously ran
> > > > > > 11.3 and 12.0 without problems.  The initial boot from micro SD=
 gets to
> > > > > > this point [with some preceding lines as well; note that the "s=
upport
> > > > > > voltages" line does not appear on 12.0]:
> > > > > >=20
> > > > > > sdhci_ti1: <TI MMCHS (SDHCI 2.0)> mem 0-0xfff irq 48 on ti_sysc=
35
> > > > > > sdhci_ti1-slot0: Hardware doesn't report any support voltages.
> > > > > > mmc1: <MMC/SD bus> on sdhci_ti1
> > > > > > ...
> > > > > > mmcsd0: 16GB <SDHC SD    0.2 SN 00335010 MFG 11/2017 by 116 J`>=
 at mmc0 48.0MHz/4bit/65535-block
> > > > > > iicbus1: <OFW I2C bus> on iichb1
> > > > > > iic1: <I2C generic I/O> on iicbus1
> > > > > > icee1: <AT24C256> at addr 0xa8 on iicbus1
> > > > > > icee2: <AT24C256> at addr 0xaa on iicbus1
> > > > > > icee3: <AT24C256> at addr 0xac on iicbus1
> > > > > > icee4: <AT24C256> at addr 0xae on iicbus1
> > > > > > sdhci_ti1-slot0: Bus power failed to enable
> > > > > > uhub0: 1 port with 1 removable, self powered
> > > > > > uhub1: 1 port with 1 removable, self powered
> > > > > > sdhci_ti1-slot0: Controller timeout
> > > > > > sdhci_ti1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D REG=
ISTER DUMP =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > > > > sdhci_ti1-slot0: Sys addr: 0x00000000 | Version:  0x00003101
> > > > > > sdhci_ti1-slot0: Blk size: 0x00000000 | Blk cnt:  0x00000000
> > > > > > sdhci_ti1-slot0: Argument: 0x00000000 | Trn mode: 0x00000000
> > > > > > sdhci_ti1-slot0: Present:  0x01f70000 | Host ctl: 0x00000000
> > > > > > sdhci_ti1-slot0: Power:    0x00000000 | Blk gap:  0x00000000
> > > > > > sdhci_ti1-slot0: Wake-up:  0x00000000 | Clock:    0x00008007
> > > > > > sdhci_ti1-slot0: Timeout:  0x00000000 | Int stat: 0x00000000
> > > > > > sdhci_ti1-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb
> > > > > > sdhci_ti1-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000
> > > > > > sdhci_ti1-slot0: Caps:     0x04e10080 | Caps2:    0x00000000
> > > > > > sdhci_ti1-slot0: Max curr: 0x00000000 | ADMA err: 0x00000000
> > > > > > sdhci_ti1-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000
> > > > > > sdhci_ti1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> > > > > >=20
> > > > > > and then the timeout and dumps repeat every few seconds.
> > > > > >=20
> > > > > > This board cannot boot from the on-board EMMC, which seems to b=
e at issue
> > > > > > here, but it can access it under FreeBSD.
> > > > > >=20
> > > > > > The full boot transcript follows.  The "bad CRC" errors show up=
 on 12.0
> > > > > > as well.
> > > > > >=20
> > > > > > 		Mike
> > > > > >=20
> > > >=20
> > > > >  I thought that the issue was solved but it seems that there is s=
till
> > > > > some weird shit happening. Here's what's working :
> > > >=20
> > > > >  - Booting from SDcard with eMMC formated
> > > > >  - Booting from eMMC without an sdcard inserted
> > > > >  - Booting from eMMC with an sdcard inserted (no sdcard-boot butt=
on
> > > > > press)
> > > >=20
> > > > >  What's not working is booting from SDcard by pressing the button=
 (to
> > > > > force sdcard boot).=20
> > > > > To me it's clearly some u-boot or bootrom problem
> > > > > but maybe I'm wrong.=20
> > > >=20
> > > > > So if you boot from the sdcard but have u-boot on the eMMC so can=
 do :
> > > >=20
> > > > >  1) First confirmed that you booted off the SDCard, you should se=
e=20
> > > > > U-Boot SPL 2019.07 (Sep 27 2019 - 15:17:40 +0000)
> > > > > Trying to boot from MMC1
> > > >=20
> > > > >  MMC1 is the sdcard while MMC2 is the eMMC
> > > >=20
> > > > >  2) Interrupt u-boot autoboot by pressing any key
> > > > >  3) Confirm that you have u-boot files on the eMMC by doing
> > > > > =3D> fatls mmc 1
> > > > >             EFI/
> > > > >    106148   MLO
> > > > >             dtb/
> > > > >    700756   u-boot.img
> > > > >    364264   ubldr.bin
> > > > >  MLO is the file that we want to delete.
> > > > >  4) Delete MLO file=20
> > > > > =3D> fatrm mmc 1 MLO
> > > > >  5) Confirm that it was deleted
> > > > > =3D> fatls mmc 1   =20
> > > > >             EFI/
> > > > >             dtb/
> > > > >    700756   u-boot.img
> > > > >    364264   ubldr.bin
> > > >=20
> > > > >  Power cycle the board so you can boot from 12.1 sdcard image and=
 update
> > > > > your eMMC (or whatever you want to do).
> > > >=20
> > > > Thanks.  I tried that, and the results are still the same.  I verif=
ied
> > > > after booting 12.0 again that the eMMC's MLO is gone.  The ufs file=
system
> > > > on the eMMC had been reused as swap for an experiment, and I restor=
ed a
> > > > valid filesystem just in case; unsurprisingly, that didn't matter.
> > > > The console output is appended again.
> > > >=20
> > > > Any suggestions?  I see that there was a DTS fix, but I have no idea
> > > > if that could be related.
> > > >=20
> > >=20
> > > I don't recall seeing an issue so far with 12.1, but I'll double check
> > > that I tested the right card.  In the meantime, what class is your SD
> > > card?  I have seen issues with some SD cards on a few different SoCs
> > > where certain classes (i.e., 4) are too slow for some boards, and hig=
her
> > > classes (i.e., 10) are too fast for others.
> > >=20
> >=20
> > I re-tested 12.1-BETA3 on my BeagleBone Black, and do not see any boot
> > failures.  This is with a class 10 SD card.
> >=20
> > Glen
> >=20
>=20
>  Even when using the button to force booting from sdcard ?
>=20

Huh.  Yeah, I do see 'sdhci_ti1-slot0: Controller timeout' when using
the button.

Glen


--u4YTXYx8N/vaYnQM
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAl2czR0ACgkQAxRYpUeP
4pNnwA//b1QK3Th4J8EzgOxTwRUlZiUAqCjnagMUnKUznLMK6QltTGq98cvTAjBW
Lpf3Wjs7BjA+iLT9eHrnB86NMsAUtpo3Afykbhr9C3B15Pzr38tnuU6uei+xrKXE
giH7da7da5JwjZZc7qBEtca2KLuQb8TNJeATyq4vISZZndRFgwGESqTVWoLUit74
3sAbN4tDUtmnt54R3KIF02puCRg798IwZkh64YD+Q88FefpImXVgGLBIfnqRauNY
x0yWe8/iHI3NjfAohTrYb4lQyb8ERr9TH0u63LNB4cTal+b0aQVg4VgKvVNiPiGC
/e64f1dcv0AT+Vbjc3SHjlJeKUuV/+rVB6VuRUhK69r410bRIfN3gnykzdCUR266
8XNMoUxQU7zFKGW+LWXJTDoxYGv30FQKgWca/iFo6ke7RlnGskPMmXg6GOAVyXhd
biX8RbXTdvGK1Jh6W/0CwBwkWC0tAaQE28ImVQWRrIfX3wtJnBZWVtT87QF1+fV9
OSvEXtWT82TGXcIV9k6Qv9q2BxvDxfJMMvwBh0xqK6+pKVKbcz6U+tj/07M2MUMl
Rs3PTYG4CaIQ5jWThYnSZsb0I9W/Sfs2qzrcT/g4BNhYbAsozkPRwvH1dBGhDs5U
tpsq/OKcx+cKe5PsFh86O4nw70FkNdMx451R6/DihxjB1oeG2HQ=
=S8VB
-----END PGP SIGNATURE-----

--u4YTXYx8N/vaYnQM--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191008175337.GX27491>