From: Frank Neuber <linux-mips@kernelport.de>
To: borasah@gmail.com
Cc: linux-mips@linux-mips.org
Subject: Re: Au1200 and NAND Flash - K9F1G08U0A -
Date: Thu, 12 Feb 2009 08:55:37 +0100 [thread overview]
Message-ID: <1234425337.12847.124.camel@t60p> (raw)
In-Reply-To: <200705192213.12019.borasah@gmail.com>
Hi Bora,
I have the same problem here.
Did you find a solution for this nand large page device.
I tried to copy nand_command_lp from nand_base.c and added the -CE stuff
including disabling interrupts during read.
The result is that I found just one bad block during scan :-). Also
erasing nand seems to be possible (usinf eraseall /dev/mtdX).
But if I write and read back the data (using dd) I get io errors :-(
I found your posting on this list wihout an answer so I hope you was
able to manage the nand stuff.
Kind Regards,
Frank
Am Samstag, den 19.05.2007, 22:13 +0300 schrieb borasah@gmail.com:
> Hi,
>
> We want to use NAND flash on Alchemy Au1200 and have a custom board along with
> Db1200; so tried it both on our custom board and Db1200 without success.
> (Because Db1200 has a slot we opened it and replaced the original with our
> part)
>
> 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. As far as I understand
> "au1xxx_nand_command" seems doesnt work correctly. Has someone succeded to
> work with these large block parts in the Au1200/Au1550?
>
> Thanks...
>
> --
> Bora SAHIN
next prev parent reply other threads:[~2009-02-12 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 19:13 Au1200 and NAND Flash - K9F1G08U0A - borasah
2007-05-19 19:13 ` borasah
2009-02-12 7:55 ` Frank Neuber [this message]
2009-02-12 8:17 ` Manuel Lauss
2009-02-12 8:40 ` Frank Neuber
2009-02-12 8:53 ` Manuel Lauss
2009-02-12 13:24 ` Frank Neuber
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=1234425337.12847.124.camel@t60p \
--to=linux-mips@kernelport.de \
--cc=borasah@gmail.com \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox