From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gw1.transmode.se ([213.115.205.20]) by canuck.infradead.org with esmtps (Exim 4.72 #1 (Red Hat Linux)) id 1PnwMO-0001G5-7W for linux-mtd@lists.infradead.org; Fri, 11 Feb 2011 17:00:44 +0000 In-Reply-To: <4D542657.2060903@users.sourceforge.net> References: <16826B66-31FE-41AD-A6EF-E668A45AF1FE@prograde.net> <4D4BDD48.6040600@keymile.com> <541E19B8-D428-4F59-B6BB-A3BD8F455AE4@prograde.net> <0488D3BA-7BA3-4E98-B289-3F3D1DB485D4@prograde.net> <4D542657.2060903@users.sourceforge.net> Subject: Re: Numonyx NOR and chip->mutex bug? To: =?ISO-8859-15?Q?Anders_Grafstr=F6m?= Message-ID: From: Joakim Tjernlund Date: Fri, 11 Feb 2011 18:00:39 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-15 Content-transfer-encoding: quoted-printable Cc: linux-mtd@lists.infradead.org, Holger brunck , stefan.bigler@keymile.com, Michael Cashwell List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Anders Grafstr=F6m wrote on 2011/02/10 = 18:54:31: > > On 2011-02-10 17:43, Michael Cashwell wrote: > > On Feb 10, 2011, at 10:59 AM, Michael Cashwell wrote: > > Troublesome 65nm parts: > > run 1: > > NOR Flash: block erase suspended and resumed 29 times. > > buffered write fails. > > Buffered write fails with SR[4] set? > > Have you configured with CONFIG_MTD_UBI_DEBUG_PARANOID > so that UBI does the all 0xff check after erase? > > I'm wondering if the blocks being written to are in a properly erased= state. Looking at the write buffer flow chart for Numonyx I noted that it specifies that while waiting for the write buffer one have to retry the= WB cmd each time, a la: for (;;) { map_write(map, CMD(0xe8), cmd_adr); status =3D map_read(map, cmd_adr); if (map_word_andequal(map, status, CMD(0x80), CMD(0x80))) break; if (timeout) abort write } What does other specs say? Jocke=