From: Scott Wood <scottwood@freescale.com>
To: Vipin Kumar <vipin.kumar@st.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
linux-mtd@lists.infradead.org
Subject: Re: [U-Boot] 4k page ONFI NAND
Date: Tue, 3 Jan 2012 11:25:29 -0600 [thread overview]
Message-ID: <4F033A09.10202@freescale.com> (raw)
In-Reply-To: <4F02CC0C.8020203@st.com>
On 01/03/2012 03:36 AM, Vipin Kumar wrote:
> Hello,
>
> We have a Micron 4K page sized ONFI NAND MT29F16G08
> I am encountering frequent errors while reading the device. Although the
> data area is protected for 8bit correction with BCH8 algorithm, the oob
> area is unprotected and is susceptible to bit flips
>
> These errors are very frequent and it results in jffs2 file system
> mounting problems and other related issues
>
> I also confirmed the problem through oobtest module.
>
> Can you please suggest any solutions/workaround
Use ubi -- the OOB will then only be used for ECC.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] 4k page ONFI NAND
Date: Tue, 3 Jan 2012 11:25:29 -0600 [thread overview]
Message-ID: <4F033A09.10202@freescale.com> (raw)
In-Reply-To: <4F02CC0C.8020203@st.com>
On 01/03/2012 03:36 AM, Vipin Kumar wrote:
> Hello,
>
> We have a Micron 4K page sized ONFI NAND MT29F16G08
> I am encountering frequent errors while reading the device. Although the
> data area is protected for 8bit correction with BCH8 algorithm, the oob
> area is unprotected and is susceptible to bit flips
>
> These errors are very frequent and it results in jffs2 file system
> mounting problems and other related issues
>
> I also confirmed the problem through oobtest module.
>
> Can you please suggest any solutions/workaround
Use ubi -- the OOB will then only be used for ECC.
-Scott
next prev parent reply other threads:[~2012-01-03 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 9:36 4k page ONFI NAND Vipin Kumar
2012-01-03 9:36 ` [U-Boot] " Vipin Kumar
2012-01-03 17:25 ` Scott Wood [this message]
2012-01-03 17:25 ` Scott Wood
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=4F033A09.10202@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=u-boot@lists.denx.de \
--cc=vipin.kumar@st.com \
/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.