[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem in loading JFFS2 file system on Strong ARM sa1110/1111 target board
> We have made zimage by enabling Jffs2 filesystem
> and MTD option in configaration file.I can able download kernel and
> JFFS2 filesystem successfully by following redboot procedure but
> unable to see JFFS2's Memory address or flash address or length entry
> point as shown by redboot procedure by using "fis list" commond . and
> at the neponset console i got these messages as shown
> below......please help me in this regard.
Please show the output of the 'fis list' command. The log you posted shows
that the kernel is using the space between 0x100000 and 0x1f80000 for JFFS2:
> Kernel command line: root=/dev/mtdblock2
> 0x00100000-0x01f80000 : "unallocated space"
> mtd: Giving out device 2 to unallocated space
> blkmtd: error, missing `device' name
Turn off CONFIG_MTD_BLKMTD
> $Id: ftl.c,v 1.39 2001/10/02 15:05:11 dwmw2 Exp $
> ftl_cs: FTL header not found.
Turn off CONFIG_FTL
> NFTL driver: nftlcore.c $Revision: 1.83 $, nftlmount.c $Revision: 1.23 $
Turn off CONFIG_NFTL
> jffs2_scan_empty(): Empty block at 0x0000fffc ends at 0x00010000 (with
> 0xe0021985)! Marking dirty
Create your image with the correct '-e 0x40000' option to mkfs.jffs2
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00277424:
> 0x1a1a instead
Use the '-p' option to mkfs.jffs2 so that it pads the image to an erase
block boundary, and you don't get this noise at the end of the image.
To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to firstname.lastname@example.org