Hi All, It seems the following answer is wrong. The u-boot cannot recognize the JFFS2's files after write files to JFFS2 many times in linux. I guess maybe it's a JFFS2 compatible problem in u-boot and linux kernel. Does anyone know what combination of u-boot and linux kernel version is compatible for JFFS2? I think to upgrade u-boot or downgrade kernel could be a solution for this problem.
BRs, H. Johnny 2010/5/7 H. Johnny <johnny.hung...@gmail.com>: > Hi All, > > The ls command in u-boot can list contains of JFFS2 filesystem. It > works fine after copy (cp.b $memaddr $noraddr) jffs2 image file to > flash in u-boot. > After boot to linux system and copy a file to JFFS2 filesystem and do > sync, reboot then got following message in u-boot. > The kernel I used is 2.6.23 and u-boot is 1.3.0. > > ### JFFS2 loading 'image1' to 0x400000 > Scanning JFFS2 FS: .- Unknown node type: 2006 len 684 offset 0x7ffd54 > \ > Unknown node type: 2006 len 764 offset 0x83fd04 > | > Unknown node type: 2006 len 616 offset 0x85fd98 > .... > > Google this message and got some information, but is it true reason? > below is from google. > http://docwiki.gumstix.org/Tutorial > == > ### JFFS2 loading 'boot/uImage' to 0xa2000000 > Scanning JFFS2 FS: . Unknown node type: 2006 len 4288 offset 0x5ef40 > Unknown node type: 2006 len 6480 offset 0x7e6b0 > / Unknown node type: 2006 len 4988 offset 0x9ec84 > . Unknown node type: 2006 len 7368 offset 0xbe338 > - Unknown node type: 2006 len 10128 offset 0xdd870 > > that's currently normal. The 2.6.15 kernel has changed the JFFS2 > filesystem in a way that cause u-boot to report these unknown > node-type messages. You can ignore the messages > == > > Thaks for any reply. > -- > [To be different, do different. To be appear different, change the name.] > H. Johnny > -- [To be different, do different. To be appear different, change the name.] H. Johnny _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
