All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: How to map nand chip ?
Date: Fri, 16 Nov 2007 11:41:26 +0100	[thread overview]
Message-ID: <473D73D6.5010209@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711152241450.11612@lnxricardw.se.axis.com>

On 15.11.2007 22:44, Ricard Wanderlof wrote:
> On Thu, 15 Nov 2007, Carlos Munoz wrote:
>
>   
>> When I load the nand driver module, the nand chip is detected correctly
>> but it seems all the erase blocks are bad. I wonder if it's caused by
>> the wrong timings when accessing the nand chip. However, the
>> manufacturer and chip id are read correctly. Does anyone know what may
>> be the cause for these errors ?
>>     
>
> The timing requirements when reading chip id's are not as severe as when 
> actually accessing the memory, so if you are just below the limit, you can 
> get the id ok but other things fail.

Side note: I have seen very old chips (from 1999, don't remember whether
they were NAD though) where reading chip IDs needed longer timing than
reading memory, but that is not the case here.


Regards,
Carl-Daniel

  reply	other threads:[~2007-11-16 10:40 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 [this message]
2007-11-20 23:50     ` Carlos Munoz

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=473D73D6.5010209@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --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.