Jedec probe for strange 28F800B3 chips (patch)

Jedec probe for strange 28F800B3 chips (patch)

[Colin Cross]

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

I'm working on an embedded system that has two Flash chips labeled
28F800B3-10BD.  The Intel datasheets say they should have an identifier
of 0x8893 (which matches jedec_probe.c), but they report an identifier
of 0x889D.  I found one errata datasheet that says the correct
identifier for these chips is in fact 0x889D.  However, the block map of
this chip is completely different from the one described in the
datasheets.  It has 1 16kB block, 2 8kB blocks, 1 96kB, and 7 128kB
blocks.  This matches the block map for some other random Intel 8Mb
flash chip, but I can't find any datasheets that give this block map and
identifier together.  I've added these chips to jedec_probe.c, and they
work fine once added, but I'm at a loss as to why these chips don't
agree with the datasheets.  Can anyone offer any insight?  Does anyone
have 28F800B3 chips that follow the datasheet?  I've attached a patch
that adds support for them, but I'm not sure what to call them (Intel
28F800B3B version 2? for now).

[-- Attachment #2: jedec_probe_patch.txt --]
[-- Type: text/plain, Size: 1176 bytes --]

--- /home/colin/src/arm/mtd/mtd/drivers/mtd/chips/jedec_probe.c	Thu Apr 25 08:03:18 2002
+++ jedec_probe.c	Mon Apr 29 21:39:54 2002
@@ -66,6 +66,8 @@
 #define I28F008B3B	0x00d3
 #define I28F800B3T	0x8892
 #define I28F800B3B	0x8893
+#define I28F800B3T2	0x889C
+#define I28F800B3B2	0x889D
 #define I28F016S3	0x00aa
 #define I28F016B3T	0x00d0
 #define I28F016B3B	0x00d1
@@ -441,6 +399,32 @@
 		}
 	}, {
 		mfr_id:			MANUFACTURER_INTEL,
+		dev_id:			I28F800B3B2,
+		name:			"Intel 28F800B3B version 2?",
+		DevSize:		SIZE_1MiB,
+		CmdSet:			P_ID_INTEL_STD,
+		NumEraseRegions:	4,
+		regions: {
+			ERASEINFO(0x04000, 1),
+			ERASEINFO(0x02000, 2),
+			ERASEINFO(0x18000, 1),
+			ERASEINFO(0x20000, 7),
+		}
+	}, {
+		mfr_id:			MANUFACTURER_INTEL,
+		dev_id:			I28F800B3T2,
+		name:			"Intel 28F800B3T version 2?",
+		DevSize:		SIZE_1MiB,
+		CmdSet:			P_ID_INTEL_STD,
+		NumEraseRegions:	4,
+		regions: {
+			ERASEINFO(0x20000, 7),
+			ERASEINFO(0x18000, 1),
+			ERASEINFO(0x02000, 2),
+			ERASEINFO(0x04000, 1),
+		}
+	}, {
+		mfr_id:			MANUFACTURER_INTEL,
 		dev_id:			I28F016B3B,
 		name:			"Intel 28F016B3B",
 		DevSize:		SIZE_2MiB,

RE: Jedec probe for strange 28F800B3 chips (patch)

[Gregg C Levine]

Hello from Gregg C Levine
Parts like that, are not uncommon, just darned annoying to fellow
designers. Suggest you call them, part-number-A, such as 28F800B3A. In
fact I suggest you examine the parts, to see what part number they have
stamped on them. I'd be surprised, if the thought never occurred to
Intel before.
-------------------
Gregg C Levine mrspock1962@hotmail.com
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: linux-mtd-admin@lists.infradead.org [mailto:linux-mtd-
> admin@lists.infradead.org] On Behalf Of Colin Cross
> Sent: Wednesday, May 08, 2002 5:06 PM
> To: linux-mtd@lists.infradead.org
> Subject: Jedec probe for strange 28F800B3 chips (patch)
> 
> I'm working on an embedded system that has two Flash chips labeled
> 28F800B3-10BD.  The Intel datasheets say they should have an
identifier
> of 0x8893 (which matches jedec_probe.c), but they report an identifier
> of 0x889D.  I found one errata datasheet that says the correct
> identifier for these chips is in fact 0x889D.  However, the block map
of
> this chip is completely different from the one described in the
> datasheets.  It has 1 16kB block, 2 8kB blocks, 1 96kB, and 7 128kB
> blocks.  This matches the block map for some other random Intel 8Mb
> flash chip, but I can't find any datasheets that give this block map
and
> identifier together.  I've added these chips to jedec_probe.c, and
they
> work fine once added, but I'm at a loss as to why these chips don't
> agree with the datasheets.  Can anyone offer any insight?  Does anyone
> have 28F800B3 chips that follow the datasheet?  I've attached a patch
> that adds support for them, but I'm not sure what to call them (Intel
> 28F800B3B version 2? for now).

RE: Jedec probe for strange 28F800B3 chips (patch)

[Conley, Christopher]

I apologize for responding so late, 

the configuration is actually for the 5V bottom boot part.

Here is the datasheet for it:
ftp://download.intel.com/design/flcomp/datashts/29059907.pdf



Chris
---------
Disclaimer: These opinions are mine and mine alone, and do not reflect those
of my employer or its agents.



-----Original Message-----
From: linux-mtd-admin@lists.infradead.org
[mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of Colin Cross
Sent: Wednesday, May 08, 2002 2:06 PM
Subject: Jedec probe for strange 28F800B3 chips (patch)


I'm working on an embedded system that has two Flash chips labeled
28F800B3-10BD.  The Intel datasheets say they should have an identifier
of 0x8893 (which matches jedec_probe.c), but they report an identifier
of 0x889D.  I found one errata datasheet that says the correct
identifier for these chips is in fact 0x889D.  However, the block map of
this chip is completely different from the one described in the
datasheets.  It has 1 16kB block, 2 8kB blocks, 1 96kB, and 7 128kB
blocks.  This matches the block map for some other random Intel 8Mb
flash chip, but I can't find any datasheets that give this block map and
identifier together.  I've added these chips to jedec_probe.c, and they
work fine once added, but I'm at a loss as to why these chips don't
agree with the datasheets.  Can anyone offer any insight?  Does anyone
have 28F800B3 chips that follow the datasheet?  I've attached a patch
that adds support for them, but I'm not sure what to call them (Intel
28F800B3B version 2? for now).