DOC2000 flash: Do I miss something?

Tue Mar 24 03:00:48 EDT 2009

Hi,

Forgotton to add the info for cleanmarker, info is available at 
http://www.infradead.org/pipermail/linux-mtd/2007-June/018584.html
http://www.infradead.org/pipermail/linux-mtd/2004-June/009835.html

Regards,
Ravi

________________________________________
From: linux-mtd-bounces at lists.infradead.org [linux-mtd-bounces at lists.infradead.org] On Behalf Of Ravi Vasarla [ravi.vasarla at sasken.com]
Sent: Tuesday, March 24, 2009 12:16
To: Juergen Beisert; linux-mtd at lists.infradead.org
Subject: RE: DOC2000 flash: Do I miss something?

Hi,

Just check with nandwrite with option -j (--jffs2 oob layout) instead of autoplace oob layout. Also check the oob structure is filled in nandwrite and respective info is
available at diskonchip.c file should match.
 The below message is coming due to mis matching the oob and ecc layout.  Which should be same in diskonchip.c with respect to writing the data using nandwrite.c

Regards,
Ravi

________________________________________
From: Juergen Beisert [jbe at pengutronix.de]
Sent: Tuesday, March 24, 2009 00:59
To: linux-mtd at lists.infradead.org
Cc: Ravi Vasarla
Subject: Re: DOC2000 flash: Do I miss something?

On Montag, 23. März 2009, Ravi Vasarla wrote:
> Hi,
>
> Kindly check the DOC2000 driver which is available under  -> Device
> Drivers-> Memory Technology Devices (MTD)-> Memory Technology Device (MTD)
> support (MTD [=m])-> NAND Flash Device Drivers (Which has recommanded too).
> The below error message due to the way old doc driver implemented.

What is the correct setup of this device to make it work?

I tried:

$ flash_eraseall /dev/mtd0
$ nandwrite -a /dev/mtd0 root.jffs2

$ mount -t jffs2 /dev/mtdblock0 /mnt
When I try to mount it, I get many of these messages:
[...]
CLEANMARKER node found at 0x003e4000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x003e8000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x003ec000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x003f0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x003f4000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x003f8000 has totlen 0xc != normal 0x0
[...]

But the mount seems successfull, as I can see the files and I can also modify
some text files in this filesystem. After unmount and reboot at the next
mount again I see many of these messages:
[...]
CLEANMARKER node found at 0x003fc000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00400000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00404000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00408000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x0040c000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00410000 has totlen 0xc != normal 0x0
[...]

But now also these ones:
[...]
mtd->read(0x3a50 bytes from 0x4105b0) returned ECC error
mtd->read(0x1a14 bytes from 0x4125ec) returned ECC error
Empty flash at 0x004125e8 ends at 0x00412600
mtd->read(0x1cc bytes from 0x412834) returned ECC error
mtd->read(0x200 bytes from 0x412600) returned ECC error
mtd->read(0x33 bytes from 0x412800) returned ECC error

Device broken or setup wrong?

Regards,
Juergen

--
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |
SASKEN BUSINESS DISCLAIMER
-------------------------
This message may contain confidential, proprietary or legally privileged information. In
case you are not the original intended Recipient of the message, you must not, directly or
indirectly, use, Disclose, distribute, print, or copy any part of this message and you are
requested to delete it and inform the sender. Any views expressed in this message are
those of the individual sender unless otherwise stated. Nothing contained in this message
shall be construed as an offer or acceptance of any offer by Sasken Communication
Technologies Limited ("Sasken") unless sent with that express intent and with due
authority of Sasken. Sasken has taken enough precautions to prevent the spread of
viruses. However the company accepts no liability for any damage caused by any virus
transmitted by this email

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
SASKEN BUSINESS DISCLAIMER
-------------------------
This message may contain confidential, proprietary or legally privileged information. In 
case you are not the original intended Recipient of the message, you must not, directly or 
indirectly, use, Disclose, distribute, print, or copy any part of this message and you are 
requested to delete it and inform the sender. Any views expressed in this message are 
those of the individual sender unless otherwise stated. Nothing contained in this message 
shall be construed as an offer or acceptance of any offer by Sasken Communication 
Technologies Limited ("Sasken") unless sent with that express intent and with due 
authority of Sasken. Sasken has taken enough precautions to prevent the spread of 
viruses. However the company accepts no liability for any damage caused by any virus 
transmitted by this email