LH28F160BJB-TTL90 LHF16J10 16M-BIT DQ0-DQ15 48-BALL A0-A19 A15-A19 A12-A19 - Datasheet Archive

 

16M (x8/x16) Flash Memory LH28F160BJB-TTL90 May. 23. 2000 LHF16J10 qHandle this document carefully for it contains material

 

Date 16M (x8/x16) Flash Memory LH28F160BJB-TTL90 LH28F160BJB-TTL90 May. 23. 2000 LHF16J10 LHF16J10 qHandle this document carefully for it contains material protected by international copyright law. Any reproduction, full or in part, of this material is prohibited without the express written permission of the company. qWhen using the products covered herein, please observe the conditions written herein and the precautions outlined in the following paragraphs. In no event shall the company be liable for any damages resulting from failure to strictly adhere to these conditions and precautions. (1) The products covered herein are designed and manufactured for the following application areas. When using the products covered herein for the equipment listed in Paragraph (2), even for the following application areas, be sure to observe the precautions given in Paragraph (2). Never use the products for the equipment listed in Paragraph (3). ·Office electronics ·Instrumentation and measuring equipment ·Machine tools ·Audiovisual equipment ·Home appliance ·Communication equipment other than for trunk lines (2) Those contemplating using the products covered herein for the following equipment which demands high reliability, should first contact a sales representative of the company and then accept responsibility for incorporating into the design fail-safe operation, redundancy, and other appropriate measures for ensuring reliability and safety of the equipment and the overall system. ·Control and safety devices for airplanes, trains, automobiles, and other transportation equipment ·Mainframe computers ·Traffic control systems ·Gas leak detectors and automatic cutoff devices ·Rescue and security equipment ·Other safety devices and safety equipment, etc. (3) Do not use the products covered herein for the following equipment which demands extremely high performance in terms of functionality, reliability, or accuracy. ·Aerospace equipment ·Communications equipment for trunk lines ·Control equipment for the nuclear power industry ·Medical equipment related to life support, etc. (4) Please direct all queries and comments regarding the interpretation of the above three Paragraphs to a sales representative of the company. qPlease direct all queries regarding the products covered herein to a sales representative of the company. Rev. 1.26 LHF16J10 LHF16J10 1 CONTENTS PAGE PAGE 1 INTRODUCTION. 3 5 DESIGN CONSIDERATIONS . 25 1.1 Features . 3 5.1 Three-Line Output Control . 25 1.2 Product Overview. 3 5.2 RY/BY# and WSM Polling . 25 1.3 Product Description. 4 5.3 Power Supply Decoupling . 25 1.3.1 Package Pinout . 4 5.4 VCCW Trace on Printed Circuit Boards . 25 1.3.2 Block Organization. 4 5.5 VCC, VCCW, RP# Transitions . 25 5.6 Power-Up/Down Protection. 26 2 PRINCIPLES OF OPERATION. 7 5.7 Power Dissipation . 26 2.1 Data Protection. 8 5.8 Data Protection Method . 26 3 BUS OPERATION . 8 6 ELECTRICAL SPECIFICATIONS . 27 3.1 Read. 8 6.1 Absolute Maximum Ratings . 27 3.2 Output Disable. 8 6.2 Operating Conditions . 27 3.3 Standby. 8 6.2.1 Capacitance . 27 3.4 Reset. 8 6.2.2 AC Input/Output Test Conditions . 28 3.5 Read Identifier Codes. 9 6.2.3 DC Characteristics . 29 3.6 Write. 9 6.2.4 AC Characteristics - Read-Only Operations . 31 6.2.5 AC Characteristics - Write Operations . 34 4 COMMAND DEFINITIONS. 9 6.2.6 Alternative CE#-Controlled Writes. 36 4.1 Read Array Command. 12 6.2.7 Reset Operations . 38 4.2 Read Identifier Codes Command . 12 6.2.8 Block Erase, Full Chip Erase, Word/Byte Write and 4.3 Read Status Register Command . 12 Lock-Bit Configuration Performance . 39 4.4 Clear Status Register Command. 12 4.5 Block Erase Command. 13 4.6 Full Chip Erase Command . 13 4.7 Word/Byte Write Command. 13 4.8 Block Erase Suspend Command . 14 4.9 Word/Byte Write Suspend Command . 14 4.10 Set Block and Permanent Lock-Bit Command. 15 4.11 Clear Block Lock-Bits Command . 15 4.12 Block Locking by the WP# . 16 Rev. 1.26 LHF16J10 LHF16J10 2 LH28F160BJB-TTL90 LH28F160BJB-TTL90 16M-BIT 16M-BIT ( 1Mbit ×16 / 2Mbit ×8 ) Boot Block Flash MEMORY s Low Voltage Operation VCC=VCCW=2.7V-3.6V Single Voltage s User-Configurable ×8 or ×16 Operation s High-Performance Read Access Time 90ns(VCC=2.7V-3.6V) s Operating Temperature 0°C to +70°C s Low Power Management Typ. 2µA (VCC=3.0V) Standby Current Automatic Power Savings Mode Decreases ICCR in Static Mode Typ. 120µA (VCC=3.0V, TA=+25°C, f=32kHz) Read Current s Optimized Array Blocking Architecture Two 4K-word (8K-byte) Boot Blocks Six 4K-word (8K-byte) Parameter Blocks Thirty-one 32K-word (64K-byte) Main Blocks Top Boot Location s Extended Cycling Capability Minimum 100,000 Block Erase Cycles s Enhanced Automated Suspend Options Word/Byte Write Suspend to Read Block Erase Suspend to Word/Byte Write Block Erase Suspend to Read s Enhanced Data Protection Features Absolute Protection with VCCWVCCWLK Block Erase, Full Chip Erase, Word/Byte Write and Lock-Bit Configuration Lockout during Power Transitions Block Locking with Command and WP# Permanent Locking s Automated Block Erase, Full Chip Erase, Word/Byte Write and Lock-Bit Configuration Command User Interface (CUI) Status Register (SR) s SRAM-Compatible Write Interface s Chip-Size Packaging 48-Ball CSP s ETOXTM* Nonvolatile Flash Technology s CMOS Process (P-type silicon substrate) s Not designed or rated as radiation hardened SHARP's LH28F160BJB-TTL90 LH28F160BJB-TTL90 Flash memory is a high-density, low-cost, nonvolatile, read/write storage solution for a wide range of applications. LH28F160BJB-TTL90 LH28F160BJB-TTL90 can operate at VCC=2.7V-3.6V and VCCW=2.7V-3.6V or 11.7V-12.3V. Its low voltage operation capability realize battery life and suits for cellular phone application. Its Boot, Parameter and Main-blocked architecture, low voltage and extended cycling provide for highly flexible component suitable for portable terminals and personal computers. Its enhanced suspend capabilities provide for an ideal solution for code + data storage applications. For secure code storage applications, such as networking, where code is either directly executed out of flash or downloaded to DRAM, the LH28F160BJB-TTL90 LH28F160BJB-TTL90 offers four levels of protection: absolute protection with VCCWVCCWLK, selective hardware block locking or flexible software block locking. These alternatives give designers ultimate control of their code security needs. The LH28F160BJB-TTL90 LH28F160BJB-TTL90 is manufactured on SHARP's 0.25µm ETOXTM* process technology. It come in chip-size package: the 48-ball CSP, ideal for board constrained applications. *ETOX is a trademark of Intel Corporation. Rev. 1.26 LHF16J10 LHF16J10 1 INTRODUCTION This datasheet contains LH28F160BJB-TTL90 LH28F160BJB-TTL90 specifications. Section 1 provides a flash memory overview. Sections 2, 3, 4 and 5 describe the memory organization and functionality. Section 6 covers electrical specifications. 1.1 Features Key enhancements of LH28F160BJB-TTL90 LH28F160BJB-TTL90 boot block Flash memory are: ·Single low voltage operation ·Low power consumption ·Enhanced Suspend Capabilities ·Boot Block Architecture Please note following: ·VCCWLK has been lowered to 1.0V to support 2.7V3.6V block erase, full chip erase, word/byte write and lock-bit configuration operations. The VCCW voltage transitions to GND is recommended for designs that switch VCCW off during read operation. 1.2 Product Overview The LH28F160BJB-TTL90 LH28F160BJB-TTL90 is a high-performance 16M-bit Boot Block Flash memory organized as 1M-word of 16 bits or 2M-byte of 8 bits. The 1M-word/2M-byte of data is arranged in two 4K-word/8K-byte boot blocks, six 4Kword/8K-byte parameter blocks and thirty-one 32Kword/64K-byte main blocks which are individually erasable, lockable and unlockable in-system. The memory map is shown in Figure 3. The dedicated VCCW pin gives complete data protection when VCCWVCCWLK. A Command User Interface (CUI) serves as the interface between the system processor and internal operation of the device. A valid command sequence written to the CUI initiates device automation. An internal Write State Machine (WSM) automatically executes the algorithms and timings necessary for block erase, full chip erase, word/byte write and lock-bit configuration operations. 3 A block erase operation erases one of the device's 32Kword/64K-byte blocks typically within 1.2s (3V VCC, 3V VCCW), 4K-word/8K-byte blocks typically within 0.6s (3V VCC, 3V VCCW) independent of other blocks. Each block can be independently erased minimum 100,000 times. Block erase suspend mode allows system software to suspend block erase to read or write data from any other block. Writing memory data is performed in word/byte increments of the device's 32K-word blocks typically within 33µs (3V VCC, 3V VCCW), 64K-byte blocks typically within 31µs (3V VCC, 3V VCCW), 4K-word blocks typically within 36µs (3V VCC, 3V VCCW), 8Kbyte blocks typically within 32µs (3V VCC, 3V VCCW). Word/byte write suspend mode enables the system to read data or execute code from any other flash memory array location. Individual block locking uses a combination of bits, thirtynine block lock-bits, a permanent lock-bit and WP# pin, to lock and unlock blocks. Block lock-bits gate block erase, full chip erase and word/byte write operations, while the permanent lock-bit gates block lock-bit modification and locked block alternation. Lock-bit configuration operations (Set Block Lock-Bit, Set Permanent Lock-Bit and Clear Block Lock-Bits commands) set and cleared lock-bits. The status register indicates when the WSM's block erase, full chip erase, word/byte write or lock-bit configuration operation is finished. The RY/BY# output gives an additional indicator of WSM activity by providing both a hardware signal of status (versus software polling) and status masking (interrupt masking for background block erase, for example). Status polling using RY/BY# minimizes both CPU overhead and system power consumption. When low, RY/BY# indicates that the WSM is performing a block erase, full chip erase, word/byte write or lock-bit configuration. RY/BY#-high Z indicates that the WSM is ready for a new command, block erase is suspended (and word/byte write is inactive), word/byte write is suspended, or the device is in reset mode. Rev. 1.26 LHF16J10 LHF16J10 4 The access time is 90ns (tAVQV) over the operating temperature range (0°C to +70°C) and VCC supply voltage range of 2.7V-3.6V. 1.3 Product Description The Automatic Power Savings (APS) feature substantially reduces active current when the device is in static mode (addresses not switching). In APS mode, the typical ICCR current is 2µA (CMOS) at 3.0V VCC. LH28F160BJB-TTL90 LH28F160BJB-TTL90 Boot Block Flash memory is available in 48-ball CSP package (see Figure 2). When CE# and RP# pins are at VCC, the ICC CMOS standby mode is enabled. When the RP# pin is at GND, reset mode is enabled which minimizes power consumption and provides write protection. A reset time (tPHQV) is required from RP# switching high until outputs are valid. Likewise, the device has a wake time (tPHEL) from RP#-high until writes to the CUI are recognized. With RP# at GND, the WSM is reset and the status register is cleared. Please do not execute reprogramming "0" for the bit which has already been programed "0". Overwrite operation may generate unerasable bit. In case of reprogramming "0" to the data which has been programed "1". ·Program "0" for the bit in which you want to change data from "1" to "0". ·Program "1" for the bit which has already been programmed "0". For example, changing data from "10111101" to "10111100" requires "11111110" programming. 1.3.1 Package Pinout 1.3.2 Block Organization This product features an asymmetrically-blocked architecture providing system memory integration. Each erase block can be erased independently of the others up to 100,000 times. For the address locations of the blocks, see the memory map in Figure 3. Boot Blocks: The boot block is intended to replace a dedicated boot PROM in a microprocessor or microcontroller-based system. This boot block 4K words (4,096words) features hardware controllable writeprotection to protect the crucial microprocessor boot code from accidental modification. The protection of the boot block is controlled using a combination of the VCCW, RP#, WP# pins and block lock-bit. Parameter Blocks: The boot block architecture includes parameter blocks to facilitate storage of frequently update small parameters that would normally require an EEPROM. By using software techniques, the word-rewrite functionality of EEPROMs can be emulated. Each boot block component contains six parameter blocks of 4K words (4,096 words) each. The protection of the parameter block is controlled using a combination of the VCCW, RP# and block lock-bit. Main Blocks: The reminder is divided into main blocks for data or code storage. Each 16M-bit device contains thirtyone 32K words (32,768 words) blocks. The protection of the main block is controlled using a combination of the VCCW, RP# and block lock-bit. Rev. 1.26 LHF16J10 LHF16J10 5 DQ0-DQ15 DQ0-DQ15 Input Buffer Output Buffer I/O Logic Data Register Output Multiplexer Identifier Register Status Register VCC BYTE# CE# WE# Command User Interface OE# RP# WP# Data Comparator Y Decoder 32K-Word (64K-Byte) Main Blocks ×31 Address Counter Main Block 29 Write State Machine Main Block 30 Main Block 1 X Decoder Main Block 0 Address Latch Y-Gating Boot Block 0 Boot Block 1 Parameter Block 0 Parameter Block 1 Parameter Block 2 Parameter Block 3 Parameter Block 4 Parameter Block 5 Input Buffer A-1-A19 RY/BY# Program/Erase Voltage Switch VCCW VCC GND Figure 1. Block Diagram 1 2 3 4 5 6 7 8 A A2 A5 A17 WP# WE# A8 A11 A14 B A3 A6 A18 VCCW RP# NC A10 A13 C A1 A4 A7 A19 RY/BY# A9 A12 A15 D A0 OE# DQ1 DQ10 DQ12 DQ6 DQ15 /A-1 A16 E GND DQ8 DQ2 DQ11 VCC DQ5 DQ14 GND F CE# DQ0 DQ9 DQ3 DQ4 DQ13 DQ7 BYTE# 48-BALL 48-BALL CSP PINOUT 8mm x 8mm TOP VIEW Figure 2. CSP 48-Ball Pinout Rev. 1.26 LHF16J10 LHF16J10 Symbol Type A-1 A0-A19 A0-A19 INPUT DQ0-DQ15 DQ0-DQ15 INPUT/ OUTPUT CE# INPUT RP# INPUT OE# INPUT WE# INPUT WP# INPUT BYTE# INPUT RY/BY# OPEN DRAIN OUTPUT VCCW SUPPLY VCC SUPPLY GND NC SUPPLY 6 Table 1. Pin Descriptions Name and Function ADDRESS INPUTS: Inputs for addresses during read and write operations. Addresses are internally latched during a write cycle. A-1: Lower address input while BYTE# is VIL. A-1 pin changes DQ15 pin while BYTE# is VIH. A15-A19 A15-A19: Main Block Address. A12-A19 A12-A19: Boot and Parameter Block Address. DATA INPUT/OUTPUTS: Inputs data and commands during CUI write cycles; outputs data during memory array, status register and identifier code read cycles. Data pins float to highimpedance when the chip is deselected or outputs are disabled. Data is internally latched during a write cycle. DQ8-DQ15 DQ8-DQ15 pins are not used while byte mode (BYTE#=VIL). Then, DQ15 pin changes A-1 address input. CHIP ENABLE: Activates the device's control logic, input buffers, decoders and sense amplifiers. CE#-high deselects the device and reduces power consumption to standby levels. RESET: Resets the device internal automation. RP#-high enables normal operation. When driven low, RP# inhibits write operations which provides data protection during power transitions. Exit from reset mode sets the device to read array mode. RP# must be VIL during power-up. OUTPUT ENABLE: Gates the device's outputs during a read cycle. WRITE ENABLE: Controls writes to the CUI and array blocks. Addresses and data are latched on the rising edge of the WE# pulse. WRITE PROTECT: When WP# is VIL, boot blocks cannot be written or erased. When WP# is VIH, locked boot blocks can not be written or erased. WP# is not affected parameter and main blocks. BYTE ENABLE: BYTE# VIL places device in byte mode (×8). All data is then input or output on DQ0-7, and DQ8-15 DQ8-15 float. BYTE# VIH places the device in word mode (×16), and turns off the A-1 input buffer. READY/BUSY#: Indicates the status of the internal WSM. When low, the WSM is performing an internal operation (block erase, full chip erase, word/byte write or lock-bit configuration). RY/BY#-high Z indicates that the WSM is ready for new commands, block erase is suspended, and word/byte write is inactive, word/byte write is suspended, or the device is in reset mode. BLOCK ERASE, FULL CHIP ERASE, WORD/BYTE WRITE OR LOCK-BIT CONFIGURATION POWER SUPPLY: For erasing array blocks, writing words/bytes or configuring lock-bits. With VCCWVCCWLK, memory contents cannot be altered. Block erase, full chip erase, word/byte write and lock-bit configuration with an invalid VCCW (see 6.2.3 DC Characteristics) produce spurious results and should not be attempted. Applying 12V±0.3V to VCCW during erase/write can only be done for a maximum of 1000 cycles on each block. VCCW may be connected to 12V±0.3V for a total of 80 hours maximum. DEVICE POWER SUPPLY: Do not float any power pins. With VCCVLKO, all write attempts to the flash memory are inhibited. Device operations at invalid VCC voltage (see 6.2.3 DC Characteristics) produce spurious results and should not be attempted. GROUND: Do not float any ground pins. NO CONNECT: Lead is not internal connected; it may be driven or floated. Rev. 1.26 LHF16J10 LHF16J10 7 2 PRINCIPLES OF OPERATION [A19-A0 A19-A0] The LH28F160BJB-TTL90 LH28F160BJB-TTL90 flash memory includes an onchip WSM to manage block erase, full chip erase, word/byte write and lock-bit configuration functions. It allows for: 100% TTL-level control inputs, fixed power supplies during block erase, full chip erase, word/byte write and lock-bit configuration, and minimal processor overhead with RAM-like interface timings. After initial device power-up or return from reset mode (see section 3 Bus Operations), the device defaults to read array mode. Manipulation of external memory control pins allow array read, standby and output disable operations. Status register and identifier codes can be accessed through the CUI independent of the VCCW voltage. High voltage on VCCW enables successful block erase, full chip erase, word/byte write and lock-bit configurations. All functions associated with altering memory contents-block erase, full chip erase, word/byte write, lock-bit configuration, status and identifier codes-are accessed via the CUI and verified through the status register. Commands are written using standard microprocessor write timings. The CUI contents serve as input to the WSM, which controls the block erase, full chip erase, word/byte write and lock-bit configuration. The internal algorithms are regulated by the WSM, including pulse repetition, internal verification and margining of data. Addresses and data are internally latched during write cycles. Writing the appropriate command outputs array data, accesses the identifier codes or outputs status register data. Interface software that initiates and polls progress of block erase, full chip erase, word/byte write and lock-bit configuration can be stored in any block. This code is copied to and executed from system RAM during flash memory updates. After successful completion, reads are again possible via the Read Array command. Block erase suspend allows system software to suspend a block erase to read/write data from/to blocks other than that which is suspend. Word/byte write suspend allows system software to suspend a word/byte write to read data from any other flash memory array location. FFFFF FF000 FF000 FEFFF FE000 FE000 FDFFF FD000 FD000 FCFFF FC000 FC000 FBFFF FB000 FB000 FAFFF FA000 FA000 F9FFF F9000 F9000 F8FFF F8000 F8000 F7FFF F0000 F0000 EFFFF E8000 E8000 E7FFF E0000 E0000 DFFFF D8000 D8000 D7FFF D0000 D0000 CFFFF C8000 C8000 C7FFF C0000 C0000 BFFFF B8000 B8000 B7FFF B0000 B0000 AFFFF A8000 A8000 A7FFF A0000 A0000 9FFFF 98000 97FFF 97FFF 90000 8FFFF 88000 87FFF 87FFF 80000 7FFFF 78000 77FFF 77FFF 70000 6FFFF 68000 67FFF 67FFF 60000 5FFFF 58000 57FFF 57FFF 50000 4FFFF 48000 47FFF 47FFF 40000 3FFFF 38000 37FFF 37FFF 30000 2FFFF 28000 27FFF 27FFF 20000 1FFFF 18000 17FFF 17FFF 10000 0FFFF 08000 07FFF 07FFF 00000 Top Boot 4KW/8KB Boot Block [A19-A-1 A19-A-1] 0 4KW/8KB Boot Block 1 4KW/8KB Parameter Block 0 4KW/8KB Parameter Block 1 4KW/8KB Parameter Block 2 4KW/8KB Parameter Block 3 4KW/8KB Parameter Block 4 4KW/8KB Parameter Block 5 32KW/64KB 32KW/64KB Main Block 0 32KW/64KB 32KW/64KB Main Block 1 32KW/64KB 32KW/64KB Main Block 2 32KW/64KB 32KW/64KB Main Block 3 32KW/64KB 32KW/64KB Main Block 4 32KW/64KB 32KW/64KB Main Block 5 32KW/64KB 32KW/64KB Main Block 6 32KW/64KB 32KW/64KB Main Block 7 32KW/64KB 32KW/64KB Main Block 8 32KW/64KB 32KW/64KB Main Block 9 32KW/64KB 32KW/64KB Main Block 10 32KW/64KB 32KW/64KB Main Block 11 32KW/64KB 32KW/64KB Main Block 12 32KW/64KB 32KW/64KB Main Block 13 32KW/64KB 32KW/64KB Main Block 14 32KW/64KB 32KW/64KB Main Block 15 32KW/64KB 32KW/64KB Main Block 16 32KW/64KB 32KW/64KB Main Block 17 32KW/64KB 32KW/64KB Main Block 18 32KW/64KB 32KW/64KB Main Block 19 32KW/64KB 32KW/64KB Main Block 20 32KW/64KB 32KW/64KB Main Block 21 32KW/64KB 32KW/64KB Main Block 22 32KW/64KB 32KW/64KB Main Block 23 32KW/64KB 32KW/64KB Main Block 24 32KW/64KB 32KW/64KB Main Block 25 32KW/64KB 32KW/64KB Main Block 26 32KW/64KB 32KW/64KB Main Block 27 32KW/64KB 32KW/64KB Main Block 28 32KW/64KB 32KW/64KB Main Block 29 32KW/64KB 32KW/64KB Main Block 30 1FFFFF 1FE000 1FE000 1FDFFF 1FC000 1FC000 1FBFFF 1FA000 1FA000 1F9FFF 1F8000 1F8000 1F7FFF 1F6000 1F6000 1F5FFF 1F4000 1F4000 1F3FFF 1F2000 1F2000 1F1FFF 1F0000 1F0000 1EFFFF 1E0000 1E0000 1DFFFF 1D0000 1D0000 1CFFFF 1C0000 1C0000 1BFFFF 1B0000 1B0000 1AFFFF 1A0000 1A0000 19FFFF 19FFFF 190000 18FFFF 18FFFF 180000 17FFFF 17FFFF 170000 16FFFF 16FFFF 160000 15FFFF 15FFFF 150000 14FFFF 14FFFF 140000 13FFFF 13FFFF 130000 12FFFF 12FFFF 120000 11FFFF 11FFFF 110000 10FFFF 10FFFF 100000 0FFFFF 0F0000 0F0000 0EFFFF 0E0000 0E0000 0DFFFF 0D0000 0D0000 0CFFFF 0C0000 0C0000 0BFFFF 0B0000 0B0000 0AFFFF 0A0000 0A0000 09FFFF 09FFFF 090000 08FFFF 08FFFF 080000 07FFFF 07FFFF 070000 06FFFF 06FFFF 060000 05FFFF 05FFFF 050000 04FFFF 04FFFF 040000 03FFFF 03FFFF 030000 02FFFF 02FFFF 020000 01FFFF 01FFFF 010000 00FFFF 00FFFF 000000 Figure 3. Memory Map Rev. 1.26 LHF16J10 LHF16J10 8 2.1 Data Protection 3.3 Standby When VCCWVCCWLK, memory contents cannot be altered. The CUI, with two-step block erase, full chip erase, word/byte write or lock-bit configuration command sequences, provides protection from unwanted operations even when high voltage is applied to VCCW. All write functions are disabled when VCC is below the write lockout voltage VLKO or when RP# is at VIL. The device's block locking capability provides additional protection from inadvertent code or data alteration by gating block erase, full chip erase and word/byte write operations. Refer to Table 5 for write protection alternatives. CE# at a logic-high level (VIH) places the device in standby mode which substantially reduces device power consumption. DQ0-DQ15 DQ0-DQ15 outputs are placed in a highimpedance state independent of OE#. If deselected during block erase, full chip erase, word/byte write or lock-bit configuration, the device continues functioning, and consuming active power until the operation completes. 3 BUS OPERATION In read modes, RP#-low deselects the memory, places output drivers in a high-impedance state and turns off all internal circuits. RP# must be held low for a minimum of 100ns. Time tPHQV is required after return from reset mode until initial memory access outputs are valid. After this wake-up interval, normal operation is restored. The CUI is reset to read array mode and status register is set to 80H. The local CPU reads and writes flash memory in-system. All bus cycles to or from the flash memory conform to standard microprocessor bus cycles. 3.1 Read Information can be read from any block, identifier codes or status register independent of the VCCW voltage. RP# can be at VIH. The first task is to write the appropriate read mode command (Read Array, Read Identifier Codes or Read Status Register) to the CUI. Upon initial device power-up or after exit from reset mode, the device automatically resets to read array mode. Six control pins dictate the data flow in and out of the component: CE#, OE#, BYTE#, WE#, RP# and WP#. CE# and OE# must be driven active to obtain data at the outputs. CE# is the device selection control, and when active enables the selected memory device. OE# is the data output (DQ0-DQ15 DQ0-DQ15) control and when active drives the selected memory data onto the I/O bus. BYTE# is the device I/O interface mode control. WE# must be at VIH, RP# must be at VIH, and BYTE# and WP# must be at VIL or VIH. Figure 14, 15 illustrates read cycle. 3.2 Output Disable 3.4 Reset RP# at VIL initiates the reset mode. During block erase, full chip erase, word/byte write or lock-bit configuration modes, RP#-low will abort the operation. RY/BY# remains low until the reset operation is complete. Memory contents being altered are no longer valid; the data may be partially erased or written. Time tPHWL is required after RP# goes to logic-high (VIH) before another command can be written. As with any automated device, it is important to assert RP# during system reset. When the system comes out of reset, it expects to read from the flash memory. Automated flash memories provide status information when accessed during block erase, full chip erase, word/byte write or lock-bit configuration modes. If a CPU reset occurs with no flash memory reset, proper CPU initialization may not occur because the flash memory may be providing status information instead of array data. SHARP's flash memories allow proper CPU initialization following a system reset through the use of the RP# input. In this application, RP# is controlled by the same RESET# signal that resets the system CPU. With OE# at a logic-high level (VIH), the device outputs are disabled. Output pins (DQ0-DQ15 DQ0-DQ15) are placed in a high-impedance state. Rev. 1.26 LHF16J10 LHF16J10 9 3.5 Read Identifier Codes The read identifier codes operation outputs the manufacturer code, device code, block lock configuration codes for each block and the permanent lock configuration code (see Figure 4). Using the manufacturer and device codes, the system CPU can automatically match the device with its proper algorithms. The block lock and permanent lock configuration codes identify locked and unlocked blocks and permanent lock-bit setting. 3.6 Write Writing commands to the CUI enable reading of device data and identifier codes. They also control inspection and clearing of the status register. When VCC=2.7V-3.6V and VCCW=VCCWH1/2, the CUI additionally controls block erase, full chip erase, word/byte write and lock-bit configuration. [A19-A0 A19-A0]* FFFFF Reserved for Future Implementation FF003 FF003 FF002 FF002 FF001 FF001 FF000 FF000 The CUI does not occupy an addressable memory location. It is written when WE# and CE# are active. The address and data needed to execute a command are latched on the rising edge of WE# or CE# (whichever goes high first). Standard microprocessor write timings are used. Figures 16 and 17 illustrate WE# and CE# controlled write operations. Boot Block 0 Lock Configuration Code Reserved for Future Implementation Boot Block 0 FEFFF Reserved for Future Implementation FE003 FE003 FE002 FE002 FE001 FE001 FE000 FE000 Boot Block 1 Lock Configuration Code Reserved for Future Implementation Boot Block 1 FDFFF Reserved for Future Implementation FD003 FD003 FD002 FD002 The Block Erase command requires appropriate command data and an address within the block to be erased. The Full Chip Erase command requires appropriate command data and an address within the device. The Word/Byte Write command requires the command and address of the location to be written. Set Permanent and Block Lock-Bit commands require the command and address within the device (Permanent Lock) or block within the device (Block Lock) to be locked. The Clear Block Lock-Bits command requires the command and address within the device. Top Boot FD001 FD001 FD000 FD000 FCFFF F9000 F9000 Parameter Block 0 Lock Configuration Code Reserved for Future Implementation Parameter Block 0 (Parameter Blocks 1 through 4) F8FFF Reserved for Future Implementation F8003 F8003 F8002 F8002 F8001 F8001 F8000 F8000 Parameter Block 5 Lock Configuration Code Reserved for Future Implementation Parameter Block 5 F7FFF Reserved for Future Implementation F0003 F0003 F0002 F0002 F0001 F0001 F0000 F0000 EFFFF 08000 4 COMMAND DEFINITIONS Reserved for Future Implementation Main Block 0 (Main Blocks 1 through 29) 07FFF 07FFF When the VCCW voltage VCCWLK, read operations from the status register, identifier codes, or blocks are enabled. Placing VCCWH1/2 on VCCW enables successful block erase, full chip erase, word/byte write and lock-bit configuration operations. Main Block 0 Lock Configuration Code 00004 Reserved for Future Implementation Device operations are selected by writing specific commands into the CUI. Table 3 defines these commands. 00003 00002 00001 00000 *: Permanent Lock Configuration Code Main Block 30 Lock Configuration Code Device Code Manufacturer Code Main Block 30 Address A-1 don't care. Figure 4. Device Identifier Code Memory Map Rev. 1.26 LHF16J10 LHF16J10 Mode Read Output Disable Standby Reset Read Identifier Codes Notes 8 4 Table 2.1. RP# VIH VIH VIH VIL Mode Read Output Disable Standby Reset Read Identifier Codes VIH 6,7,8 Write 8 VIH Notes 8 4 8 Table 2.2. RP# VIH VIH VIH VIL VIH Bus Operations (BYTE#=VIH)(1,2) CE# OE# WE# Address VIL VIL VIH X VIL VIH VIH X VIH X X X X X X X See VIL VIL VIH Figure 4 VIL VIH VIL X Bus Operations (BYTE#=VIL)(1,2) CE# OE# WE# Address VIL VIL VIH X VIL VIH VIH X VIH X X X X X X X See VIL VIL VIH Figure 4 VIL VIH VIL X 10 VCCW X X X X DQ0-15 DQ0-15 DOUT High Z High Z High Z RY/BY#(3) X X X High Z X Note 5 High Z X DIN X VCCW X X X X DQ0-7 DOUT High Z High Z High Z RY/BY#(3) X X X High Z X Note 5 High Z Write 6,7,8 VIH X DIN X NOTES: 1. Refer to DC Characteristics. When VCCWVCCWLK, memory contents can be read, but not altered. 2. X can be VIL or VIH for control pins and addresses, and VCCWLK or VCCWH1/2 for VCCW. See DC Characteristics for VCCWLK voltages. 3. RY/BY# is VOL when the WSM is executing internal block erase, full chip erase, word/byte write or lock-bit configuration algorithms. It is High Z during when the WSM is not busy, in block erase suspend mode (with word/byte write inactive), word/byte write suspend mode or reset mode. 4. RP# at GND±0.2V ensures the lowest power consumption. 5. See Section 4.2 for read identifier code data. 6. Command writes involving block erase, full chip erase, word/byte write or lock-bit configuration are reliably executed when VCCW=VCCWH1/2 and VCC=2.7V-3.6V. 7. Refer to Table 3 for valid DIN during a write operation. 8. Never hold OE# low and WE# low at the same timing. Rev. 1.26 LHF16J10 LHF16J10 Command Read Array/Reset Read Identifier Codes Read Status Register Clear Status Register Block Erase Full Chip Erase Word/Byte Write Table 3. Command Definitions(10) Bus Cycles First Bus Cycle (1) Req'd. Notes Oper Addr(2) Data(3) 1 Write X FFH 4 Write X 90H 2 2 Write X 70H 1 Write X 50H 2 5 Write X 20H 2 Write X 30H 40H or 2 5,6 Write X 10H 11 Second Bus Cycle Addr(2) Data(3) Oper(1) Read Read IA X ID SRD Write Write BA X D0H D0H Write WA WD Block Erase and Word/Byte 1 5 Write X B0H Write Suspend Block Erase and Word/Byte 1 5 Write X D0H Write Resume Set Block Lock-Bit 2 8 Write X 60H Write BA 01H Clear Block Lock-Bits 2 7,8 Write X 60H Write X D0H Set Permanent Lock-Bit 2 9 Write X 60H Write X F1H NOTES: 1. BUS operations are defined in Table 2.1 and Table 2.2. 2. X=Any valid address within the device. IA=Identifier Code Address: see Figure 4. BA=Address within the block being erased. WA=Address of memory location to be written. 3. SRD=Data read from status register. See Table 6 for a description of the status register bits. WD=Data to be written at location WA. Data is latched on the rising edge of WE# or CE# (whichever goes high first). ID=Data read from identifier codes. 4. Following the Read Identifier Codes command, read operations access manufacturer, device, block lock configuration and permanent lock configuration codes. See Section 4.2 for read identifier code data. 5. If WP# is VIL, boot blocks are locked without block lock-bits state. If WP# is VIH, boot blocks are locked by block lockbits. The parameter and main blocks are locked by block lock-bits without WP# state. 6. Either 40H or 10H are recognized by the WSM as the word/byte write setup. 7. The clear block lock-bits operation simultaneously clears all block lock-bits. 8. If the permanent lock-bit is set, Set Block Lock-Bit and Clear Block Lock-Bits commands can not be done. 9. Once the permanent lock-bit is set, permanent lock-bit reset is unable. 10. Commands other than those shown above are reserved by SHARP for future device implementations and should not be used. Rev. 1.26 LHF16J10 LHF16J10 12 4.1 Read Array Command 4.3 Read Status Register Command Upon initial device power-up and after exit from reset mode, the device defaults to read array mode. This operation is also initiated by writing the Read Array command. The device remains enabled for reads until another command is written. Once the internal WSM has started a block erase, full chip erase, word/byte write or lock-bit configuration the device will not recognize the Read Array command until the WSM completes its operation unless the WSM is suspended via an Erase Suspend or Word/Byte Write Suspend command. The Read Array command functions independently of the VCCW voltage and RP# can be VIH. The status register may be read to determine when a block erase, full chip erase, word/byte write or lock-bit configuration is complete and whether the operation completed successfully. It may be read at any time by writing the Read Status Register command. After writing this command, all subsequent read operations output data from the status register until another valid command is written. The status register contents are latched on the falling edge of OE# or CE#, whichever occurs. OE# or CE# must toggle to VIH before further reads to update the status register latch. The Read Status Register command functions independently of the VCCW voltage. RP# can be VIH. 4.2 Read Identifier Codes Command 4.4 Clear Status Register Command The identifier code operation is initiated by writing the Read Identifier Codes command. Following the command write, read cycles from addresses shown in Figure 4 retrieve the manufacturer, device, block lock configuration and permanent lock configuration codes (see Table 4 for identifier code values). To terminate the operation, write another valid command. Like the Read Array command, the Read Identifier Codes command functions independently of the VCCW voltage and RP# can be VIH. Following the Read Identifier Codes command, the following information can be read: Table 4. Identifier Codes Address(2) Data(3) Code [A19-A0 A19-A0] [DQ7-DQ0] Manufacture Code 00000H 00000H B0H Device Code 00001H 00001H E8H (1)+2 Block Lock Configuration BA DQ0=0 ·Block is Unlocked ·Block is Locked To clear the status register, the Clear Status Register command (50H) is written. It functions independently of the applied VCCW Voltage. RP# can be VIH. This command is not functional during block erase or word/byte write suspend modes. DQ0=1 ·Reserved for Future Use Permanent Lock Configuration Status register bits SR.5, SR.4, SR.3 or SR.1 are set to "1"s by the WSM and can only be reset by the Clear Status Register command. These bits indicate various failure conditions (see Table 6). By allowing system software to reset these bits, several operations (such as cumulatively erasing multiple blocks or writing several words/bytes in sequence) may be performed. The status register may be polled to determine if an error occurred during the sequence. DQ1-7 00003H 00003H ·Device is Unlocked DQ0=0 ·Device is Locked DQ0=1 DQ1-7 ·Reserved for Future Use NOTE: 1. BA selects the specific block lock configuration code to be read. See Figure 4 for the device identifier code memory map. 2. A-1 don't care in byte mode. 3. DQ15-DQ8 DQ15-DQ8 outputs 00H in word mode. Rev. 1.26 LHF16J10 LHF16J10 4.5 Block Erase Command 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 FFFFH/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 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 register bits SR.4 and SR.5 being set to "1". Also, reliable block erasure can only occur when VCC=2.7V-3.6V and VCCW=VCCWH1/2. In the absence of this high voltage, block contents are protected against erasure. If block erase is attempted while VCCWVCCWLK, SR.3 and SR.5 will be set to "1". Successful block erase requires for boot blocks that WP# is VIH and the corresponding block lock-bit be cleared. In parameter and main blocks case, it must be cleared the corresponding block lock-bit. If block erase is attempted when the excepting above conditions, SR.1 and SR.5 will be set to "1". 4.6 Full Chip Erase Command This command followed by a confirm command erases all of the unlocked blocks. A full chip erase setup (30H) is first written, followed by a full chip erase confirm (D0H). After a confirm command is written, device erases the all unlocked blocks 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 RY/BY# 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 13 status register mode until a new command is issued. If error is detected on a block during full chip erase operation, WSM stops erasing. Full chip erase operation start from lower address block, finish the higher address block. Full chip erase can not be suspended. 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=2.7V-3.6V and VCCW=VCCWH1/2. In the absence of this high voltage, block contents are protected against erasure. If full chip erase is attempted while VCCWVCCWLK, SR.3 and SR.5 will be set to "1". Successful full chip erase requires for boot blocks that WP# is VIH and the corresponding block lock-bit be cleared. In parameter and main blocks case, it must be cleared the corresponding block lock-bit. If all blocks are locked, SR.1 and SR.5 will be set to "1". 4.7 Word/Byte Write Command Word/Byte write is executed by a two-cycle command sequence. Word/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 word/byte write and write verify algorithms internally. After the word/byte write sequence is written, the device automatically outputs status register data when read (see Figure 7). The CPU can detect the completion of the word/byte write event by analyzing the RY/BY# pin or status register bit SR.7. When word/byte write is complete, status register bit SR.4 should be checked. If word/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 word/byte writes can only occur when VCC=2.7V-3.6V and VCCW=VCCWH1/2. In the absence of this high voltage, memory contents are protected against word/byte writes. If word/byte write is attempted while VCCWVCCWLK, status register bits SR.3 and SR.4 will be set to "1". Successful word/byte write requires for boot blocks that WP# is VIH and the corresponding block lockbit be cleared. In parameter and main blocks case, it must be cleared the corresponding block lock-bit. If word/byte write is attempted when the excepting above conditions, SR.1 and SR.4 will be set to "1". Rev. 1.26 LHF16J10 LHF16J10 14 4.8 Block Erase Suspend Command 4.9 Word/Byte Write Suspend Command The Block Erase Suspend command allows block-erase interruption to read or word/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 High Z. Specification tWHRZ2 defines the block erase suspend latency. The Word/Byte Write Suspend command allows word/byte write interruption to read data in other flash memory locations. Once the word/byte write process starts, writing the Word/Byte Write Suspend command requests that the WSM suspend the Word/Byte write sequence at a predetermined point in the algorithm. The device continues to output status register data when read after the Word/Byte Write Suspend command is written. Polling status register bits SR.7 and SR.2 can determine when the word/byte write operation has been suspended (both will be set to "1"). RY/BY# will also transition to High Z. Specification tWHRZ1 defines the word/byte write suspend latency. When Block Erase Suspend command write to the CUI, if block erase was finished, the device places read array mode. Therefore, after Block Erase Suspend command write to the CUI, Read Status Register command (70H) has to write to CUI, then status register bit SR.6 should be checked for places the device in suspend mode. At this point, a Read Array command can be written to read data from blocks other than that which is suspended. A Word/Byte Write command sequence can also be issued during erase suspend to program data in other blocks. Using the Word/Byte Write Suspend command (see Section 4.9), a word/byte write operation can also be suspended. During a word/byte write operation with block erase suspended, status register bit SR.7 will return to "0" and the RY/BY# output will transition to VOL. However, SR.6 will remain "1" to indicate block erase suspend status. The only other valid commands while block erase is suspended are Read Status Register and Block Erase Resume. After a Block Erase Resume command is written to the flash memory, the WSM will continue the block erase process. Status register bits SR.6 and SR.7 will automatically clear and RY/BY# will return to VOL. After the Erase Resume command is written, the device automatically outputs status register data when read (see Figure 8). VCCW must remain at VCCWH1/2 (the same VCCW level used for block erase) while block erase is suspended. RP# must also remain at VIH. WP# must also remain at VIL or VIH (the same WP# level used for block erase). Block erase cannot resume until word/byte write operations initiated during block erase suspend have completed. When Word/Byte Write Suspend command write to the CUI, if word/byte write was finished, the device places read array mode. Therefore, after Word/Byte Write Suspend command write to the CUI, Read Status Register command (70H) has to write to CUI, then status register bit SR.2 should be checked for places the device in suspend mode. At this point, a Read Array command can be written to read data from locations other than that which is suspended. The only other valid commands while word/byte write is suspended are Read Status Register and Word/Byte Write Resume. After Word/Byte Write Resume command is written to the flash memory, the WSM will continue the word/byte write process. Status register bits SR.2 and SR.7 will automatically clear and RY/BY# will return to VOL. After the Word/Byte Write Resume command is written, the device automatically outputs status register data when read (see Figure 9). VCCW must remain at VCCWH1/2 (the same VCCW level used for word/byte write) while in word/byte write suspend mode. RP# must also remain at VIH. WP# must also remain at VIL or VIH (the same WP# level used for word/byte write). If the period of from Word/Byte Write Resume command write to the CUI till Word/Byte Write Suspend command write to the CUI be short and done again and again, write time be prolonged. If the period of from Block Erase Resume command write to the CUI till Block Erase Suspend command write to the CUI be short and done again and again, erase time be prolonged. Rev. 1.26 LHF16J10 LHF16J10 4.10 Set Block and Permanent Lock-Bit Commands A flexible block locking and unlocking scheme is enabled via a combination of block lock-bits, a permanent lock-bit and WP# pin. The block lock-bits and WP# pin gates program and erase operations while the permanent lock-bit gates block-lock bit modification. With the permanent lock-bit not set, individual block lock-bits can be set using the Set Block Lock-Bit command. The Set Permanent Lock-Bit command, sets the permanent lock-bit. After the permanent lock-bit is set, block lock-bits and locked block contents cannot altered. See Table 5 for a summary of hardware and software write protection options. Set block lock-bit and permanent lock-bit are executed by a two-cycle command sequence. The 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 Figure 10). 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=2.7V-3.6V and VCCW=VCCWH1/2. 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. 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. 15 4.11 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, block lock-bits can be cleared using only the Clear Block Lock-Bits command. If the permanent lock-bit is set, block lock-bits cannot cleared. See Table 5 for a summary of hardware and software write protection options. Clear block lock-bits operation 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 Figure 11). 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-bit 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=2.7V-3.6V and VCCW=VCCWH1/2. If a clear block lock-bits operation is attempted while VCCWVCCWLK, SR.3 and SR.5 will be set to "1". In the absence of this high voltage, the block lock-bits content are protected against alteration. A successful clear block lock-bits operation requires that the permanent lock-bit is not set. If it is attempted with the permanent lock-bit set, SR.1 and SR.5 will be set to "1" and the operation will fail. If a clear block lock-bits operation is aborted due to VCCW or VCC transitioning out of valid range or RP# active transition, block lock-bit values are left in an undetermined state. A repeat of clear block lock-bits is required to initialize block lock-bit contents to known values. Once the permanent lock-bit is set, it cannot be cleared. Rev. 1.26 LHF16J10 LHF16J10 4.12 Block Locking by the WP# This Boot Block Flash memory architecture features two hardware-lockable boot blocks so that the kernel code for the system can be kept secure while other blocks are programmed or erased as necessary. 16 result in an error, which will be reflected in the status register. For top configuration, the top two boot blocks are lockable. For the bottom configuration, the bottom two boot blocks are lockable. If WP# is VIH and block lockbit is not set, boot block can be programmed or erased normally (Unless VCCW is below VCCWLK). WP# is valid only two boot blocks, other blocks are not affected. The lockable two boot blocks are locked when WP#=VIL; any program or erase operation to a locked block will Operation VCCW RP# Block Erase VCCWLK or >VCCWLK Word/Byte Write X VIL VIH Full Chip Erase VCCWLK >VCCWLK X VIL VIH Set Block Lock-Bit VCCWLK >VCCWLK X VIL VIH Clear Block VCCWLK Lock-Bits >VCCWLK X VIL VIH VCCWLK >VCCWLK X VIL VIH Set Permanent Lock-Bit Table 5. Write Protection Alternatives Permanent Block WP# Effect Lock-Bit Lock-bit X X X All Blocks Locked. X X X All Blocks Locked. X 0 VIL 2 Boot Blocks Locked. VIH Block Erase and Word/Byte Write Enabled. 1 VIL Block Erase and Word/Byte Write Disabled. VIH Block Erase and Word/Byte Write Disabled. X X X All Blocks Locked. X X X All Blocks Locked. X X VIL All Unlocked Blocks are Erased. 2 Boot Blocks and Locked Blocks are NOT Erased. VIH All Unlocked Blocks are Erased, Locked Blocks are NOT Erased. X X X Set Block Lock-Bit Disabled. X X X Set Block Lock-Bit Disabled. 0 X X Set Block Lock-Bit Enabled. 1 X X Set Block Lock-Bit Disabled. X X X Clear Block Lock-Bits Disabled. X X X Clear Block Lock-Bits Disabled. 0 X X Clear Block Lock-Bits Enabled. 1 X X Clear Block Lock-Bits Disabled. X X X Set Permanent Lock-Bit Disabled. X X X Set Permanent Lock-Bit Disabled. X X X Set Permanent Lock-Bit Enabled. Rev. 1.26 LHF16J10 LHF16J10 WSMS BESS ECBLBS 7 6 17 Table 6. Status Register Definition WBWSLBS VCCWS WBWSS 5 4 3 R 1 2 DPS 0 NOTES: SR.7 = WRITE STATE MACHINE STATUS (WSMS) 1 = Ready 0 = Busy Check RY/BY# or SR.7 to determine block erase, full chip erase, word/byte write or lock-bit configuration completion. SR.6-0 are invalid while SR.7="0". SR.6 = BLOCK ERASE SUSPEND STATUS (BESS) 1 = Block Erase Suspended 0 = Block Erase in Progress/Completed SR.5 = ERASE AND CLEAR BLOCK LOCK-BITS STATUS (ECBLBS) 1 = Error in Block Erase, Full Chip Erase or Clear Block Lock-Bits 0 = Successful Block Erase, Full Chip Erase or Clear Block Lock-Bits SR.4 = WORD/BYTE WRITE AND SET LOCK-BIT STATUS (WBWSLBS) 1 = Error in Word/Byte Write or Set Block/Permanent Lock-Bit 0 = Successful Word/Byte Write or Set Block/Permanent Lock-Bit SR.3 = VCCW STATUS (VCCWS) 1 = VCCW Low Detect, Operation Abort 0 = VCCW OK SR.2 = WORD/BYTE WRITE SUSPEND STATUS (WBWSS) 1 = Word/Byte Write Suspended 0 = Word/Byte Write in Progress/Completed SR.1 = DEVICE PROTECT STATUS (DPS) 1 = Block Lock-Bit, Permanent Lock-Bit and/or WP# Lock Detected, Operation Abort 0 = Unlock SR.0 = RESERVED FOR FUTURE ENHANCEMENTS (R) If both SR.5 and SR.4 are "1"s after a block erase, full chip erase or lock-bit configuration attempt, an improper command sequence was entered. SR.3 does not provide a continuous indication of VCCW level. The WSM interrogates and indicates the VCCW level only after Block Erase, Full Chip Erase, Word/Byte Write or Lock-Bit Configuration command sequences. SR.3 is not guaranteed to reports accurate feedback only when VCCWVCCWH1/2. SR.1 does not provide a continuous indication of permanent and block lock-bit and WP# values. The WSM interrogates the permanent lock-bit, block lock-bit and WP# only after Block Erase, Full Chip Erase, Word/Byte Write or Lock-Bit Configuration command sequences. It informs the system, depending on the attempted operation, if the block lock-bit is set, permanent lock-bit is set and/or WP# is VIL. Reading the block lock and permanent lock configuration codes after writing the Read Identifier Codes command indicates permanent and block lock-bit status. SR.0 is reserved for future use and should be masked out when polling the status register. Rev. 1.26 LHF16J10 LHF16J10 18 Start Bus Operation Command Write 70H Write Read Status Register Read Status Register Read Comments Data=70H Addr=X Status Register Data Check SR.7 Standby SR.7= 1=WSM Ready 0 0=WSM Busy Write Write 20H Write D0H, Block Address Erase Setup Write 1 Erase Confirm Addr=X Data=D0H Addr=Within Block to be Erased Status Register Data Read Read Status Register Check SR.7 Suspend Block Erase Loop No SR.7= Data=20H 0 Suspend Block Erase 1=WSM Ready Standby 0=WSM Busy Repeat for subsequent block erasures. Yes Full status check can be done after each block erase or after a sequence of block erasures. 1 Write FFH after the last operation to place device in read array mode. Full Status Check if Desired Block Erase Complete FULL STATUS CHECK PROCEDURE Read Status Register Data(See Above) SR.3= Bus Operation 1 Standby SR.1= Standby 1 Device Protect Error 0 Check SR.3 1=VCCW Error Detect VCCW Range Error 0 Comments Command Standby Standby Check SR.1 1=Device Protect Detect Check SR.4,5 Both 1=Command Sequence Error Check SR.5 1=Block Erase Error SR.4,5= 1 Command Sequence Error where multiple blocks are erased before full status is checked. If error is detected, clear the Status Register before attempting retry or other error recovery. 0 SR.5= SR.5, SR.4, SR.3 and SR.1 are only cleared by the Clear Status Register Command in cases 1 Block Erase Error 0 Block Erase Successful Figure 5. Automated Block Erase Flowchart Rev. 1.26 LHF16J10 LHF16J10 Start 19 Bus Operation Write Write 70H Read Status Register Command Read Status Register Comments Data=70H Addr=X Status Register Data Read Check SR.7 SR.7= Standby 0 1=WSM Ready 0=WSM Busy Write Full Chip Erase Setup Data=30H Write 1 Full Chip Erase Confirm Data=D0H Write 30H Write D0H Addr=X Addr=X Status Register Data Read Check SR.7 Read Status Register Standby 1=WSM Ready 0=WSM Busy SR.7= Full status check can be done after each full chip erase. 0 Write FFH after the last operation to place device in read array mode. 1 Full Status Check if Desired Full Chip Erase Complete FULL STATUS CHECK PROCEDURE Read Status Register Data(See Above) SR.3= Bus Operation 1 Comments Command Standby VCCW Range Error Check SR.3 1=VCCW Error Detect Check SR.1 0 Standby 1=Device Protect Detect (All Blocks are locked) SR.1= 1 Device Protect Error Standby Check SR.4,5 Both 1=Command Sequence Error 0 Standby SR.4,5= 1 Command Sequence Error Check SR.5 1=Full Chip Erase Error SR.5, SR.4, SR.3 and SR.1 are only cleared by the Clear Status Register Command in cases where multiple blocks are erased before full status is checked. 0 If error is detected, clear the Status Register before attempting retry or other error recovery. SR.5= 1 Full Chip Erase Error 0 Full Chip Erase Successful Figure 6. Automated Full Chip Erase Flowchart Rev. 1.26 LHF16J10 LHF16J10 20 Start Bus Operation Command Write 70H Write Read Status Register Read Status Register Read Comments Data=70H Addr=X Status Register Data Check SR.7 Standby SR.7= 1=WSM Ready 0 0=WSM Busy Write Write 40H or 10H Write Word/Byte Data and Address Setup Word/Byte Write Write 1 Word/Byte Write Read Addr=X Data=Data to Be Written Addr=Location to Be Written Status Register Data Read Status Register Check SR.7 No SR.7= Data=40H or 10H 0 Suspend Word/Byte Write Suspend Word/Byte Write Loop 1=WSM Ready Standby 0=WSM Busy Repeat for subsequent word/byte writes. Yes SR full status check can be done after each word/byte write, or after a sequence of word/byte writes. 1 Write FFH after the last word/byte write operation to place device in read array mode. Full Status Check if Desired Word/Byte Write Complete FULL STATUS CHECK PROCEDURE Read Status Register Data(See Above) SR.3= Bus Operation 1 Standby VCCW Range Error Standby 0 SR.1= 1 Device Protect Error Comments Command Standby Check SR.3 1=VCCW Error Detect Check SR.1 1=Device Protect Detect Check SR.4 1=Data Write Error SR.4, SR.3 and SR.1 are only cleared by the Clear Status Register command in cases 0 where multiple locations are written before full status is checked. If error is detected, clear the Status Register before attempting retry or other error recovery. SR.4= 1 Word/Byte Write Error 0 Word/Byte Write Successful Figure 7. Automated Word/Byte Write Flowchart Rev. 1.26 LHF16J10 LHF16J10 Start 21 Bus Operation Write Write B0H Command Erase Suspend Comments Data=B0H Addr=X Status Register Data Read Addr=X Read Status Register Check SR.7 1=WSM Ready Standby 0=WSM Busy 0 SR.7= Check SR.6 Standby 1=Block Erase Suspended 0=Block Erase Completed 1 Write 0 SR.6= Erase Resume Data=D0H Addr=X Block Erase Completed 1 Read or Word/Byte Write ? Read Read Array Data Word/Byte Write Word/Byte Write Loop No Done? Yes Write D0H Write FFH Block Erase Resumed Read Array Data Figure 8. Block Erase Suspend/Resume Flowchart Rev. 1.26 LHF16J10 LHF16J10 Start 22 Bus Operation Write Write B0H Command Word/Byte Write Suspend Comments Data=B0H Addr=X Status Register Data Read Addr=X Read Status Register Check SR.7 Standby 1=WSM Ready 0=WSM Busy SR.7= 0 Check SR.2 Standby 1=Word/Byte Write Suspended 0=Word/Byte Write Completed 1 Write SR.2= 0 Read Array Data=FFH Addr=X Word/Byte Write Completed Read Array locations other Read than that being written. 1 Write Write FFH Word/Byte Write Resume Data=D0H Addr=X Read Array Data Done Reading No Yes Write D0H Write FFH Word/Byte Write Resumed Read Array Data Figure 9. Word/Byte Write Suspend/Resume Flowchart Rev. 1.26 LHF16J10 LHF16J10 23 Start Bus Operation Command Write 70H Write Read Status Register Read Status Register Read Comments Data=70H Addr=X Status Register Data Check SR.7 Standby SR.7= 1=WSM Ready 0 0=WSM Busy Write Set Block/Permanent Lock-Bit Setup Write 1 Set Block or Permanent Lock-Bit Confirm Data=60H Addr=X Write 60H Data=01H(Block), Write 01H/F1H 01H/F1H, Block/Device Address F1H(Permanent) Addr=Block Address(Block), Device Address(Permanent) Read Status Register Status Register Data Read Check SR.7 SR.7= Standby 0 1=WSM Ready 0=WSM Busy 1 Repeat for subsequent lock-bit set operations. Full status check can be done after each lock-bit set operation or after a sequence of Full Status Check if Desired lock-bit set operations. Write FFH after the last lock-bit set operation to place device in read array mode. Set Lock-Bit Complete FULL STATUS CHECK PROCEDURE Read Status Register Data(See Above) SR.3= Bus Operation 1 Standby VCCW Range Error Command Comments Check SR.3 1=VCCW Error Detect Check SR.1 0 Standby SR.1= 1 (Set Block Lock-Bit Operation) Standby 1 Permanent Lock-Bit is Set Device Protect Error 0 SR.4,5= 1=Device Protect Detect Command Sequence Error 0 Standby Check SR.4,5 Both 1=Command Sequence Error Check SR.4 1=Set Lock-Bit Error SR.5, SR.4, SR.3 and SR.1 are only cleared by the Clear Status Register command in cases where multiple lock-bits are set before full status is checked. SR.4= 1 If error is detected, clear the Status Register before attempting retry or other error recovery. Set Lock-Bit Error 0 Set Lock-Bit Successful Figure 10. Set Block and Permanent Lock-Bit Flowchart Rev. 1.26 LHF16J10 LHF16J10 24 Start Bus Operation Command Write 70H Write Read Status Register Read Status Register Read Comments Data=70H Addr=X Status Register Data Check SR.7 Standby SR.7= 1=WSM Ready 0 0=WSM Busy Write Write 60H Write D0H Clear Block Lock-Bits Setup Data=60H Write 1 Clear Block Lock-Bits Confirm Data=D0H Addr=X Status Register Data Read Read Status Register Addr=X Check SR.7 Standby 1=WSM Ready 0=WSM Busy SR.7= 0 Write FFH after the Clear Block Lock-Bits operation to place device in read array mode. 1 Full Status Check if Desired Clear Block Lock-Bits Complete FULL STATUS CHECK PROCEDURE Read Status Register Data(See Above) Bus Operation 1 SR.3= Comments Command Standby VCCW Range Error Check SR.3 1=VCCW Error Detect Check SR.1 0 Standby 1=Device Protect Detect Permanent Lock-Bit is Set SR.1= 1 Device Protect Error Standby Check SR.4,5 Both 1=Command Sequence Error 0 SR.4,5= 1 Standby Command Sequence Error 1=Clear Block Lock-Bits Error SR.5, SR.4, SR.3 and SR.1 are only cleared by the Clear Status Register command. 0 SR.5= Check SR.5 If error is detected, clear the Status Register before attempting retry or other error recovery. 1 Clear Block Lock-Bits Error 0 Clear Block Lock-Bits Successful Figure 11. Clear Block Lock-Bits Flowchart Rev. 1.26 LHF16J10 LHF16J10 25 5 DESIGN CONSIDERATIONS 5.3 Power Supply Decoupling 5.1 Three-Line Output Control Flash memory power switching characteristics require careful device decoupling. System designers are interested in three supply current issues; standby current levels, active current levels and transient peaks produced by falling and rising edges of CE# and OE#. Transient current magnitudes depend on the device outputs' capacitive and inductive loading. Two-line control and proper decoupling capacitor selection will suppress transient voltage peaks. Each device should have a 0.1µF ceramic capacitor connected between its VCC and GND and between its VCCW and GND. These high-frequency, low inductance capacitors should be placed as close as possible to package leads. Additionally, for every eight devices, a 4.7µF electrolytic capacitor should be placed at the array's power supply connection between VCC and GND. The bulk capacitor will overcome voltage slumps caused by PC board trace inductance. The device will often be used in large memory arrays. SHARP provides three control inputs to accommodate multiple memory connections. Three-line control provides for: a. Lowest possible memory power dissipation. b. Complete assurance that data bus contention will not occur. To use these control inputs efficiently, an address decoder should enable CE# while OE# should be connected to all memory devices and the system's READ# control line. This assures that only selected memory devices have active outputs while deselected memory devices are in standby mode. RP# should be connected to the system POWERGOOD signal to prevent unintended writes during system power transitions. POWERGOOD should also toggle during system reset. 5.2 RY/BY# and WSM Polling RY/BY# is an open drain output that should be connected to VCC by a pull up resistor to provides a hardware method of detecting block erase, full chip erase, word/byte write and lock-bit configuration completion. It transitions low after block erase, full chip erase, word/byte write or lockbit configuration commands and returns to VOH (while RY/BY# is pull up) when the WSM has finished executing the internal algorithm. RY/BY# can be connected to an interrupt input of the system CPU or controller. It is active at all times. RY/BY# is also High Z when the device is in block erase suspend (with word/byte write inactive), word/byte write suspend or reset modes. 5.4 VCCW Trace on Printed Circuit Boards Updating flash memories that reside in the target system requires that the printed circuit board designer pay attention to the VCCW Power supply trace. The VCCW pin supplies the memory cell current for word/byte writing and block erasing. Use similar trace widths and layout considerations given to the VCC power bus. Adequate VCCW supply traces and decoupling will decrease VCCW voltage spikes and overshoots. 5.5 VCC, VCCW, RP# Transitions Block erase, full chip erase, word/byte write and lock-bit configuration are not guaranteed if VCCW falls outside of a valid VCCWH1/2 range, VCC falls outside of a valid 2.7V3.6V range, or RP#VIH. If VCCW error is detected, status register bit SR.3 is set to "1" along with SR.4 or SR.5, depending on the attempted operation. If RP# transitions to VIL during block erase, full chip erase, word/byte write or lock-bit configuration, RY/BY# will remain low until the reset operation is complete. Then, the operation will abort and the device will enter reset mode. The aborted operation may leave data partially altered. Therefore, the command sequence must be repeated after normal operation is restored. Device power-off or RP# transitions to VIL clear the status register. The CUI latches commands issued by system software and is not altered by VCCW or CE# transitions or WSM actions. Its state is read array mode upon power-up, after exit from reset mode or after VCC transitions below VLKO. Rev. 1.26 LHF16J10 LHF16J10 26 5.6 Power-Up/Down Protection 5.8 Data Protection Method The device is designed to offer protection against accidental block erase, full chip erase, word/byte write or lock-bit configuration during power transitions. Upon power-up, the device is indifferent as to which power supply (VCCW or VCC) powers-up first. Internal circuitry resets the CUI to read array mode at power-up. Noises having a level exceeding the limit specified in the specification may be generated under specific operating conditions on some systems. Such noises, when induced onto WE# signal or power supply, may be interpreted as false commands, causing undesired memory updating. To protect the data stored in the flash memory against unwanted overwriting, systems operating with the flash memory should have the following write protect designs, as appropriate: A system designer must guard against spurious writes for VCC voltages above VLKO when VCCW is active. Since both WE# and CE# must be low for a command write, driving either to VIH will inhibit writes. The CUI's twostep command sequence architecture provides added level of protection against data alteration. In-system block lock and unlock capability prevents inadvertent data alteration. The device is disabled while RP#=VIL regardless of its control inputs state. 5.7 Power Dissipation When designing portable systems, designers must consider battery power consumption not only during device operation, but also for data retention during system idle time. Flash memory's nonvolatility increases usable battery life because data is retained when system power is removed. 1) Protecting data in specific block When a lock bit is set, the corresponding block (includes the 2 boot blocks) is protected against overwriting. By setting a WP# to low, only the 2 boot blocks can be protected against overwriting. By using this feature, the flash memory space can be divided into the program section (locked section) and data section (unlocked section). The permanent lock bit can be used to prevent false block bit setting. For further information on setting/resetting lock-bit, refer to the specification. (See chapter 4.10 and 4.11.) 2) Data protection through VCCW When the level of VCCW is lower than VCCWLK (lockout voltage), write operation on the flash memory is disabled. All blocks are locked and the data in the blocks are completely write protected. For the lockout voltage, refer to the specification. (See chapter 6.2.3.) 3) Data protection through RP# When the RP# is kept low during read mode, the flash memory will be reset mode, then write protecting all blocks. When the RP# is kept low during power up and power down sequence such as voltage transition, write operation on the flash memory is disabled, write protecting all blocks. For the details of RP# control, refer to the specification. (See chapter 5.6 and 6.2.7.) Rev. 1.26 LHF16J10 LHF16J10 6 ELECTRICAL SPECIFICATIONS 6.1 Absolute Maximum Ratings* Operating Temperature During Read, Block Erase, Full Chip Erase, Word/Byte Write and Lock-Bit Configuration .0°C to +70°C(1) Storage Temperature During under Bias . -10°C to +80°C During non Bias . -65°C to +125°C Voltage On Any Pin (except VCC and VCCW) . -0.5V to VCC+0.5V(2) VCC Supply Voltage. -0.2V to +4.6V(2) VCCW Supply Voltage. -0.2V to +13.0V(2,3) Output Short Circuit Current.100mA(4) 27 *WARNING: Stressing the device beyond the "Absolute Maximum Ratings" may cause permanent damage. These are stress ratings only. Operation beyond the "Operating Conditions" is not recommended and extended exposure beyond the "Operating Conditions" may affect device reliability. NOTES: 1. Operating temperature is for commercial temperature product defined by this specification. 2. All specified voltages are with respect to GND. Minimum DC voltage is -0.5V on input/output pins and -0.2V on VCC and VCCW pins. During transitions, this level may undershoot to -2.0V for periods