From: James <jamessteward@optusnet.com.au>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: Alessandro Rubini <rubini-list@gnudd.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
michael <trimarchi@gandalf.sssup.it>
Subject: Re: Help needed with MTD on AT91SAM9263-EK please.
Date: Thu, 29 May 2008 16:46:51 +1000 [thread overview]
Message-ID: <1212043611.12909.8.camel@Ubuntu-Desktop> (raw)
In-Reply-To: <80b317760805282341n3ffbdc9bw2a919b22568ae618@mail.gmail.com>
On Thu, 2008-05-29 at 08:41 +0200, Richard Genoud wrote:
> > Just out of interest, I did the same over 10 pages.
> > $ ./flash_eraseall /dev/mtd0
> > $ dd if=/dev/urandom bs=2k count=10 of=/dev/mtd0
> > $ nanddump -p -l20480 /dev/mtd0 1> /dev/null
> > ECC failed: 3
> > 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 0x00005000...
> > ECC: 1 uncorrectable bitflip(s) at offset 0x00003800
> >
> > Foobar!
> ok, so this must be a hardware problem...
I've emailed Atmel. I suspect a chip has undergone a dies shrink and
now there's a timing spec that's violated, unless I've got 2-3 boards
all with the same hardware problem.
I'll look through the EBI timing setup and the chip requirements when I
get another moment.
Thanks for your help in the diagnosis. It was good just to know that
others are using this without such problems.
Regards,
James.
next prev parent reply other threads:[~2008-05-29 6:47 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
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 [this message]
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=1212043611.12909.8.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox