datasheetbank_Logo
Технический паспорт Поисковая и бесплатно техническое описание Скачать

LH28F320S5-L100 Просмотр технического описания (PDF) - Sharp Electronics

Номер в каталоге
Компоненты Описание
Список матч
LH28F320S5-L100
Sharp
Sharp Electronics Sharp
LH28F320S5-L100 Datasheet PDF : 61 Pages
First Prev 11 12 13 14 15 16 17 18 19 20 Next Last
sharp
LHF32K10
16
4.6 Block Erase Command
Block erase is executed one block at a time and
initiated by a two-cycle command. A block erase
setup is first written, followed by an block erase
confirm. This command sequence requires
appropriate sequencing and an address within the
block to be erased (erase changes all block data to
FFH). Block preconditioning, erase and verify are
handled internally by the WSM (invisible to the
system). After the two-cycle block erase sequence is
written, the device automatically outputs status
register data when read (see Figure 5). The CPU can
detect block erase completion by analyzing the
output data of the STS pin or status register bit SR.7.
When the block erase is complete, status register bit
SR.5 should be checked. If a block erase error is
detected, the status register should be cleared before
system software attempts corrective actions. The CUI
remains in read status register mode until a new
command is issued.
This two-step command sequence of set-up followed
by execution ensures that block contents are not
accidentally erased. An invalid Block Erase command
sequence will result in both status register bits SR.4
and SR.5 being set to "1". Also, reliable block erasure
can only occur when VCC=VCC1/2 and VPP=VPPH1. In
the absence of this high voltage, block contents are
protected against erasure. If block erase is attempted
while VPPVPPLK, SR.3 and SR.5 will be set to "1".
Successful block erase requires that the
corresponding block lock-bit be cleared or if set, that
WP#=VIH. If block erase is attempted when the
corresponding block lock-bit is set and WP#=VIL,
SR.1 and SR.5 will be set to "1".
4.7 Full Chip Erase Command
This command followed by a confirm command
(D0H) erases all of the unlocked blocks. A full chip
erase setup is first written, followed by a full chip
erase confirm. After a confirm command is written,
device erases the all unlocked blocks from block 0 to
Block 63 block by block. This command sequence
requires appropriate sequencing. Block
preconditioning, erase and verify are handled
internally by the WSM (invisible to the system). After
the two-cycle full chip erase sequence is written, the
device automatically outputs status register data
when read (see Figure 6). The CPU can detect full
chip erase completion by analyzing the output data of
the STS pin or status register bit SR.7.
When the full chip erase is complete, status register
bit SR.5 should be checked. If erase error is
detected, the status register should be cleared before
system software attempts corrective actions. The CUI
remains in read status register mode until a new
command is issued. If error is detected on a block
during full chip erase operation, WSM stops erasing
the block and begin to erase the next block. Reading
the block valid status by issuing Read ID Codes
command or Query command informs which blocks
failed to its erase.
This two-step command sequence of set-up followed
by execution ensures that block contents are not
accidentally erased. An invalid Full Chip Erase
command sequence will result in both status register
bits SR.4 and SR.5 being set to "1". Also, reliable full
chip erasure can only occur when VCC=VCC1/2 and
VPP=VPPH1. In the absence of this high voltage, block
contents are protected against erasure. If full chip
erase is attempted while VPPVPPLK, SR.3 and SR.5
will be set to "1". When WP#=VIH, all blocks are
erased independent of block lock-bits status. When
WP#=VIL, only unlocked blocks are erased. Full chip
erase can not be suspended.
Rev. 1.55

Share Link: 

datasheetbank.com [ Privacy Policy ] [ Request Datasheet ] [ Contact Us ]