public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: michael <trimarchi@gandalf.sssup.it>
To: Mangesh Edake <m_edake@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 as rootfs on DataFlash
Date: Thu, 21 Feb 2008 19:50:23 +0100	[thread overview]
Message-ID: <47BDC7EF.5060603@gandalf.sssup.it> (raw)
In-Reply-To: <389154.92868.qm@web50802.mail.re2.yahoo.com>

Mangesh Edake wrote:
Hi
> Hi Michel,
>
> Many thanks for your reply. 
>
> I tried with removing -s 0x210 option, so command now
> looks like,
> mkfs.jffs2 -p -l -e 0x2100 -n -d /home/me/rootdir -o
> jffs2.img
>
> At the same time I added erase command in the u-boot
> as suggested by you. But unfortunately the result is
> same...
>
> However I found that dataflash driver in u-boot
> doesnot deal with extra 16-bytes (oob) and doesnot
> write any JFFS2 specific magic bitmask, node crc,
> cleanmarker etc. info to the oob. But the nand flash
> (legacy) driver does the same in u-boot. Also
> kernel-mtd driver for at45 dataflash is missing with
> read_oob, write_oob functions whereas mtd-nand uses
> those routines. So my concern is, while copying the
> jffs2 image to dataflash is it necessory to write
> jffs2 specific info in oob region..? My assumption is,
> this info should be present in image itself and
> mkfs.jffs2 must take care of this while creating an
> image. (Please corret me if I'm wrong...)
> I've also seen code of nandwrite (mtd utility) where
> it uses -j option that takes care of jffs2_oobinfo.
>   
No,
using in linux flash_eraseall to clean your partition. Maybe start from 
a ramdisk.
It is the only partinion? If no, you must remember to align it at a 
block size.
Example my partionin start from 0x131400

setenv bootargs console=ttyS0,115200 mem=8M rootfstype=jffs2 
root=/dev/mtdblock1
rw mtdparts=spi0.1-AT45DB321x:1221k(ARMboot)ro,-@1221k(root)

For the creation use:
mkfs.jffs2 -d romfs -l -p -e 0x2100 -v -n -o images/ramdisk.img > log.txt

Let me know!!

Regards Michael

  reply	other threads:[~2008-02-21 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 15:04 JFFS2 as rootfs on DataFlash Mangesh Edake
2008-02-19 15:38 ` trimarchi
2008-02-21 10:10   ` michael
2008-02-21 16:01     ` Mangesh Edake
2008-02-21 18:50       ` michael [this message]
2008-02-26  7:18         ` Mangesh Edake
2008-02-22 12:15       ` Ricard Wanderlof
     [not found] <47C3C90B.9070605@gandalf.sssup.it>
2008-03-24  6:59 ` Mangesh Edake

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=47BDC7EF.5060603@gandalf.sssup.it \
    --to=trimarchi@gandalf.sssup.it \
    --cc=linux-mtd@lists.infradead.org \
    --cc=m_edake@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