From: ivan.djelic@parrot.com (Ivan Djelic)
To: linux-arm-kernel@lists.infradead.org
Subject: [i.MX28 GPMI] problem overwriting all-0xff data in NAND
Date: Tue, 19 Jul 2011 08:48:02 +0200 [thread overview]
Message-ID: <20110719064802.GA5788@parrot.com> (raw)
In-Reply-To: <20005.7506.283476.184839@ipc1.ka-ro>
On Tue, Jul 19, 2011 at 06:59:46AM +0100, Lothar Wa?mann wrote:
> I'm writing a JFFS2 image file that is padded with 0xff to eraseblock
> size to flash (either from the bootloader or with the nandwrite
> utility from Linux).
> When mounting the filesystem everything is OK until the first file is
> being written. A subsequent read of the affected flash page gives ECC
> errors.
>
> JFFS2 is giving out the first all-FF page in the last used block for
> creating the new file. Since that block has a non-FF ECC pattern, the
> ECC information is being corrupted on write.
OK, thanks for the clarification. So the problem only happens on partially
programmed blocks in the JFFS2 image, that end up fully programmed on the
device because of the 0xff padding.
I think the cleaner solution is to use a non-padded image and avoid programming
pages with 0xff in the last used block; programming nand pages multiple times
should be avoided if possible, as it is not supported on all (especially the
most recent) devices.
BR,
--
Ivan
next prev parent reply other threads:[~2011-07-19 6:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 13:13 [i.MX28 GPMI] problem overwriting all-0xff data in NAND Lothar Waßmann
2011-07-18 14:56 ` Ivan Djelic
2011-07-19 5:59 ` Lothar Waßmann
2011-07-19 6:48 ` Ivan Djelic [this message]
2011-07-18 16:43 ` Shawn Guo
2011-07-19 2:12 ` Huang Shijie
2011-07-19 6:02 ` Lothar Waßmann
2011-07-19 7:03 ` Huang Shijie
2011-07-19 9:55 ` Lothar Waßmann
2011-07-19 13:36 ` Wolfram Sang
2011-07-20 2:18 ` Huang Shijie
2011-07-20 8:51 ` Wolfram Sang
2011-07-20 4:55 ` Huang Shijie
2011-07-20 6:22 ` Lothar Waßmann
2011-07-20 5:16 ` Artem Bityutskiy
2011-07-20 5:19 ` Artem Bityutskiy
2011-07-19 6:00 ` Lothar Waßmann
2011-07-20 6:44 ` Huang Shijie
2011-07-20 8:10 ` Lothar Waßmann
2011-07-20 8:35 ` Artem Bityutskiy
2011-07-20 5:12 ` 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=20110719064802.GA5788@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=linux-arm-kernel@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