public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ruediger Haertel <hae@port.de>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD/ DoC Millenium Plus - Failure in flash detection
Date: Thu, 7 Jul 2005 17:04:19 +0200	[thread overview]
Message-ID: <200507071704.19393.hae@port.de> (raw)
In-Reply-To: <200507071532.17991.hae@port.de>

Am Donnerstag, 7. Juli 2005 15:32 schrieb Ruediger Haertel:
> Am Donnerstag, 7. Juli 2005 15:21 schrieb Thomas Gleixner:
> > On Thu, 2005-07-07 at 15:05 +0200, Ruediger Haertel wrote:
> > > For the NAND DiskOnChip driver I had to apply the patch mentioned
> > > here:
> > > http://lists.infradead.org/pipermail/linux-mtd/2004-October/01064
> > >0. html
> > >
> > >
> > > What irritates me is the output:
> > > DiskOnChip BNAND Media Header not found.
> > >
> > > Why is that ?
> >
> > Obviously the header is not at the expected place.
> >
> > > />nanddump /dev/mtd5 /var/xxx 0 128
> > > MTD_open
> > > MTD_ioctl
> > > Unknown flash (not normalM NAND)
> >
> > Is this nanddump from latest MTD-CVS ?
>
> No. I use the one of the uClinux-dist-20041215. I'll give the one
> from mtd-cvs a try. Should I use realy the latest snapshot or the one
> I am using from date 2005.03.03.
>

Now I used the nanddump from mtd-cvs 2005-03-03. The same result. It 
reads oobsize and oobblock as 0.

I printed the values of the mtd structure during probing and they are:
oob size: 16, oob block: 512

Seems ok. So I guess my device file is not correct. I am 
using /dev/mtd5,c,90,9. 

Just for completeness here is the probing output of the driver:

Using configured DiskOnChip probe address 0x40000000
DiskOnChip found at 0x40000000
NAND device: Manufacturer ID: 0x98, Chip ID: 0x73 (Toshiba NAND 16MiB 
3,3V 8-bit)
oob size: 16, oob block: 512
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
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

-- 

Ruediger Haertel

  parent reply	other threads:[~2005-07-07 15:04 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
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 [this message]
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=200507071704.19393.hae@port.de \
    --to=hae@port.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.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