From owner-freebsd-arm@freebsd.org Tue Oct 8 15:54:18 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 19EB712E9B1 for ; Tue, 8 Oct 2019 15:54:18 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46nhjj72sMz49bF; Tue, 8 Oct 2019 15:54:17 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 9D8AF2D7F; Tue, 8 Oct 2019 15:54:14 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Tue, 8 Oct 2019 15:54:04 +0000 From: Glen Barber To: Mike Karels Cc: Emmanuel Vadot , freebsd-arm@freebsd.org Subject: Re: FreeBSD 12.1-BETA3 won't boot on Beaglebone Black Message-ID: <20191008155404.GU27491@FreeBSD.org> References: <20191007093947.69ae5d772ebedfc1e1c98328@bidouilliste.com> <201910080102.x98127Jk048407@mail.karels.net> <20191008153417.GQ27491@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tpcaav3s83TeuU58" Content-Disposition: inline In-Reply-To: <20191008153417.GQ27491@FreeBSD.org> User-Agent: Mutt/1.12.1 (2019-06-15) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2019 15:54:18 -0000 --tpcaav3s83TeuU58 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 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 previousl= y ran > > > > 11.3 and 12.0 without problems. The initial boot from micro SD get= s to > > > > this point [with some preceding lines as well; note that the "suppo= rt > > > > voltages" line does not appear on 12.0]: > > > >=20 > > > > sdhci_ti1: mem 0-0xfff irq 48 on ti_sysc35 > > > > sdhci_ti1-slot0: Hardware doesn't report any support voltages. > > > > mmc1: on sdhci_ti1 > > > > ... > > > > mmcsd0: 16GB at = mmc0 48.0MHz/4bit/65535-block > > > > iicbus1: on iichb1 > > > > iic1: on iicbus1 > > > > icee1: at addr 0xa8 on iicbus1 > > > > icee2: at addr 0xaa on iicbus1 > > > > icee3: at addr 0xac on iicbus1 > > > > icee4: 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 REGISTE= R 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 be 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 still > > > 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 button > > > 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 see=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 upd= ate > > > your eMMC (or whatever you want to do). > >=20 > > Thanks. I tried that, and the results are still the same. I verified > > after booting 12.0 again that the eMMC's MLO is gone. The ufs filesyst= em > > on the eMMC had been reused as swap for an experiment, and I restored 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 higher > classes (i.e., 10) are too fast for others. >=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. Glen --tpcaav3s83TeuU58 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAl2csRwACgkQAxRYpUeP 4pNFag/9Ec1fraEy7bMr1cJ0PlURtUTzehIv5gzHqIhIsFlyp2A9468dX0FTvqjz iyVeaBfRLnVifp6DCqSNytkc9pA9OJIdWwSJv5YdvdK/O2h+QXwxXlVLFtqBuLNQ qrzu/jujmG0ddIoqw/G6KFCcmhX+xG7nLrNdu0ZVEnBQGMSx/AcMfNB34iolrpNS jxuh4qA2FO8LMV4TLJUNXIWn6z1euRvPJZRB/2zDxWtKvict8lpcdI+pHLvAKfGD IMVtZTslkacfSIExybbmHI0O+/Ok2/4yW4fxIqiH3+pdZZiaJwthmutEVv8V9IGO 8Hkir2WSzfvayiwjKOfA7x6NRHLYoLoyhdtdekLrodhSipQRV1+hE025ahWFYhBr 6wgmWetBl3927AkqnOpRLnaR2fP3wNAdOE+fdIwVoMfv5Mc2gkfpmBfLtxLIMQod POHXQBoLQUAkysors3fAjsiQJBgCjM/vgRoLSQB3BEEBCdCla3khMXEtCn44eFjl l7esCCNHAEx/GrO+FqaqDf2HrIeRnV2j5RzNqmAlZNbz8rGfaMGYpXu0sECp9t0D Y3VeYPwf5P/jw1dOIMEKjeIOtUFleMs3oGshihdYSBFuE5s3i31Uaq6f/V3U0n5n 1IhSgjPBYvzaKaRo+yYplg3L9yJZ8x6ummBhuv2Y+kj+SJ9KKzU= =Hdly -----END PGP SIGNATURE----- --tpcaav3s83TeuU58--