US20010000816A1 - Volatile lock architecture for individual block locking on flash memory - Google Patents

Volatile lock architecture for individual block locking on flash memory Download PDF

Info

Publication number
US20010000816A1
US20010000816A1 US09/748,826 US74882600A US2001000816A1 US 20010000816 A1 US20010000816 A1 US 20010000816A1 US 74882600 A US74882600 A US 74882600A US 2001000816 A1 US2001000816 A1 US 2001000816A1
Authority
US
United States
Prior art keywords
block
lock
set
blocks
command
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US09/748,826
Other versions
US6446179B2 (en
Inventor
Robert Baltar
Original Assignee
Baltar Robert L.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US09/076,330 priority Critical patent/US6209069B1/en
Application filed by Baltar Robert L. filed Critical Baltar Robert L.
Priority to US09/748,826 priority patent/US6446179B2/en
Publication of US20010000816A1 publication Critical patent/US20010000816A1/en
Application granted granted Critical
Publication of US6446179B2 publication Critical patent/US6446179B2/en
Anticipated expiration legal-status Critical
Application status is Expired - Lifetime legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/14Protection against unauthorised use of memory or access to memory
    • G06F12/1416Protection against unauthorised use of memory or access to memory by checking the object accessibility, e.g. type of access defined by the memory independently of subject rights
    • G06F12/1425Protection against unauthorised use of memory or access to memory by checking the object accessibility, e.g. type of access defined by the memory independently of subject rights the protection being physical, e.g. cell, word, block
    • G06F12/1433Protection against unauthorised use of memory or access to memory by checking the object accessibility, e.g. type of access defined by the memory independently of subject rights the protection being physical, e.g. cell, word, block for a module or a part of a module
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C16/00Erasable programmable read-only memories
    • G11C16/02Erasable programmable read-only memories electrically programmable
    • G11C16/06Auxiliary circuits, e.g. for writing into memory
    • G11C16/22Safety or protection circuits preventing unauthorised or accidental access to memory cells
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C8/00Arrangements for selecting an address in a digital store
    • G11C8/12Group selection circuits, e.g. for memory block selections, chip selection, array selection

Abstract

A circuit for protecting memory blocks in a block-based flash EPROM device is disclosed. A non-volatile memory array includes a number of blocks that are capable of being placed in a locked state or an unlocked state. A volatile lock register is coupled to each of the lockable blocks in the memory array. A logic gate is coupled to one input of the volatile lock register, and a block set/reset line is coupled to a second input of the volatile lock register. A block latch control line is coupled to one input of the logic gate, and a group latch control line is coupled to a second input of the logic gate.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • The present application is related to the following U.S. Patent Applications entitled, “Flexible Block Protection Scheme for Flash Memory”, having application Ser. No. ______, filed on ______; and “A Method and Apparatus for Hardware Block Locking in a Non-Volatile Memory”, having application Ser. No. _____, filed on ______, both applications of which are assigned to the assignee of the present invention. [0001]
  • FIELD OF THE INVENTION
  • The present invention relates generally to integrated circuit memory devices, and more specifically to lock protecting one or more memory blocks in a non-volatile memory array. [0002]
  • BACKGROUND OF THE INVENTION
  • Flash EPROM (erasable programmable read-only memory) devices have developed into a popular source of non-volatile, electrically erasable memory in a wide range of digital applications. Flash memory devices typically use a one-transistor memory cell which allows for high memory densities, high reliability, and low power consumption. These characteristics have made flash memory very popular for low power applications, such as battery-backed or embedded memory circuits. Common uses of non-volatile memory include portable computers, personal digital assistant (PDA) devices, digital cameras, and cellular telephones. In these devices, both program code and system data, such as configuration parameters and other firmware, are often stored in flash memory because of the compact storage and relative ease of software upgradeability. The use of flash memory to store upgradeable data has necessitated the development of mechanisms to protect the data from unintended erasure or reprogramming. [0003]
  • With original flash memory devices, erasing stored code or data required erasing the entire device. Newer devices, however, are based on a block-erase architecture in which the flash memory is divided into blocks that are loosely analogous to the disk sectors recognized by disk operating systems. This block based architecture allows file systems to erase blocks of flash memory instead of the whole device. The block architecture also allows users to flexibly erase different portions of code or data in a flash device. For example, critical system code, such as boot code, can be stored in a lockable “boot block” of the device, while other blocks are allocated to other portions of code or data. [0004]
  • To ensure the integrity of block-based flash memory, block protection schemes are needed to protect stored data when the memory is modified through program or erase operations. Memory blocks must be protected against unintended writes when data is written to the device or when a new code segment is updated. Likewise, data blocks must be protected when other data blocks are modified or when code updates occur. [0005]
  • One present method of block protection for flash memory includes protecting a pre-determined number of blocks through a lock/unlock hardware pin. This requires the user to determine which blocks of memory are hardware protectable and reserve those blocks for critical data or program code. This approach is highly inflexible in that the user can only protect code or data in these predetermined hardware protectable blocks. [0006]
  • A second present method of block protection for flash memory includes the use of a block locking configuration table that is stored in the flash memory device itself. Typically the configuration is stored in a flash mini-array that is separate from the main flash memory array. Each bit in the configuration table represents a block that can be either locked or unlocked. This approach, however, has several disadvantages. One disadvantage is the excessive latency incurred in locking or unlocking individual blocks of memory. For example, in a typical flash device, on the order of ten microseconds are required to program a lock bit and one second is required to erase a lock bit. In systems in which code is being executed on the order of thousands of megahertz, these long cycle times required to protect memory blocks can create periods of vulnerability in which data corruption may occur. [0007]
  • Another disadvantage to this method is that, because the table is implemented in a dedicated flash mini-array, in which individual bits represent the different lockable blocks, reprogramming a particular block typically requires erasing the entire set of bits in the table, instead of only the bit for that block. Thus, reconfiguring even a single block incurs the erase cycle times for each of the bits in the table and the associated vulnerability to data corruption of these bits during the relatively long erase times. [0008]
  • An additional disadvantage of the flash based configuration table is that it occupies valuable die space in the flash device and each bit in the table requires associated flash sense, and program and erase circuitry. [0009]
  • Therefore, present methods of block protecting flash memory present several significant disadvantages, including inflexibility of lock configuration, higher costs due to addition of a flash mini-array, and possible data corruption due to vulnerability resulting from long program and erase cycle times. [0010]
  • SUMMARY OF THE INVENTION
  • A circuit is disclosed for protecting memory blocks in a block-based flash EPROM device. A non-volatile memory array includes a number of blocks that are capable of being placed in a locked state or an unlocked state. A volatile lock register is coupled to each of the lockable blocks in the memory array. A logic gate is coupled to one input of the volatile lock register, and a block set/reset line is coupled to a second input of the volatile lock register. A block latch control line is coupled to one input of the logic gate, and a group latch control line is coupled to a second input of the logic gate. [0011]
  • Other features and advantages of the present invention will be apparent from the accompanying drawings and from the detailed description that follows. [0012]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which: [0013]
  • FIG. 1 is a block diagram of a computer system that includes an embodiment of the present invention; [0014]
  • FIG. 2 is block diagram of a block controller coupled to a flash memory array, according to one embodiment of the present invention; [0015]
  • FIG. 3 is a circuit diagram of a block lock controller within the block controller of FIG. 2, according to one embodiment of the present invention; [0016]
  • FIG. 4A is a timing diagram illustrating the sequence of execution of a single block lock/unlock command, according to one embodiment of the present invention; [0017]
  • FIG. 4B is a timing diagram illustrating the sequence of execution of a multi-block lock/unlock command, according to one embodiment of the present invention; [0018]
  • FIG. 5 is a flowchart illustrating the locking or unlocking of single or multiple blocks in a flash array, according to one embodiment of the present invention. [0019]
  • DETAILED DESCRIPTION
  • A block protection control circuit for a flash memory array is described. In one embodiment of the present invention, a set of volatile memory lock registers sets each lockable block of the flash memory to a locked or unlocked state, and a two-cycle command specifies whether a single block or a group of multiple blocks is to be locked or unlocked. [0020]
  • It is an intended advantage of embodiments of the invention to provide a block protection controller for flash memory that allows a user to dynamically select which blocks of a flash array to lock or unlock. It is a further intended advantage of embodiments of the invention to provide a block control circuit that locks or unlocks blocks of flash memory at high speeds and minimizes the possibility of data corruption during block lock and unlock cycles. [0021]
  • FIG. 1 illustrates a block diagram of a computer system that incorporates embodiments of the present invention. The computer system [0022] 100 includes a processor 102 coupled through a bus 101 to a memory 104 and a mass storage device 106. In certain embodiments of the present invention, memory 104 is random access memory (“RAM”), read-only memory (“ROM”), or other non-volatile memory, such as flash memory; and mass storage device 106 is a large-capacity persistent storage device, such as a hard disk drive, CD-ROM drive, or tape drive. A keyboard controller 110 is coupled to bus 101 for receiving commands or data entered through a keyboard, mouse, or similar input device. A display device controller 112 is also coupled to bus 101 for providing output through an appropriately coupled display device 114. Also coupled to bus 101 is an input/output controller 108 for interfacing processor 102 to other devices, such as network interface devices and the like.
  • In one embodiment of the present invention, memory [0023] 104 is a block-erase architecture type of flash EPROM memory. Memory 104 includes a block controller unit 116 that configures the blocks within memory 104 in either a locked or unlocked state. The composition and operation of embodiments of block controller unit 116 will be provided in greater detail in the discussion that follows.
  • It should be noted that the architecture of FIG. 1 is provided only for purposes of illustration, and that a computer system that implements embodiments of the present invention is not limited to this specific architecture. For example, flash memory is often prominently used in digital devices other than computer systems. Such devices, as exemplified by cellular telephones, pagers, digital cameras, and personal digital assistants, typically include a microprocessor or other processing unit, and a flash memory device that is used to store program code and system data. [0024]
  • FIG. 2 is a block diagram that illustrates the interface between the block controller unit [0025] 116 and a flash memory array according to one embodiment of the present invention. Memory 104 includes a flash memory array 202 that is divided into a number of memory blocks. As illustrated in FIG. 2, flash memory array 202 includes 32 blocks numbered blocks 0 to 31. It is to be noted, however, that a flash memory device with any number of blocks may be used in conjunction with embodiments of the present invention. In a typical application, a specific block of the memory array may be a “boot block” that stores boot code for a computer or similar processing system, and one or more blocks, e.g., block 31, are reserved as spare blocks. Each of the remaining blocks is then available to store either additional program code or data. As illustrated in FIG. 2, the first block (block 0) is the boot block, however, the location of the boot block may vary among different computer systems, and depends on the memory address mapping scheme implemented in the actual computer system.
  • One or more the blocks in flash memory array [0026] 202 is capable of being locked. A locked block is protected against program or erase operations. Flash memory array 202 is coupled to block controller unit 116 that controls the lock and unlock configuration of each of the lockable blocks in memory 104. Block controller unit 116 includes a command buffer 204 that receives read/write commands from the processor. Command buffer 204 is coupled to block control circuit 206. In one embodiment of the present invention, block control circuit 206 contains a number of digital registers, with each register controlling the lock status of a corresponding lockable block. In response to a particular lock or unlock command received from command buffer 204, block control circuit 206 generates the appropriate control signal to flash memory array 202 to configure the blocks accordingly. Block control circuit 206 also serves as a status register that is polled when the processor attempts to erase or write to a locked block. Block control circuit 206 can thus be configured to issue a status or error message in response to an invalid erase or write command.
  • Volatile Latch Block Lock Architecture [0027]
  • FIG. 3 is a circuit diagram that illustrates in greater detail the internal structure of block control circuit [0028] 206, according to one embodiment of the present invention. The block control circuit 206 consists of a bank of latches with one latch for each of the lockable blocks in flash memory array 202. Each of the latches can be individually set or reset by a user using a standard command format. As illustrated in FIG. 3, the block control circuit 206 includes n D-type registers, 302 to 306, where n corresponds to the number of lockable blocks in the memory array coupled to circuit 206. For the example illustrated in FIG. 2, if each of the blocks in memory array 202 is capable of being locked, then for block control circuit 206, n=32. Although registers 302 to 306 in FIG. 3 are illustrated as D-type registers, block control circuit 206 may be implemented using of other types of digital latch or register circuits.
  • The Q output of each register [0029] 302 to 306 generates a block lock control signal that is input, through logic circuits that control write operations to memory, to a corresponding block in memory array 202. Thus, the output from register 302 is denoted “block 1 lock control” signal, the output from register 304 is denoted “block 2 lock control” signal, and so on. The D input to each of the registers 302 to 306 are connected to block set/reset lines 320 to 324 that are driven by commands generated from command buffer 204. The logic state of a block set/reset signal connected to a register determines the state of the lock control signal transmitted to the corresponding block in the memory array. In one embodiment of the present invention, a logic high (“1”) block set/reset level will cause the corresponding block to be locked. Conversely, a logic low (“0”) block set/reset level will cause the corresponding block to be unlocked.
  • In one embodiment of the present invention, the clock inputs to each of the registers [0030] 302 to 306 are driven by a latch control signal. The latch control signal is generated by a group latch control signal 310 that enables latching of all of the registers in a group, or by individual block latch control signals that enable only corresponding block control registers. In this manner, block set/reset commands must be synchronized with either a group latch control signal or individual block latch control signals 312 to 316 in order to lock or unlock the blocks in flash memory array 202. A system reset signal 308 is connected to the reset inputs of each of the registers 302 to 306 to allow a common reset of each of the block control registers upon the occurrence of a reset condition, such as a software reset or power-down condition.
  • In one embodiment of the present invention, the registers [0031] 302 to 306 comprising the block control circuit 206 in FIG. 3 are implemented in a volatile memory device, such as a static random access memory (SRAM) device. Typical SRAM devices feature much faster read/write cycle times than flash memory. Using volatile memory registers, thus allows much faster lock programming of flash memory blocks over present methods that use non-volatile memory tables to configure the lock configuration. For example, if such a configuration table is implemented in flash memory, a set or reset of the lock configuration may take up to one or two seconds (based on the erase cycles of typical flash cells). This update time represents a period of vulnerability in which the data may be corrupted by a spurious write operation. If the processor coupled to the memory is executing code on the order of millions of cycles per second, the possibility of a spurious write during the period of vulnerability is quite high. The use of volatile registers in embodiments of the present invention, thus minimizes this period of vulnerability by allowing reconfiguration of these volatile registers at cycle times approximating SRAM memory cycles or flash read times.
  • Lock Commands [0032]
  • In one embodiment of the present invention, two-cycle write commands are issued from command buffer [0033] 204 to lock or unlock blocks in flash memory array 202. The first cycle of the two-cycle command selects the configuration command. The configuration command determines whether a particular block or group of blocks in the flash memory array is to be locked or unlocked. The second cycle of the two-cycle command specifies whether the configuration command of the first cycle applies to a single block or to a group of blocks in the flash memory array.
  • In the block control circuit of FIG. 3, each block of the flash array can be locked or unlocked using software commands that change the protection status of the block. The protection status can be set to one of the following two states, locked or unlocked. This protection status is specified in the configuration command transmitted in a first cycle of a two-cycle command. [0034]
  • Locked blocks are fully protected from alteration. Any program or erase operations attempted on a locked block will return an error to a status register. In one embodiment of the present invention, the status of a locked block can be changed to unlocked or lock-down using appropriate software commands. Unlocked blocks can be programmed or erased. The status of an unlocked block can be changed to a locked block using appropriate software commands. [0035]
  • FIG. 4A is a timing diagram illustrating the sequence of execution of a single block lock/unlock command according to one embodiment of the present invention. The data line [0036] 404 transmits the two-cycle command that specifies the block configuration and the type of command, i.e., single block. The two cycles of the command on the data line are valid during positive cycles of the write enable signal 402. For a single block command, the address 406 input to memory 104 is decoded to determine which lock bit in block control circuit 206 to set or reset. The configuration command takes effect on the block specified by the address upon a positive-going cycle of the block latch control signal 408. The lock bit in block control circuit 206 that is set or reset corresponds to the D-register that controls the particular block. In one embodiment of the present invention, the single block latch control line (e.g., 312, 314, or 316) to the register is enabled and the state of the block set/reset line (e.g., 320, 322, or 324) to the register is latched.
  • Thus, in FIG. 4A, a block is configured by first determining the lock configuration of the block, establishing that the command is a single block command, determining the specific block to be configured by decoding the address, and unlocking or locking the block through the block latch control signal. [0037]
  • FIG. 4B is a timing diagram illustrating the sequence of execution of a multi-block lock/unlock command according to one embodiment of the present invention. The data line [0038] 454 transmits the two-cycle command that specifies the block configuration and the type of command, i.e., multi-block. The two cycles of the command on the data line are valid during positive cycles of the write enable signal 452. In the multi-block lock command, each bit of the address encoded in the address signal 456 corresponds to an individual block in the memory array. Each block is locked or unlocked depending on whether the corresponding bit is set or reset. The lock bits in block control circuit 206 that are set or reset correspond to the D-registers that controls those particular blocks. In one embodiment of the present invention, the group latch control line (e.g., 310) to the registers to be set are enabled and the state of the block set/reset line (e.g., 320, 322, or 324) to the appropriate registers are latched.
  • Thus, in FIG. 4B, a group of blocks is configured by first determining the lock configuration of the blocks, establishing that the command is a multi-block command, determining the specific blocks to be configured by decoding the address, and unlocking or locking the blocks through the group latch control signal. [0039]
  • For the multi-block method illustrated in FIG. 4B, in one embodiment of the present invention, if there are more blocks in the array than address pads, block control circuit [0040] 206 is configured such that each bit is configured to control multiple blocks. In an alternative embodiment of the present invention, if there are more blocks in the array than address pads, multiple configuration commands could be defined to allow individual block control. The configuration command takes effect on the block specified by the address upon a positive-going cycle of the group latch control signal 458.
  • In FIGS. 4A and 4B, the write commands to lock or unlock blocks in flash memory array [0041] 202, were illustrated as two-cycle commands. In an alternative embodiment of the present invention, single cycle commands are used. Single-cycle commands specify both the identity of the block to be configured, and its locked or unlocked configuration. Similarly, in further alternative embodiments of the present invention, multi-cycle commands (consisting of three or more cycles) are used to configure the flash blocks to locked or unlocked states.
  • FIG. 5 is a flowchart illustrating the locking or unlocking of single or multiple blocks in a flash array, according to one embodiment of the present invention. The process starts in step [0042] 500. In step 502, the configuration command is read by the block control circuit. In one embodiment of the present invention, the configuration command is encoded in the first command cycle of a two-cycle command. The configuration command specifies whether the block or blocks being addressed are to be locked or unlocked. In step 504, the block lock/unlock command is read by the block control circuit. In one embodiment of the present invention, the block lock/unlock command is encoded in the second command cycle of a two-cycle command. The block lock/unlock command specifies whether the lock or unlock configuration command specified in step 502 is a single-block command or a multi-block command.
  • If, in step [0043] 508, it is determined the configuration command is a single-block command, the address on the address pad is decoded to determine which lock bit in the block control circuit to set or reset, step 508. The appropriate memory address is then locked or unlocked depending on the configuration command, step 510. At this point the process ends at step 516.
  • If, in step [0044] 508, it is determined the configuration command is a multiple-block command, each bit of the address on the address pad corresponds to an individual block. These address bits are decoded to determine lock bits in the block control circuit to set or reset, step 512. The appropriate memory addresses are then locked or unlocked depending on the configuration command, step 514. At this point the process ends at step 516.
  • Embodiments of the present invention, as exemplified by FIGS. 3 and 5, are used in applications requiring secure storage of sensitive or vulnerable data or code. The use of volatile lock and, as well as lock-down registers allows real-time data protection by minimizing the lock and unlock cycle times, and hence the period of vulnerability of the non-volatile memory to data corruption during these cycle times. The use of two-cycle commands that specify that a single block or a group of blocks is to be configured allows for fast and flexible lock configuration of different memory blocks in a flash memory array. [0045]
  • In the foregoing, a circuit has been described for flexibly locking individual or multiple blocks in a flash memory array. Although the present invention has been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention as set forth in the claims. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. [0046]

Claims (18)

What is claimed is:
1. An apparatus comprising:
a non-volatile memory array including a plurality of blocks, one or more blocks of said plurality of blocks being capable of being placed in a locked state or an unlocked state;
a volatile lock register coupled to a block of said one or more blocks;
a logic gate coupled to a first input to said volatile lock register;
a block set/reset line coupled to a second input to said volatile lock register;
a block latch control line coupled to a first input to said logic gate; and
a group latch control line coupled to a second input to said logic gate.
2. The apparatus of
claim 1
wherein said non-volatile memory array is a flash memory and said lock register is embodied in a static random access memory circuit.
3. The apparatus of
claim 3
wherein said logic gate is an or-type combinatorial logic gate.
4. The apparatus of
claim 3
wherein said volatile lock register is set to a first state or a second state depending on the logic state of a signal transmitted on said block set/reset line, and wherein said volatile lock register transmits a lock control signal to said block of said one or more blocks.
5. The apparatus of
claim 4
wherein said volatile register being set to said first state causes said block of said one or more blocks to be locked to a protected state from write or erase operations, and said volatile register being set to said second state causes said block of said one or more blocks to be unlocked to allow modification by write or erase operations.
6. The apparatus of
claim 5
wherein said first input to said volatile lock register is a clock input.
7. An apparatus comprising:
a non-volatile memory array including a plurality of blocks, one or more blocks of said plurality of blocks being capable of being placed in a locked state or an unlocked state;
a set of volatile lock registers, each lock register of said set of lock registers coupled to a corresponding block of said one or more blocks, and operable to prevent corresponding blocks from being modified;
a block set/reset line coupled to a first input to each lock register of said volatile lock registers; and
a block latch control line and a group latch control line coupled through combinatorial logic to a second input to each lock register of said volatile lock registers.
8. The apparatus of
claim 7
further comprising a command buffer coupled to said set of lock registers and said set of lock-down registers, said command buffer operable to transmit a two-cycle command to each register of said set of lock registers, wherein the first cycle comprises a command specifying whether a lock configuration of said non-volatile memory array is to be changed, and the second cycle comprises a command specifying whether said first cycle command applies to a single block of said memory array or to multiple blocks of said memory array.
9. The apparatus of
claim 8
wherein if said first cycle command is a first command type, a block of said non-volatile memory is to be locked, and if said first cycle command is a second command type, a block of said non-volatile memory is to be unlocked.
10. The apparatus of
claim 9
wherein if said second cycle command applies to a single block, an address input on an address bus coupled to said apparatus is decoded to set or reset one register of said set of lock registers.
11. The apparatus of
claim 9
wherein if said second cycle command applies to multiple blocks, an address input on an address bus coupled to said apparatus is decoded to set or reset two or more lock registers of said set of lock registers, each bit of said address corresponding to a lock register of said two or more lock registers.
12. The apparatus of
claim 11
wherein said non-volatile memory array is a flash memory and said set of lock registers is embodied in static random access memory circuits.
13. A method comprising the steps of:
reading a first command of a multi-cycle command, said first command specifying a lock configuration of one or more memory blocks of a non-volatile memory array; and
reading a second command of said multi-cycle command, said second command specifying the number of memory blocks of said one or more memory blocks to be lock configured.
14. The method of
claim 13
wherein said first command specifies if said one or more memory blocks are to be set to a locked state or an unlocked state.
15. The method of
claim 14
wherein said multi-cycle command is a two-cycle command.
16. The method of
claim 15
wherein said first command programs a set of lock registers coupled to said memory array, each register of said set of registers capable of being set to a first state and a second state, and coupled to a corresponding block of said memory array.
17. The method of
claim 16
wherein if a register is set to said first state, a corresponding block of said memory array is set to a locked state, and if said register is set to a second state, said corresponding block is set to an unlocked state.
18. The method of
claim 17
wherein an address transmitted on an address bus is decoded to determine which lock register of said set of lock registers is set according to said first command.
US09/748,826 1998-05-11 2000-12-26 Computing system with volatile lock architecture for individual block locking on flash memory Expired - Lifetime US6446179B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US09/076,330 US6209069B1 (en) 1998-05-11 1998-05-11 Method and apparatus using volatile lock architecture for individual block locking on flash memory
US09/748,826 US6446179B2 (en) 1998-05-11 2000-12-26 Computing system with volatile lock architecture for individual block locking on flash memory

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US09/748,826 US6446179B2 (en) 1998-05-11 2000-12-26 Computing system with volatile lock architecture for individual block locking on flash memory

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/076,330 Continuation US6209069B1 (en) 1998-05-11 1998-05-11 Method and apparatus using volatile lock architecture for individual block locking on flash memory

Publications (2)

Publication Number Publication Date
US20010000816A1 true US20010000816A1 (en) 2001-05-03
US6446179B2 US6446179B2 (en) 2002-09-03

Family

ID=22131325

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/076,330 Expired - Lifetime US6209069B1 (en) 1998-05-11 1998-05-11 Method and apparatus using volatile lock architecture for individual block locking on flash memory
US09/748,826 Expired - Lifetime US6446179B2 (en) 1998-05-11 2000-12-26 Computing system with volatile lock architecture for individual block locking on flash memory

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/076,330 Expired - Lifetime US6209069B1 (en) 1998-05-11 1998-05-11 Method and apparatus using volatile lock architecture for individual block locking on flash memory

Country Status (1)

Country Link
US (2) US6209069B1 (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030142561A1 (en) * 2001-12-14 2003-07-31 I/O Integrity, Inc. Apparatus and caching method for optimizing server startup performance
US20040083346A1 (en) * 2002-10-24 2004-04-29 Micron Technology, Inc. Permanent memory block protection in a flash memory device
US6842371B2 (en) 2003-06-03 2005-01-11 Micron Technology, Inc. Permanent master block lock in a memory device
US20050063242A1 (en) * 2001-07-16 2005-03-24 Yuqing Ren Embedded software update methods and systems for digital devices
US20050273560A1 (en) * 2004-06-03 2005-12-08 Hulbert Jared E Method and apparatus to avoid incoherency between a cache memory and flash memory
US20060288182A1 (en) * 2005-06-03 2006-12-21 Lightuning Tech. Inc. Portable storage device capable of automatically running biometrics application programs and methods of automatically running the application programs
US20150347053A1 (en) * 2014-05-28 2015-12-03 Sandisk Technologies Inc. Systems and Methods for Immediate Physical Erasure of Data Stored In a Memory System In Response to a User Command

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6209069B1 (en) * 1998-05-11 2001-03-27 Intel Corporation Method and apparatus using volatile lock architecture for individual block locking on flash memory
US7549056B2 (en) 1999-03-19 2009-06-16 Broadcom Corporation System and method for processing and protecting content
JP3351398B2 (en) * 1999-08-09 2002-11-25 株式会社村田製作所 Data communication equipment
US7958376B2 (en) * 2000-11-02 2011-06-07 Ati Technologies Ulc Write once system and method for facilitating digital encrypted transmissions
US6937680B2 (en) * 2001-04-24 2005-08-30 Sun Microsystems, Inc. Source synchronous receiver link initialization and input floating control by clock detection and DLL lock detection
US6772307B1 (en) 2001-06-11 2004-08-03 Intel Corporation Firmware memory having multiple protected blocks
US7318146B2 (en) * 2001-06-19 2008-01-08 Micron Technology, Inc. Peripheral device with hardware linked list
JP2003036681A (en) * 2001-07-23 2003-02-07 Hitachi Ltd Non-volatile memory device
US6948026B2 (en) * 2001-08-24 2005-09-20 Micron Technology, Inc. Erase block management
US6614695B2 (en) * 2001-08-24 2003-09-02 Micron Technology, Inc. Non-volatile memory with block erase
US6624688B2 (en) 2002-01-07 2003-09-23 Intel Corporation Filtering variable offset amplifer
US6650184B2 (en) 2002-03-15 2003-11-18 Intel Corporation High gain amplifier circuits and their applications
US7810152B2 (en) * 2002-05-08 2010-10-05 Broadcom Corporation System and method for securely controlling access to device functions
US6789159B1 (en) * 2002-05-08 2004-09-07 Broadcom Corporation System and method for programming non-volatile memory
KR100543442B1 (en) * 2002-09-06 2006-01-23 삼성전자주식회사 Nonviolation memory system of establishing write-protection blocks
KR100492774B1 (en) * 2002-12-24 2005-06-07 주식회사 하이닉스반도체 Nonvolatile Memory Device Comprising Write Protected Region
KR100532442B1 (en) * 2003-06-17 2005-11-30 삼성전자주식회사 Data processing method and data processing apparatus
KR100614639B1 (en) * 2003-07-24 2006-08-22 삼성전자주식회사 Memory system with lockable buffer memory and information processing system including the same
EP1538507A1 (en) * 2003-12-02 2005-06-08 Axalto S.A. Flash memory access method and system
US8082382B2 (en) * 2004-06-04 2011-12-20 Micron Technology, Inc. Memory device with user configurable density/performance
US8032727B2 (en) * 2004-07-23 2011-10-04 Broadcom Corporation Method and system for locking OTP memory bits after programming
DE602005013344D1 (en) 2005-01-19 2009-04-30 St Microelectronics Srl Advanced secure storage access method and Archtitektur
US20080189557A1 (en) * 2005-01-19 2008-08-07 Stmicroelectronics S.R.I. Method and architecture for restricting access to a memory device
US8375189B2 (en) * 2005-12-30 2013-02-12 Intel Corporation Configuring levels of program/erase protection in flash devices
US20080077590A1 (en) * 2006-09-22 2008-03-27 Honeywell International Inc. Efficient journaling and recovery mechanism for embedded flash file systems
US8041912B2 (en) * 2007-09-28 2011-10-18 Macronix International Co., Ltd. Memory devices with data protection
JP2010191849A (en) * 2009-02-20 2010-09-02 Renesas Electronics Corp Circuit and method for holding state
US8572334B2 (en) * 2010-04-23 2013-10-29 Psion, Inc. System and method for locking portions of a memory card
US8782330B2 (en) * 2011-05-09 2014-07-15 Bae Systems Information And Electronic Systems Integration Inc. Flash boot and recovery area protection to meet GMR requirements
CN103377086A (en) * 2012-04-27 2013-10-30 华为技术有限公司 Method, device and system used for asynchronous multinuclear system to operate sharing resource
US9658787B2 (en) 2014-02-26 2017-05-23 Macronix International Co., Ltd. Nonvolatile memory data protection using nonvolatile protection codes and volatile mask codes

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE69033438D1 (en) 1989-04-13 2000-03-02 Sandisk Corp Replacement of faulty memory cells of a EEprommatritze
US5065364A (en) 1989-09-15 1991-11-12 Intel Corporation Apparatus for providing block erasing in a flash EPROM
US5126808A (en) 1989-10-23 1992-06-30 Advanced Micro Devices, Inc. Flash EEPROM array with paged erase architecture
US5210845A (en) 1990-11-28 1993-05-11 Intel Corporation Controller for two-way set associative cache
US5197034A (en) 1991-05-10 1993-03-23 Intel Corporation Floating gate non-volatile memory with deep power down and write lock-out
US5293424A (en) * 1992-10-14 1994-03-08 Bull Hn Information Systems Inc. Secure memory card
US5353256A (en) 1993-06-30 1994-10-04 Intel Corporation Block specific status information in a memory device
US5509134A (en) 1993-06-30 1996-04-16 Intel Corporation Method and apparatus for execution of operations in a flash memory array
US5592641A (en) 1993-06-30 1997-01-07 Intel Corporation Method and device for selectively locking write access to blocks in a memory array using write protect inputs and block enabled status
US5513136A (en) * 1993-09-27 1996-04-30 Intel Corporation Nonvolatile memory with blocks and circuitry for selectively protecting the blocks for memory operations
US5442704A (en) 1994-01-14 1995-08-15 Bull Nh Information Systems Inc. Secure memory card with programmed controlled security access control
US5438546A (en) 1994-06-02 1995-08-01 Intel Corporation Programmable redundancy scheme suitable for single-bit state and multibit state nonvolatile memories
JP3487690B2 (en) * 1995-06-20 2004-01-19 シャープ株式会社 Nonvolatile semiconductor memory device
US5886582A (en) * 1996-08-07 1999-03-23 Cypress Semiconductor Corp. Enabling clock signals with a phase locked loop (PLL) lock detect circuit
US5954818A (en) * 1997-02-03 1999-09-21 Intel Corporation Method of programming, erasing, and reading block lock-bits and a master lock-bit in a flash memory device
US5822251A (en) * 1997-08-25 1998-10-13 Bit Microsystems, Inc. Expandable flash-memory mass-storage using shared buddy lines and intermediate flash-bus between device-specific buffers and flash-intelligent DMA controllers
JP3884839B2 (en) * 1997-10-17 2007-02-21 株式会社ルネサステクノロジ A semiconductor memory device
US5974500A (en) 1997-11-14 1999-10-26 Atmel Corporation Memory device having programmable access protection and method of operating the same
US6154819A (en) * 1998-05-11 2000-11-28 Intel Corporation Apparatus and method using volatile lock and lock-down registers and for protecting memory blocks
US6026016A (en) * 1998-05-11 2000-02-15 Intel Corporation Methods and apparatus for hardware block locking in a nonvolatile memory
US6209069B1 (en) * 1998-05-11 2001-03-27 Intel Corporation Method and apparatus using volatile lock architecture for individual block locking on flash memory

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050063242A1 (en) * 2001-07-16 2005-03-24 Yuqing Ren Embedded software update methods and systems for digital devices
US20030142561A1 (en) * 2001-12-14 2003-07-31 I/O Integrity, Inc. Apparatus and caching method for optimizing server startup performance
US20040083346A1 (en) * 2002-10-24 2004-04-29 Micron Technology, Inc. Permanent memory block protection in a flash memory device
US6948041B2 (en) * 2002-10-24 2005-09-20 Micron Technology, Inc. Permanent memory block protection in a flash memory device
US6842371B2 (en) 2003-06-03 2005-01-11 Micron Technology, Inc. Permanent master block lock in a memory device
US20050273560A1 (en) * 2004-06-03 2005-12-08 Hulbert Jared E Method and apparatus to avoid incoherency between a cache memory and flash memory
US20060288182A1 (en) * 2005-06-03 2006-12-21 Lightuning Tech. Inc. Portable storage device capable of automatically running biometrics application programs and methods of automatically running the application programs
US7539830B2 (en) * 2005-06-03 2009-05-26 Egis Technology Inc. Portable storage device capable of automatically running biometrics application programs and methods of automatically running the application programs
US20150347053A1 (en) * 2014-05-28 2015-12-03 Sandisk Technologies Inc. Systems and Methods for Immediate Physical Erasure of Data Stored In a Memory System In Response to a User Command
US9658788B2 (en) * 2014-05-28 2017-05-23 Sandisk Technologies Llc Systems and methods for immediate physical erasure of data stored in a memory system in response to a user command
US10089226B2 (en) 2014-05-28 2018-10-02 Sandisk Technologies Llc Systems and methods for immediate physical erasure of data stored in a memory system in response to a user command

Also Published As

Publication number Publication date
US6446179B2 (en) 2002-09-03
US6209069B1 (en) 2001-03-27

Similar Documents

Publication Publication Date Title
US7603525B2 (en) Flash memory management method that is resistant to data corruption by power loss
US5432950A (en) System for securing a data processing system and method of operation
US6292874B1 (en) Memory management method and apparatus for partitioning homogeneous memory and restricting access of installed applications to predetermined memory ranges
EP1242868B1 (en) Organization of blocks within a nonvolatile memory unit to effectively decrease sector write operation time
JP5038292B2 (en) Use of the data latches in the cache operation of the nonvolatile memory
US6947323B2 (en) Chip protection register unlocking
US5388248A (en) Flash memory card including plural flash memories and circuitry for selectively outputting ready/busy signals in different operating modes
JP3517680B2 (en) Safety memory card having a program control system security access control
US7707354B2 (en) SRAM cache and flash micro-controller with differential packet interface
US6154808A (en) Method and apparatus for controlling data erase operations of a non-volatile memory device
US5237616A (en) Secure computer system having privileged and unprivileged memories
KR100347450B1 (en) The non-volatile memory and a memory card with the information processing apparatus and method for controlling software write protection of the non-volatile memory using it
US5911778A (en) Processing system security
US6148441A (en) Method for reprogramming flash ROM in a personal computer implementing an EISA bus system
JP5123410B2 (en) Integrated embedded flash and a mobile communication device having a sram memory
JP3703507B2 (en) Non-volatile memory
US5388083A (en) Flash memory mass storage architecture
EP1729304B1 (en) Space management for managing high capacity nonvolatile memory
US7870330B2 (en) Controller for refreshing memories
US5479638A (en) Flash memory mass storage architecture incorporation wear leveling technique
US6034897A (en) Space management for managing high capacity nonvolatile memory
US9201730B2 (en) Multiple level cell memory device with single bit per cell, re-mappable memory block
KR100448905B1 (en) Computer system with nand flash memory for booting and storagement
US5097445A (en) Semiconductor integrated circuit with selective read and write inhibiting
US8296467B2 (en) Single-chip flash device with boot code transfer capability

Legal Events

Date Code Title Description
CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12