From: Charles Manning <manningc2@actrix.gen.nz>
To: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>,
linux-mtd@lists.infradead.org
Subject: Re: word line disturbance
Date: Fri, 17 Oct 2003 08:34:53 +1300 [thread overview]
Message-ID: <20031016192902.9EF784FDB@blood.actrix.co.nz> (raw)
In-Reply-To: <3F8CF52E.1050502@elsoft.ch>
On Wednesday 15 October 2003 20:20, David Müller (ELSOFT AG) wrote:
> Hello
>
> Magnus Mårtensson wrote:
> > Hi.
> > I had a discussion with flash manufacturer Atmel last week regarding a
> > phenomenon that we had seen. The phenomenon was called "word line
> > disturbance" and it could occur if you tried to program only ones to a
> > location that already contained ones. The result could be that some bit
> > on another address got tainted. Ex writing 0xffff to address A could
> > result in the content on address B changing from 0xffff to 0xfffe.
>
> Does anybody know more about the technical background of this "it's not
> a bug, it's a feature" problem? Or is it just a manager driven decision
> to save some money at the wrong place?
>
This is likely to be the result of a compromise to simplify the flash
internals to save cost. Some of these compromises are acceptable for certain
usage scenarios, but not others. Atmel do this sort of thing a lot.
Atmel design their DataFlash range of parts for data use and their other
parts for code storage. If the problem showed up in their Dataflash parts I'd
consider it a true bug.
-- Charles
prev parent reply other threads:[~2003-10-16 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 15:31 word line disturbance Magnus Mårtensson
2003-10-14 15:46 ` Steven Scholz
2003-10-14 17:31 ` Thayne Harbaugh
2003-10-14 21:39 ` Charles Manning
2003-10-15 7:20 ` "David Müller (ELSOFT AG)"
2003-10-16 19:34 ` Charles Manning [this message]
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=20031016192902.9EF784FDB@blood.actrix.co.nz \
--to=manningc2@actrix.gen.nz \
--cc=d.mueller@elsoft.ch \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.