From: James <jamessteward@optusnet.com.au>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Alessandro Rubini <rubini-list@gnudd.com>,
michael <trimarchi@gandalf.sssup.it>
Subject: Re: Help needed with MTD on AT91SAM9263-EK please.
Date: Wed, 28 May 2008 07:46:19 +1000 [thread overview]
Message-ID: <1211924779.6140.9.camel@Ubuntu-Desktop> (raw)
In-Reply-To: <80b317760805270042w39c409d4j230c1a2967bf0242@mail.gmail.com>
Hi Richard,
On Tue, 2008-05-27 at 09:42 +0200, Richard Genoud wrote:
> well, I would say hardware failure, as far as we all used this board
> without any problem.
It's good to know the problem is (hopefully) isolated. After the test
below, I feel it might be more than just a hardware failure though.
> Maybe a last test to be sure :
> flash_eraseall /dev/mtd0
> dd if=/dev/zero bs=2K count=1 of=/dev/mtd0
> nanddump -p -l2048 /dev/mtd0
>
> (try to write a page and read it back).
>
> if you can post this dump, I'm curious...
root@at91sam9263ek:~/mtd-tools$ ./flash_eraseall /dev/mtd0
Erasing 128 Kibyte @ 3ee0000 -- 99 % complete.
root@at91sam9263ek:~/mtd-tools$ dd if=/dev/zero bs=2k count=1
of=/dev/mtd0
1+0 records in
1+0 records out
root@at91sam9263ek:~/mtd-tools$ ./nanddump -p -l2048 /dev/mtd0
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00000800...
0x00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<skip all zeros>
0x000007e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x000007f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Hmm. So I tried a block that previously had problems with mount.
root@at91sam9263ek:~/mtd-tools$ dd if=/dev/zero bs=2k count=1 seek=5120
of=/dev/mtd0
1+0 records in
1+0 records out
root@at91sam9263ek:~/mtd-tools$ ./nanddump -p -l2048
-s0xa00000 /dev/mtd0
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00a00000 and ending at 0x00a00800...
0x00a00000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00a00010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00a00020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<snip all zeros>
0x00a007e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00a007f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
And an unwritten to page...
root@at91sam9263ek:~/mtd-tools$ ./nanddump -p -l2048
-s0xdc0000 /dev/mtd0
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00dc0000 and ending at 0x00dc0800...
0x00dc0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x00dc0010: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x00dc0020: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<snip all 0xff>
So, a page at a time seems ok?
I wonder, what markings are on your CPU and NAND flash? I have;
AT91SAM9263 CU-ES 0747 8 QH59R.07
0742 29F2G08AAC WP C LJK6
I assume some of this will be a batch code, but I wonder if there's been
a die shrink that's caused some marginal timing issue?
Regards,
James.
next prev parent reply other threads:[~2008-05-27 21:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 6:20 Help needed with MTD on AT91SAM9263-EK please James
2008-05-23 6:26 ` Richard Genoud
2008-05-23 6:38 ` James
2008-05-23 6:48 ` michael
2008-05-23 7:02 ` James
2008-05-23 7:12 ` michael
2008-05-23 7:13 ` michael
2008-05-23 7:19 ` michael
2008-05-23 7:28 ` James
2008-05-23 6:52 ` Richard Genoud
2008-05-23 7:05 ` James
2008-05-23 7:27 ` Richard Genoud
2008-05-23 7:32 ` James
2008-05-23 7:41 ` michael
2008-05-25 22:50 ` James
2008-05-27 7:42 ` Richard Genoud
2008-05-27 21:46 ` James [this message]
2008-05-28 6:24 ` Richard Genoud
2008-05-28 22:52 ` James
2008-05-28 22:59 ` James
2008-05-29 6:41 ` Richard Genoud
2008-05-29 6:46 ` James
2008-05-30 2:05 ` James
2008-05-23 7:03 ` Alessandro Rubini
2008-05-23 7:08 ` James
2008-05-23 7:09 ` James
2008-05-23 7:39 ` Alessandro Rubini
2008-05-23 7:42 ` James
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=1211924779.6140.9.camel@Ubuntu-Desktop \
--to=jamessteward@optusnet.com.au \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.genoud@gmail.com \
--cc=rubini-list@gnudd.com \
--cc=trimarchi@gandalf.sssup.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.