[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

JFFS2 for multi-partition Flash

Hello all,
    I apologize I advance for my long email but I'll try to state
The few questions that I have in a detailed fashion. My flash
(sect_size=0x20000, starting@0xFE000000) looks like this:
0x00000->0x20000	   PPC hardware reset word
0x20000->0x1F00000   Filesystem section
0x1F00000->0x1F40000 U-boot
0x1F40000->0x1F80000 U-boot env

Basically, I only need a portion of Flash to use JFFS2. So I built my
Jffs2.img (padded to 0x1F00000-0x20000=0x1ee0000), burned it in flash.
/proc/mtd shows the proper partitions created (in proc at least).

I get my jffs2.img filessize = 0x100000 (1MB) even though I'm padding to
0x1ee0000. Is this because of internal compression?

When linux comes up, I "mknod /dev/mtdblock1 b 31 0". If I try to "mount
-t jffs2 /dev/mtdblock1 /mnt", I see the jffs2_do_mount_fs call scanning
For the magic keys (0x1985) at offset 0x0 (where I don't have a JFFS
Image burned). How can I get the scan_medium and mount_fs files to start
at the proper offset!?

Even after hardcoding the offsets in the jffs2_do_fill_super call, 
after the scan_medium is happy for the first 0x100000 bytes, I 
start to see the msgs (0x1985 not found at 0x00100a18: xyz instead).
Jffs2_scan_eraseblock() scans every 4bytes & keeps complaining about n
ot finding the magic key (0x1985). I figured this is because my
img size is 0x100000 even though I padded it to 0x1ee0000. What am I
missing here?

Thank you so much for any pointers that you may offer.

-----Original Message-----
From: owner-jffs-dev@xxxxxxx.com">mailto:owner-jffs-dev@xxxxxxx.com] On Behalf
Of David Woodhouse
Sent: Tuesday, December 21, 2004 3:39 AM
To: Pedro Aguilar
Cc: jffs-dev@xxxxxxx.org
Subject: Re: Kernel freezing when booting with jffs2

On Sat, 2004-12-11 at 16:11 +0100, Pedro Aguilar wrote:
> The problem is that when mounting the jffs2 filesystem it says
> (I'm not giving it any read-only flag in the MTD partition) and then
> the msg 'Warning: unable to open an initial console'

Is there a /dev/console node in your file system? Mounting read-only is
normal -- add 'rw' on the command line if you don't want it read-only.


To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo@xxxxxxx.com

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo@xxxxxxx.com