DatasheetQ Logo
Electronic component search and free download site. Transistors,MosFET ,Diode,Integrated circuits

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

Номер в каталоге
Компоненты Описание
производитель
LH28F800SGR-L70
Sharp
Sharp Electronics Sharp
LH28F800SGR-L70 Datasheet PDF : 45 Pages
First Prev 11 12 13 14 15 16 17 18 19 20 Next Last
set block or permanent lock-bit setup along with
appropriate block or device address is written
followed by either the set block lock-bit confirm (and
an address within the block to be locked) or the set
permanent lock-bit confirm (and any device
address). The WSM then controls the set lock-bit
algorithm. After the sequence is written, the device
automatically outputs status register data when
read (see Fig. 7). The CPU can detect the
completion of the set lock-bit event by analyzing the
RY/BY# pin output or status register bit SR.7.
When the set lock-bit operation is complete, status
register bit SR.4 should be checked. If an error is
detected, the status register should be cleared. The
CUI will remain in read status register mode until a
new command is issued.
This two-step sequence of set-up followed by
execution ensures that lock-bits are not accidentally
set. An invalid Set Block or Permanent Lock-Bit
command will result in status register bits SR.4 and
SR.5 being set to "1". Also, reliable operations
occur only when VCC = VCC1/2/3/4 and VPP =
VPPH1/2/3. In the absence of this high voltage, lock-
bit contents are protected against alteration.
A successful set block lock-bit operation requires
that the permanent lock-bit be cleared and WP# =
VIH or RP# = VHH. If it is attempted with the
permanent lock-bit set, SR.1 and SR.4 will be set
to "1" and the operation will fail. Set block lock-bit
operations while VIH < RP# < VHH produce
spurious results and should not be attempted. A
successful set permanent lock-bit operation requires
that RP# = VHH. If it is attempted with RP# = VIH,
SR.1 and SR.4 will be set to "1" and the operation
will fail. Set permanent lock-bit operations with VIH
< RP# < VHH produce spurious results and should
not be attempted.
LH28F800SG-L/SGH-L (FOR TSOP, CSP)
4.10 Clear Block Lock-Bits Command
All set block lock-bits are cleared in parallel via the
Clear Block Lock-Bits command. With the
permanent lock-bit not set and WP# = VIH or RP#
= VHH, block lock-bits can be cleared using the
Clear Block Lock-Bits command. If the permanent
lock-bit is set, clear block lock-bits operation is
unable. See Table 5 for a summary of hardware
and software write protection options.
Clear block lock-bits option is executed by a two-
cycle command sequence. A clear block lock-bits
setup is first written. After the command is written,
the device automatically outputs status register data
when read (see Fig. 8). The CPU can detect
completion of the clear block lock-bits event by
analyzing the RY/BY# pin output or status register
bit SR.7.
When the operation is complete, status register bit
SR.5 should be checked. If a clear block lock-bits
error is detected, the status register should be
cleared. The CUI will remain in read status register
mode until another command is issued.
This two-step sequence of set-up followed by
execution ensures that block lock-bits are not
accidentally cleared. An invalid Clear Block Lock-Bits
command sequence will result in status register bits
SR.4 and SR.5 being set to "1". Also, a reliable clear
block lock-bits operation can only occur when VCC =
VCC1/2/3/4 and VPP = VPPH1/2/3. In a clear block lock-
bits operation is attempted while VPP VPPLK, SR.3
and SR.5 will be set to "1". In the absence of this
high voltage, the block lock-bit contents are
protected against alteration. A successful clear block
lock-bits operation requires that the permanent lock-
bit is not set and WP# = VIH or RP# = VHH. If it is
attempted with the permanent lock-bit set or WP# =
VIL and RP# = VIH, SR.1 and SR.5 will be set to "1"
and the operation will fail. A clear block lock-bits
operation with VIH < RP# < VHH produce spurious
results and should not be attempted.
- 15 -

Share Link: 

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