From: Philippe De Muyter <phdm@macqel.be>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Nicolas Pitre <nico@cam.org>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: Apply Numonyx Axcell P33/P30 workaround for Lock/Unlock bug.
Date: Thu, 21 Oct 2010 11:33:43 +0200 [thread overview]
Message-ID: <20101021093343.GA17631@frolo.macqel> (raw)
In-Reply-To: <1287650398.2932.5.camel@localhost>
On Thu, Oct 21, 2010 at 11:39:58AM +0300, Artem Bityutskiy wrote:
> On Tue, 2010-10-19 at 16:24 +0200, Philippe De Muyter wrote:
> > Some flash chips have a small but annoying bug, documented in
> > "Numonyx Axcell P33/P30 256-Mbit Specification Update"
> >
> > It states :
> > When customer uses [...] block unlock, the block lock status might
> > be altered inadvertently. Lock status might be set to either 01h
> > or 03h unexpectedly (00h as expected data), which leads to
> > program/erase failure on certain blocks.
> >
> > A workaround is given, (summary : issue a "Read Lock Status" before
> > the "Lock" or "Unlock" command) which I have applied and tested
> > with success.
> >
> > Signed-off-by: Philippe De Muyter <phdm@macqel.be>
>
> Is this Numonyx-specific issue? Should there be some kind of "if
> (numonyx)" statement?
This is clearly a bug specific to some Numonyx flashes.
My chips have Manufacturer ID: 0x89, Device ID: 0x881B, but there are
other chips in the same family. The errata
http://www.numonyx.com/Documents/Specification%20Updates/509003_P3X_65nm_3V_256Mbit_Discrete.pdf does not list the ManufacturerIDs/DeviceIDs of the affected
chips.
Philippe
--
Philippe De Muyter phdm at macqel dot be Tel +32 27029044
Macq Electronique SA rue de l'Aeronef 2 B-1140 Bruxelles Fax +32 27029077
next prev parent reply other threads:[~2010-10-21 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 14:24 [PATCH] mtd: Apply Numonyx Axcell P33/P30 workaround for Lock/Unlock bug Philippe De Muyter
2010-10-21 8:39 ` Artem Bityutskiy
2010-10-21 9:33 ` Philippe De Muyter [this message]
2010-10-21 10:29 ` Artem Bityutskiy
2010-10-21 16:32 ` Nicolas Pitre
2010-10-21 19:34 ` Philippe De Muyter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101021093343.GA17631@frolo.macqel \
--to=phdm@macqel.be \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).