From: borasah@gmail.com
To: linux-mtd@lists.infradead.org
Subject: 128 MiB NAND flash - all eraseblocks bad
Date: Mon, 21 May 2007 13:44:02 +0300 [thread overview]
Message-ID: <200705211344.02914.borasah@gmail.com> (raw)
Hi,
After I did some progress on 64MiB NAND flash on the eval board(Au1200 -
DB1200), I decided to try my chance on our custom board.
The NAND part we use in our custom board is K9F1G08U0A. It has (2K + 64) page
size and (128K + 4K) eraseblock size.
Kernel -> 2.6.20.1. Error messages:
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V
8-bit)
Scanning device for bad blocks
Bad eraseblock 0 at 0x00000000
Bad eraseblock 1 at 0x00020000
...
Bad eraseblock 1022 at 0x07fc0000
Bad eraseblock 1023 at 0x07fe0000
Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
It marks all the eraseblocks as BAD. I tried it in 2.6.11 but the same...
The first thing I suspect was timings. I examined processor and NAND
datasheets; seems processor NAND block timing paramters are slower than
equivalent NAND flash timing paremeters. Also the driver can access
manufacturer id etc. So I think it shouldnt be a problem. Then I debugged
"nand_scan"(linux-2.6.11) a bit and reached to the point that there may be
some wrong things in "au1xxx_nand_command". What may be the cause of these
error messages? Where should I look at?
Thanks...
--
Bora SAHIN
reply other threads:[~2007-05-21 10:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200705211344.02914.borasah@gmail.com \
--to=borasah@gmail.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.