All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Munoz <carlos@kenati.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: How to map nand chip ?
Date: Tue, 20 Nov 2007 15:50:54 -0800	[thread overview]
Message-ID: <474372DE.7020707@kenati.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711152241450.11612@lnxricardw.se.axis.com>

Ricard Wanderlof wrote:
> Another thing that can cause this is if the ready/busy-pin is not read 
> properly by the chip driver. Again, the chip will probably respond quickly 
> to an id request, but when reading or writing the memory array, the access 
> times will be longer causing failure.
>
>   

That was the problem. The ready/busy pin was not working. Somehow, it's 
always high.

For now I added a 20 usec delay and everything works.

Thanks,


Carlos

      parent reply	other threads:[~2007-11-20 23:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 19:26 How to map nand chip ? Carlos Munoz
2007-11-15 19:25 ` Carlos Munoz
2007-11-15 21:44   ` Ricard Wanderlof
2007-11-16 10:41     ` Carl-Daniel Hailfinger
2007-11-20 23:50     ` Carlos Munoz [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=474372DE.7020707@kenati.com \
    --to=carlos@kenati.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ricard.wanderlof@axis.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.