From: "Steve Tsai" <startec@ms11.hinet.net>
To: "'Ken Offer'" <koffer@arlut.utexas.edu>
Cc: "Linux MTD mailing list" <linux-mtd@lists.infradead.org>
Subject: RE: ECC in Nand_write_page
Date: Fri, 12 Jul 2002 10:39:36 +0800 [thread overview]
Message-ID: <003701c2294d$5dcd6e40$5501a8c0@synso.com.tw> (raw)
In-Reply-To: <A4461AAE-94D1-11D6-A71C-000393467F1A@arlut.utexas.edu>
I don't think nand_write_page can write partial page, if someone enable
ECC. For example, when I write the partial page to the page 100, it will
write ECC code into the page also, but when I write the other data to
the empty area of the same page, I can write data into the empty area
of the page, but I can not write the ECC code, because the area storing
ECC code was written at the previous time.
Steve Tsai
-----Original Message-----
From: linux-mtd-admin@lists.infradead.org
[mailto:linux-mtd-admin@lists.infradead.org] On Behalf Of Ken Offer
Sent: Thursday, July 11, 2002 9:25 PM
To: Steve Tsai
Cc: LinuxMTD
Subject: Re: ECC in Nand_write_page
On Thursday, July 11, 2002, at 05:19 AM, Steve Tsai wrote:
> The board I used will display the message, "nand_write_ecc: Failed ECC
> write", so I try to trace the function nand_write_ecc, I found it can
> not write the ECC code into OOB sometime because the ECC in OOB are
> not set as 0xff. There are two conditions to cause the problem, one
> condition is the erase does not success, another condition is that the
> page was written before. Nand_write_page could write partial page to
> the flash. Does it cause the ECC in OOB was written and ECC can not be
> written next time. For example, nand_write_page write 100 byte the
> first time and if it want to write 412 bytes to the same page next
> time, it will fail. Does anyone have this problem?
I have read that some NAND memory devices can read partial pages
but must write full pages. Could this be your problem? In such
cases you might have to read the page, make a write to part of
the page and then write out the modified full page.
+-----------------------------------------------------------+
| Ken Offer koffer@arlut.utexas.edu ARL:UT |
| Office: 512-835-3859 Fax: 512-835-3259 |
+-----------------------------------------------------------+
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2002-07-12 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 10:19 ECC in Nand_write_page Steve Tsai
2002-07-11 13:25 ` Ken Offer
2002-07-12 2:39 ` Steve Tsai [this message]
2002-07-12 12:30 ` Jörn Engel
2002-07-12 6:11 ` Thomas Gleixner
2002-07-12 6:58 ` Steve Tsai
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='003701c2294d$5dcd6e40$5501a8c0@synso.com.tw' \
--to=startec@ms11.hinet.net \
--cc=koffer@arlut.utexas.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox