From: David Vrabel <dvrabel@arcom.com>
To: linux-mtd list <linux-mtd@lists.infradead.org>
Subject: Re: Help: Error on mounting JFFS2
Date: Thu, 19 Feb 2004 10:30:55 +0000 [thread overview]
Message-ID: <4034905F.505@arcom.com> (raw)
In-Reply-To: <20040218230358.72448.qmail@web20727.mail.yahoo.com>
>>> cfi_cmdset_0002: Disabling fast programming due to code
>>> brokenness.
>>
>>
>> What MTD version you are using? I recommend to get the latest code
>> from CVS, since there was another bug in the cmdset2. You should
>> in fact get two "Disabled X due to bugs" messages.
>
>
> The version of cfi_cmdset_0002.c is 1.94, which is almost up-to-date
> without David Vrabel's patches. I have some questions on the
> debugging messages shown below. [...] MTD do_write_oneword(): WRITE
> 0x00780000(0xc03bdd84) MTD do_write_oneword(): Check 0xffffffff
> 0xffffffff MTD do_write_oneword(): Check 0xffffffff 0xffffffff
This looks like you're not write-enabling the flash device or the
sectors are write protected so nothing ever gets written. I'm a bit
surprised the write didn't fail with an error though. The datasheet I
have here for the AM29LV128M doesn't say what the chip is supposed to do
when you try to erase/program protected sectors.
The reason the latest CVS appears to work better is because it no longer
checks the flash to see if the data actually got written -- it assumes
the status reported by the chip is correct.
David Vrabel
--
David Vrabel, Design Engineer
Arcom, Clifton Road Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK Web: http://www.arcom.com/
next prev parent reply other threads:[~2004-02-19 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 23:26 Help: Error on mounting JFFS2 Shawn Jin
2004-02-13 7:41 ` Florian Schirmer
2004-02-18 23:03 ` Shawn Jin
2004-02-19 10:30 ` David Vrabel [this message]
2004-02-19 1:02 ` Shawn Jin
[not found] <40348A59.1000401@arcom.com>
2004-02-19 23:28 ` Shawn Jin
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=4034905F.505@arcom.com \
--to=dvrabel@arcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox