LH28F0020SUT-N80 View Datasheet(PDF) - Sharp Electronics

Part Name

Description

Manufacturer

LH28F0020SUT-N80

2M (256K × 8) Flash Memory

Sharp Electronics 

LH28F020SU-N

2M (256K × 8) Flash Memory

2M FLASH MEMORY

SOFTWARE ALGORITHMS

Overview

With the advanced Command User Interface, its Per-

formance Enhancement commands and Status Regis-

ters, the software code required to perform a given

operation may become more intensive but it will result

in much higher write/erase performance compared with

current flash memory architectures.

The software flow charts describing how a given

operation proceeds are shown here Figure 5 through

Figure 7 depict flowcharts using the second generation

flash device in the LH28F008SA compatible mode.

Figure 8 through Figure 14 depict flowcharts using the

second generation flash device’s performance enhance-

ment commands mode.

When the device power-up or reset is completed, all

blocks come up locked. Therefore, Byte Write, Two Byte

Serial Write and Block Erase cannot be performed in

each block. However, at that time, Erase All Unlocked

Block is performed normally, if used, and reflect actual

lock status, also the unlocked block data is erased. When

the device power-up or reset is completed, Set Write

Protect command must be written to reflect actual block

lock status.

Reset Write Protect command must be written

before Write Block Lock command.To reflect actual block

lock status, Set Write Protect command is succeeded.

The Compatible Status Register (CSR) is used to

determine which blocks are locked. In order to see Lock

Status of certain block, a Byte Write command (WA =

Block Address, WD = FFH) is written to the CUI, after

issuing Set Write Protect command. If CSR.7, CSR.5,

and CSR.4 (WSMS, ES and DWS) are set to ‘1’s, the

block is locked. If CSR.7 is set to ‘1’, the block is not

locked.

Reset Write Protect command enables Write/Erase

operation to each block.

In the case of Block Erase is performed, the block

lock information is also erased. Block Lock command

and Set Write Protect command must be written to

prohibit Write/Erase operation to each block.

There are unassigned commands. It is not recom-

mended that the customer use any command other than

the valid commands specified in “Command Bus Defi-

nitions”. Sharp reserves the right to redefine these codes

for future functions.

8

Share Link: