Secure erase in a memory device

Abstract

The various implementations described herein include systems, methods and/or devices used to enable secure erase in a memory device. In one aspect, the method includes detecting a secure erase trigger. The method further includes determining a secure erase algorithm from among one or more secure erase algorithms to use in accordance with the detected secure erase trigger. The method further includes performing a secure erase operation in accordance with the selected secure erase algorithm, the secure erase operation including: (1) signaling a secure erase condition to a plurality of controllers on the memory device, (2) erasing one or more non-volatile memory devices on the memory device, (3) monitoring the secure erase operation, and (4) recording data related to the secure erase operation.

Description

TECHNICAL FIELD

The disclosed embodiments relate generally to memory systems, and in particular, to secure erase in a memory device.

BACKGROUND

Semiconductor memory devices, including flash memory, typically utilize memory cells to store data as an electrical value, such as an electrical charge or voltage. A flash memory cell, for example, includes a single transistor with a floating gate that is used to store a charge representative of a data value. Flash memory is a non-volatile data storage device that can be electrically erased and reprogrammed. More generally, non-volatile memory (e.g., flash memory, as well as other types of non-volatile memory implemented using any of a variety of technologies) retains stored information even when not powered, as opposed to volatile memory, which requires power to maintain the stored information.

In normal operations, as memory components fail, the failed memory components are replaced. In some cases, memory components are replaced on a scheduled maintenance interval. For example, dual in-line memory module (DIMM) devices may be routinely replaced. Traditionally, a DIMM device includes a series of dynamic random-access memory (DRAM) integrated circuits. DRAM is volatile memory since it loses its data quickly when power is removed, so no data remains on traditional DIMM devices when power is removed. However, for memory devices with non-volatile memory, data stored in the non-volatile memory remains stored when the memory devices are removed for service or replacement or in other situations unless measures are taken to erase the data stored in the non-volatile memory. Such measures may be appropriate when data security is desired or required.

SUMMARY

Various implementations of systems, methods and devices within the scope of the appended claims each have several aspects, no single one of which is solely responsible for the attributes described herein. Without limiting the scope of the appended claims, after considering this disclosure, and particularly after considering the section entitled “Detailed Description” one will understand how the aspects of various implementations are used to enable secure erase in a memory device. In one aspect, a secure erase operation is performed in accordance with a secure erase trigger.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the present disclosure can be understood in greater detail, a more particular description may be had by reference to the features of various implementations, some of which are illustrated in the appended drawings. The appended drawings, however, merely illustrate the more pertinent features of the present disclosure and are therefore not to be considered limiting, for the description may admit to other effective features.

FIG. 1 is a block diagram illustrating an implementation of a data storage system, in accordance with some embodiments.

FIG. 2 is a block diagram illustrating an implementation of secure erase circuitry, in accordance with some embodiments.

FIG. 3 is a block diagram illustrating an implementation of a storage controller, in accordance with some embodiments.

FIG. 4 is a block diagram illustrating an implementation of a non-volatile memory (NVM) controller, in accordance with some embodiments.

FIGS. 5A-5E illustrate a flowchart representation of a method of erasing data in a memory device, in accordance with some embodiments.

In accordance with common practice the various features illustrated in the drawings may not be drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may not depict all of the components of a given system, method or device. Finally, like reference numerals may be used to denote like features throughout the specification and figures.

DETAILED DESCRIPTION

The various implementations described herein include systems, methods and/or devices used to enable secure erase in a memory device. Some implementations include systems, methods and/or devices to perform a secure erase operation in accordance with a secure erase trigger.

More specifically, some implementations include a method of erasing data in a memory device. In some implementations, the method includes detecting a secure erase trigger. The method further includes determining a secure erase algorithm from among one or more secure erase algorithms to use in accordance with the detected secure erase trigger. The method further includes performing a secure erase operation in accordance with the selected secure erase algorithm, the secure erase operation including: (1) signaling a secure erase condition to a plurality of controllers on the memory device, (2) erasing one or more non-volatile memory devices on the memory device, (3) monitoring the secure erase operation, and (4) recording data related to the secure erase operation.

In some embodiments, the secure erase trigger includes a secure erase signal from a host system.

In some embodiments, the secure erase signal from the host system is communicated to the memory device through a double data rate (DDR) interface.

In some embodiments, the secure erase signal from the host system is communicated to the memory device through a Serial Presence Detect (SPD) interface.

In some embodiments, the secure erase trigger includes activation of a physical button on the memory device.

In some embodiments, the secure erase trigger is internally generated in the memory device when predefined criteria are satisfied, the predefined criteria including connection of the memory device to a new slot location.

In some embodiments, the secure erase trigger is internally generated in the memory device when predefined criteria are satisfied, the predefined criteria including failure to receive a command to preserve the memory device in a predetermined time period.

In some embodiments, the secure erase trigger is generated by a debug port associated with the memory device, wherein the debug port is password protected.

In some embodiments, the plurality of controllers on the memory device include a storage controller and one or more flash controllers, the one or more flash controllers coupled by the storage controller to a host interface of the memory device.

In some embodiments, the plurality of controllers on the memory device include at least one non-volatile storage controller and at least one other storage controller other than the at least one non-volatile storage controller.

In some embodiments, one of the plurality of controllers on the memory device maps double data rate (DDR) interface commands to serial advance technology attachment (SATA) interface commands.

In some embodiments, erasing one or more non-volatile memory devices on the memory device includes putting the memory device into a state that will erase the one or more non-volatile memory devices on the memory device the next time the memory device is powered up.

In some embodiments, performing a secure erase operation further includes preventing continued operation of the memory device by a host system.

In some embodiments, signaling the secure erase condition to the plurality of controllers on the memory device includes separately signaling the secure erase condition to each of the plurality of controllers.

In some embodiments, erasing one or more non-volatile memory devices on the memory device includes erasing a subset of flash memory devices associated with a flash controller of the plurality of controllers on the memory device.

In some embodiments, erasing one or more non-volatile memory devices on the memory device includes erasing all flash memory devices associated with a flash controller of the plurality of controllers on the memory device.

In some embodiments, erasing one or more non-volatile memory devices on the memory device includes erasing all flash memory devices associated with a subset of flash controllers of the plurality of controllers on the memory device.

In some embodiments, erasing one or more non-volatile memory devices on the memory device includes erasing all flash memory devices associated with all flash controllers of the plurality of controllers on the memory device.

In some embodiments, erasing one or more non-volatile memory devices on the memory device includes erasing the one or more non-volatile memory devices in a predefined sequence.

In some embodiments, the predefined sequence is programmable.

In some embodiments, the method further includes blocking host data from being preserved in response to a data hardening event while performing the secure erase operation. For example, in some embodiments, the method includes, in response to a data hardening event that occurs after initiation but prior to completion of the secure erase operation, saving metadata but not host data for the portions of memory to be erased by the secure erase operation.

In some embodiments, erasing one or more non-volatile memory devices on the memory device includes preserving at least predefined portions of metadata (e.g., usage metrics indicating or corresponding to cumulative usage or remaining endurance, maintained for respective portions (e.g., blocks, superblocks, or other storage units) of the non-volatile memory devices) on the memory device, while host data stored in the one or more non-volatile memory devices on the memory device is erased.

In some embodiments, the method further includes (1) prior to performing the secure erase operation, determining whether a variable is set to prevent the secure erase operation, and (2) in accordance with a determination that the variable is set, preventing performance of the secure erase operation.

In some embodiments, the variable is password protected, thereby preventing modification of the variable's value except in accordance with the provision of a password matching a previously established password.

In some embodiments, the non-volatile memory comprises one or more flash memory devices.

In some embodiments, the memory device includes a dual in-line memory module (DIMM) device.

In another aspect, any of the methods described above are performed by a memory device including (1) an interface for coupling the memory device to a host system, (2) a plurality of controllers (e.g., including a storage controller and one or more flash controllers), and (3) secure erase circuitry including one or more processors, the secure erase circuitry configured to perform or control performance of any of the methods described above.

In yet another aspect, any of the methods described above are performed by a memory device operable to erase data. In some embodiments, the device includes (1) an interface for coupling the memory device to a host system, (2) means for detecting a secure erase trigger, (3) means for determining a secure erase algorithm from among one or more secure erase algorithms to use in accordance with the detected secure erase trigger, and (4) means for performing a secure erase operation in accordance with the selected secure erase algorithm, the means for performing the secure erase operation including: (a) means for signaling a secure erase condition to a plurality of controllers on the memory device, (b) means for erasing one or more non-volatile memory devices on the memory device, (c) means for monitoring the secure erase operation, and (d) means for recording data related to the secure erase operation.

In yet another aspect, a non-transitory computer readable storage medium stores one or more programs for execution by one or more processors of a memory device having a plurality of controllers and secure erase circuitry, the one or more programs including instructions for performing any of the methods described above.

In some embodiments, the non-transitory computer readable storage medium includes a non-transitory computer readable storage medium associated with each of the plurality of controllers on the memory device and a non-transitory computer readable storage medium associated with the secure erase circuitry.

Numerous details are described herein in order to provide a thorough understanding of the example implementations illustrated in the accompanying drawings. However, some embodiments may be practiced without many of the specific details, and the scope of the claims is only limited by those features and aspects specifically recited in the claims. Furthermore, well-known methods, components, and circuits have not been described in exhaustive detail so as not to unnecessarily obscure more pertinent aspects of the implementations described herein.

FIG. 1 is a block diagram illustrating an implementation of a data storage system 100, in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, data storage system 100 includes memory device 120 (sometimes herein called a storage device, information storage device, or data storage device), which includes host interface 122, serial presence detect (SPD) device 124, secure erase circuitry 126, storage controller 128 (sometimes herein called a memory controller), one or more non-volatile memory (NVM) controllers 130 such as flash controllers, and non-volatile memory (NVM) (e.g., one or more NVM device(s) 140, 142 such as one or more flash memory devices), and is used in conjunction with computer system 110. In some implementations, memory device 120 includes a single flash memory device while in other implementations memory device 120 includes a plurality of flash memory devices. In some implementations, NVM devices 140, 142 include NAND-type flash memory or NOR-type flash memory. Further, in some implementations, NVM controller 130 is a solid-state drive (SSD) controller. However, one or more other types of storage media may be included in accordance with aspects of a wide variety of implementations.

Computer system 110 is coupled to memory device 120 through data connections 101. However, in some implementations computer system 110 includes memory device 120 as a component and/or sub-system. Computer system 110 may be any suitable computer device, such as a personal computer, a workstation, a computer server, or any other computing device. Computer system 110 is sometimes called a host or host system. In some implementations, computer system 110 includes one or more processors, one or more types of memory, optionally includes a display and/or other user interface components such as a keyboard, a touch screen display, a mouse, a track-pad, a digital camera and/or any number of supplemental devices to add functionality. Further, in some implementations, computer system 110 sends one or more host commands (e.g., read commands and/or write commands) on control line 111 to memory device 120. In some implementations, computer system 110 is a server system, such as a server system in a data center, and does not have a display and other user interface components.

In some implementations, memory device 120 includes NVM devices 140, 142 such as flash memory devices (e.g., NVM devices 140-1 through 140-n and NVM devices 142-1 through 142-k) and NVM controllers 130 such as flash controllers (e.g., NVM controllers 130-1 through 130-m). In some implementations, each NVM controller of NVM controllers 130 includes one or more processing units (also sometimes called CPUs or processors or microprocessors or microcontrollers) configured to execute instructions in one or more programs (e.g., in NVM controllers 130). In some implementations, the one or more processors are shared by one or more components within, and in some cases, beyond the function of NVM controllers 130. NVM devices 140, 142 are coupled to NVM controllers 130 through connections that typically convey commands in addition to data, and optionally convey metadata, error correction information and/or other information in addition to data values to be stored in NVM devices 140, 142 and data values read from NVM devices 140, 142. For example, NVM devices 140, 142 can be configured for enterprise storage suitable for applications such as cloud computing, or for caching data stored (or to be stored) in secondary storage, such as hard disk drives. Additionally and/or alternatively, flash memory (e.g., NVM devices 140, 142) can also be configured for relatively smaller-scale applications such as personal flash drives or hard-disk replacements for personal, laptop and tablet computers. Although flash memory devices and flash controllers are used as an example here, in some embodiments memory device 120 includes other non-volatile memory device(s) and corresponding non-volatile storage controller(s).

In some implementations, memory device 120 also includes host interface 122, SPD device 124, secure erase circuitry 126, and storage controller 128. Memory device 120 may include various additional features that have not been illustrated for the sake of brevity and so as not to obscure more pertinent features of the example implementations disclosed herein, and a different arrangement of features may be possible. Host interface 122 provides an interface to computer system 110 through data connections 101.

In some implementations, secure erase circuitry 126 includes one or more processing units (also sometimes called CPUs or processors or microprocessors or microcontrollers) configured to execute instructions in one or more programs (e.g., in secure erase circuitry 126). In some implementations, the one or more processors and the one or more programs executed by the one or more processors of secure erase circuitry 126 are used to perform functions beyond the function of securely erasing data. Secure erase circuitry 126 is sometimes herein called a supervisory controller or SPD/supervisory controller. Secure erase circuitry 126 is coupled to host interface 122, SPD device 124, storage controller 128, and NVM controllers 130 in order to coordinate the operation of these components, including supervising and controlling functions such as secure erase, data logging, and other aspects of managing functions on memory device 120.

Storage controller 128 is coupled to host interface 122, secure erase circuitry 126, and NVM controllers 130. In some implementations, during a write operation, storage controller 128 receives data from computer system 110 through host interface 122 and during a read operation, storage controller 128 sends data to computer system 110 through host interface 122. Further, host interface 122 provides additional data, signals, voltages, and/or other information needed for communication between storage controller 128 and computer system 110. In some embodiments, storage controller 128 and host interface 122 use a defined interface standard for communication, such as double data rate type three synchronous dynamic random access memory (DDR3). In some embodiments, storage controller 128 and NVM controllers 130 use a defined interface standard for communication, such as serial advance technology attachment (SATA). In some other implementations, the device interface used by storage controller 128 to communicate with NVM controllers 130 is SAS (serial attached SCSI), or other storage interface. In some implementations, storage controller 128 includes one or more processing units (also sometimes called CPUs or processors or microprocessors or microcontrollers) configured to execute instructions in one or more programs (e.g., in storage controller 128). In some implementations, the one or more processors are shared by one or more components within, and in some cases, beyond the function of storage controller 128.

SPD device 124 is coupled to host interface 122 and secure erase circuitry 126. Serial presence detect (SPD) refers to a standardized way to automatically access information about a computer memory module (e.g., memory device 120). For example, information about the type of the device (e.g., where the device type is one of a predefined set of device types), and the storage capacity of the device can be communicated with a host system (e.g., computer system 110) through SPD device 124. In another example, if the memory module has a failure, the failure can be communicated with a host system (e.g., computer system 110) through SPD device 124.

In some embodiments, SPD device 124 is a non-volatile memory device used to store data associated with secure erase circuitry 126. For example, in some embodiments, SPD device 124 stores data that indicates which events can trigger a secure erase operation (e.g., a host command, a change in slot location within a host, etc.), erase sequencing lists (e.g., for use in limited peak power usage), trigger matching codes (e.g., used as a key to allow secure erase operations), and/or other data associated with secure erase circuitry 126. Further, in some embodiments, SPD device 124 is used to record data related to a secure erase operation. For example, in some implementations, SPD device 124 records (1) a timestamp or other time value that indicates or represents the time (e.g., a real time clock value) when a secure erase operation was triggered (or requested or generated) (e.g., Thursday, Oct. 17, 2013, at 12:03:17 AM), (2) current status of the request to perform the secure erase operation, (3) current completion status of the secure erase operation, (4) reason for the secure erase operation (e.g., what type of secure erase trigger was detected), (5) the length of time the secure erase operation took to complete, and/or (6) other information regarding the secure erase operation.

FIG. 2 is a block diagram illustrating an implementation of secure erase circuitry 126, in accordance with some embodiments. Secure erase circuitry 126 typically includes one or more processors (also sometimes called CPUs or processing units or microprocessors or microcontrollers) 202 for executing modules, programs and/or instructions stored in memory 206 and thereby performing processing operations, memory 206, and one or more communication buses 208 for interconnecting these components. Communication buses 208 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Secure erase circuitry 126 is coupled to host interface 122, SPD device 124, storage controller 128, and NVM controllers 130 (e.g., NVM controllers 130-1 through 130-m) by communication buses 208. Memory 206 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 206 optionally includes one or more storage devices remotely located from processor(s) 202. Memory 206, or alternately the non-volatile memory device(s) within memory 206, comprises a non-transitory computer readable storage medium. In some embodiments, memory 206, or the computer readable storage medium of memory 206 stores the following programs, modules, and data structures, or a subset thereof:

• • a trigger module 210 that is used for detecting a secure erase trigger or internally generating a secure erase trigger;
  • an algorithm module 212 that is used for determining a secure erase algorithm from among one or more secure erase algorithms to use for a secure erase operation; and
  • a secure erase module 214 that is used for performing a secure erase operation in accordance with the selected secure erase algorithm.

In some embodiments, memory 206, or the computer readable storage medium of memory 206 further stores a configuration module for configuring memory device 120 and secure erase circuitry 126, and/or configuration values (such as one or more predefined sequences for a secure erase operation) for configuring secure erase circuitry 126, neither of which is explicitly shown in FIG. 2. In some implementations, upon power up and upon reset, the configuration module automatically sets the values of one or more configuration parameters of memory device 120 (and, optionally, determines which of two or more secure erase modules, etc. to use) in accordance with the components of memory device 120 (e.g., the type of non-volatile memory components in memory device 120) and/or characteristics of the data storage system 100 that includes memory device 120.

In some embodiments, the secure erase module 214 optionally includes the following modules or sub-modules, or a subset thereof:

• • a signal module 216 that is used for signaling a secure erase condition to a plurality of controllers on the memory device (e.g., storage controller 128 and NVM controllers 130, FIG. 1);
  • optionally, an erase module 218 that is used for erasing one or more non-volatile memory devices (e.g., NVM devices 140, 142, FIG. 1) on the memory device;
  • a monitor module 220 that is used for monitoring the secure erase operation;
  • a recording module 222 that is used for recording data related to the secure erase operation; and
  • a prevention module 224 that is used for preventing one or more activities (e.g., host commands, data hardening events, and/or the secure erase operation).

In some embodiments, secure erase module 214 does not include an erase module 218, and instead each of the NVM controllers 130 has an erase module (e.g., erase module 414, FIG. 4) that it executes in order to erase data in one or more non-volatile memory devices in response to detecting a signal from secure erase circuitry 126 that signals a secure erase condition.

Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 206 may store a subset of the modules and data structures identified above. Furthermore, memory 206 may store additional modules and data structures not described above. In some embodiments, the programs, modules, and data structures stored in memory 206, or the computer readable storage medium of memory 206, provide instructions for implementing any of the methods described below with reference to FIGS. 5A-5E.

Although FIG. 2 shows secure erase circuitry 126, FIG. 2 is intended more as a functional description of the various features which may be present in secure erase circuitry than as a structural schematic of the embodiments described herein. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated.

FIG. 3 is a block diagram illustrating an implementation of a storage controller 128, in accordance with some embodiments. Storage controller 128 typically includes one or more processors (also sometimes called CPUs or processing units or microprocessors or microcontrollers) 302 for executing modules, programs and/or instructions stored in memory 306 and thereby performing processing operations, memory 306, and one or more communication buses 308 for interconnecting these components. Communication buses 308 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Storage controller 128 is coupled to host interface 122, secure erase circuitry 126, and NVM controllers 130 (e.g., NVM controllers 130-1 through 130-m) by communication buses 308. Memory 306 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 306 optionally includes one or more storage devices remotely located from processor(s) 302. Memory 306, or alternately the non-volatile memory device(s) within memory 306, comprises a non-transitory computer readable storage medium. In some embodiments, memory 306, or the computer readable storage medium of memory 306 stores the following programs, modules, and data structures, or a subset thereof:

• • an interface module 310 that is used for communicating with other components, such as host interface 122, secure erase circuitry 126, and NVM controllers 130;
  • optionally, a secure erase module 312 that is used for performing a secure erase operation;
  • volatile data 318, including volatile data associated with storage controller 128; and
  • non-volatile data 320, including non-volatile data associated with storage controller 128.

In some embodiments, the secure erase module 312, if provided, includes the following modules or sub-modules, or a subset thereof:

• • an erase module 314 that is used for instructing the one or more non-volatile storage controllers (e.g., NVM controllers 130, FIG. 1) to erase one or more non-volatile memory devices (e.g., NVM devices 140, 142, FIG. 1) on the memory device; and
  • a state module 316 that is used for maintaining one or more state variables (e.g., indicating status of a secure erase operation).

Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 306 may store a subset of the modules and data structures identified above. Furthermore, memory 306 may store additional modules and data structures not described above. In some embodiments, the programs, modules, and data structures stored in memory 306, or the computer readable storage medium of memory 306, provide instructions for implementing respective operations in the methods described below with reference to FIGS. 5A-5E.

Although FIG. 3 shows a storage controller 128, FIG. 3 is intended more as a functional description of the various features which may be present in a storage controller than as a structural schematic of the embodiments described herein. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated.

FIG. 4 is a block diagram illustrating an implementation of a non-volatile memory (NVM) controller 130-1, in accordance with some embodiments. NVM controller 130-1 typically includes one or more processors (also sometimes called CPUs or processing units or microprocessors or microcontrollers) 402 for executing modules, programs and/or instructions stored in memory 306 and thereby performing processing operations, memory 406, and one or more communication buses 408 for interconnecting these components. Communication buses 408 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. NVM controller 130-1 is coupled to storage controller 128, secure erase circuitry 126, and NVM devices 140 (e.g., NVM devices 140-1 through 140-n) by communication buses 408. Memory 406 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 406 optionally includes one or more storage devices remotely located from processor(s) 402. Memory 406, or alternately the non-volatile memory device(s) within memory 406, comprises a non-transitory computer readable storage medium. In some embodiments, memory 406, or the computer readable storage medium of memory 406 stores the following programs, modules, and data structures, or a subset thereof:

• • an interface module 410 that is used for communicating with other components, such as storage controller 128, secure erase circuitry 126, and NVM devices 140;
  • a secure erase module 412 that is used for performing a secure erase operation;
  • volatile data 418, including volatile data associated with NVM controller 130-1; and
  • non-volatile data 420, including non-volatile data associated with NVM controller 130-1.

In some embodiments, the secure erase module 412 optionally includes the following modules or sub-modules, or a subset thereof:

• • an erase module 414 that is used for erasing one or more non-volatile memory devices (e.g., NVM devices 140-1 through 140-n) on the memory device; and
  • a state module 416 that is used for maintaining one or more state variables (e.g., indicating status of a secure erase operation).

Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 406 may store a subset of the modules and data structures identified above. Furthermore, memory 406 may store additional modules and data structures not described above. In some embodiments, the programs, modules, and data structures stored in memory 406, or the computer readable storage medium of memory 406, provide instructions for implementing respective operations in the methods described below with reference to FIGS. 5A-5E.

Although FIG. 4 shows a NVM controller 130-1, FIG. 4 is intended more as a functional description of the various features which may be present in a NVM controller than as a structural schematic of the embodiments described herein. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated. Further, although FIG. 4 shows a NVM controller 130-1, the description of FIG. 4 similarly applies to other NVM controllers (e.g., NVM controllers 130-2 through 130-m) in memory device 120 (FIG. 1).

FIGS. 5A-5E illustrate a flowchart representation of a method 500 of erasing data in a memory device, in accordance with some embodiments. A memory device (e.g., memory device 120, FIG. 1) coordinates and manages multiple sub-system components to erase data, which initiates performance of method 500. At least in some implementations, method 500 is performed by a memory device (e.g., memory device 120, FIG. 1) or one or more components of the memory device (e.g., secure erase circuitry 126, storage controller 128, and/or NVM controllers 130, FIG. 1). In some embodiments, method 500 is governed by instructions that are stored in a non-transitory computer readable storage medium and that are executed by one or more processors of a device, such as the one or more processors 202 of secure erase circuitry 126, the one or more processors 302 of storage controller 128, and/or the one or more processors 402 of NVM controllers 130, as shown in FIGS. 2-4.

A memory device (e.g., memory device 120, FIG. 1) detects (502) a secure erase trigger. In some embodiments, or in some circumstances, the memory device receives the secure erase trigger from a source external to the memory device (e.g., from a host system), as described in more detail below. In other embodiments, or in other circumstances, the memory device receives the secure erase trigger from a source internal to the memory device and/or the secure erase trigger is internally generated in the memory device, as described in more detail below. As discussed above, in some embodiments, the memory device stores data (e.g., in SPD device 124, FIG. 1) that indicates which events can trigger a secure erase operation. Thus, in some configurations, one subset of events will cause a secure erase trigger, while in other configurations another subset of events will cause a secure erase trigger. For example, in one configuration a regular (not password-protected) host command can be used to trigger a secure erase operation, while in another configuration that same host command is blocked from triggering a secure erase operation. In another example, in one configuration a secure erase operation is triggered by detection (by the memory device) that the memory device has powered up in a different memory slot than the memory slot in which it was previously located, while in another configuration, detection of that condition does not trigger a secure erase operation. In some embodiments, programmable data stored in non-volatile memory (e.g., in SPD device 124, FIG. 1) provides control over allowable trigger types. In some implementations, a trigger module (e.g., trigger module 210, FIG. 2) is used to detect a secure erase trigger, as described above with respect to FIG. 2.

In some embodiments, the secure erase trigger includes (504) a secure erase signal from a host system (e.g., computer system 110, FIG. 1). In some implementations, the secure erase signal from the host system is (506) communicated to the memory device through a double data rate (DDR) interface (e.g., the memory device is coupled to the host system by a DDR interface compliant with an interface standard for DDR DRAM devices). In some implementations, the secure erase signal from the host system is (508) communicated to the memory device through a Serial Presence Detect (SPD) interface.

In some embodiments, the secure erase trigger includes (510) activation of a physical button on the memory device. For example, in some implementations, a user presses a physical button on the memory device (e.g., memory device 120, FIG. 1) to generate the secure erase trigger.

In some embodiments, the secure erase trigger is (512) internally generated in the memory device (e.g., memory device 120, FIG. 1) when predefined criteria are satisfied, the predefined criteria including connection of the memory device to a new slot location. In some implementations, via the Serial Presence Detect (SPD) interface, position information (e.g., slot location in a host system) can be obtained and used as a secure erase trigger if the slot location is different from the slot location during the last boot operation. For example, the memory device may be in slot number 17 out of 64 slots in the host system (e.g., computer system 110, FIG. 1), and the secure erase trigger is internally generated in the memory device when the memory device is connected to a new slot location (e.g., a slot location other than slot number 17 in the host system, or a slot location in another host system). In some implementations, a trigger module (e.g., trigger module 210, FIG. 2) is used to internally generate the secure erase trigger when predefined criteria are satisfied, the predefined criteria including connection of the memory device to a new slot location, as described above with respect to FIG. 2.

In some embodiments, the secure erase trigger is (514) internally generated in the memory device (e.g., memory device 120, FIG. 1) when predefined criteria are satisfied, the predefined criteria including failure to receive a command to preserve data stored in the memory device within a predetermined time period. In some embodiments, a “watch dog” system automatically erases data stored in the memory device (e.g., by internally generating the secure erase trigger) if a boot command to preserve data stored in the memory device is not issued by the host at system startup. In some embodiments, a “watch dog” system automatically erases data stored in the memory device (e.g., by internally generating the secure erase trigger) if a command to preserve the memory is not received every predetermined time period (e.g., every 24 hours). In some implementations, a trigger module (e.g., trigger module 210, FIG. 2) is used to internally generate the secure erase trigger when predefined criteria are satisfied, the predefined criteria including failure to receive a command to preserve data stored in the memory device within a predetermined time period, as described above with respect to FIG. 2.

In some embodiments, the secure erase trigger is (516) generated by a debug port associated with the memory device (e.g., memory device 120, FIG. 1), and the debug port is password protected. In some embodiments, the debug port is password protected and generates a secure erase trigger if a user enters (e.g., sends to the debug port of the memory device) a predefined password (e.g., enters a password that matches a predefined password, which optionally a special “erase” password used to enable the issuance of the secure erase trigger) and a predefined “erase” command.

Next, after the memory device (e.g., memory device 120, FIG. 1) detects (502) a secure erase trigger, the memory device determines (518) a secure erase algorithm from among one or more secure erase algorithms to use in accordance with the detected secure erase trigger. In some embodiments, the one or more secure erase algorithms include algorithms to overwrite a storage medium with specific overwrite patterns and optionally, with multiple passes (repeated erase operations on the same memory locations). In some embodiments, the one or more secure erase algorithms include applying a high energy impulse to destroy the one or more non-volatile memory devices on the memory device. In some embodiments, the one or more secure erase algorithms include other types of secure erase procedures. In some implementations, the one or more secure erase algorithms are stored in secure erase circuitry (e.g., secure erase circuitry 126, FIG. 1) and in controllers (e.g., NVM controllers 130, FIG. 1, and optionally storage controller 128), and are selected in accordance with the detected secure erase trigger, allowing one or more different secure erase procedures to be performed on the memory device. In some implementations, an algorithm module (e.g., algorithm module 212, FIG. 2) is used to determine a secure erase algorithm from among one or more secure erase algorithms to use in accordance with the detected secure erase trigger, as described above with respect to FIG. 2.

Next, the memory device performs (520) a secure erase operation in accordance with the selected secure erase algorithm. For example, if it was determined in operation 518 to use a first secure erase algorithm in accordance with the detected secure erase trigger, then the memory device performs a secure erase operation in accordance with the first secure erase algorithm. In some implementations, a secure erase module (e.g., secure erase module 214, FIG. 2) in secure erase circuitry (e.g., secure erase circuitry 126, FIGS. 1 and 2) and/or a secure erase module on one or more controllers (e.g., secure erase module 312 in storage controller 128, FIG. 3 and/or secure erase module 412 in NVM controller 130, FIG. 4) are used to perform a secure erase operation in accordance with the selected secure erase algorithm, as described above with respect to FIGS. 2-4.

First, the secure erase operation includes (520) signaling (522) a secure erase condition to a plurality of controllers on the memory device (e.g., storage controller 128 and NVM controllers 130, FIG. 1). In some implementations, a signal module (e.g., signal module 216, FIG. 2) is used to signal a secure erase condition to a plurality of controllers on the memory device, as described above with respect to FIG. 2.

In some embodiments, the plurality of controllers on the memory device include (524) a storage controller (e.g., storage controller 128, FIG. 1) and one or more flash controllers (e.g., NVM controllers 130, FIG. 1), the one or more flash controllers coupled by the storage controller to a host interface (e.g., host interface 122, FIG. 1) of the memory device.

In some embodiments, the plurality of controllers on the memory device include (526) at least one non-volatile storage controller and at least one other controller other than the at least one non-volatile storage controller. In some implementations, the at least one non-volatile storage controller is a flash controller (e.g., NVM controller 130-1, FIG. 1). In other implementations, the at least one non-volatile storage controller controls one or more other types of non-volatile memory devices.

In some embodiments, one of the plurality of controllers on the memory device maps (528) double data rate (DDR) interface commands to serial advance technology attachment (SATA) interface commands. For example, a storage controller (e.g., storage controller 128, FIG. 1) maps double data rate type three (DDR3) interface commands to SATA interface commands. In some implementations, a storage controller (e.g., storage controller 128, FIG. 1) uses a defined interface standard, such as DDR3, to communicate with a host interface (e.g., host interface 122, FIG. 1) and uses a defined interface standard, such as SATA, to communicate with other controllers on the memory device (e.g., NVM controllers 130, FIG. 1).

In some embodiments, signaling (522) the secure erase condition to the plurality of controllers on the memory device includes separately signaling (530) the secure erase condition to each of the plurality of controllers (e.g., storage controller 128, NVM controller 130-1, . . . , NVM controller 130-m, FIG. 1). In some implementations, individual secure erase signals to each of the plurality of controllers allow for sequential sequencing of the secure erase operation across the plurality of controllers, parallel performance of the secure erase operation across the plurality of controllers, or a combination of sequential and parallel sequencing for the secure erase operation. In a non-limiting example of a sequential sequence, the secure erase operation for a first NVM controller (e.g., NVM controller 130-1, FIG. 1) will be performed prior in time, or started prior in time, to the secure erase operation for a second NVM controller (e.g., NVM controller 130-m, FIG. 1). Further, in a non-limiting example of a combination of sequential and parallel sequences, the secure erase operations of two or more NVM controllers (e.g., NVM controller 130-1 and NVM controller 130-2, FIG. 1) are performed simultaneously, while the secure erase operation for another NVM controller (e.g., NVM controller 130-m, FIG. 1) is performed prior to, or started prior to, the parallel secure erase operation of the aforementioned NVM controllers. In some implementations, a signal module (e.g., signal module 216, FIG. 2) is used to separately signal the secure erase condition to each of the plurality of controllers, as described above with respect to FIG. 2.

Next, the secure erase operation includes (520) erasing (532) one or more non-volatile memory devices (e.g., NVM devices 140, 142, FIG. 1) on the memory device (e.g., memory device 120, FIG. 1). In some implementations, an erase module of the secure erase circuitry and/or an erase module of the one or more controllers (e.g., erase module 218, FIG. 2, erase module 314, FIG. 3, and/or erase module 414, FIG. 4) are used to erase one or more non-volatile memory devices on the memory device, as described above with respect to FIGS. 2-4.

In some embodiments, erasing (532) one or more non-volatile memory devices on the memory device includes putting (534) the memory device into a state that will erase the one or more non-volatile memory devices (e.g., NVM devices 140, 142, FIG. 1) on the memory device the next time the memory device is powered up. In some implementations, the memory device records the state in non-volatile memory associated with the secure erase circuitry (e.g., in SPD device 124, FIG. 1) and/or in non-volatile memory associated with one or more controllers (e.g., in non-volatile data 320 of storage controller 128, FIG. 3, and/or in non-volatile data 420 of NVM controller 130, FIG. 4). In some embodiments, for example, if the memory device is powered off during the secure erase operation, after the memory device powers back up, the memory device disallows host commands and continues erasing the one or more non-volatile memory devices. In some implementations, an erase module of the secure erase circuitry and/or an erase module of one or more controllers (e.g., erase module 218, FIG. 2, erase module 314, FIG. 3, and/or erase module 414, FIG. 4) are used to put the memory device into a state that will erase the one or more non-volatile memory devices on the memory device the next time the memory device is powered up, as described above with respect to FIGS. 2-4. In some implementations, state modules on one or more controllers (e.g., state module 316, FIG. 3 and/or state module 416, FIG. 4) are used to maintain one or more state variables (e.g., indicating status of the secure erase operation), as described above with respect to FIGS. 3-4.

In some embodiments, erasing (532) one or more non-volatile memory devices on the memory device includes erasing (536) a subset of flash memory devices associated with a flash controller of the plurality of controllers on the memory device (e.g., erasing a subset of NVM devices 140-1 through 140-n associated with NVM controller 130-1). For example, in some embodiments, erasing a subset of flash memory devices associated with a flash controller of the plurality of controllers on the memory device includes erasing two (out of n) flash memory devices (e.g., NVM device 140-1 and NVM device 140-3, FIG. 1) associated with a flash controller (e.g., NVM controller 130-1, FIG. 1). In some implementations, an erase module of the secure erase circuitry and/or an erase module of one or more controllers (e.g., erase module 218, FIG. 2, erase module 314, FIG. 3, and/or erase module 414, FIG. 4) are used to erase a subset of flash memory devices associated with a flash controller of the plurality of controllers on the memory device, as described above with respect to FIGS. 2-4.

In some embodiments, erasing (532) one or more non-volatile memory devices on the memory device includes erasing (538) all flash memory devices associated with a flash controller of the plurality of controllers on the memory device. For example, in some embodiments, erasing all flash memory devices associated with a flash controller of the plurality of controllers on the memory device includes erasing n (out of n) flash memory devices (e.g., NVM device 140-1 through NVM device 140-n, FIG. 1) associated with a flash controller (e.g., NVM controller 130-1, FIG. 1). In some implementations, an erase module of the secure erase circuitry and/or an erase module of one or more controllers (e.g., erase module 218, FIG. 2, erase module 314, FIG. 3, and/or erase module 414, FIG. 4) are used to erase all flash memory devices associated with a flash controller of the plurality of controllers on the memory device, as described above with respect to FIGS. 2-4.

In some embodiments, erasing (532) one or more non-volatile memory devices on the memory device includes erasing (540) all flash memory devices associated with a subset of flash controllers of the plurality of controllers on the memory device. For example, in some embodiments, erasing all flash memory devices associated with a subset of flash controllers of the plurality of controllers (e.g., associated with 2 flash controllers out of m flash controllers) on the memory device includes erasing n (out of n) flash memory devices (e.g., NVM device 140-1 through NVM device 140-n, FIG. 1) associated with a first flash controller (e.g., NVM controller 130-1, FIG. 1) and erasing p (out of p) flash memory devices (e.g., NVM device 141-1 though NVM device 141-p, not shown in FIG. 1) associated with a second flash controller (e.g., NVM controller 130-2, not shown in FIG. 1). In some implementations, an erase module of the secure erase circuitry and/or an erase module of one or more controllers (e.g., erase module 218, FIG. 2, erase module 314, FIG. 3, and/or erase module 414, FIG. 4) are used to erase all flash memory devices associated with a subset of flash controllers of the plurality of controllers on the memory device, as described above with respect to FIGS. 2-4.

In some embodiments, erasing (532) one or more non-volatile memory devices on the memory device includes erasing (542) all flash memory devices associated with all flash controllers of the plurality of controllers on the memory device. For example, in some embodiments, erasing all flash memory devices associated with all flash controllers of the plurality of controllers on the memory device includes erasing n (out of n) flash memory devices (e.g., NVM device 140-1 through NVM device 140-n, FIG. 1) associated with a first flash controller (e.g., NVM controller 130-1, FIG. 1), erasing k (out of k) flash memory devices (e.g., NVM device 142-1 through NVM device 142-k, FIG. 1) associated with a last flash controller (e.g., NVM controller 130-m, FIG. 1), and every flash memory device in between (not shown in FIG. 1). In some implementations, an erase module of the secure erase circuitry and/or an erase module of one or more controllers (e.g., erase module 218, FIG. 2, erase module 314, FIG. 3, and/or erase module 414, FIG. 4) are used to erase all flash memory devices associated with all flash controllers of the plurality of controllers on the memory device, as described above with respect to FIGS. 2-4.

In some embodiments, erasing (532) one or more non-volatile memory devices on the memory device includes erasing (544) the one or more non-volatile memory devices in a predefined sequence. In some embodiments, since secure erase functions typically consume more power than regular operations, the erasing is sequenced so a peak power limit is not reached or exceeded. As explained above with respect to operation 530, in some implementations, the one or more non-volatile memory devices are erased sequentially, in parallel, or with a combination of sequential and parallel sequencing. In some implementations, an erase module on secure erase circuitry and/or on one or more controllers (e.g., erase module 218, FIG. 2, erase module 314, FIG. 3, and/or erase module 414, FIG. 4) are used to erase the one or more non-volatile memory devices in a predefined sequence, as described above with respect to FIGS. 2-4.

In some embodiments, the predefined sequence is (546) programmable. For example, in some implementations, the predefined sequence is programmed to include sequential erasing (e.g., erasing NVM devices associated with NVM controller 130-1, followed by erasing NVM devices associated with NVM controller 130-2, etc.). In some implementations, the predefined sequence is programmed to include parallel erasing (e.g., erasing NVM devices associated with a first NVM controller 130-1 in parallel with erasing NVM devices associated with a second NVM controller 130). In some implementations, the predefined sequence is programmed to include a combination of sequential and parallel sequencing (e.g., erasing NVM devices associated with a first NVM controller 130-1, followed by erasing NVM devices associated with a second NVM controller 130 in parallel with erasing NVM devices associated with a third NVM controller 130).

In some embodiments, the non-volatile memory comprises (548) one or more flash memory devices (e.g., NVM devices 140, 142, FIG. 1). In some implementations, the non-volatile memory includes a single flash memory device, while in other implementations the non-volatile memory includes a plurality of flash memory devices. In some implementations, the non-volatile memory includes NAND-type flash memory or NOR-type flash memory. In other embodiments, the non-volatile memory comprises one or more other types of non-volatile storage devices.

In some embodiments, the memory device is or includes (550) a dual in-line memory module (DIMM) device. In some implementations, the memory device is compatible with a DIMM memory slot. For example, in some implementations, the memory device is compatible with a 240-pin DIMM memory slot and is compatible with signaling in accordance with a DDR3 interface specification.

Next, the secure erase operation includes (520) monitoring (552) the secure erase operation. In some implementations, monitoring the secure erase operation includes monitoring (1) current completion status of the secure erase operation, (2) time spent on the secure erase operation, and/or (3) other information regarding the secure erase operation. In some implementations, a monitor module (e.g., monitor module 220, FIG. 2) is used to monitor the secure erase operation, as described above with respect to FIG. 2.

The secure erase operation also includes (520) recording (554) data related to the secure erase operation. In some embodiments, data related to the secure erase operation is recorded to non-volatile memory associated with the secure erase circuitry (e.g., SPD device 124 associated with secure erase circuitry 126, FIG. 1). In some embodiments, recording data related to the secure erase operation includes recording (1) a timestamp or other time value that indicates or represents the time (e.g., a real time clock value) when a secure erase operation was triggered (or requested or generated) (e.g., Thursday, Oct. 17, 2013, at 12:03:17 AM), (2) current status of the request (or trigger) of the secure erase operation, (3) current completion status of the secure erase operation, (4) reason for the secure erase operation (e.g., what type of secure erase trigger was detected), (5) the length of time the secure erase operation took to complete, and/or (6) other information regarding the secure erase operation. In some implementations, a recording module (e.g., recording module 222, FIG. 2) is used to record data related to the secure erase operation, as described above with respect to FIG. 2.

Optionally, the secure erase operation includes (520) preventing (556) continued operation of the memory device by a host system. In some embodiments, for example, if the memory device is powered off during the secure erase operation, after the memory device powers back up, the memory device disallows (e.g., ignores, or does not execute) host commands (e.g., from computer system 110, FIG. 1) and continues erasing the one or more non-volatile memory devices. In some implementations, a prevention module (e.g., prevention module 224, FIG. 2) is used to prevent continued operation of the memory device by a host system, as described above with respect to FIG. 2.

Optionally, the memory device blocks (558) host data (e.g., data received from one or more hosts, and associated error correction values) from being preserved (sometimes called “hardened”) in response to data hardening events that occur while performing the secure erase operation. For example, while performing the secure erase operation, the memory device does not allow data hardening events to harden host data (e.g., host data is not transferred from volatile memory to non-volatile memory in response to a power failure). Instead, in some implementations, if the memory device loses power during the secure erase operation, the memory device saves the current secure erase state and device usage and/or endurance metadata for the non-volatile memory devices being erased, and resumes the secure erase operation after the memory device regains power. In some implementations, a prevention module (e.g., prevention module 224, FIG. 2) is used to block host data from being preserved in response to data hardening events while performing the secure erase operation, as described above with respect to FIG. 2. For example, in some embodiments, the method includes, in response to a data hardening event that occurs after initiation but prior to completion of the secure erase operation, saving metadata but not host data for the non-volatile memory devices to be erased by the secure erase operation. In some implementations, the metadata saved includes metadata representing or corresponding to cumulative usage and/or remaining endurance, maintained for respective portions (e.g., blocks, superblocks, or other storage units) of the non-volatile memory devices being erased.

In some embodiments, erasing one or more non-volatile memory devices on the memory device includes preserving at least predefined portions of metadata (e.g., usage metrics indicating or corresponding to cumulative usage or remaining endurance, maintained for respective portions (e.g., blocks, superblocks, or other storage units) of the non-volatile memory devices) on the memory device, while host data stored in the one or more non-volatile memory devices on the memory device is erased. For further information concerning preserving metadata while erasing data, see U.S. Provisional Patent Application No. 61/911,403, filed Dec. 3, 2013, and U.S. application Ser. No. 14/135,256, filed Dec. 19, 2013, both of which are herein incorporated by reference in their entireties.

Optionally, prior to performing the secure erase operation, the memory device determines (560) whether a variable is set to prevent the secure erase operation. In some embodiments, the variable is stored in non-volatile memory associated with the secure erase circuitry (e.g., in SPD device 124 associated with secure erase circuitry 126, FIG. 1). In some embodiments, the variable is set when conditions that would normally trigger a secure erase should be overridden or ignored (e.g., during manufacturing and/or testing). In some implementations, a prevention module (e.g., prevention module 224, FIG. 2) is used to determine whether a variable is set (or has been set) to prevent the secure erase operation, as described above with respect to FIG. 2.

In some embodiments, the aforementioned variable is password protected (562), thereby preventing modification of the variable's value except in accordance with the provision of a password matching a previously established password. In some implementations, the variable is stored in non-volatile memory and is safeguarded against modification (sometimes called editing) unless a password matching the previously established password is entered. In some embodiments, editing the variable includes setting the variable to prevent the secure erase operation. In some embodiments, editing the variable includes resetting the variable to allow the secure erase operation. In some implementations, the variable is stored as a flag. In some implementations, the variable is stored as a command.

Further, in some implementations, in accordance with a determination that the variable is set, the memory device prevents (564) performance of the secure erase operation. In some embodiments, as long as the variable is set, performance of the secure erase operation is prevented (e.g., secure erase functionality is disabled when the variable is set). In some implementations, a prevention module (e.g., prevention module 224, FIG. 2) is used to prevent performance of the secure erase operation, as described above with respect to FIG. 2.

In some implementations, with respect to any of the methods described above, the non-volatile memory is a single flash memory device, while in other implementations, the non-volatile memory includes a plurality of flash memory devices.

In some implementations, with respect to any of the methods described above, a memory device includes (1) an interface for coupling the memory device to a host system, (2) a plurality of controllers (e.g., including a storage controller and one or more flash controllers), and (3) secure erase circuitry including one or more processors, the memory device configured to perform or control performance of any of the methods described above.

It will be understood that, although the terms “first,” “second,” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, which changing the meaning of the description, so long as all occurrences of the “first contact” are renamed consistently and all occurrences of the second contact are renamed consistently. The first contact and the second contact are both contacts, but they are not the same contact.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the claims. As used in the description of the embodiments and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in accordance with a determination” or “in response to detecting,” that a stated condition precedent is true, depending on the context. Similarly, the phrase “if it is determined [that a stated condition precedent is true]” or “if [a stated condition precedent is true]” or “when [a stated condition precedent is true]” may be construed to mean “upon determining” or “in response to determining” or “in accordance with a determination” or “upon detecting” or “in response to detecting” that the stated condition precedent is true, depending on the context.

The foregoing description, for purpose of explanation, has been described with reference to specific implementations. However, the illustrative discussions above are not intended to be exhaustive or to limit the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The implementations were chosen and described in order to best explain principles of operation and practical applications, to thereby enable others skilled in the art.

Claims

1. A method of erasing data in a memory device, the method comprising: in the memory device, the memory device having a plurality of hardware controllers: detecting a secure erase trigger;determining a secure erase algorithm from among a plurality of secure erase algorithms to use in accordance with the detected secure erase trigger;performing a secure erase operation in accordance with the determined secure erase algorithm, the secure erase operation including: signaling a secure erase condition to the plurality of hardware controllers on the memory device;erasing, in parallel, two or more non-volatile memory devices on the memory device;monitoring the secure erase operation, wherein monitoring the secure erase operation includes monitoring a completion status of the secure erase operation; andbased on the monitoring, recording data related to the secure erase operation, the recorded data including data indicating the completion status of the secure erase operation.

2. The method of claim 1, further comprising saving data indicating a state of the secure erase operation in response to a loss of power prior to completion of the secure erase operation.

3. The method of claim 1, wherein the plurality of secure erase algorithms include at least one algorithm to overwrite a storage medium with specific overwrite patterns and at least one algorithm other than an overwrite algorithm.

4. The method of claim 1, wherein the secure erase trigger includes a secure erase signal from a host system, and wherein the secure erase signal is communicated from the host system to the memory device through a Serial Presence Detect (SPD) interface.

5. The method of claim 1, wherein at least one of the plurality of secure erase algorithms applies a high energy impulse to destroy the one or more volatile memory devices on the memory device.

6. The method of claim 1, wherein the secure erase trigger is internally generated in the memory device when predefined criteria are satisfied, the predefined criteria including connection of the memory device to a new slot location.

7. The method of claim 1, wherein the secure erase trigger is internally generated in the memory device when predefined criteria are satisfied, the predefined criteria including failure to receive a command to preserve the memory device in a predetermined time period.

8. The method of claim 1, wherein the secure erase trigger is generated by a debug port associated with the memory device, wherein the debug port is password protected.

9. The method of claim 1, wherein the plurality of controllers on the memory device include a storage controller and one or more flash controllers, the one or more flash controllers coupled by the storage controller to a host interface of the memory device.

10. The method of claim 1, wherein the plurality of controllers on the memory device include at least one non-volatile storage controller and at least one other storage controller other than the at least one non-volatile storage controller.

11. The method of claim 1, wherein one of the plurality of controllers on the memory device maps double data rate (DDR) interface commands to serial advance technology attachment (SATA) interface commands.

12. The method of claim 1, wherein erasing one or more non-volatile memory devices on the memory device includes putting the memory device into a state that will erase the one or more non-volatile memory devices on the memory device the next time the memory device is powered up.

13. The method of claim 1, wherein performing a secure erase operation further includes preventing continued operation of the memory device by a host system.

14. The method of claim 1, wherein signaling the secure erase condition to the plurality of controllers on the memory device includes separately signaling the secure erase condition to each of the plurality of controllers.

15. The method of claim 1, wherein erasing one or more non-volatile memory devices on the memory device includes erasing a subset of flash memory devices associated with a flash controller of the plurality of controllers on the memory device.

16. The method of claim 1, wherein erasing one or more non-volatile memory devices on the memory device includes erasing all flash memory devices associated with a flash controller of the plurality of controllers on the memory device.

17. The method of claim 1, wherein erasing one or more non-volatile memory devices on the memory device includes erasing all flash memory devices associated with a subset of flash controllers of the plurality of controllers on the memory device.

18. The method of claim 1, wherein erasing one or more non-volatile memory devices on the memory device includes erasing all flash memory devices associated with all flash controllers of the plurality of controllers on the memory device.

19. The method of claim 1, wherein erasing one or more non-volatile memory devices on the memory device includes erasing the one or more non-volatile memory devices in a predefined sequence.

20. The method of claim 19, wherein the predefined sequence is programmable.

21. The method of claim 1, further comprising blocking host data from being preserved in response to data hardening events that occur while performing the secure erase operation.

22. The method of claim 1, further comprising: prior to performing the secure erase operation, determining whether a variable is set to prevent the secure erase operation; andin accordance with a determination that the variable is set, preventing performance of the secure erase operation.

23. The method of claim 1, wherein signaling the secure erase condition to the plurality of hardware controllers on the memory device further comprises: signaling a first hardware controller of the plurality of hardware controllers to securely erase a first portion of the one or more non-volatile memory devices, andsignaling a second hardware controller of the plurality of hardware controllers to securely erase a second portion of the one or more non-volatile memory devices in parallel with the first hardware controller securely erasing the first portion of the one or more non-volatile memory devices.

24. The method of claim 1, wherein the non-volatile memory comprises one or more flash memory devices.

25. The method of claim 1, wherein the memory device includes a dual in-line memory module (DIMM) device.

26. A memory device, comprising: an interface for coupling the memory device to a host system;two or more controllers; andsecure erase circuitry including one or more processors, the secure erase circuitry configured to: detect a secure erase trigger;determine a secure erase algorithm from among a plurality of secure erase algorithms to use in accordance with the detected secure erase trigger;perform a secure erase operation in accordance with the determined secure erase algorithm, the secure erase operation including: signaling a secure erase condition to a plurality of the two or more controllers on the memory device;erasing, in parallel, two or more non-volatile memory devices on the memory device;monitoring the secure erase operation, wherein monitoring the secure erase operation includes monitoring a completion status of the secure erase operation; andbased on the monitoring, recording data related to the secure erase operation, the recorded data including data indicating the completion status of the secure erase operation.

27. The memory device of claim 26, wherein the plurality of controllers on the memory device include a storage controller and one or more flash controllers, the one or more flash controllers coupled by the storage controller to a host interface of the memory device.

28. The memory device of claim 26, wherein the interface for coupling the memory device to a host system comprises a double data rate (DDR) interface, and the secure erase signal from the host system is communicated to the memory device through the double data rate (DDR) interface.

29. The memory device of claim 26, wherein the plurality of secure erase algorithms include at least one algorithm to overwrite a storage medium with specific overwrite patterns and at least one algorithm other than an overwrite algorithm.

30. A non-transitory computer readable storage medium, storing one or more programs for execution by one or more hardware processors of a memory device having a plurality of hardware controllers and secure erase circuitry, the one or more programs including instructions for: detecting a secure erase trigger;determining a secure erase algorithm from among a plurality of secure erase algorithms to use in accordance with the detected secure erase trigger;performing a secure erase operation in accordance with the determined secure erase algorithm, the secure erase operation including: signaling a secure erase condition to the plurality of hardware controllers on the memory device;erasing, in parallel, two or more non-volatile memory devices on the memory device;monitoring the secure erase operation, wherein monitoring the secure erase operation includes monitoring a completion status of the secure erase operation; andbased on the monitoring, recording data related to the secure erase operation, the recorded data including data indicating the completion status of the secure erase operation.