From: Thomas Pang <thomaspang@shaw.ca>
To: 'J B' <mad_flasher@hotmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Problem with mtd-snapshot-20031211.tar
Date: Fri, 19 Dec 2003 08:16:30 -0800 [thread overview]
Message-ID: <000501c3c64b$767a9de0$a68c5018@ThomasVan> (raw)
In-Reply-To: <Law11-F49ynA6xSm1A00005337c@hotmail.com>
I am using AMD NOR+SRAM flash in MCP (multi-chip packages) with CFI
support.
Thanks.
Thomas
-----Original Message-----
>I download the boot image into my target system and successfully boot
up
>the board. I also download the file systems, one is CRAMFS, another
one
>is JFFS2.
What kind of flash chips does your board have? AMD, Intel, etc and NOR
or
NAND?
>
>I am using the latest mkfs.jffs2 to create my JFFS2 file system as
shown
>below:
>
>mkfs.jffs2 -p -e 0x10000 -c 12 -b -r rootfs -o jffsImage
>
>Problem 1 (Fail to mount JFFS2 file system)
>===========================================
>
>I seem to be able to mount the JFFS2 file system but when I access the
>JFFS2 file system, the system complains "Chip not ready after erase
>suspended: status = 0x1985". Any idea?
0x1985 is the magic number on a jffs2 filesystem. Looks like the chip
driver is trying to read the status register of the chips and its in
read
array mode, not read status.
># ls
>Chip not ready after erase suspended: status = 0x1985
>error -5 reading node at 0x001901f8 in get_inode_nodes()
>jffs2_get_inode_nodes() for ino 2 returned -5
>ls: ./bin: Input/output error
see comment about magic number above. JFFS2 is probably erasing any
extra
eraseblocks you have so it can use them and the erase suspend is
failing
when the ls command is done.
>Problem 2 (Writing to JFFS2 file system still slow)
<snip>
> rm myfile
> cp bin/myfile .
> Chip not ready after erase suspended: status = 0xffff
> Chip not ready after erase suspended: status = 0xffff
looks like the same problem. 0xffff is what erased flash blocks look
like.
So two questions are, what kind of flash chips do you have, and what mtd
chip driver are you using?
j
_________________________________________________________________
Enjoy the holiday season with great tips from MSN.
http://special.msn.com/network/happyholidays.armx
next parent reply other threads:[~2003-12-19 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Law11-F49ynA6xSm1A00005337c@hotmail.com>
2003-12-19 16:16 ` Thomas Pang [this message]
2004-01-14 21:33 Problem with mtd-snapshot-20031211.tar VD
2004-01-15 20:54 ` Thayne Harbaugh
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 20:10 thomaspang
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='000501c3c64b$767a9de0$a68c5018@ThomasVan' \
--to=thomaspang@shaw.ca \
--cc=linux-mtd@lists.infradead.org \
--cc=mad_flasher@hotmail.com \
/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