From owner-freebsd-arm@freebsd.org Fri Aug 10 03:02:50 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA78B1056FE4 for ; Fri, 10 Aug 2018 03:02:50 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic305-22.consmr.mail.ne1.yahoo.com (sonic305-22.consmr.mail.ne1.yahoo.com [66.163.185.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 649EF74646 for ; Fri, 10 Aug 2018 03:02:50 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: ipnRuygVM1lZJWP.dy7TvNdCCrMpA_b6S4hMBX_fm.pVQvDVAgMYOev1qCR7zc. 8BKLmWCnoQZMuxoSNhnmeXcjlfaBJrP3eN.rchmyL9KzbaRKkUEUcN9tHzRt1LxzCo9ZgvlAndfP 3HG.YaxPhxLYAI8__oAgsVeC61U6TkDi7RKgNWkAvQyAV.N1gtr2Fab_lg5yJC9wvWbCuglIKThA IlrnjuROWfefHEuraTEyMp8Tguqp_khESwaJ4CB3gYzl_Z1aXXnJR1BeND5roIgLj.fy187tg.v8 YONPO_udtsHAuGZXA40GguWzg6PVWVnq2CVm.OUYDn1iIxdQTkgY99hWBPTzbNBUV4QR3.P1nmOX d0sSSZOKChKLFPv4aYPanWIYmeLhsm7YtVO6NlT3LsBzPJGsXducp0eavogBSqpLYGgyBNK.RoeA X5kSB3Z_vHm9NKYV7K2BtIfWFz44td1e8vuU0kGiUuimWUBT86bji9XJS4Miev3nvsWr6DtGrvtg 6.mCHmBDPszHqcjucp_Hdm2zdlp_8jASOjaDHVvlZujvX0CPvY7kMfNw83Y2uj3Xk.VG5i8i_ych S8GDKoT3VDCWNf8PiUeUKfoWzEkUfX_aKwtnOxcOg6trlIZzPpQG9GeQsSFbjHD5lGUdk9N1MZ1C 40pDmL7GZQ_RXPCQ8q.XDptJkgBAhtkceBWuXH7tuWQS5ekFqvF9UmbJ1Zi8SJVDIbqRpPVXmymI ftIONxZ5cEle8l1mk6ZPIShYUJpF29hxO7O5QIkmhJWZKVxDNvwsqXLnnjCNsEh_qx9rOFs2m3zR mTiWVsAajiX6iXWjiIENqOIQF6_g18hKeDIrvLXhLxwJ5EFNFkAhuj8DhJ65yUFv3SljXLVRVe07 yqhhLU6hs2pIrh5o6.AKwgH57sas1kLgKvceeOjCNiErDPt..FoibZZe9Oos9h13hSFuERDakUiI l0cma2fwxfwI81wTwls9HraRSt6WeHox0By11COpGSovj7CNnqntAjFny1_1zejdLA8ZitWB5wyW 1mpK4g84- Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.ne1.yahoo.com with HTTP; Fri, 10 Aug 2018 03:02:44 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp426.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID e407f09cd8962aad00baae025a14336c; Fri, 10 Aug 2018 03:02:40 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Attempted large jump to head -r337347 for pine64+ 2GB did not finish the boot: eventual MMC handling problems before root file system is mounted From: Mark Millard In-Reply-To: <20180809220012.GU21523@alchemy.franken.de> Date: Thu, 9 Aug 2018 20:02:38 -0700 Cc: Emmanuel Vadot , Mark Millard via freebsd-arm Content-Transfer-Encoding: 7bit Message-Id: <22CDDB1E-48D5-4F60-9345-78992867299F@yahoo.com> References: <0918383D-5A5A-40A0-ADCB-08C500153BE1@yahoo.com> <20180806124421.0b622761272370d2946cac29@bidouilliste.com> <0FF066AF-D9F3-4523-8203-B9405091F10A@yahoo.com> <20180806193755.8c4e9a63bcd0870d55fe3969@bidouilliste.com> <05447ED6-3E61-4D67-B300-3182CB07079A@yahoo.com> <93D377C9-9123-40AF-AF5F-B3437831A91D@yahoo.com> <5A44C1CC-DB88-4C07-8F31-FD4348BBA6C6@yahoo.com> <20180809220012.GU21523@alchemy.franken.de> To: Marius Strobl X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 03:02:51 -0000 On 2018-Aug-9, at 3:00 PM, Marius Strobl wrote: > On Wed, Aug 08, 2018 at 02:02:58AM -0700, Mark Millard wrote: >> . . . > > It's true that an eMMC chip can support DDR52 at 3.0 V VCCQ. However, > with eMMC devices on SDHCI controllers, eMMC DDR52 translates to SD > DDR50 which - like any UHS-I mode - requires 1.8 V signaling (see for > example figure 3-14 in the SD physical layer specification version > 6.00). Thus, DDR52 at 3.0 V VCCQ is not supposed to be possible with > SDHCI controllers and at the time DDR5{0,2} support for FreeBSD was > written, Linux didn't support the former either so I saw no point in > adding a MMC_CAP_MMC_DDR52_300 to FreeBSD (Linux grew MMC_CAP_3_3V_DDR > a bit later in January 2017, though). > While I have no problem with support for DDR52 at 3.0 V VCCQ being > added to mmc(4), I doubt that will solve your problem given that Linux > doesn't set mmc-ddr-3_3v and MMC_CAP_3_3V_DDR respectively for Pine64+ > or any other Allwinner gear. Based on what I could figure out about > Allwinner MMC controllers, their capabilities actually differ depending > on the particular instance of MMC controller of a given SoC (apparently, > they are intended for different purposes, i. e. eMMC, eSD, SD, SDIO). > So I guess what needs to be done is to let aw_mmc(4) announce and > support different sets of capabilities depending on which instance of > the controller it is driving. For your adapter this likely means that > high-speed at 3.0 V VCCQ is the achievable maximum so that the microSD > slot complies with the SD physical layer specification if 1.8 V VCCQ > isn't supported by the particular board. Thanks for the notes. Clearly there is something that I'm missing because: *) Historically (before the switch to official dts's and such) I was able to boot, buildworld, buildkernel, poudreire-devel and the like booting from the e.MCC over the sdcard adapter plugged into the Pine64+ 2GB's sdcard slot. It had been my standard configuration for some time before I made the jump to a more modern environment. As for now: A) u-boot successfully gets the loader from the e.MCC over the sdcard adapter plugged into the Pine64+ 2GB's sdracard slot. B) The loader successfully loads the kernel from the e.MCC over the sdcard adapter plugged into the Pine64+ 2GB's sdracard slot. C) The first failure is from the kernel attempting to deal with the e.MCC (via the adapter). I may have read into this (and the messages from boot -v and what was said about them) the wrong assumptions about what is wrong. What I can say is that the issue looks to be specific to the FreeBSD kernel but not to the prior loader (nor to u-boot). === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)