From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] JFFS2 images written from U-Boot unusable in Linux? (Round 2)
Date: Fri, 07 Jan 2005 12:00:05 +0100 [thread overview]
Message-ID: <crlq3v$t6e$1@sea.gmane.org> (raw)
Hi there,
Now I've gotten a bit further in my quest for getting JFFS2 images to
work between U-Boot and Linux.
I upgraded to ELDK 3.1 and configured the CONFIG_JFFS2_NAND_SIZE to the
proper size. So, now I can succesfully put an image on the flash from
U-Boot and "ls" it. (Thanks again for that...)
Further, if I erase the NAND from Linux and create some files/dir's, I
can see them succesfully from U-Boot with "ls".
However, if I put a JFFS2-image on the NAND _from U-Boot_, Linux cannot
mount the device any longer:
# cd /tmp
# mkdir image
# cd image/
# echo "Test1" > testfile
# mkdir testdir
# echo "Test12" > testdir/testfile
# mkfs.jffs2 --pad --big-endian --root=. --output=../test20050107.jffs2
=> nand erase clean
=> tftp 100000 test20050107.jffs2
=> nand write.jffs2 100000 0 $(filesize)
=> ls
Scanning JFFS2 FS: . done.
drwxr-xr-x 0 Tue Nov 30 17:45:59 2004 testdir
-rw-r--r-- 6 Tue Nov 30 17:45:45 2004 testfile
=> ls testdir
-rw-r--r-- 7 Tue Nov 30 17:45:59 2004 testfile
# mkdir /mnt
# mount -t jffs2 /dev/mtdblock0 /mnt
jffs2: Erase block size too small (16KiB). Using virtual blocks size
(32KiB) instead
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 0, bad_blocks 5, c->nr_blocks 2048
mount: Mounting /dev/mtdblock0 on /mnt failed: Invalid argument
I have the following kernel configuration options concerning JFFS2:
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_NAND=y
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
# CONFIG_JFFS2_LZO is not set
# CONFIG_JFFS2_LZARI is not set
# CONFIG_JFFS2_CMODE_NONE is not set
CONFIG_JFFS2_CMODE_PRIORITY=y
# CONFIG_JFFS2_CMODE_SIZE is not set
# CONFIG_JFFS2_PROC is not set
Are there anything else needed in order to support the way U-Boot writes
an image?
Best regards,
Martin Egholm
next reply other threads:[~2005-01-07 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 11:00 Martin Egholm Nielsen [this message]
2005-01-09 17:03 ` [U-Boot-Users] JFFS2 images written from U-Boot unusable in Linux? (Round 2) Craig Hughes
2005-01-09 17:30 ` Allen Curtis
2005-01-09 18:32 ` Craig Hughes
2005-01-10 8:50 ` [U-Boot-Users] " Martin Egholm Nielsen
2005-01-10 20:15 ` Martin Egholm Nielsen
2005-01-12 12:29 ` Pantelis Antoniou
2005-01-12 13:46 ` Martin Egholm Nielsen
2005-02-16 7:35 ` Martin Egholm Nielsen
2005-02-16 9:34 ` Wolfgang Denk
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='crlq3v$t6e$1@sea.gmane.org' \
--to=martin@egholm-nielsen.dk \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox