From: Grant Erickson <gerickson@nuovations.com>
To: Philip Rakity <prakity@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: setting PAD parameter with JFFS2 and NAND -- what is correct thing to do ?
Date: Wed, 03 Dec 2008 08:44:05 -0800 [thread overview]
Message-ID: <C55BF755.133A7%gerickson@nuovations.com> (raw)
In-Reply-To: <461019.6371.qm@web58901.mail.re1.yahoo.com>
On 12/2/08 9:23 AM, Philip Rakity wrote:
> I am trying to understand what value to set the pad parameter to when making a
> JFFS2 image (including using sumtool) for NAND flash.
>
> The NAND flash has 2KiB sectors, 256KiB erase size, and is 2GB.
>
> I use flase_eraseall -j when erasing the flash and the flash HAS bad blocks.
>
> The image size is less than the 2GB size of the flash.
>
> I have tried both specifying pad (rounded up) to the erase block size and
> omitting pad. When I write to the NAND there are recovered CRC errors from
> time to time as well as the other "errors" indicated in the FAQ.
>
> If could set pad to the SIZE of the NAND flash, but because of bad blocks I am
> not sure this is correct...
>
> Guidance Please.
>
> Philip
Philip:
You should set the padding to the page size. For the two systems I have, the
mkfs.jffs2 commands used to build the root file systems are as follows:
mkfs.jffs2 --big-endian \
--no-cleanmarkers \
--pad 512 \
--pagesize 512 \
--eraseblock 16384 \
-d /tmp/fs/stripped/root \
-D root.devtable \
-o root.jffs2
and:
mkfs.jffs2 --big-endian \
--no-cleanmarkers \
--pad 2048 \
--pagesize 2048 \
--eraseblock 131072 \
-d /tmp/fs/stripped/root \
-D root.devtable \
-o root.jffs2
Regards,
Grant
prev parent reply other threads:[~2008-12-03 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 17:23 setting PAD parameter with JFFS2 and NAND -- what is correct thing to do ? Philip Rakity
2008-12-03 16:44 ` Grant Erickson [this message]
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=C55BF755.133A7%gerickson@nuovations.com \
--to=gerickson@nuovations.com \
--cc=linux-mtd@lists.infradead.org \
--cc=prakity@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox