Intel K3 Flash + MTD

[Chuck Meade]

Hey Dan,

Abhishek sent me a response directly that he got it working
with the email I sent him, but then he had trouble getting
a msg back to the list that he is up and running now.

The reason it was in "status mode" was his unlock logic was
leaving it that way.

Chuck

> -----Original Message-----
> From: Dan Post [mailto:djp.mtd at onemyth.net]
> Sent: Wednesday, October 29, 2003 1:16 PM
> To: Chuck Meade; Karoliya,Abhishek
> Cc: linux-mtd at lists.infradead.org
> Subject: RE: Intel K3 Flash + MTD
> 
> 
> 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