Auto-Select VCC and VPP Voltages
– 2.7 V, 3.3 V, or 5 V Read Operation (V
– 2.7 V, 3.3 V, 5 V, or 12 V Program Erase
(V
)
PP
D
Fast Read Access Time
– 5 V:80/90 ns MAX
– 2.7 V, 3.3 V:90/100 ns MAX
D
Low Power Consumption (VCC = 5.5V)
– Active Write220 mW (Byte Mode)
– Active Read248 mW (Byte Mode)
– Active Write220 mW (Word Mode)
– Active Read248 mW (Word Mode)
– Block-Erase220 mW
– Standby0.55 mW
– Deep Power-Down Mode 0.044 mW
D
Automatic Power-Saving Mode
D
Sector Architecture
– One 16K-Byte Protected Boot Block
– Two 8K-Byte Parameter Blocks
– One 96K-Byte Main Block
– Fifteen 128K-Byte Main Blocks
– Top or Bottom Boot Locations
D
User-Selectable x8 or x16 Operation
D
Fully Automated On-Chip Erase and
Byte/Word Program Operations
D
All Inputs/Outputs TTL-Compatible
D
Supports Concurrent Operations
– Read During Program
– Read During Erase
– Program During Erase
– Two-Byte/-Word Programming
– Two Sector Combinations Erasure
†
†
†
CC
†
†
TMS28F1600T, TMS28F1600B
16M-BIT (1M BY 16, 2M BY 8)
SMJS836 – JANUARY 1997
D
Enhanced Suspend Options
)
– Sector-Erase-Suspend to Read
– Sector-Erase-Suspend to Program
– Program-Suspend to Read
D
Command Set Compatible With Previous
Generation of Flash
D
Transition Between Single-Operation and
Concurrent-Operations Mode by way of
Software Command
D
100000 Program/Erase Cycles Per Sector
D
Hardware Write-Protection for Boot Block
D
Two Temperature Ranges
– Commercial0°C to 70° C
– Extended–40°C to 85° C
D
Industry Standard Packaging (JEDEC)
– 48-Pin TSOP (DCD Suffix)
PIN NOMENCLATURE
A0–A19Address Inputs
BYTE
DQ0–DQ14Data In/Data out
DQ15/A–1Data In/Out (word-wide mode)
CE
OE
NCNo Internal Connection
RP
V
CC
V
PP
V
SS
WE
WP
Byte Enable
Low Order Address (byte-wide mode)
Chip Enable
Output Enable
Reset/Deep Power Down
Power Supply
Power Supply for Program/Erase
Ground
Write Enable
Write Protect
PRODUCT PREVIEW
description
The TMS28F1600T/B is a 16777216-bit, boot-block flash memory that can be electrically block-erased and
reprogrammed. The TMS28F1600T/B is organized in a sectored architecture consisting of one 16K-byte
protected boot sector, two 8K-byte parameter sectors, one 96K-byte main sector, and fifteen 128K-byte main
sectors. Operation as a 2M-byte (8-bit) or a 1M-word (16-bit) organization is user-selectable.
Embedded program and block-erase functions are fully automated by two on-chip write state machines
(WSMs), simplifying these operations and relieving the system microcontroller of these secondary tasks. WSM
statuses can be monitored by two on-chip status registers, one for each WSM, to determine progress of
program/erase tasks.
Please be aware that an important notice concerning availability, standard warranty, and use in critical applications of
Texas Instruments semiconductor products and disclaimers thereto appears at the end of this data sheet.
†
In single-operation mode
PRODUCT PREVIEW information concerns products in the formative or
design phase of development. Characteristic data and other
specifications are design goals. Texas Instruments reserves the right to
change or discontinue these products without notice.
POST OFFICE BOX 1443 • HOUSTON, TEXAS 77251–1443
Copyright 1997, Texas Instruments Incorporated
1
TMS28F1600T, TMS28F1600B
16M-BIT (1M BY 16, 2M BY 8)
CONCURRENT OPERATIONS AUTO-SELECT BOOT-BLOCK FLASH MEMORY
The ’28F1600 has the auto-select feature that allows the user alternative read and program/erase voltages for
maximum flexibility . Memory reads can be performed using V
or at V
V
PP
Alternatively, 12-V V
= 5 V for device performance. Erasing or programming the device can be accomplished with
CC
= 2.7 V, 3.3 V, or 5 V which eliminates having to use a 12-V source and/or in-system voltage converters.
operation exists for systems that already have a 12-V power supply.
PP
device symbol nomenclature
80CDCDLTMS28F1600
T
Temperature Range Designator
L=0°Cto70°C
E = – 40°Cto85°C
Package Designator
DCD = Plastic Dual Small-Outline Package (48-Pin)
Program/Erase Endurance
C = 100000 Cycles
B = 10000 Cycles
= 2.7 or 3.3 V for optimum power consumption
CC
Speed Designator
80 = 80 ns
90 = 90 ns
Boot-Block Location Indicator
T = Top Location
B = Bottom Location
†
DEVICE CONFIGURATIONREAD VOLTAGE (VCC)PROGRAM/ERASE VOLTAGE (VPP)
TMS28F1600T2.7 V to 3.6 V, 5 V ± 10 %3 V/5 V ± 10% or 12 V " 5%
TMS28F1600B2.7 V to 3.6 V, 5 V ± 10 %3 V/5 V ± 10% or 12 V " 5%
†
3-V range indicates 2.7 V to 3.6 V maximum.
Table 1. VCC/VPP Voltage Configurations
architecture
The TMS28F1600T/B uses a sectored architecture to allow independent erasure of selected memory blocks.
The sector to be erased is selected by using any valid address within that sector.
The TMS28F1600T/B has two (2) memory banks. Bank A consists of:
D
One 16K-byte protected boot sector
D
Two 8K-byte parameter sectors
D
One 96K-byte main sector and
PRODUCT PREVIEW
D
Seven 128K-byte main sectors
and bank B consists of:
D
Eight 128K-byte main sectors
POST OFFICE BOX 1443 • HOUSTON, TEXAS 77251–1443
3
TMS28F1600T, TMS28F1600B
All sectors unlocked
16M-BIT (1M BY 16, 2M BY 8)
CONCURRENT OPERATIONS AUTO-SELECT BOOT-BLOCK FLASH MEMORY
SMJS836 – JANUARY 1997
architecture (continued)
Embedded program and block-erase functions for each memory bank are fully automated by a separate and
independent WSM. With two WSMs, each controlling one memory bank (8M bits of memory space), the overall
system performance is greatly improved by allowing the device to be programmed/erased in one bank while
simultaneously reading data from another sector of the other memory bank. The device also can be
erased/programmed in one sector of one memory bank while simultaneously erased/programmed in another
sector of the other memory bank.
Within each bank, the suspend command can be used to suspend the erase operation to read from or program
data to another sector not being erased. The suspend command can be used also to suspend the program
operation so that data from any address location other than the one being programmed can be read.
The TMS28F1600 is available with the sector architecture mapped with the boot block located at the top
(TMS28F1600T) or at the bottom (TMS28F1600B) of the memory array, as required by different
microprocessors. The bottom boot block is mapped with the 16K-byte boot block located at the low-order
address range (00000h to 01FFFh, word mode). The top boot block is mapped with the 16K-byte boot block
located at the high-order address range (FFFFFh to FE000h, word mode). Figure 1 and Figure 2 show the
memory maps for the top and bottom boot block configuration, respectively.
boot-sector data protection
The 16K-byte boot block can be used to store key system data that is seldom changed in normal operation. Data
in this block can be protected by using different combinations of the reset/power-down pin (RP
pin (WP
) and VPP supply levels. See Table 2 for a listing of these combinations.
TMS28F1600T, TMS28F1600B
16M-BIT (1M BY 16, 2M BY 8)
CONCURRENT OPERATIONS AUTO-SELECT BOOT-BLOCK FLASH MEMORY
SMJS836 – JANUARY 1997
parameter sector
Two parameter sectors of 8K bytes each can be used like a scratch pad to store frequently updated data.
Alternatively , the parameter sectors can be used for additional boot or main-sector data. If a parameter sector
is used to store additional boot-block data, caution should be exercised because the parameter sector does not
have the boot-block data protection safety feature.
main sector
Primary memory on the TMS28F1600T/B is located in sixteen main sectors. Fifteen of the sectors have storage
capacity for 128K-bytes and the remaining sector has storage capacity of 96K bytes.
Data is secured or unsecured by using different combinations of the reset/power-down pin (RP), the write
protect pin (WP
) and VPP supply levels. Table 2 lists these combinations.
There are two ways to secure the entire memory against inadvertent alteration of data. The V
be held below the V
a logic-low level. Note that if RP
lock-out voltage level (V
PP
is held low, the device resets, which means it powers down and, therefore,
) or the reset/deep power-down pin (RP) can be pulled to
PPLK
supply pin can
PP
cannot be read. Typically, this pin is tied to the system reset for additional protection during system power up.
The boot sector has an additional security feature through the WP
the WP
is protected. When WP
pin controls whether the boot sector is protected. When WP is held at logic-low level, the boot sector
is held at logic-high level, the boot sector is unprotected along with the rest of the other
sectors. Alternatively, the entire memory can be unprotected by pulling the RP
pin. When the RP pin is at logic-high level,
pin to VHH (12 V).
command state machine (CSM)
There are two CSMs and each is corresponded to one WSM. The CSMs act as an interface between the external
microprocessor and the two internal WSMs. Commands are issued to the CSMs using standard microprocessor
write timings. Since both CSMs share the same data path, commands issued to the device are processed by
both CSMs simultaneously . If CSM A determines that the command is not applicable to the memory bank/WSM
that it is interfacing with (memory bank A), then that command is ignored and CSM B sends the command to
bank B/WSM B for execution. The CSM main task is to determine if the inputted command is valid and to send
the valid command to the corresponding WSM. In single-operation mode, the contents of both status registers
and the state of both CSMs are synchronized. Therefore, from the user’s point of view, the device behaves as
if there is only one CSM, one status register and one WSM that control both memory banks. In
concurrent-operations mode, the contents of both status registers and the state of both CSMs are independent.
When a program or erase command is issued to the CSM for one memory bank, the WSM for that memory bank
controls the internal program/erase sequences and the CSM responds to status-read and suspend/resume
only. After the WSM completes its task, the WSM status bit (SB7) is set to a logic-high level (1), allowing the
CSM to respond to the full command set again (see Table 5 for the status register bit definition). The complete
command sets are listed in Table 3 and the description of these commands are shown in Table 4.
Table 3. Command State Machine Codes for Device-Mode Selection
COMMAND CODE
ON DQ0–DQ7
00hInvalid / Reserved
10hAlternate Program Setup
20hBlock-Erase Setup
40hProgram Setup
50hClear Status Register
70hRead Status Register
DQ0 is the least significant bit. DQ8–DQ15 can be any valid 2-state level.
†
Standard Command Set
Extended Command Set
DEVICE MODE
PRODUCT PREVIEW
POST OFFICE BOX 1443 • HOUSTON, TEXAS 77251–1443
9
TMS28F1600T, TMS28F1600B
BUS CYCLE
16M-BIT (1M BY 16, 2M BY 8)
CONCURRENT OPERATIONS AUTO-SELECT BOOT-BLOCK FLASH MEMORY
SMJS836 – JANUARY 1997
command state machine (CSM) (continued)
Table 4. Command Definitions for Single and Concurrent Operations
FIRST BUS CYCLESECOND BUS CYCLE
COMMAND
Read Array1Write
Read Algorithm-Selection Code3WriteX90hReadA0M/D
Read Status Register2WriteX70hRead
Clear Status Register1Write
Program-Setup / Program
(byte/word)
Program-Suspend/
Program-Resume
Block-Erase Setup/
Block-Erase Confirm
Erase-Suspend/
Erase-Resume
Enable Concurrent Mode
(see Note 2)
Disable Concurrent Mode
(see Note 2)
Legend:
PRODUCT PREVIEW
BEABlock-erase address. Any address selected within a block selects that block for erase.
M/DManufacturer-equivalent / device-equivalent code
PAAddress to be programmed
PDData to be programmed at PA
RAAddress to be read from
SRBStatus-register data byte that can be found on DQ0–DQ7
XDon’t care
NOTES: 1. For single operation: address = don’t care
For concurrent operation:
address = 0xxxxxh for low-order address memory bank/WSM
address = 1xxxxxh for high-order address memory bank/WSM
2. To operate the device concurrently , the user must first issue the enable concurrent mode command. This command is valid only when
the device is not busy performing any operation (that is, WSM is not active). To exit the concurrent-operation mode, the user must
issue the disable concurrent mode command. This command is valid only when the device is in concurrent-operations mode and
none of the memory banks/WSMs are active.
The TMS28F1600T/B is capable of performing either single or concurrent operations. Single operation means
that the device is performing one operation on one memory bank at a time, or in other words, only one WSM
is active. A WSM is considered active even when it is in a suspended state. Therefore, from the user’s point
of view, the device behaves as if there is only one WSM that controls both memory banks. Concurrent operations
mean that the device is performing two operations on two memory banks simultaneously , or in other words, both
WSMs are active.
Device operations are selected by entering 8-bit command codes with conventional microprocessor timing into
two on-chip CSMs through I/O pins DQ0–DQ7. When the device is powered up, internal reset circuitry initializes
the CSMs to single-operation, read-array mode. In single-operation mode, the device is functionally compatible
with the existing 8-Mbit boot-block devices (TMS28F800T/B). Changing the mode of operation requires a
command code to be entered into the CSM. Table 3 lists the CSM codes for all modes of operation.
To enable the concurrent-operations mode, the user must issue the enable concurrent mode command to the
CSM. This command is valid only when the device is not busy performing any operation (that is, WSM is not
active). Once the concurrent-operations mode is enabled, both status registers are cleared, both CSMs are
reset to the read-array mode, and any commands issued to the CSMs from that point forward must be in
accordance with the concurrent-operations command definitions. Command definitions for both single and
concurrent-operations modes are listed in Table 4. Note that both command definitions are the same except
for four commands: read array, read status register, clear status register, and suspend/resume. In
single-operation mode, the addresses are don’t care for those commands. However, in concurrent-operations
mode, the user must indicate to the CSMs to which write-state machine/memory bank the command is
applicable by supplying the memory bank address. This is the only difference between single and concurrent
operations as far as command definitions are concerned.
To initiate concurrent operations once the concurrent mode is enabled, the user sequentially issues two
commands to the CSMs, one for each memory bank; the issued commands must be in accordance with the
concurrent-operations command definitions. Note that while the concurrent mode is enabled, the user does not
have to operate the device concurrently; the user can operate the device as in single-operation mode but with
the command definitions slightly modified. In addition, the user can access and clear each status register
individually in concurrent mode.
To exit the concurrent-operations mode and return to the standard flash single-operation mode, the user must
issue a disable concurrent mode command to the CSMs. This command is valid only when the device is in
concurrent-operations mode and none of the memory banks/WSMs are active. Once concurrent-operations
mode is disabled, both status registers are cleared and both CSMs reset to the read-array mode. Alternatively ,
the user can use the reset/power-down mode to reset the device to single-operation, read-array mode.
Since both registers are cleared when concurrent-operations mode is enabled/disabled, it is recommended that
the status register be read, if required, before the concurrent mode is enabled/disabled.
concurrent operations
Since the TMS28F1600T /B has two independent WSMs, two operations can be performed on two memory
banks concurrently. However, there are some rules and restrictions that must be adhered to when operating
the device concurrently.
First, read is an operation that cannot be performed concurrently with another read. Second, if read is to be a
part of a concurrent operation, then read must be the last command issued to the CSM. Third, once a read
command is issued, the CSM does not accept
array , read algorithm-selection, read status register and clear status register commands are considered to be
the same (that is, a read operation) as far as concurrent operations are concerned.
any other command
until the read operation is complete. Read
PRODUCT PREVIEW
POST OFFICE BOX 1443 • HOUSTON, TEXAS 77251–1443
11
TMS28F1600T, TMS28F1600B
16M-BIT (1M BY 16, 2M BY 8)
CONCURRENT OPERATIONS AUTO-SELECT BOOT-BLOCK FLASH MEMORY
SMJS836 – JANUARY 1997
concurrent operations (continued)
For example, a concurrent read-erase operation is
command, no other command is processed until the read operation is complete. Whereas, a concurrent
erase-read operation is possible because the erase command is given first (for example, to erase a sector in
memory bank A) and the read command is given last (for example, to access bank B). Only when the read
operation is complete, is the CSM ready to accept any other valid command. At this point, the user has two
options from which to choose. If operation on memory bank B is desired, then the user can send a read, program,
or erase command. If operation on memory bank A is desired, then the user can either do an erase-suspend
to read or an erase-suspend to program; both of which must be done in a sector that is not being erased.
Two rules/restrictions govern the suspend operation:
D
Read array, read status register, and program-resume are the only valid commands for the applicable
WSM / memory bank after a program operation is suspended; all other commands are invalid and are
ignored by the CSM. If concurrent-operations mode is enabled, then the other CSM will accept any other
valid command for the other WSM/memory bank.
D
Read array , read status register, program, and erase-resume are the only valid commands for the applicable
WSM/memory bank after a sector-erase operation is suspended; all other commands are invalid and are
ignored by the CSM. If concurrent-operations mode is enabled, then the other CSM will accept any other
valid command for the other WSM/memory bank.
In general, any operation or combination of operations is possible as long as it does not violate the
rules/restrictions mentioned above. Note that multiple suspension within the same memory bank is allowed.
For example, if an erase operation is suspended for a program operation, then that program operation can also
be suspended to read data. Table 5 shows all the legal operations that can be performed concurrently.
not
possible because as soon as the CSM receives the read
Reset/deep power-down places both write-state machines/memory banks in the reset/deep power-down mode.
‡
Read array, algorithm-selection, read status register, and clear status register are considered “read” operations. Therefore, if a read operation is to be a part of concurrent operations,
it must be the last command issued. If the read operation is issued first, then the CSM will not process any other command until the read operation is complete.
§
Either WSM can access the manufacturer and device ID information
¶
The clear-status-register and read-algorithm-selection commands are not functional during erase-suspend and program-suspend modes.
PRODUCT PREVIEW
SMJS836 – JANUARY 1997
TMS28F1600T, TMS28F1600B
16M-BIT (1M BY 16, 2M BY 8)
CONCURRENT OPERATIONS AUTO-SELECT BOOT-BLOCK FLASH MEMORY
SMJS836 – JANUARY 1997
command definition
Command definitions for both single and concurrent operations are listed in Table 4. Note that both command
definitions are the same except for four commands: read array, read status register, clear status register, and
suspend / resume. In single-operation mode, the address is a don’t care for these commands. However, in
concurrent-operations mode, the user must indicate to the CSM which write-state machine/memory bank the
command is applicable to by supplying the memory bank address.
In single-operation mode, the user can use either single or concurrent operations command definitions to send
the desired command to the CSM. However, once the concurrent-operations mode is enabled, all subsequent
commands issued must be in accordance with the concurrent-operations mode command definitions.
Once a specific command code has been entered, the WSM executes an internal algorithm generating the
necessary timing signals to program, erase, and verify data. See Table 4 for the CSM command definitions and
data for each of the bus cycles.
Following the read-algorithm-selection-code command, two read cycles are required to access the
manufacturer-equivalent code and the device-equivalent code. Table 7 and Table 8 show the code for
word-wide mode and byte-wide mode, respectively.
status register
There are two 8-bit on-chip status registers. Status register A corresponds to WSM A and status register B
corresponds to WSM B. The status register can be monitored to see whether the state of a program/erase
operation is pending or complete by writing a read-status command to the CSM and reading the resulting status
code on I/O pins DQ0–DQ7. This is valid for operation in either the byte or word-wide mode. When writing to
the CSM in word-wide mode, the high-order I/O pins (DQ8–DQ15) can be set to any valid 2-state level. When
reading the status bit during a word-wide read operation, the high-order I / Os (DQ8–DQ15) are set to 00h
internally, so the user needs to interpret only the low-order I/O pins (DQ0–DQ7).
After a read-status command has been given, the data appearing on DQ0–DQ7 remains as status register data
until a new command is issued to the CSM. To return the device to other modes of operation, a new command
must be issued to the CSM.
Register data is updated on the falling edge of OE
updates the latches within a given read cycle. Latching the data prevents errors from occurring should the
PRODUCT PREVIEW
register input change during a status register read. To assure that the status register output contains updated
status data, CE
The status registers provide the internal state of the WSMs to the external microprocessor. During periods when
the WSMs are active, the status registers can be polled to determine the status of the WSMs. Table 6 defines
the status register bits and their functions.
In single-operation mode, the contents of both status registers and the state of both CSMs are synchronized.
Therefore, from the user’s point of view, the device behaves as if only one CSM, one status register, and one
WSM are controlling both memory banks. In concurrent-operations mode, the contents of both status registers
and the state of both CSMs are independent. Therefore, in concurrent-operations mode, the user can access
and clear each status register individually.
or OE must be toggled for each subsequent status read.
or CE. The latest falling edge of either of these two signals
14
POST OFFICE BOX 1443 • HOUSTON, TEXAS 77251–1443
Loading...
+ 30 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.