From: Angus CLARK <angus.clark@st.com>
To: "Kumar, Goutam" <goutam.kumar@ti.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: ubifs not working with 3.1 kernel and MT29F2G08ABAEAWP NAND Flash.
Date: Wed, 19 Oct 2011 16:25:16 +0100 [thread overview]
Message-ID: <4E9EEBDC.5000002@st.com> (raw)
In-Reply-To: <0680EC522D0CC943BC586913CF3768C0059050481E@dbde02.ent.ti.com>
Hi Goutam,
On 10/19/2011 03:28 PM, Kumar, Goutam wrote:
>
> There is MT29F2G08ABAEAWP (256MB, 8-bit) NAND device on TI EVM.
>
This particular NAND device requires 4-bit ECC. As far as I can tell, you are
using the OMAP2 driver with 1-bit Hamming H/W ECC. This will throw
uncorrectable ECC errors (as seen in your log) if there are 2 bit flips in any
ECC block. The problem gets worse if there are 3 or 4 bit flips, which is still
within spec of the NAND device.
This may, or may not, be the source of your problem, but it might be worth
taking a look anyway.
The device does include a 4-bit on-die ECC engine, which can be enabled using
the 'SET_FEATURE' command. I don't believe this is available in nand_base.c at
present, but it is not too hard to add. You would also need to disable the
OMAP2 H/W ECC support to avoid any layout clashes in the OOB area. Of course,
whatever changes you make to the kernel, would also have to be made to u-boot.
Cheers,
Angus
next prev parent reply other threads:[~2011-10-19 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 14:28 ubifs not working with 3.1 kernel and MT29F2G08ABAEAWP NAND Flash Kumar, Goutam
2011-10-19 15:25 ` Angus CLARK [this message]
2011-10-19 15:49 ` Ivan Djelic
2011-10-20 6:47 ` Kumar, Goutam
2011-10-20 17:03 ` Ivan Djelic
2011-10-21 20:06 ` Artem Bityutskiy
2011-10-24 5:02 ` Kumar, Goutam
2011-10-28 14:21 ` Artem Bityutskiy
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=4E9EEBDC.5000002@st.com \
--to=angus.clark@st.com \
--cc=goutam.kumar@ti.com \
--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