From: "benszau@googlemail.com" <benszau@googlemail.com>
To: linux-mtd@lists.infradead.org
Subject: Issues with flashcp
Date: Mon, 30 Jul 2007 13:38:21 +0200 [thread overview]
Message-ID: <46ADCDAD.80200@googlemail.com> (raw)
In general flashing works well, but I have issues when flashing certain
images. This problem is reproduceable:
* The target is a MPC5200-tiny board with 16MB of Intel Strata Flash
connected to a PPC processor.
* First I flash a large image via bootloader (u-Boot).
* Then I can boot the system.
* After system has booted, i transfer a smaller, second image to the
target /tmp folder via SCP.
* "flashcp /tmp/<image_small.img>" /dev/mtd2 -v
* The progess suggests, that everything went well, but when I reboot
i get inode errors like the following:
...
JFFS2 error: (1) jffs2_build_inode_pass1: child dir "tc" (ino
#473) of dir ino #334 appears to be a hard link
VFS: Mounted root (jffs2 filesystem).
Freeing unused kernel memory: 92k init
JFFS2 error: (160) jffs2_do_read_inode_internal: Argh. Special
inode #467 with mode 0xa1ff had more than one node
Returned error for crccheck of ino #467. Expect badness...
...
* Now i am curious what went wrong. The small image works well if i
flash using the bootloader, so it should not be an issue with the
image itself. May it be possible that i have found a bug? Any help
is appreciated.
Kind regards,
Simon
reply other threads:[~2007-07-30 11:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46ADCDAD.80200@googlemail.com \
--to=benszau@googlemail.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.