What is flash trouble?

      What is flash trouble?

      Hi at allI'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:Source Code
      [33554141.773437] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "e2pm" (ino #988) of dir ino #984 appears to be a hard link
      [33554141.703125] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "e2pm" (ino #988) of dir ino #984 appears to be a hard link
      [33554141.742187] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "e2pm" (ino #995) of dir ino #991 appears to be a hard link
      [33554141.773437] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "pcm" (ino #891) of dir ino #885 appears to be a hard link
      [33554141.804687] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "init" (ino #890) of dir ino #885 appears to be a hard link
      [33554141.843750] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "cards" (ino #889) of dir ino #885 appears to be a hard link
      [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
      Are you using the original PicoCOM1 or the new PicoCOM1.2?

      Do you erase the flash with nand erase clean? Do you write the new data with nand write.jffs2? Is there a bad block involved (nand bad).

      Your F&S Support Team
      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.