From: MarekSk <mareksk7@gazeta.pl>
To: linux-mtd@lists.infradead.org
Subject: Intel compatible flash device issue
Date: Tue, 22 Jun 2004 21:03:29 +0200 [thread overview]
Message-ID: <40D88281.2080300@gazeta.pl> (raw)
Hi,
I have encountered a problem using M28W160CT flash chip as
LINUX character device. This chips is compatible with INTEL standard
command set.
Since the chip is locked after power-up, there is required to unlock
some blocks before write operation. Of course, this can be done
from any application using MEMUNLOCK command.
Once the MEMUNLOCK command is executed (without any error)
the flash chip remains in the "command" state.
This state after MEMUNLOCK blocks any read access to data stored
in the flash.
Reviewing the cfi_cmdset_0001.c file I have found that single block
(un)lock algorithm (do_xxlock_oneblock) is different from these
described in the following documents:
- STM M28W160CT datasheet (figure 22)
<http://www.st.com/stonline/books/pdf/docs/7358.pdf>
- Intel 28F160C3 datasheet (figure 20)
<ftp://download.intel.com/design/flcomp/datashts/29064518.pdf>
It seems that there should be issued the reset command (0xff) just
after lock (0x01)/unlock (0xd0) command.
Any comments, ideas ?
Thanks in advance,
MarekSk
next reply other threads:[~2004-06-22 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 19:03 MarekSk [this message]
2004-06-24 17:40 ` Intel compatible flash device issue MarekSk
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=40D88281.2080300@gazeta.pl \
--to=mareksk7@gazeta.pl \
--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