flash trouble

  • Hi at all


    I'm using picocom1 with NAND flash as storageplace for linux kernel and targetfs.


    Using U-Boot to flash a new kernel and/or targetfs seams to work without errors, erasing and writing gives no error messages.
    But when running the system out of the flash and the kernel mounts the targetfs errors from the jffs2-system appears.
    for example:

    Code
    1. [33554141.773437] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "e2pm" (ino #988) of dir ino #984 appears to be a hard link
    2. [33554141.703125] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "e2pm" (ino #988) of dir ino #984 appears to be a hard link
    3. [33554141.742187] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "e2pm" (ino #995) of dir ino #991 appears to be a hard link
    4. [33554141.773437] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "pcm" (ino #891) of dir ino #885 appears to be a hard link
    5. [33554141.804687] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "init" (ino #890) of dir ino #885 appears to be a hard link
    6. [33554141.843750] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "cards" (ino #889) of dir ino #885 appears to be a hard link
    7. [33554141.875000] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "speaker-test" (ino #894) of dir ino #885 appears to be a hard link


    This messages appears at certain picocom1-modules, other runs the same targetfs without any problems.


    What's going wrong?
    What can I do to solv the problem?


    Thanks
    Günter

  • But this is what is told in the documentation. All examples with the kernel and the targetfs always erase the *whole* partition and then write the new file with the given $filesize. This is important or there remain parts of old files. JFFS2 needs the unused space of the partition clean, including clean markers. Only then this space is ignored and later reused. If it is not marked clean, JFFS2 tries to collect the data blocks found there, of course running in lots of inconsistencies now, where large parts of the data are overwritten with the new contents. This can easily result in the given messages.


    I always assumed that you've followed exactly these steps as given in the documentation! And then the behavior was inexplicable. Of course if you just erased part of the partition, then it can be explained rather easily.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.