public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: Will Wagner <will_wagner@carallon.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND and JFFS2 newbie question
Date: Wed, 28 Jan 2009 13:29:23 +0100	[thread overview]
Message-ID: <49804FA3.7010604@kernelconcepts.de> (raw)
In-Reply-To: <497F3CBF.4000309@carallon.com>

Will Wagner schrieb:
> Hi All,
> 
> I have an arm iMx31 board with 128M of NAND flash. It all appears to be working however I 
> get a lot of error/warning messages and I'd just like to check I am doing things right.
> 
> The NAND chip is a ST NAND01G-B2B used in 8-bit mode which has 2048+64 byte pages and 128k 
> block size. Linux is 2.6.24.7 with Freescale patches for MTD support on the iMx31 chip.
> 
> I am wanting to create a JFFS2 partition on the device. The partition is created using:
> 
> mkfs.jffs2 -s 2 -e 128 -c 12 -o fs.jffs2 -r jffs2_fs

I guess one of the problems will be that the sizes you specified are way
too small. Fomr the man-page of mkfs.jffs2:
"Options that take SIZE arguments can be specified as either decimal
(e.g., 65536), octal (0200000), or hexidecimal (0x1000)"

So for an eraseblocksize of 128kbytes you would specify "-e 131072".

Wrong settings can confuse jffs2 pretty easily.

> Thanks,
> Will
Cheers
  nils faerber

-- 
kernel concepts GbR        Tel: +49-271-771091-12
Sieghuetter Hauptweg 48    Fax: +49-271-771091-19
D-57072 Siegen             Mob: +49-176-21024535
http://www.kernelconcepts.de

  reply	other threads:[~2009-01-28 12:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 16:56 NAND and JFFS2 newbie question Will Wagner
2009-01-28 12:29 ` Nils Faerber [this message]
2009-01-28 13:19   ` Will Wagner

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=49804FA3.7010604@kernelconcepts.de \
    --to=nils.faerber@kernelconcepts.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=will_wagner@carallon.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