From: Ruediger Haertel <hae@port.de>
To: linux-mtd@lists.infradead.org
Subject: Re: MTD/ DoC Millenium Plus - Failure in flash detection
Date: Thu, 7 Jul 2005 15:05:51 +0200 [thread overview]
Message-ID: <200507071505.51557.hae@port.de> (raw)
In-Reply-To: <200507061745.18226.hae@port.de>
Am Mittwoch, 6. Juli 2005 17:45 schrieb Ruediger Haertel:
> Hello all,
>
> I am trying to get the DOC Millenium Plus chip 16 MB, ChipID = 0x41)
> on my board (Coldfire 5272, uClinux) running. The chip as such is
> detected. If the DoC is accessed correctly then the flash chip has id
> 0xA5. This id is not in the table of NAND IDs in the file nand_ids.c.
>
> The cvs MTD drivers has 0xA5 assigned to a SAMSUNG 2 GiB chip. But as
> far as I know the Doc MilPlus 16MB uses a Toshiba flash.
>
> Any suggestions what's wrong here.
I updated the mtd drivers as stated on the infradead website. Because
the API changed I had to make small fixes to my cfi mapping module. Now
the chip is correctly detected. Both drivers, ie. the old DiskOnChip
and the new NAND DiskOnChip, work.
For the NAND DiskOnChip driver I had to apply the patch mentioned here:
http://lists.infradead.org/pipermail/linux-mtd/2004-October/010640.html
Using configured DiskOnChip probe address 0x40000000
DiskOnChip found at 0x40000000
NAND device: Manufacturer ID: 0x98, Chip ID: 0x73 (Toshiba NAND 16MiB
3,3V 8-bi)
nand_read_ecc: Failed ECC read, page 0x00000020 on chip 0
ECC error scanning DOC at 0x4000
nand_read_ecc: Failed ECC read, page 0x00000040 on chip 0
ECC error scanning DOC at 0x8000
nand_read_ecc: Failed ECC read, page 0x00000060 on chip 0
ECC error scanning DOC at 0xc000
doc200x_correct_data corrected 2 errors
nand_read_ecc: Failed ECC read, page 0x00000080 on chip 0
ECC error scanning DOC at 0x10000
DiskOnChip BNAND Media Header not found.
mtd: Giving out device 5 to DiskOnChip Millennium Plus
What irritates me is the output:
DiskOnChip BNAND Media Header not found.
Why is that ?
How can I make a first test of the DoC, ie. reading writing reading?
I tried nanddump and nandtest. But no success:
/>nanddump /dev/mtd5 /var/xxx 0 128
MTD_open
MTD_ioctl
Unknown flash (not normalM NAND)
TD_close
pid 29: failed 256
/> nandtest /dev/mtd5
MTD_open
open flash: Permission denied
pid 31: failed 256
Any help apreciated :)
--
Ruediger Haertel
next prev parent reply other threads:[~2005-07-07 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 15:45 MTD/ DoC Millenium Plus - Failure in flash detection Ruediger Haertel
2005-07-07 13:05 ` Ruediger Haertel [this message]
2005-07-07 13:21 ` Thomas Gleixner
2005-07-07 13:32 ` Ruediger Haertel
2005-07-07 14:00 ` Thomas Gleixner
2005-07-07 15:04 ` Ruediger Haertel
2005-07-08 8:48 ` Ruediger Haertel
2005-07-08 9:21 ` Ruediger Haertel
2005-07-11 8:04 ` Ruediger Haertel
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=200507071505.51557.hae@port.de \
--to=hae@port.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox