LH28F016SC-L datasheet(13/44 Pages) SHARP

13 / 44 page

- 13 -

LH28F016SC-L/SCH-L

the device automatically outputs status register data

when read (see Fig. 3). The CPU can detect block

erase completion by analyzing the output data of

the RY/BY# 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

reliable block erasure can only occur when VCC =

VCC2/3/4 and VPP = VPPH1/2/3. In the absence of this

high voltage, block contents are protected against

erasure. If block erase is attempted while VPP

≤

VPPLK, 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 RP# = VHH. If

block erase is attempted when the corresponding

block lock-bit is set and RP# = VIH, SR.1 and SR.5

will be set to “1”. Block erase operations with VIH <

RP# < VHH produce spurious results and should

not be attempted.

4.6

Byte Write Command

Byte write is executed by a two-cycle command

sequence. Byte write setup (standard 40H or

alternate 10H) is written, followed by a second write

that specifies the address and data (latched on the

rising edge of WE#). The WSM then takes over,

controlling the byte write and write verify algorithms

internally. After the byte write sequence is written,

the device automatically outputs status register data

when read (see Fig. 4). The CPU can detect the

completion of the byte write event by analyzing the

RY/BY# pin or status register bit SR.7.

When byte write is complete, status register bit

SR.4 should be checked. If byte write error is

detected, the status register should be cleared. The

internal WSM verify only detects errors for “1”s that

do not successfully write to “0”s. The CUI remains

in read status register mode until it receives another

command.

Reliable byte writes can only occur when VCC =

VCC2/3/4 and VPP = VPPH1/2/3. In the absence of this

high voltage, memory contents are protected

against byte writes. If byte write is attempted while

VPP

≤ VPPLK, status register bits SR.3 and SR.4 will

be set to "1". Successful byte write requires that the

corresponding block lock-bit be cleared or, if set,

that RP# = VHH. If byte write is attempted when the

corresponding block lock-bit is set and RP# = VIH,

SR.1 and SR.4 will be set to "1". Byte write

operations with VIH < RP# < VHH produce spurious

results and should not be attempted.

4.7

Block Erase Suspend Command

The Block Erase Suspend command allows block

erase interruption to read or byte write data in

another block of memory. Once the block erase

process starts, writing the Block Erase Suspend

command requests that the WSM suspend the

block erase sequence at a predetermined point in

the algorithm. The device outputs status register

data when read after the Block Erase Suspend

command is written. Polling status register bits

SR.7 and SR.6 can determine when the block

erase operation has been suspended (both will be

set to "1"). RY/BY# will also transition to VOH.

Specification tWHRH2 defines the block erase

suspend latency.

At this point, a Read Array command can be

written to read data from blocks other than that

which is suspended. A Byte Write command

sequence can also be issued during erase suspend

to program data in other blocks. Using the Byte

LH28F016SC-L Datasheet(PDF) 13 Page - Sharp Corporation

LH28F016SC-L Datasheet(HTML) 13 Page - Sharp Corporation

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

Datasheet Download

Link URL