From: James <jamessteward@optusnet.com.au>
To: Mark Roths <mroths@softairmicro.com>
Cc: linux-mtd@lists.infradead.org
Subject: RE: u-boot reports ecc error on blocks written by nandwrite
Date: Tue, 03 Jun 2008 08:18:59 +1000 [thread overview]
Message-ID: <1212445139.6121.19.camel@Ubuntu-Desktop> (raw)
In-Reply-To: <01c001c8c4fb$8ac04170$6601a8c0@mrothsduo>
On Mon, 2008-06-02 at 14:56 -0700, Mark Roths wrote:
> Yes, u-boot can erase, write, and read with no problems on its own.
> I use the u-boot nand utilities to build my flash with bootloader, u-boot,
> linux and initrd. All that works fantastically.
>
> The only time I have problems is when I write a block in my boot partition
> using nandwrite, and then subsequently read it with u-boot on the next boot.
> And the completely strange behavior is that if I request 1 byte using 'nand
> read', it fails the 1st time and then succeeds - all reads succeed after
> that with no ecc errors.
Sounds almost like a cache problem.
> Both the mtdchar driver and u-boot are configured for soft ecc, or so I
> believe from my reading of the code.
Likely.
I've had a plethora of problems using the NAND MT29F2G08AACWP on some
AT91SAM9263-EK boards. I now feel it might be a timing issue. Maybe
yours is too!
Regards,
James.
next parent reply other threads:[~2008-06-02 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01c001c8c4fb$8ac04170$6601a8c0@mrothsduo>
2008-06-02 22:18 ` James [this message]
2008-06-03 4:28 ` u-boot reports ecc error on blocks written by nandwrite Mark Roths
2008-06-02 18:09 Mark Roths
2008-06-02 21:35 ` James
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=1212445139.6121.19.camel@Ubuntu-Desktop \
--to=jamessteward@optusnet.com.au \
--cc=linux-mtd@lists.infradead.org \
--cc=mroths@softairmicro.com \
/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.