From: "Andrew E. Mileski" <andrewm@isoar.ca>
To: linux-mtd@lists.infradead.org
Subject: Re: Problem with Micron 256 MB NAND on 440EPx
Date: Mon, 26 May 2008 15:44:45 -0400 [thread overview]
Message-ID: <483B132D.80103@isoar.ca> (raw)
In-Reply-To: <48079979.3030201@isoar.ca>
Andrew E. Mileski wrote:
> I'm looking for some pointers in the right direction with this problem
> I'm having with Micron 256 MB NAND part MT29F2G08AACWP:C with a JFFS2
> filesystem on a AMCC PowerPC 440EPx board using the NDFC driver.
>
snip
>
> Write verify error (ECC correction failed) at 0e480000. Wrote:
> 00000000: 19 85 e0 02 00 00 04 44 c0 83 e7 3a 00 00 00 03
> ...
> Read back:
> 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 00000010: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 00000020: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 00000030: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 00000040: 19 85 e0 02 00 00 04 44 c0 83 e7 3a 00 00 00 03
>
> Notice that the data appears to be "offset" by 64 bytes, which just
> happens to be the size of the OOB, but that could be a coincidence.
I've now verified with a logic analyzer that the NFREN strobe is active
during when NFRDYBSY is low (NAND chip is busy), and latching bogus data
as a result (the bus has pull-ups so 0xff).
I've verified the pin is connected, and I have seen transitions on it
through the PPC register.
Any suggestions on what I might be missing still?
Thanks.
--
Andrew E. Mileski
next prev parent reply other threads:[~2008-05-26 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 18:39 Problem with Micron 256 MB NAND on 440EPx Andrew E. Mileski
2008-05-26 19:44 ` Andrew E. Mileski [this message]
2008-05-26 20:36 ` Alessandro Rubini
2008-05-26 23:04 ` Andrew E. Mileski
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=483B132D.80103@isoar.ca \
--to=andrewm@isoar.ca \
--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