From: "Mark Roths" <mroths@softairmicro.com>
To: <linux-mtd@lists.infradead.org>
Subject: u-boot reports ecc error on blocks written by nandwrite
Date: Mon, 2 Jun 2008 11:09:17 -0700 [thread overview]
Message-ID: <01b301c8c4db$c5ebb560$6601a8c0@mrothsduo> (raw)
I am running 2.6.20.11 on Atmel AT91SAM9261 and u-boot 1.1.5 with Atmel
patch 1.6.
I have ST 1Gb flash - NAND01GR3B2BZA6, 2k page, 128k eraseblock, 64 oob.
I would like to use nanderase and nandwrite to overwrite the u-boot
environment from Linux. Unfortunately,
although the data is written correctly, as verified by cmp, u-boot always
reports an ecc error
upon bootup afterwards. I am using nandwrite
* $Id: nandwrite.c,v 1.32 2005/11/07 11:15:13 gleixner Exp $
I have tried exactly copying a block using nanddump, including oob data, and
writing it back but I still have the ecc error.
I tried without the oob data, and lots of variations on the options to
nanddump and nandwrite.
Any block written by nandwrite appears to u-boot to have ecc errors after a
reboot. A further weirdness is that if I request a very small number of
bytes from the block, e.g. 1, it fails once, then succeeds. I am using the
u-boot command 'nand read 0x20800000 0xa0000 1'. All further reads of any
size up to the entire block then will succeed. If I reboot, the error
recurs.
There appears to be a discrepancy between how the linux mtd driver and
u-boot handle the ecc. Or I am doing something
boneheadded.
Mark Roths
Softair Microsystems
phone: 831 621 6274
fax: 831 621 6275
next reply other threads:[~2008-06-02 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 18:09 Mark Roths [this message]
2008-06-02 21:35 ` u-boot reports ecc error on blocks written by nandwrite James
[not found] <01c001c8c4fb$8ac04170$6601a8c0@mrothsduo>
2008-06-02 22:18 ` James
2008-06-03 4:28 ` Mark Roths
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='01b301c8c4db$c5ebb560$6601a8c0@mrothsduo' \
--to=mroths@softairmicro.com \
--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