All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Munoz <carlos@kenati.com>
To: linux-mtd@lists.infradead.org
Cc: Carlos Munoz <carlos@kenati.com>
Subject: Re: How to map nand chip ?
Date: Thu, 15 Nov 2007 11:25:58 -0800	[thread overview]
Message-ID: <473C9D46.9060007@kenati.com> (raw)
In-Reply-To: <4739FA7A.9050403@kenati.com>

Carlos Munoz wrote:
> I'm working on a custom board that has both nor and nand flash. I mapped 
> the nor flash (cfi) using do_map_probe("cfi_probe", &map). However, I'm 
> not sure what argument to pass to do_map_probe() to map the nand flash.
>
> Does anyone know how nand flash is mapped or point me to the right 
> documents ?
>   
OK. I figured it out... had to write a board nand driver.

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 output is as follows:

modprobe migo_r
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 
3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 1 at 0x00020000
Bad eraseblock 2 at 0x00040000
Bad eraseblock 3 at 0x00060000
Bad eraseblock 4 at 0x00080000
Bad eraseblock 5 at 0x000a0000
Bad eraseblock 6 at 0x000c0000
Bad eraseblock 7 at 0x000e0000
Bad eraseblock 8 at 0x00100000
Bad eraseblock 9 at 0x00120000
Bad eraseblock 10 at 0x00140000
....


Thanks,


Carlos

  reply	other threads:[~2007-11-15 19:24 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 [this message]
2007-11-15 21:44   ` Ricard Wanderlof
2007-11-16 10:41     ` Carl-Daniel Hailfinger
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=473C9D46.9060007@kenati.com \
    --to=carlos@kenati.com \
    --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.