AnsweredAssumed Answered

unable to mount jffs2 file system in bf548

Question asked by sachin@eilabs.co.in on Jan 31, 2014
Latest reply on Feb 12, 2014 by Aaronwu

I have set the bootargs in uboot as below

    bfin>set bootargs 'root=/dev/mtdblock2 mem=64M ip=dhcp rw noinitrd earlyprintk=serial,uart2,115200 console=ttyBF2,115200 rootfstype=jffs2

I believe that using   bootargs command  in uboot & specifying the root=/dev/mtdblock2 is how you tell the kernel. Let me know if my understanding is correct. 


and iam getting the following error... What does this error really mean. &  i have copied the rootfs.jffs2 at 0x20480000 location on the burst flash (parallel nor flash). Let me know how to tell the kernel that the file system is @ 0x20480000

 

Creating 5 MTD partitions on "physmap-flash.0":

0x000000000000-0x000000080000 : "Uboot(nor)"

0x000000080000-0x000000480000 : "linux kernel(nor)"

0x000000480000-0x000000fe0000 : "file system(nor)"

0x000000fe0000-0x000000ff8000 : "config(nor)"

0x000000ff8000-0x000001000000 : "u-boot env(nor)"

bf5xx-nand bf5xx-nand.0: data_width=8, wr_dly=3, rd_dly=3

ONFI param page 0 valid

ONFI flash detected

NAND device: Manufacturer ID: 0x2c, Chip ID: 0x48 (Micron MT29F32G08AFACAWP), 2048MiB, page size: 4096, OOB size: 224

Creating 3 MTD partitions on "MT29F32G08AFACAWP":

0x000000000000-0x000000080000 : "bootloader(nand)"

0x000000080000-0x000000480000 : "linux kernel(nand)"

0x000000480000-0x000080000000 : "file system(nand)"

input: bf54x-keys as /devices/platform/bf54x-keys/input/input0

TCP: cubic registered

NET: Registered protocol family 17

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0x30ff instead

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004: 0x30ff instead

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008: 0x30ff instead

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c: 0x30ff instead

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010: 0x30ff instead

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014: 0x30ff instead

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018: 0x30ff instead

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c: 0x30ff instead

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020: 0x30ff instead

jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024: 0x30ff instead

jffs2: Further such events for this erase block will not be printed

jffs2: Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes

jffs2: empty_blocks 90, bad_blocks 0, c->nr_blocks 91

VFS: Cannot open root device "mtdblock2" or unknown-block(31,2): error -5

Please append a correct "root=" boot option; here are the available partitions:

1f00             512 mtdblock0  (driver?)

1f01            4096 mtdblock1  (driver?)

1f02           11648 mtdblock2  (driver?)

1f03              96 mtdblock3  (driver?)

1f04              32 mtdblock4  (driver?)

1f05             512 mtdblock5  (driver?)

1f06            4096 mtdblock6  (driver?)

1f07         2092544 mtdblock7  (driver?)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)

Outcomes