From: Alberto Panizzo <maramaopercheseimorto@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: ARM: MTD: mxc_nand: Question on NAND Flash support for mxc
Date: Thu, 21 May 2009 17:46:11 +0200 [thread overview]
Message-ID: <20090521174611.5a18ea3a@Marramao-laptop> (raw)
Hi all!
I am trying to give support for NAND flash device to Atmark Armadillo 500
developing board.
This board has an iMX31 processor and is shipped with an ST Micro NAND 256MiB 3,3V 8-bit Flash.
Atmark support this board with an old 2.6.26 kernel with some modification.
For this NAND Flash Atmark installed the old Freescale mxc_nd driver brought up by
Sascha Hauer in the on tree mxc_nand.
Now the problem:
With the old driver kernel message is as follow:
--
MXC MTD nand Driver 2.0
NAND device: Manufacturer ID: 0x20, Chip ID: 0xda (ST Micro NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 592 at 0x04a00000
Creating 4 MTD partitions on "NAND 256MiB 3,3V 8-bit":
--
With the new in tree driver i get:
--
NAND device: Manufacturer ID: 0x20, Chip ID: 0xda (ST Micro NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 0 at 0x000000000000
Bad eraseblock 1 at 0x000000020000
Bad eraseblock 2 at 0x000000040000
Bad eraseblock 3 at 0x000000060000
Bad eraseblock 4 at 0x000000080000
Bad eraseblock 5 at 0x0000000a0000
Bad eraseblock 6 at 0x0000000c0000
Bad eraseblock 7 at 0x0000000e0000
.... all blocks ...
Bad eraseblock 2045 at 0x00000ffa0000
Bad eraseblock 2046 at 0x00000ffc0000
Bad eraseblock 2047 at 0x00000ffe0000
RedBoot partition parsing not available
Registering mxc_nand as whole device
--
All blocks are recognized as Bad eraseblocks!
Digging the problem I switch off bbt scanning and Bad eraseblock check in flash_eraseall (mtd utils 1.2.0)
running this utility results in a mixture of:
--
Erasing 128 Kibyte @ 2e60000 -- 18 % complete.
flash_eraseall: /dev/mtd4: MTD Erase failure: Input/output error
Erasing 128 Kibyte @ 2ea0000 -- 18 % nand_erase: attempt to erase a bad block at page 0x00005e40
--
Thanks for any suggestions.
Alberto!
next reply other threads:[~2009-05-21 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 15:46 Alberto Panizzo [this message]
2009-05-21 16:11 ` ARM: MTD: mxc_nand: Question on NAND Flash support for mxc Magnus Lilja
2009-05-21 16:47 ` Alberto Panizzo
2009-05-25 8:29 ` Vladimir Barinov
2009-05-22 8:06 ` Claudio Lanconelli
2009-05-25 8:26 ` Vladimir Barinov
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=20090521174611.5a18ea3a@Marramao-laptop \
--to=maramaopercheseimorto@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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