public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Dan Post" <djp.mtd@onemyth.net>
To: "Chuck Meade" <chuckmeade@mindspring.com>,
	"Karoliya,Abhishek" <Abhishek.Karoliya@fci.com>
Cc: linux-mtd@lists.infradead.org
Subject: RE: Intel K3 Flash + MTD
Date: Wed, 29 Oct 2003 10:16:23 -0800	[thread overview]
Message-ID: <20031029181623.M2380@onemyth.net> (raw)
In-Reply-To: <IIEEICKJLNEPBBDJICNGGEICEBAA.chuckmeade@mindspring.com>

On Sun, 26 Oct 2003 15:17:35 -0500, Chuck Meade wrote
> That sounds like the status bit that you are reading back.
> Most flashes give back status after you issue them commands
> (like all of your unlocks, for instance).  Usually you put them 
> back into "read mode" by writing a particular byte to them
> after reading the status.  Try writing an FF to the flash.
> Check your flash chip's datasheet for the exact sequence that
> you must use to put it back in read mode.

For K3's, writing an FF should work, though I don't know why it's coming up in
status mode.  I don't think that behavior is typical.  You probably should
check the datasheet.  Or it could be your bootloader that's setting it to
status mode (maybe not changing it to Read Array after a program or erase etc).

However, you should be aware that some NOR chips, such as Intel's L18/L30's,
are multi-partitioned and each partition must be set to read array mode... the
details of its multipartitioning can be very sticky, but very cool too...

Dan

  reply	other threads:[~2003-10-29 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26 20:00 Intel K3 Flash + MTD Karoliya, Abhishek
2003-10-26 20:17 ` Chuck Meade
2003-10-29 18:16   ` Dan Post [this message]
2003-10-29 20:21     ` Chuck Meade

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=20031029181623.M2380@onemyth.net \
    --to=djp.mtd@onemyth.net \
    --cc=Abhishek.Karoliya@fci.com \
    --cc=chuckmeade@mindspring.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