From owner-freebsd-arm@freebsd.org Fri Aug 31 20:39:30 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 258D3FDBFB7 for ; Fri, 31 Aug 2018 20:39:30 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8372584660; Fri, 31 Aug 2018 20:39:29 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id f008c3a5; Fri, 31 Aug 2018 22:39:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=/R/3vlNf0GBHf4ZXsxNKX5Yxr7M=; b=ZPslnDL0KP8zK60gJjHgkshGZ9ad 1gIs0Vh02JtkH/n4iQuO1f7vfIGlxdf1NFYxRdLyRaHqeES+a5sfpT6kSv+aqQ11 0ysY4xkGtGdTNklF7ZiRMIuJwOQ4mkEyOve/LT2dP7Jj9m0yrZHpTjH+YTO+cXlD +dCw9AL8ngeu564= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=OQsD8Iz1lrfV3jTjVsu+GSV5f+k4yqj4LpKPqkzqCd5mGP6xeKdlv1rC 4JlrAZK/4n4jhg2JHAtZy1su1GU3OoG3t23t/3vE3k7kCXVRnb3t4xnoP+jvFHKa DRsTu7rrxTMG2fU4jQGy68n033iIu66ae43wRa7Y182r2mPFBmg= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 43d4f532 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Fri, 31 Aug 2018 22:39:21 +0200 (CEST) Date: Fri, 31 Aug 2018 22:39:20 +0200 From: Emmanuel Vadot To: Mark Millard Cc: Mark Millard via freebsd-arm , Marius Strobl 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 Message-Id: <20180831223920.426cde04de5230f4a5a55bb9@bidouilliste.com> In-Reply-To: <9FD914F2-0630-45B0-B5B8-9CFD85F158C7@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> <9FD914F2-0630-45B0-B5B8-9CFD85F158C7@yahoo.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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, 31 Aug 2018 20:39:30 -0000 On Fri, 31 Aug 2018 13:32:01 -0700 Mark Millard wrote: > [FYI: sdhc cards (or the one I have) also gets a VCCQ notice. > Mathcing boot -v output included. Most other material > removed.] > > On 2018-Aug-6, at 10:37 AM, Emmanuel Vadot wrote: > > > On Mon, 6 Aug 2018 10:12:43 -0700 > > Mark Millard wrote: > > > >> On 2018-Aug-6, at 3:44 AM, Emmanuel Vadot wrote: > >> > >>> . . . > >> > >>> Can you boot -v and post the result please ? > >> > >> Glad to . . . > >> > . . . > >> aw_mmc0: Powering up sd/mmc > >> mmc0: Probing bus > >> ugen0.1: at usbus0 > >> uhub0: on usbus0 > >> ugen1.1: at usbus1 > >> uhub1: on usbus1 > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> mmc0: SD probe: failed > >> mmc0: MMC probe: OK (OCR: 0x40ff8080) > >> mmc0: Current OCR: 0x00ff8080 > >> mmc0: Probing cards > >> mmc0: New card detected (CID 150100444a4e423452079f43b2e7636f) > >> mmc0: New card detected (CSD d02701320f5903fff6dbffef8e40400d) > >> aw_mmc0: error rint: 0x00008010 > >> AW_MMC_INT_DATA_END_BIT_ERR > >> mmc0: Card at relative address 0x0002 added: > >> mmc0: card: MMCHC DJNB4R 0.7 SN MFG 06/2016 by 21 0x0000 > >> mmc0: quirks: 0 > >> mmc0: bus: 4bit, 200MHz (HS200 timing) > >> mmc0: memory: 244277248 blocks, erase sector 1024 blocks > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> aw_mmc0: error rint: 0x00000100 > >> AW_MMC_INT_RESP_TIMEOUT > >> mmc0: setting transfer rate to 52.000MHz (dual data rate timing) > >> mmc0: Failed to set VCCQ for card at relative address 2 > > > > So the driver is selecting DDR52 transfer rate but, of course, > > cannot switch the IO voltage to 1.8V as on this board the IO voltage > > for the SD card is tied to 3.3V > > > > sdhc cards (or the one I have) also get the VCCQ notice. Here > is a segment of the matching boot -v output (serial numbers > and some interlaced material removed): > > aw_mmc0: Powering up sd/mmc > axp8xx_pmu0: Enable vcc-3v3 (dcdc1) > mmc0: Probing bus > ugen1.1: . . . > . . . > uhub3: . . . > mmc0: SD probe: OK (OCR: 0x40ff8000) > mmc0: Current OCR: 0x00ff8000 > mmc0: Probing cards > mmc0: New card detected (CID 035344534533324780????????01171d) > mmc0: New card detected (CSD 400e00325b590000edc87f800a4040c3) > mmc0: Card at relative address 0xaaaa added: > mmc0: card: SDHC SE32G 8.0 SN MFG 07/2017 by 3 SD > mmc0: quirks: 0 > mmc0: bus: 4bit, 50MHz (high speed timing) > mmc0: memory: 62333952 blocks, erase sector 8192 blocks > mmc0: setting transfer rate to 50.000MHz (high speed timing) > mmcsd0: 32GB at mmc0 50.0MHz/4bit/32768-block > GEOM: new disk mmcsd0 > mmc0: setting bus width to 4 bits high speed timing > mmc0: Failed to set VCCQ for card at relative address 43690 > > (This is still based on head -r338341 despite the typo in the > subject line.) > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) What is the point of this mail exactly ? I've already answered why you are seeing this and that it is harmless. -- Emmanuel Vadot