From: Savin Zlobec <savinz@users.sourceforge.net>
To: linux-mtd@lists.infradead.org
Subject: Re: Problems with ST NAND512W3A nand flash
Date: Thu, 17 May 2007 17:45:14 +0200 [thread overview]
Message-ID: <464C788A.8020209@users.sourceforge.net> (raw)
In-Reply-To: <464B17F3.9040804@users.sourceforge.net>
Savin Zlobec wrote:
> Hi All!
>
> I am working on a AT91RM9200 based board with ST NAND512W3A2B flash.
> Kernel version is 2.6.19.7 with patches from maxim.org.za/at91_26.html.
> Everything works perfectly, except for boot time NAND chip
> identification which fails every once in a while. NAND signature
> is 0x20 0x76, but sometimes I get 0x20 0x20. My first guess was
> timing problems, but I've double checked everything and all signals
> are inside the specs. I've also tested the chip with shorter and
> longer setup, hold and pulse times for read and write, but without
> any success. Trying different kernels didn't help either.
After some debugging I found what it looks like a silicon bug
in ST NAND512W3A2B. It looks like this particular chip doesn't
handle well the ALE and CLE transitions (no R or W) when in the
middle of READID command - other commands seem not affected.
I have the nand wired to AT91RM9200 according to the datasheet -
ALE and CLE go to A21 and A22. AT91RM9200 errata #34 states that
the address bus is continuously active, even if the address is
an internal one - so A2[12] toggle often. Sometimes it happens
that signature reading gets interrupted and if there is an
transition on A2[12] ... BOOOM - No NAND device found!!!
Regards,
savin
prev parent reply other threads:[~2007-05-17 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 14:40 Problems with ST NAND512W3A nand flash Savin Zlobec
2007-05-16 16:50 ` MikeW
2007-05-17 15:45 ` Savin Zlobec [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=464C788A.8020209@users.sourceforge.net \
--to=savinz@users.sourceforge.net \
--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.