Freelance Electronics Components Distributor
Closed Dec 25th-26th
800-300-1968
We Stock Hard to Find Parts

TE28F800C3BA90

Part # TE28F800C3BA90
Description NOR, Flash 512K x 16 48PinTSSOP
Category IC
Availability In Stock
Qty 375
Qty Price
1 - 78 $0.87249
79 - 157 $0.69403
158 - 236 $0.65437
237 - 315 $0.60810
316 + $0.54200
Manufacturer Available Qty
INTEL
Date Code: 0015
  • Shipping Freelance Stock: 190
    Ships Immediately
INTEL
Date Code: 0309
  • Shipping Freelance Stock: 16
    Ships Immediately
INTEL
Date Code: 0013
  • Shipping Freelance Stock: 167
    Ships Immediately
INTEL
Date Code: 0312
  • Shipping Freelance Stock: 2
    Ships Immediately



Technical Document


DISCLAIMER: The information provided herein is solely for informational purposes. Customers must be aware of the suitability of this product for their application, and consider that variable factors such as Manufacturer, Product Category, Date Codes, Pictures and Descriptions may differ from available inventory.

Intel
£
Advanced+ Boot Block Flash Memory (C3)
Datasheet 25
Table 8. Command Codes and Descriptions
Code
(HEX)
Device Mode Command Description
FF Read Array
This command places the device in read-array mode, which outputs array data on the data
pins.
40 Program Set-Up
This is a two
-cycle command. The first cycle prepares the CUI for a program operation. The
second cycle latches addresses and data information and initiates the WSM to execute the
Program algorithm. The flash outputs status-register data when CE# or OE# is toggled. A Read
Array command is required after programming to read array data. See Section 4.2, “Program
Mode” on page 21.
20 Erase Set-Up
This is a two
-cycle command. Prepares the CUI for the Erase Confirm command. If the next
command is not an Erase Confirm command, then the CUI will (a) set both SR.4 and SR.5 of
the status register to a “1,” (b) place the device into the read-status-register mode, and (c) wait
for another command. See Section 4.3, “Erase Mode” on page 22.
D0
Erase Confirm
Program/Erase
Resume
Unlock Block
If the previous command was an Erase Set-Up command, then the CUI will close the address
and data latches and begin erasing the block indicated on the address pins. During program/
erase, the device will respond only to the Read Status Register, Program Suspend and Erase
Suspend commands, and will output status-register data when CE# or OE# is toggled.
If a Program or Erase operation was previously suspended, this command will resume that
operation.
If the previous command was Block Unlock Set-Up, the CUI will latch the address and unlock
the block indicated on the address pins. If the block had been previously set to Lock-Down, this
operation will have no effect. (See Section 5.1)
B0
Program Suspend
Erase Suspend
Issuing this command will begin to suspend the currently executing Program/Erase operation.
The status register will indicate when the operation has been successfully suspended by
setting either the program-suspend SR[2] or erase-suspend SR[6] and the WSM status bit
SR[7] to a “1” (ready). The WSM will continue to idle in the SUSPEND state, regardless of the
state of all input-control pins except RP#, which will immediately shut down the WSM and the
remainderofthechipifRP#isdriventoV
IL
. See Sections 3.2.5.1 and 3.2.6.1.
70
Read Status
Register
This command places the device into read-status-register mode. Reading the device will
output the contents of the status register, regardless of the address presented to the device.
The device automatically enters this mode after a Program or Erase operation has been
initiated. See Section 4.1.4, “Read Status Register” on page 20.
50
Clear Status
Register
The WSM can set the block-lock status SR[1], V
PP
Status SR[3], program status SR[4], and
erase-status SR[5] bits in the status register to “1,” but it cannot clear them to 0.” Issuing this
command clears those bits to “0.”
90
Read
Identifier
Puts the device into the read-identifier mode so that reading the device will output the
manufacturer/device codes or block-lock status. See Section 4.1.2, “Read Identifier” on
page 19.
60
Block Lock, Block
Unlock, Block
Lock-Down Set-
Up
Prepares the CUI for block-locking changes. If the next command is not Block Unlock, Block
Lock, or Block Lock-Down, then the CUI will set both the program and erase-status-register
bits to indicate a command-sequence error. See Section 5.0, “Security Modes” on page 27.
01 Lock-Block
If the previous command was Lock Set-Up, the CUI will latch the address and lock the block
indicated on the address pins. (See Section 5.1)
2F Lock-Down
If the previous command was a Lock-Down Set-Up command, the CUI will latch the address
and lock-down the block indicated on the address pins. (See Section 5.1)
98
CFI
Query
Puts the device into the CFI-Query mode so that reading the device will output Common Flash
Interface information. See Section 4.1.3 and Appendix C, “Common Flash Interface”.
C0
Protection
Program
Set-Up
This is a two-cycle command. The first cycle prepares the CUI for a program operation to the
protection register. The second cycle latches addresses and data information and initiates the
WSM to execute the Protection Program algorithm to the protection register. The flash outputs
status-register data when CE# or OE# is toggled. A Read Array command is required after
programming to read array data. See Section 5.5.
Intel
£
Advanced+ Boot Block Flash Memory (C3)
26 Datasheet
10 Alt. Prog Set-Up Operates the same as Program Set-up command. (See 0x40/Program Set-Up)
00
Invalid/
Reserved
Unassigned commands should not be used. Intel reserves the right to redefine these codes for
future functions.
NOTE: See Appendix A, “Write State Machine States” for mode transition information.
Table 8. Command Codes and Descriptions
Code
(HEX)
Device Mode Command Description
Table 9. Status Register Bit Definition
WSMS ESS ES PS VPPS PSS BLS R
76543210
NOTES:
SR[7] WRITE STATE MACHINE STATUS (WSMS)
1 = Ready
0=Busy
Check Write State Machine bit first to determine Word Program
or Block Erase completion, before checking program or erase-
status bits.
SR[6] = ERASE
-SUSPEND STATUS (ESS)
1 = Erase Suspended
0=EraseInProgress/Completed
When Erase Suspend is issued, WSM halts execution and sets
both WSMS and ESS bits to “1.” ESS bit remains set to “1” until
an Erase Resume command is issued.
SR[5] = ERASE STATUS (ES)
1=ErrorInBlockErase
0 = Successful Block Erase
When this bit is set to “1,” WSM has applied the max. number
of erase pulses to the block and is still unable to verify
successful block erasure.
SR[4] = PROGRAM STATUS (PS)
1 = Error in Programming
0 = Successful Programming
When this bit is set to “1,” WSM has attempted but failed to
program a word/byte.
SR[3] = V
PP
STATUS (VPPS)
1=V
PP
Low Detect, Operation Abort
0=V
PP
OK
The V
PP
status bit does not provide continuous indication of
V
PP
level. The WSM interrogates V
PP
level only after the
Program or Erase command sequences have been entered,
and informs the system if V
PP
has not been switched on. The
V
PP
is also checked before the operation is verified by the
WSM. The V
PP
status bit is not guaranteed to report accurate
feedback between V
PPLK
and V
PP1
Min.
SR[2] = PROGRAM SUSPEND STATUS (PSS)
1 = Program Suspended
0 = Program in Progress/Completed
When Program Suspend is issued, WSM halts execution and
sets both WSMS and PSS bits to “1.” PSS bit remains set to “1”
until a Program Resume command is issued.
SR[1] = BLOCK LOCK STATUS
1=Prog/Eraseattemptedonalockedblock;Operation
aborted.
0=Nooperationtolockedblocks
If a Program or Erase operation is attempted to one of the
locked blocks, this bit is set by the WSM. The operation
specifiedisabortedandthedeviceisreturnedtoreadstatus
mode.
SR[0] = RESERVED FOR FUTURE ENHANCEMENTS (R)
This bit is reserved for future use and should be masked out
when polling the status register.
NOTE: A Command-Sequence Error is indicated when SR[4], SR[5], and SR[7] are set.
Intel
£
Advanced+ Boot Block Flash Memory (C3)
Datasheet 27
5.0 Security Modes
5.1 Flexible Block Locking
The C3 device offers an instant, individual block-locking scheme that allows any block to be
locked or unlocked with no latency, enabling instant code and data protection.
This locking scheme offers two levels of protection. The first level allows software-only control of
block locking (useful for data blocks that change frequently), while the second level requires
hardware interaction before locking can be changed (useful for code blocks that change
infrequently).
The following sections will discuss the operation of the locking system. The term “state [abc]” will
be used to specify locking states; e.g., “state [001],” where a = value of WP#, b = bit D1 of the
Block Lock status register, and c = bit D0 of the Block Lock status register. Figure 5, “Block
Locking State Diagram” on page 27 displays all of the possible locking states.
Figure 5. Block Locking State Diagram
[X00]
[X01]
Power-Up/Reset
Unlocked
Locked
[011]
[111] [110]
Locked-
Down
4,5
Software
Locked
[011]
Hardware
Locked
5
Unlocked
WP#HardwareControl
Notes: 1. [a,b,c] represents [WP#, D1, D0]. X = Don’t Care.
2. D1 indicates block Lock-down status. D1 = ‘0’, Lock-down has not been issued to
this block. D1 = ‘1’, Lock-down has been issued to this block.
3. D0 indicates block lock status. D0 = 0’, block is unlocked. D0 = ‘1’, block is locked.
4. Locked-down = Hardware + Software locked.
5. [011] states should be tracked by system software to determine difference
between Hardware Locked and Locked-Down states.
Software Block Lock (0x60/0x01) or Software Block Unlock (0x60/0xD0)
Software Block Lock-Down (0x60/0x2F)
WP# hardware control
PREVIOUS23456789101112131415NEXT