From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Nelson Date: Mon, 7 Dec 2015 07:36:55 -0700 Subject: [U-Boot] mmc erase fails from U-Boot command line In-Reply-To: References: <5620E3A7.7040909@defengcorp.com> <5624CEC5.8040901@digi.com> <52F917CEA1B9C64C94833D53889D478C269236@dor-sms-xch01.digi.com> <565DEF80.90204@nelint.com> <565F3CD3.1010100@nelint.com> <565F4674.8010306@nelint.com> <5661C0CB.2040900@nelint.com> <566216D9.4030202@nelint.com> Message-ID: <56659987.5020703@nelint.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Fabio, On 12/06/2015 05:21 PM, Fabio Estevam wrote: > Hi Eric, > > On Fri, Dec 4, 2015 at 8:42 PM, Eric Nelson wrote: > >> I've figured out a way to repeat this on my machine. >> >> If I write 0xff's to the eMMC blocks, then issue an erase for the same, >> I get the problem with each MMC_ERASE command. >> >> I've also found something that fixes the issue in my testing. >> >> Changing SECURE_ERASE to 0 from 0x80000000 in include/mmc.h allows >> things to function for me. >> >> Page 115 of the JEDEC eMMC 4.5 spec says that bit 31 is obsolete and >> should be zero: >> http://www.jedec.org/sites/default/files/docs/jesd84-B45.pdf >> >> Hector and Fabio, can you test that change? > > Managed to get access to a revC2 board and tested your change. > > I am happy to say that 'mmc erase' works now :-) > Glad to hear it. > Good job, Eric! > > When you send a formal patch then you can add: > > Tested-by: Fabio Estevam > Will do.