Secure key update for replay of protected memory blocks
By introducing a secure key to modify firmware and configuration settings in the memory device, the problems of key mismatch and unauthorized modification are solved, and secure and effective key management is realized, ensuring the security and usage rights of the memory device.
Patent Information
- Application Number
- CN202011595178.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-12-30
- Filing Date
- 2020-12-29
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-12-29
AI Technical Summary
The prior art is difficult to modify the security key of a memory device in a secure and efficient manner, especially in cases where key mismatch may result in during manufacturing, and there is a risk of no authorization modification.
By introducing security key modification firmware into memory devices, enabling or disabling key modification features with configuration settings and operational metrics, ensuring that only authorized users can modify security keys and modify the combination of firmware and keys through custom firmware and keys , limit key replacement and erase operations.
It realizes the secure modification and locking of the security key in the memory device, prevents further modification, and ensures the control of the security and use permissions of the memory device.
Smart Images

Figure CN113126905B_ABST
Abstract
Description
[0001] Priority claim
[0002] This patent application claims priority under 35 USC Section 119 to U.S. Provisional Patent Application No. 62 / 955,135, filed by Cariello et al. on December 30, 2019, entitled "Configuring Access to Protected Memory," which is hereby incorporated herein by reference in its entirety. Technical Field
[0003] Embodiments relate to memory devices. Some embodiments relate to securely updating keys to access protected areas, such as replaying protected memory blocks. Background Art
[0004] Memory devices used in computers or other electronic devices can be classified as volatile and non-volatile memories. Volatile memory requires power to maintain the data stored on it. Volatile memory includes random access memory (RAM), dynamic random access memory (DRAM) or synchronous dynamic random access memory (SDRAM), etc. Non-volatile memory can retain stored data when not powered, and includes flash memory, read-only memory (ROM), electrically erasable programmable ROM (EEPROM), static RAM (SRAM), erasable programmable ROM (EPROM), resistance variable memory, phase change memory, storage class memory, resistance random access memory (RRAM) and magnetoresistive random access memory (MRAM), etc.
[0005] Flash memory is used as non-volatile memory for a wide range of electronic applications. A flash memory device typically includes one or more groups of transistors such as floating gate or charge trap memory cells that allow for high memory density, high reliability, and low power consumption. Summary of the invention
[0006] In one aspect, the present disclosure relates to a memory device, the memory device comprising: a memory array, the memory array comprising a plurality of memory cells, a portion of the memory array being a protected portion accessed using a security key; a controller, the controller being configured to perform operations including: receiving a request to set a configuration setting of the memory device to a first value; setting the configuration setting of the memory device to the first value; determining whether an operation metric is below a threshold; in response to setting the configuration setting of the memory device to the first value and determining that the operation metric is below the threshold, enabling a security key modification feature; receiving a request to modify the security key of the protected portion; in response to receiving the request, determining whether the security key modification feature is enabled; and in response to determining that the security key modification feature is enabled, modifying the security key of the protected portion.
[0007] In another aspect, the present disclosure relates to a method comprising: at a memory device: receiving a request to set a configuration setting of the memory device to a first value; setting the configuration setting of the memory device to the first value; determining whether an operating metric is below a threshold; in response to setting the configuration setting of the memory device to the first value and determining that the operating metric is below the threshold, enabling a security key modification feature; receiving a request to modify a security key of a protected portion of a memory array of the memory device; in response to receiving the request, determining whether the security key modification feature is enabled; and in response to determining that the security key modification feature is enabled, modifying the security key of the protected portion.
[0008] In yet another aspect, the present disclosure relates to a non-transitory machine-readable medium storing instructions that, when executed by a controller of a memory device, cause the memory device to perform operations including: receiving a request to set a configuration setting of the memory device to a first value; setting the configuration setting of the memory device to the first value; determining whether an operating metric is below a threshold; in response to setting the configuration setting of the memory device to the first value and determining that the operating metric is below the threshold, enabling a security key modification feature; receiving a request to modify a security key of a protected portion of a memory array of the memory device; in response to receiving the request, determining whether the security key modification feature is enabled; and in response to determining that the security key modification feature is enabled, modifying the security key of the protected portion. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] In the drawings, which are not necessarily drawn to scale, like reference numerals may describe similar components in different views. Like reference numerals with different letter suffixes may represent different instances of similar components. The drawings generally illustrate various embodiments discussed in this document by way of example and not limitation.
[0010] Figure 1 Diagrams showing memory devices, eg, storage devices, according to some examples of the present disclosure.
[0011] Figure 2 An example schematic diagram illustrating a portion of a NAND architecture semiconductor memory array according to some examples of the present disclosure.
[0012] Figure 3 An example schematic diagram showing a 3D NAND architecture semiconductor memory according to some examples of the present disclosure.
[0013] Figure 4 An example block diagram of a memory die according to some examples of the present disclosure is shown.
[0014] Figure 5 A first example flow for limiting unauthorized modification of security keys using matching operating firmware and key modification firmware according to some examples of the present disclosure is shown.
[0015] Figure 6 A flow chart illustrating a method of updating a security key of a protected portion of a memory device using matching firmware according to some examples of the present disclosure.
[0016] Figure 7 A first example process for limiting unauthorized modification of security keys using configuration settings according to some examples of the present disclosure is shown.
[0017] Figure 8 An example state transition diagram of a memory controller for controlling when and under what conditions key erase firmware is enabled is shown.
[0018] Fig. 9 A flow chart illustrating a method of enabling key modification firmware according to some examples of the present disclosure.
[0019] Fig.10 A flow chart illustrating a method of updating a security key of a protected portion of a memory device using a configuration value according to some examples of the present disclosure.
[0020] Fig.11 A block diagram illustrating an example machine upon which any one or more of the techniques (eg, methodologies) discussed herein may be performed. DETAILED DESCRIPTION
[0021] Memory devices such as flash memory devices can utilize "Replay Protected Memory Blocks" or RPMBs, which prevent memory access to certain memory addresses unless the requester provides the correct message authentication code (HMAC SHA-256) with the request. The message authentication code is calculated based on a cryptographically secure key as well as a write counter and a random number. The write counter and random number prevent replay attacks. During system manufacturing, the security key is programmed into the memory device and host for permanent coupling.
[0022] After the security keys are programmed in the memory device and the host device, manufacturing defects in the components of the host device may result in replacing or reworking one or more components on the host device. This may result in replacing the components on the memory device storing the security keys, or deleting the memory device and using it in another host device. In these cases, the host device and the memory device no longer have matching security keys. For security reasons, the Joint Electronics Engineering Council (JEDEC) does not allow the keys on the memory device to be replaced.
[0023] More generally, other types of protection schemes in addition to RPMB can also be used to protect access to one or more protected areas of the memory device, which may be different from the program and access control of the RPMB. These protection schemes also usually require the requester to provide a secret value to access (read, write and / or modify) these protected areas. Usually, the secret value is a security key or is calculated using a security key, which is programmed into the host and the memory device. These other schemes may also have similar problems in changing and replacing keys after manufacturing.
[0024] In some examples, methods, systems, memory devices, and machine-readable media are disclosed for providing a secure method of modifying, erasing, or updating security keys of protected areas of a memory device by using a special firmware object (key modification firmware) loaded into the memory device containing instructions to reprogram, modify, and / or erase the keys. To ensure that this key modification firmware does not become a security risk, the key modification firmware object can be protected in various ways so that it cannot be used subsequently.
[0025] In a first instance, a device or group of devices (e.g., devices provided to a host device by each original equipment manufacturer (OEM)) may have custom firmware objects specific to the device or group of devices. These custom firmware objects may be loaded by a memory device manufacturer or may be provided to a recipient of the device (e.g., an OEM) and loaded onto the memory device using a field firmware update (FFU) process performed by the recipient. These firmware objects may have corresponding custom key modification firmware objects that only work on the custom firmware objects provided for the device. The key modification firmware objects can then be used to clear, modify, and / or update security keys for protected areas (e.g., RPMB areas) of devices with matching custom firmware, but may not be used to clear, modify, and / or update security devices for other customers with different custom firmware.
[0026] In other instances, to prevent unauthorized use of special firmware objects, instead of coupling custom firmware objects and custom key modification firmware objects, a common firmware can be loaded to all memory devices. If a configuration variable of the memory device is set to a defined security key modification value before the operating metric of the memory device satisfies an enable lock condition (e.g., before the number of bytes written to the device exceeds a threshold), the memory device enables the key modification firmware object. As an example, if a defined string is written to the configuration variable before the device exceeds a specific number of bytes written (possibly zero bytes), the key modification firmware object is enabled. The key modification function can be disabled by modifying the configuration variable to another value. Since in some instances, the configuration variable must be set to a security key modification value before user data is written to the memory device, the key modification firmware cannot be enabled once the device is used.
[0027] This allows standard firmware objects to be used across groups of devices while providing OEM manufacturers with a way to control key modification functionality. In some instances, the configuration variable can be an "OEM string attribute" of a memory device defined by the JEDEC standard, which is typically set to a value indicating various device information, such as a vendor name that identifies the OEM. As previously described, as a prerequisite to allowing security keys to be updated, a custom key modification firmware object can verify that the configuration variable has been set to a specific pre-specified value before the operating metric satisfies the locking condition. The security key modification value is unique to a specific group of memory devices (e.g., the security key modification value may be unique to each OEM). If the security key modification value is compromised, this will only affect devices in the specific device group and only devices that were not locked prior to shipment to customers.
[0028] In addition to requiring that the security key modification value be set to the configuration setting before the operational measurement satisfies the lockout condition, the configuration setting can also be set to a different value and locked from further modification by locking the configuration mode. This prevents further modification of the configuration setting, thereby providing another layer of protection. As previously mentioned, to enable the key modification firmware, the configuration setting needs to be set to the security key modification value before the operational measurement satisfies the lockout condition. This prevents the manufacturer from neglecting to overwrite the configuration setting or neglecting to lock the configuration mode. For example, when the amount of data written is greater than zero. Therefore, even if the manufacturer does not touch the configuration value or lock the configuration, once the memory device is written, the security key cannot be changed, which is the case for most memory devices in the hands of end users.
[0029] In some examples, the value of the security key modification value may be different for each device (e.g., may be or include device-specific information such as a serial number); each host device OEM (e.g., may be or include an OEM-specific identifier); or a group of devices (e.g., may be or include a group-specific identifier). This may prevent the use of custom key modification firmware objects in different groups of devices, as each custom key modification firmware object may be decoded to find a different security key modification value.
[0030] In some instances, a manufacturer may load a custom key modification firmware object onto devices that need to update their security keys (e.g., using a field firmware update (FFU) process). In other instances, the key modification firmware may be loaded onto all devices by the memory device manufacturer.
[0031] The above technology provides a secure method for replacing security keys by authorized users by ensuring that the security keys can be modified and then locked to prevent further modification. The technical problem of modifying security keys in a secure manner is solved using a technical solution that protects the ability to modify firmware objects using matching firmware and keys or to modify security keys using configuration settings and operational metrics.
[0032] Memory Device Overview
[0033] As previously mentioned, flash memory is used as non-volatile memory for a wide range of electronic applications. Flash memory typically includes one or more groups of transistors such as floating gate or charge trap memory cells that allow high memory density, high reliability, and low power consumption. Two common types of flash memory array architectures include NAND and NOR architectures, named after the logical form in which the basic memory cell configuration of each is arranged. The memory cells of a memory array are typically arranged in a matrix. In an example, the gate of each memory cell in a row of the array is coupled to an access line (e.g., a word line). In a NOR architecture, the drain of each memory cell in a column of the array is coupled to a data line (e.g., a bit line). In a NAND architecture, the drain of each memory cell in a string of the array is coupled in series between a source line and a bit line in a source-to-drain manner.
[0034] Both NOR and NAND architecture semiconductor memory arrays are accessed through a decoder that activates a particular memory cell by selecting a word line coupled to the gate of the particular memory cell. In a NOR architecture semiconductor memory array, once activated, the selected memory cell places its data value on the bit line, causing different currents to flow depending on the state of the particular cell being programmed. In a NAND architecture semiconductor memory array, a high bias voltage is applied to the drain side select gate (SGD) line. The word line coupled to the gates of the unselected memory cells of each group is driven with a specified pass voltage (e.g., Vpass) to cause the unselected memory cells of each group to operate as pass transistors (e.g., pass current in a manner that is not limited by the data values they store). Current then flows from the source line through each series-coupled group to the bit line, limited only by the selected memory cell in each group, causing the currently encoded data value of the selected memory cell to be placed on the bit line.
[0035] Flash memory cells in NOR or NAND architecture semiconductor memory arrays can be programmed individually or collectively to one or more programmed states. For example, a single-level cell (SLC) can represent one of two programmed states (e.g., 1 or 0), representing one data bit. However, a flash memory cell can also represent one of more than two programmed states, allowing the manufacture of higher density memories without increasing the number of memory cells because each cell can represent more than one binary digit (e.g., more than one bit). Such cells may be referred to as multi-state memory cells, majority bit cells, or multi-level cells (MLC). In some instances, an MLC may refer to a memory cell that can store two data bits per cell (e.g., one of four programmed states), a three-level cell (TLC) may refer to a memory cell that can store three data bits per cell (e.g., one of eight programmed states), and a quad-level cell (QLC) can store four data bits per cell. MLC is used herein in its broad context to refer to any memory cell that can store more than one data bit per cell (i.e., can represent more than two programmed states).
[0036] Conventional memory arrays are two-dimensional (2D) structures arranged on the surface of a semiconductor substrate. In order to increase memory capacity and reduce cost for a given area, the size of individual memory cells has been reduced. However, there are technical limitations to the reduction in size of individual memory cells, and therefore there are technical limitations to the memory density of 2D memory arrays. In response, three-dimensional (3D) memory structures, such as 3D NAND architecture semiconductor memory devices, are being developed to further increase memory density and reduce memory cost.
[0037] Such 3D NAND devices typically include a string of memory cells coupled in series (e.g., drain to source) between one or more source-side select gates (SGS) near the source and one or more drain-side select gates (SGD) near the bit line. In an example, the SGS or SGD may include one or more field effect transistors (FETs) or metal-oxide semiconductor (MOS) structure devices, among others. In some examples, the string will extend vertically through multiple vertically spaced levels containing corresponding word lines. A semiconductor structure (e.g., a polysilicon structure) may extend adjacent to the string of memory cells to form a channel for the memory cells in the string. In the example of a vertical string, the polysilicon structure may be in the form of a vertically extending column. In some examples, the string may be "folded" and thus arranged relative to a U-shaped column. In other examples, multiple vertical structures may be stacked on top of each other to form a stacked array of memory cell strings.
[0038] The memory arrays or devices may be combined together to form a memory bank of a memory system, such as a solid state drive (SSD) or one of various forms of managed memory devices. The managed memory devices may be configured and operated in accordance with recognized industry standards. For example, the managed NAND device may be, as a non-limiting example, a Universal Flash Storage (UFS) TM ) device or embedded MMC device (eMMC TM ) and so on. For example, in the case of the above example, the UFS device may be configured according to the Joint Electronic Device Engineering Council (JEDEC) standard named "JEDEC UFS Flash Storage 3.0" and / or an updated or subsequent version of such a standard, such as JEDEC standard JESD223D. Similarly, the identified eMMC device may also be configured according to the JEDEC standard JESD84-A51 named "JEDEC eMMC Standard 5.1" and / or an updated or subsequent version of such a standard.
[0039] SSDs are particularly useful as primary storage devices for computers, having advantages over traditional hard disk drives with moving parts with respect to, for example, performance, size, weight, ruggedness, operating temperature range, and power consumption. For example, an SSD may have reduced seek times, latency, or other delays (e.g., electromechanical, etc.) associated with magnetic disk drives. An SSD uses non-volatile memory cells, such as flash memory cells, to avoid internal battery power requirements, thereby allowing the drive to be more versatile and compact.
[0040] An SSD may include several memory devices, including several dies or logical units (e.g., logical unit numbers or LUNs), and may include one or more processors or other controllers that perform the logic functions required to operate the memory devices or interface with external systems. These SSDs may include one or more flash memory dies that include several memory arrays and peripheral circuitry on these dies. The flash memory array may include several blocks of memory cells organized into several physical pages. In many instances, the SSD will also include DRAM or SRAM (or other forms of memory dies or other memory structures). The SSD may receive commands from the host in conjunction with memory operations, such as read or write operations to transfer data (e.g., user data and associated integrity data, such as error data and address data, etc.) between the memory device and the host, or erase operations to erase data from the memory device.
[0041] A memory device includes a separate memory die that implements one (or more) selected storage technologies, which memory die may, for example, include a storage area including one or more memory cell arrays. Such memory die typically includes support circuitry for operating the memory array. Other examples, sometimes collectively referred to as "managed memory devices," include an assembly of one or more memory dies associated with a controller functionality configured to control the operation of the one or more memory dies. Such controller functionality can simplify interoperability with external devices such as a "host" discussed later herein. In such managed memory devices, the controller functionality can be implemented on one or more dies that also incorporate a memory array or on a separate die. In other examples, one or more memory devices can be combined with controller functionality to form a solid-state drive (SSD) storage body. The term "memory system" is used herein to include one or more memory dies and any controller functionality (if present) for such memory dies; and therefore includes separate memory devices, managed memory devices, and SSDs.
[0042] For purposes of the present invention, example embodiments include managed memory devices implementing NAND flash memory cells, referred to as "managed NAND" devices. Such managed NAND devices may be generally constructed and operated in accordance with the described JEDEC UFS Flash Storage 3.0 specification, and may be modified as necessary to incorporate the structure and functionality described herein. However, the described functionality may be implemented with other types of memory devices described above, which may incorporate other storage technologies, several non-limiting examples of which have been discussed earlier herein; and may be configured for operation in accordance with other industry standards discussed above or in accordance with non-industry standard protocols.
[0043] Electronic devices such as mobile electronic devices (e.g., smart phones, tablet computers, etc.), electronic devices for automotive applications (e.g., automotive sensors, control units, driver assistance systems, passenger safety or comfort systems, etc.), and Internet-connected electrical equipment or devices (e.g., Internet of Things (IoT) devices, etc.) have different storage needs, especially depending on the type of electronic device, usage environment, performance expectations, etc.
[0044] An electronic device can be broken down into several major components: a processor (e.g., a central processing unit (CPU) or another host processor); a memory (e.g., one or more volatile or non-volatile random access memory (RAM) memory devices, such as dynamic RAM (DRAM), mobile or low-power double data rate synchronous DRAM (DDR SDRAM), etc.); and a storage device (e.g., a non-volatile memory (NVM) device, such as flash memory, read-only memory (ROM), SSD, MMC, or another memory card structure or assembly, etc.). In some examples, the electronic device may include a user interface (e.g., a display, a touch screen, a keyboard, one or more buttons, etc.), a graphics processing unit (GPU), a power management circuit, a baseband processor, or one or more transceiver circuits, etc.
[0045] Figure 1 A diagram of a memory device 100, such as a storage device, according to some examples of the present disclosure is shown. The memory device 100 may include one or more host interfaces 123, which may utilize one or more protocols, such as a Serial Advanced Technology Attachment (SATA) interface, a Peripheral Component Interconnect Express (PCIe) interface, a Universal Serial Bus (USB) interface, a Universal Flash Storage (UFS) interface, an eMMC interface, or a SATA-based host interface. TM The memory device 100 may include a host bus 137, a host interface 123, or one or more other connectors or interfaces to communicate with the host device 135. The host 135 may send one or more commands, such as a read command, a write command, an erase command, etc., to the memory device 100 through the host interface 123. The host interface 123 may be part of the controller 105, or may be implemented by a separate circuit system. The memory device 100 may send data, commands, responses, etc. to the host device 135 via the host interface through the host bus 137.
[0046] Memory device 100 may include one or more memory controllers 105. Controller 105 may include processing circuitry 110, which may include one or more hardware processors 115. Processor 115 may be a general purpose hardware processor that executes firmware or other software instructions to perform operations of the memory device, including implementing host interface 123, protected region logic 122, and memory die interface 125. In other examples, processor 115 may be a dedicated hardware processor specifically designed to perform operations of memory device 100 through hardware logic and / or by executing software instructions. Processing circuitry 110 may also include logic circuits and other circuit components, or portions thereof, configured to perform various control functionality and memory management operations, examples of which are described below.
[0047] In the depicted example, the memory device 100 includes a host interface 123 that provides communications to an external host device 135 through a host bus 137. Depending on the particular configuration of the memory device 100 (which may also be referred to as a "memory system"), the configuration of the host interface 123 may have various forms. For example, in an example where the memory device 100 is a UFS device, the host interface will conform to the applicable UFS standard.
[0048] The memory device 100 also has one or more memory die interfaces 125 between the processing circuitry 110 of the controller 105 and at least some portion of the memory dies 130-A-130N+1 within the memory device 100. The memory die interfaces 125 may be part of the controller 105, or may be implemented by separate circuitry. For example, in the example of a UFS device, one or more of the memory die interfaces 125 would be a suitable memory interface, such as the Open NAND Flash Interface ("ONFI"), such as defined by the ONFI 4.0 specification or subsequent versions or revisions thereof.
[0049] Components of the memory device 100, such as the controller 105, may include a random access memory (RAM) 120 for performing operations of the memory device 100. The random access memory 120 may be separate from the controller 105 or, as shown, may be integrated into the controller 105.
[0050] The controller 105 may handle one or more functions of the memory by interacting with memory cells in the memory device that are part of one or more memory dies 130-A-130N+1. Figure 4 1 shows a schematic diagram of an example implementation of a memory die 130. The controller 105 can communicate with these memory dies through a memory die interface 125 across a memory die bus 127. In some examples, the memory die may have its own device controller, including a processing circuit system and a processor to control operations on the corresponding memory die. Such a device controller can be formed on a common die with the device storage array, or can be on a die separate from the die containing the device storage array. Both configurations are covered by the identified "memory die" (130A-N+1) described herein. The memory die can be a NAND die, a three-dimensional NAND die, a phase change memory die, and the like.
[0051] Host device 135 may be a personal computer, a smartphone, a tablet computer, part of an integrated circuit, an Internet of Things (IoT) device (e.g., a refrigerator or other appliance, a sensor, a motor or actuator, a mobile communication device, a car, a drone, etc.), etc.
[0052] For purposes of this description, example memory operation and management functions may be described in the context of NAND memory. Those skilled in the art will recognize that other forms of non-volatile memory may have similar memory operation or management functions. Such NAND management functions include wear leveling (e.g., garbage collection or recycling), error detection or correction, block deregistration, or one or more other memory management functions.
[0053] The memory die 130-A-130-N+1 may include a number of memory cells arranged in, for example, multiple planes, sub-blocks, blocks, or pages. As an example, a 48GB TLC NAND memory device may include 18,592 bytes (B) (16,384+2208 bytes) of data per page, 1536 pages per block, 548 blocks per plane, and 4 or more planes per device. As another example, a 32GB MLC memory device (storing two data bits per cell (i.e., 4 programmable states)) may include 18,592 bytes (B) (16,384+2208 bytes) of data per page, 1024 pages per block, 548 blocks per plane, and 4 planes per device, but with half the write time and twice the code / erase (P / E) cycles as compared to a corresponding TLC memory device. Other examples may include other numbers or arrangements. In some examples, a memory device or portion thereof may be selectively operated in an SLC mode or in a desired MLC mode (eg, TLC, QLC, etc.). Figure 2-3 Example arrangements of memory cells are shown and described.
[0054] In operation, data is typically written to or read from the memory device 100 in pages and erased in blocks. However, one or more memory operations (e.g., read, write, erase, etc.) may be performed on larger or smaller groups of memory cells as desired. The data transfer size of the memory device 100 is typically referred to as a page, while the data transfer size of the host is typically referred to as a sector.
[0055] Although a data page may include several bytes of user data (e.g., a data payload including several data sectors) and its corresponding metadata, the size of a page often refers only to the number of bytes used to store the user data. As an example, a data page with a page size of 4KB may include 4KB of user data (e.g., 8 sectors assuming a sector size of 512B) and metadata corresponding to several bytes of user data (e.g., 32B, 54B, 224B, etc.), such as integrity data (e.g., error detection or correction code data), address data (e.g., logical address data, etc.), or other metadata associated with the user data.
[0056] Different types of memory cells may provide different page sizes, or may require different amounts of metadata associated therewith. For example, different memory device types may have different bit error rates, which may result in different amounts of metadata being required to ensure the integrity of a page of data (e.g., a memory device with a higher bit error rate may require more bytes of error correction code data than a memory device with a lower bit error rate). As an example, a multi-level cell (MLC) NAND flash device may have a higher bit error rate than a corresponding single-level cell (SLC) NAND flash device. Therefore, an MLC device may require more bytes of metadata for error data than a corresponding SLC device.
[0057] One or more memory cells of the memory die 130 may be protected regions that require authentication for access. As mentioned, authentication may be performed by providing a secret value along with a request to access one or more memory cells in the protected region. The protected region logic 122 implements access protection for one or more protected storage regions provided by the memory die 130A-N+1 (e.g., RPMB). The protected region logic 122 may verify that the request to access the protected region has been authenticated. The protected region logic 122 may receive a protected region access request and may verify that the secret (e.g., MAC value) contained in the request is correct, for example, by using a stored copy of a security key.
[0058] The security key may be stored in a location in a memory die 130A-N+1 or a special memory chip within the memory device 100. The protected area logic 122 may include instructions for replacing or modifying the key contained in a key modification firmware object. Whether this functionality is enabled may depend on one or more configuration settings, operating metrics, and enable lock conditions (e.g., thresholds) or the presence of compatible generic firmware. These configuration settings, operating metrics, and enable lock conditions may be encoded into the key modification firmware object, may be stored in memory cells of the memory die 130A-N+1, or may be stored in other memory (e.g., static memory) of the memory device. For example, the protected area logic 122 may implement Figure 6 and 9 Flowchart of Figure 8 As mentioned, the protected area logic 122 may include instructions provided by conventional firmware objects and / or key modification firmware objects. The protected area logic 122 may implement the RPMB process documented by one or more standards such as the JEDEC standard.
[0059] The host 135 may also have a host protected region logic 138 that may implement instructions for the host 135 to send access requests requesting reads, writes, and other operations on protected memory regions. The host protected region logic 138 may format requests for protected memory regions (e.g., RPMB requests in accordance with the JEDEC standard), including placing secret values in the requests (e.g., by calculating a MAC based on a security key stored on the host). The host protected region logic 138 may also perform one or more operations requesting the setting of one or more configuration settings on the memory device 100, including configuration settings that enable security key replacement. In addition, the host protected region logic 138 may have logic for replacing, erasing, or otherwise changing security keys by communicating with the protected region logic 122 (e.g., through request messages and reply messages).
[0060] Figure 2 An example schematic diagram of a portion of a NAND architecture semiconductor memory array 200 is shown, according to some examples of the present disclosure, the array including a plurality of memory cells 302 arranged in a two-dimensional array of strings (e.g., strings 205-207) and levels (e.g., shown as respective word lines (WL) WL0-WL7 210-217, drain side select gate (SGD) lines 225, source side select gate (SGS) lines 230, etc.) and a sense amplifier or device 260. The memory array 200 may be shown Figure 1 An example schematic diagram of a portion of a physical page of a memory die in FIG.
[0061] Each memory cell string is coupled to a source line (SRC) 235 using a respective source side select gate (SGS) (e.g., SGS 231-233) and to a respective data line (e.g., bit lines (BL) BL0-BL2 220-222) using a respective drain side select gate (SGD) (e.g., SGD 226-228). Figure 2 The example is shown as having eight levels (eg, using word lines (WL) WL0-WL7 210-217) and three data lines (BL0-BL2 226-228), but other examples may include memory cell strings having more or fewer levels or data lines as desired.
[0062] In a NAND architecture semiconductor memory array such as the example memory array 200, the state of a selected memory cell 202 may be accessed by sensing a current or voltage change associated with a particular data line containing the selected memory cell. The memory array 200 may be accessed using one or more drivers (e.g., by control circuitry, one or more processors, digital logic, etc.). In an example, the one or more drivers may activate a particular memory cell or set of memory cells by driving a particular potential to one or more data lines (e.g., bit lines BL0-BL2), access lines (e.g., word lines WL0-WL7), or select gates, depending on the type of desired operation to be performed on the particular memory cell or set of memory cells.
[0063] To program or write data to a memory cell, a programming voltage (Vpgm) (e.g., one or more programming pulses, etc.) may be applied to a selected word line (e.g., WL4), and thus to the control gate of each memory cell coupled to the selected word line (e.g., control gates (CG) 241-243 of the memory cells coupled to WL4). The programming pulses may start, for example, at or near 15V, and in certain examples may increase in magnitude during each programming pulse application. While the programming voltage is applied to the selected word line, a potential, such as a ground potential (e.g., Vss), may be applied to the data line (e.g., bit line) and substrate (and thus the channel between the source and drain) of the memory cell targeted for programming, resulting in charge transfer (e.g., direct injection or Fowler-Nordheim (FN) tunneling, etc.) from the channel to the charge storage structure of the target memory cell. Such a charge storage structure may include, for example, a floating gate or charge trap region of the respective memory cell. In a floating gate memory cell, charge is stored in an isolating polysilicon structure; whereas in a charge trap memory cell, charge is typically stored in a dielectric structure.
[0064] In contrast, a pass voltage (Vpass) may be applied to one or more word lines having memory cells that are not targeted for programming, or an inhibit voltage (e.g., Vcc) may be applied to data lines (e.g., bit lines) having memory cells that are not targeted for programming, for example, to inhibit charge from being transferred from the channel to the charge storage structure of these non-target memory cells. The pass voltage may vary, for example, depending on the proximity of the applied pass voltage to the word lines targeted for programming. The inhibit voltage may include a supply voltage (Vcc) relative to a ground potential (e.g., Vss), such as a voltage from an external source or supply (e.g., a battery, an AC / DC converter, etc.).
[0065] As an example, if a programming voltage (e.g., 15V or higher) is applied to a particular word line, such as WL4, a pass voltage of 10V may be applied to one or more other word lines, such as WL3, WL5, etc., to inhibit programming of non-target memory cells, or to maintain the values stored on these memory cells that are not targeted for programming. As the distance between the applied programming voltage and the non-target memory cells increases, the pass voltage required to inhibit programming of the non-target memory cells may decrease. For example, with a 15V programming voltage applied to WL4, a pass voltage of 10V may be applied to WL3 and WL5, a pass voltage of 8V may be applied to WL2 and WL6, a pass voltage of 7V may be applied to WL1 and WL7, etc. In other examples, the pass voltage or number of word lines, etc. may be higher or lower, or more or less.
[0066] A sense amplifier 260 coupled to one or more of the data lines (eg, first, second, or third bit lines (BL0-BL2) 220-222) can detect the state of each memory cell 202 in the corresponding data line by sensing the voltage or current on the particular data line.
[0067] Between the application of one or more programming pulses (e.g., Vpgm), a verify operation may be performed to determine whether the selected memory cells have reached their intended programmed states. If the selected memory cells have reached their intended programmed states, they may be inhibited from further programming. If the selected memory cells have not reached their intended programmed states, additional programming pulses may be applied. If the selected memory cells have not reached their intended programmed states after a certain number of programming pulses (e.g., a maximum number), the selected memory cells or strings, blocks, or pages associated with these selected memory cells may be marked as defective.
[0068] For a single-level cell (SLC), there are two possible voltage levels programmed into the cell, one voltage level representing a binary '1' and the other voltage level representing a binary '0'. For a multi-level cell (MLC), there are four possible voltage levels programmed into the cell. These four possible voltage levels represent '00', '01', '10', and '11'. To program an MLC cell, multiple programming pulses are applied. The first pulse programs a first "page" of data representing either the most significant bit or the least significant bit of the cell. The second pulse programs a second "page" of data representing the other bits in the cell that were not programmed by the first pulse. Similarly, a three-level cell (TLC) stores eight possible voltage levels, and a quad-level cell (QLC) stores 16 possible voltage levels.
[0069] To read the value stored in one or more memory cells, a read voltage is applied to the word line of the selected cell. If the voltage stored in the cell of the word line is greater than the read voltage, the cell passes a voltage to the sense amplifier. For SLC cells, the read voltage is selected between two voltages representing '1' and '0'. For MLC, TLC, and QLC, multiple read operations are used to read each bit stored in the cell - each read operation utilizing a different read voltage.
[0070] To erase a memory cell or group of memory cells (e.g., erasure is typically performed in blocks or sub-blocks), an erase voltage (Vers) may be applied (e.g., using one or more bit lines, select gates, etc.) to the substrate (and therefore the channel between the source and drain) of the memory cell targeted for erasure while the word line of the target memory cell is maintained at a potential such as ground potential (e.g., Vss), thereby causing charge transfer (e.g., direct injection or Fowler-Nordheim (FN) tunneling, etc.) from the charge storage structure of the target memory cell to the channel.
[0071] Figure 3 The diagram shows a block structure organized into blocks (e.g., block A 301A, block B 301B, etc.) and sub-blocks (e.g., sub-block A 301A, block B 301B, etc.). 0 301A 0 , sub-block A n 301A n , sub-block B 0 301B 0 , sub-block B n 301B n etc.) of a plurality of memory cell strings (e.g., A 0 Memory string 305A 0 -307A 0 , A n Memory string 305A n -307A n , B 0 Memory string 305B 0 -307B 0 , B n Memory string 305B n -307B n 3D NAND architecture semiconductor memory array 300 is an example schematic diagram of a 3D NAND architecture semiconductor memory array 300 having a plurality of 3D NAND structures. The memory array 300 represents a portion of a larger number of similar structures typically found in a block, device, or other unit of a memory device. The memory array 300 may show components Figure 1 0 is an example schematic diagram of a portion of a memory cell of a memory die 130 in FIG.
[0072] Each memory cell string includes a source line (SRC) 335 or a source side select gate (SGS) (eg, A) stacked in a source-to-drain manner in the Z direction. 0 SGS 331A 0 -333A 0 , A n SGS 331A n -333A n , B 0 SGS 331B 0 -333B 0 , B n SGS 231B n -233B n etc.) and the drain side select gate (SGD) (e.g., A 0 SGD 326A 0 -328A 0 , A n SGD 326A n -328A n , B 0 SGD 326B 0 -328B 0 , B n SGD 326B n -328B n Each memory cell string in the 3D memory array may be arranged as a data line (e.g., bit lines (BL) BL0-BL2 320-322) along the X direction and may be arranged as a physical page along the Y direction.
[0073] Within a physical page, each level represents a row of memory cells, and each string of memory cells represents a column. A sub-block may include one or more physical pages. A block may include multiple sub-blocks (or physical pages) (e.g., 128, 256, 384, etc.). Although shown herein as having two blocks, each block having two sub-blocks, each sub-block having a single physical page, each physical page having three strings of memory cells, and each string having 8 levels of memory cells, in other examples, the memory array 300 may include more or fewer blocks, sub-blocks, physical pages, strings of memory cells, memory cells, or levels. For example, each string of memory cells may include more or fewer levels (e.g., 16, 32, 64, 128, etc.) as desired, as well as one or more additional levels of semiconductor material above or below the charge storage transistors (e.g., select gates, data lines, etc.). As an example, a 48GB TLC NAND memory device may include 18,592 bytes (B) (16,384 + 2208 bytes) of data per page, 1536 pages per block, 548 blocks per plane, and 4 or more planes per device.
[0074] Each memory cell in the memory array 300 includes a memory cell coupled to (eg, electrically or otherwise operably connected to) an access line (eg, a word line (WL) WL0). 0 -WL7 0 310A-317A, WL0 1 -WL7 1 310B-317B, etc.), which are coupled together across a particular level or portion of a level as needed. A particular level in a 3D memory array, and a particular memory cell in a corresponding string, can be accessed or controlled using a corresponding access line. Groups of select gates can be accessed using various select lines. For example, A 0 SGD 326A 0 -328A 0 You can use A 0 SGD LineSGDA 0 325A 0 Access, A n SGD 326A n -328A n You can use the SGD line SGDA n 325A n Access, B 0 SGD 326B 0 -328B 0 You can use B 0 SGD LineSGDB 0 325B 0 Access, and B nSGD 326B n -328B n You can use B n SGD LineSGDB n 325B n Access. 0 SGS 331A 0 -333A 0 and A n SGS 331A n -333A n The gate selection line SGS can be used 0 330A access, and B 0 SGS 331B 0 -333B 0 and B n SGS 331B n -333B n The gate selection line SGS can be used 1 330B access.
[0075] In an example, the memory array 300 may include several levels of semiconductor material (e.g., polysilicon, etc.) configured to couple a control gate (CG) or select gate (or a portion of a CG or select gate) of each memory cell of a corresponding level of the array. A particular string of memory cells in the array may be accessed, selected, or controlled using a combination of a bit line (BL) and a select gate, etc., and a particular memory cell at one or more levels in a particular string may be accessed, selected, or controlled using one or more access lines (e.g., word lines).
[0076] Figure 4 An example block diagram of a memory die 400 according to some examples of the present disclosure is shown. The memory die 400 may be Figure 1 4. The memory die 400 may include a memory array 402 having a plurality of memory cells 404, and one or more circuits or components for providing communication with or performing one or more memory operations on the memory array 402. The memory die 400 may include a row decoder 412, a column decoder 414, a sense amplifier 420, a page buffer 422, a selector 424, an input / output (I / O) circuit 426, and a dedicated memory controller in the form of a memory control unit 430 that includes processing circuitry, possibly including one or more processors, as described earlier herein.
[0077] The memory cells 404 of the memory array 402 may be arranged in blocks, such as a first block 402A and a second block 402B. Each block may include sub-blocks. For example, the first block 402A may include a first sub-block 402A. 0 and the second sub-block 402A n , and the second block 402B may include the first sub-block 402B 0 and the second sub-block 402B n Each sub-block may include a number of physical pages, each page including a number of memory cells 404. Although shown herein as having two blocks, each block having two sub-blocks, and each sub-block having a number of memory cells 404, in other examples, the memory array 402 may include more or fewer blocks, sub-blocks, memory cells, etc. In other examples, the memory cells 404 may be arranged in a number of rows, columns, pages, sub-blocks, blocks, etc., and accessed using, for example, an access line 406, a first data line 410, or one or more select gates, source lines, etc.
[0078] The memory control unit 430 may be configured to control the memory interface (eg, Figure 1 One or more signals and / or instructions / commands received on control lines 432 (described in detail in the memory device 100 of the present invention) control the memory operations of the memory die 400. Such signals may include, for example, one or more clock signals or control signals indicating the desired operation (e.g., write, read, erase, etc.), or address signals (A0-AX) received on one or more address lines 416. One or more devices external to the memory die 400 may control the value of the control signals on the control lines 432 or the address signals on the address lines 416. Examples of devices external to the memory die 400 may include, but are not limited to, a host, a memory controller, a processor, or Figure 4 One or more circuits or components not shown.
[0079] The memory die 400 may use the access lines 406 and the first data lines 410 to transfer data to (e.g., write or erase) or from (e.g., read) one or more of the memory cells 404. The row decoder 412 and the column decoder 414 may receive and decode address signals (A0-AX) from the address lines 416, may determine which of the memory cells 404 are to be accessed, and may provide signals to one or more of the access lines 406 (e.g., one or more of the plurality of word lines (WL0-WLm)) or the first data lines 410 (e.g., one or more of the plurality of bit lines (BL0-BLn)), such as those described above.
[0080] The memory die 400 may include sensing circuitry, such as sense amplifiers 420, configured to determine the value of data on the memory cell 404 (e.g., read) using the first data line 410, or to determine the value of data to be written to the memory cell 404. For example, in a selected string of memory cells 404, one or more of the sense amplifiers 420 may read the logic level in the selected memory cell 404 in response to a read current flowing in the memory array 402 through the selected string to the data line 410.
[0081] One or more devices external to the memory die 400 (e.g., the controller 105) may communicate with the memory die 400 using the I / O lines (DQ0-DQN) 408, the address lines 416 (A0-AX), or the control lines 432. The input / output (I / O) circuits 426 may transfer values of data into and out of the memory die 400, such as into and out of the page buffers 422 or the memory array 402, using the I / O lines 408 according to, for example, the control lines 432 and the address lines 416. The page buffers 422 may store data received from one or more devices external to the memory die 400 and then program the data into the relevant portion of the memory array 402, or may store data read from the memory array 402 and then transmit the data to one or more devices external to the memory die 400.
[0082] The column decoder 414 may receive and decode the address signals (A0-AX) into one or more column select signals (CSEL1-CSELn). A selector 424 (e.g., a selection circuit) may receive the column select signals (CSEL1-CSELn) and select data in the page buffer 422 that represents a data value to be read from or programmed into the memory cell 404. The selected data may be transferred between the page buffer 422 and the I / O circuit 426 using the second data line 418. In some examples, a flash translation layer (not shown) may map addresses provided by the host to physical memory addresses used by the row decoder 412 and the column decoder 414 to read data in the memory array 402.
[0083] The memory control unit 430 may receive positive and negative supply signals, such as a supply voltage (Vcc) 434 and a negative supply (Vss) 436 (e.g., ground potential) from an external source or supply (e.g., an internal or external battery, an AC / DC converter, etc.). In some examples, the memory control unit 430 may include a regulator 428 to internally provide the positive or negative supply signals.
[0084] The memory control unit 430 may utilize random access memory (RAM), such as SRAM 431, to assist in executing operations to control memory operations of the memory die 400. For example, the SRAM 431 may store one or more instructions, working values, and other calculations. The memory control unit 430 may execute a software instruction set, such as microcode, which may reside in whole or in part on the SRAM 431, within the memory control unit 430 (e.g., in a dedicated register, ROM, flash, or other dedicated memory), within one or more memory cells (e.g., memory cell 404), etc. The SRAM 431 may store one or more page buffers used by the memory control unit 430 to temporarily store data read from or written to a memory cell (e.g., memory cell 404).
[0085] Key replacement
[0086] As mentioned, an OEM or otherwise authorized user of a host device may wish to reset (e.g., erase, wipe, and / or reprogram) security keys so that defects in circuit boards or other components can be reworked. Memory device manufacturers may provide specialized key modification firmware to OEM customers and other authorized users to erase keys. These firmware objects may be loaded onto memory devices via mechanisms such as field firmware updates (FFU) mechanisms. As previously described, this key modification firmware may become a security risk if an unauthorized user is able to access the key modification firmware and use it to place malware on an adversary's memory device, impersonate a security key, or perform other malicious actions.
[0087] As mentioned previously, one way to avoid such security risks is to create a unique manufacturing and key modification firmware pair for each customer. Each customer may have a specific operating firmware object and a paired key modification firmware. The key modification firmware only modifies the security keys on devices with matching operating firmware. Therefore, a leak of the key modification firmware of a first OEM will not affect a second OEM. This increases the cost and complexity of manufacturing memory devices because each custom operating firmware needs to be loaded by the memory device manufacturer. In some instances, to alleviate this burden, the memory device manufacturer can load a generic operating firmware. The custom operating firmware can then be provided to and loaded by the customer OEM using a field firmware update (FFU) process.
[0088] Figure 5 A first example process 500 is shown for limiting unauthorized modification of security keys using matching operating firmware and key modification firmware according to some examples of the present disclosure. The example process 500 utilizes a FFU update process to load custom operating firmware and key modification firmware onto a memory device.
[0089] Process 500 may be implemented by a memory device manufacturer 505, an OEM, or other authorized user. Although some organizations (e.g., memory device manufacturers, OEMs, device groups, etc.) Figure 5 , but those skilled in the art will appreciate that other organizations may also perform Figure 5 In example flow 500, a generic manufacturing firmware object is loaded into memory device 510. The generic manufacturing firmware object is configured for provision to multiple customers, represented as a first group 540 and a second group 570. Groups 540 and 570 represent other logical groupings of OEM customers or devices (e.g., device versions, distribution regions, etc.).
[0090] The example process 500 further includes providing customized firmware to customers who need specialized features or key modification functionality. For example, a first customized firmware object can be provided 515 to a first group 540, and a second customized firmware object can be provided 530 to a second group 570, so that each of the first group 540 and the second group 570 can implement customer-specific features. In some examples, the firmware objects can be transmitted from one entity to another entity, such as over a computer network.
[0091] The first custom firmware object may be loaded (e.g., via the first group 540) to those memory devices using field firmware update (FFU) techniques 545. This results in a memory device 547 having the first custom firmware. The second custom firmware object may be loaded (e.g., via the second group 570) using field firmware update (FFU) techniques 575. This results in a memory device 577 having the second custom firmware. If a key erase firmware is to be provided for secure key erase, a first custom key modification firmware may be provided 520, which may be loaded to the memory device (e.g., via the first group 540) using the FFU process 560 to produce a memory device 562 having the first custom firmware and the first key modification firmware. The FFU process 560 may load the custom key modification firmware onto the memory device without overwriting the first custom firmware object. A second custom key modification firmware may be provided 535, which may be loaded to the memory device of the second group 570 using the FFU technique 590 (e.g., via the second group 570) to produce a memory device 592 having the second custom firmware and the second key modification firmware.
[0092] Then, the user can modify one or more security keys of one or more protected areas using the custom key modification firmware. In some examples, the custom key modification firmware can be deleted from the memory device once the key is modified.
[0093] In some examples, the first customized firmware object and the second customized firmware object can be further customized using configuration settings on the memory device. For example, the OEM string value can be set to a specific value. The firmware can read this value to determine one or more settings and / or customized operating parameters of the memory device.
[0094] Figure 6 A flow chart illustrating a method 600 of updating security keys of protected portions of a memory device using matching firmware according to some examples of the present disclosure. Prior to executing the method 600, a custom key modification firmware is loaded to the memory device using an FFU process. At operation 610, the memory device receives a request to modify one or more security keys of one or more protected regions. At operation 615, the memory device may determine whether the key modification firmware matches the execution firmware.
[0095] In some instances, operation 615 is performed by the FFU when attempting to load the key modification firmware. In these instances, if the key modification firmware does not match the operating firmware, then the FFU process may not load the key modification firmware to the memory device. If the key modification firmware matches the operating firmware, then the security key may be modified at 620. In some instances, the match is checked based on one or more firmware versions—for example, the key modification firmware checks the firmware version of the operating firmware. In other instances, the key modification firmware checks a hash of the operating firmware, the size of the operating firmware, a value stored within the operating firmware, and the like.
[0096] Modifying the security key 620 may include erasing the security key 625 and / or replacing the security key 630. If the key modification firmware does not match the operating firmware, then at operation 640, the security key is not modified. This may include rejecting the request or taking no action on the request. In some examples, one or more operations in method 600 are performed by the key modification firmware and / or the operating firmware. As mentioned, in some examples, operation 615 may be performed during FFU. In these examples, the activated and / or loaded key modification firmware may respond to the request by modifying the security key 620.
[0097] Figure 5 and 6 The example process may be suitable for inventory management of released devices due to the use of field firmware updates. However, the use of field firmware updates may introduce additional steps in the OEM customer's device manufacturing (e.g., mobile phone manufacturing) operations and thus cause inefficiencies. In addition, the field firmware updates themselves may be subject to attacks, which may allow a malicious party to change the customized firmware. For example, loading the second customized firmware on the devices of the first group 540 and modifying the firmware reset security keys using the second customized key.
[0098] Figure 7A first example process 700 for limiting unauthorized modification of security keys using configuration settings according to some examples of the present disclosure is shown. Although some organizations (e.g., memory device manufacturers 705, OEMs, device groups, etc.) Figure 7 , but those skilled in the art will appreciate that other organizations may also perform Figure 7 Any and all operations in. Example process 700 utilizes the FFU update process to load key modification firmware onto a memory device. Figure 6 Customization of firmware for each group in the is enabled by a custom firmware object, but in Figure 7 These functions are provided by enabling / activating / or deactivating these features in the generic firmware using configuration values. This includes the ability to enable security key replacement or modification.
[0099] Process 700 may be implemented by one or more of a memory device manufacturer and / or an OEM or a user. In example process 700, a common manufacturing firmware object may be loaded into memory device 710 and configured to be provided to a plurality of groups, such as a first group 740 and a second group 770, to form memory device 712. Groups 740 and 770 represent OEM customers or other logical groupings of devices (e.g., device versions, distribution regions, etc.). By providing common manufacturing firmware, example process 700 may reduce or eliminate the need to track different versions of manufacturing firmware (such as Figure 5 The need for the situation in which
[0100] If key modification firmware is to be provided for secure key modification, a first custom key modification firmware may be provided 715, which may be loaded (e.g., via first group 730) to a memory device using an FFU process 745 to produce a memory device having generic firmware and the first key modification firmware 747. In some examples, key modification firmware objects may be provided by transferring them from one entity to another, for example, via a computer network.
[0101] The FFU process 745 may load the custom key modification firmware onto the memory device without overwriting the first custom firmware object. A second custom key modification firmware may be provided 725, which may be loaded onto the memory device of the second group 770 (e.g., via the second group 770) using the FFU technique 750 to produce a memory device 752 having the common firmware and the second key modification firmware.
[0102] The key modification firmware may be enabled by setting the configuration value to a specific identified value. The values of the first group 730 and the second group 740 may be the same value, but in other instances, different values may be used for the first group 730 and the second group 740 to enhance security. The values may be specified in each version of the first and second key modification firmware and may be checked by the key modification firmware before the security key can be modified.
[0103] As previously described, in some instances, existing JEDEC attributes may be used to configure settings. These attributes may be stored in a non-volatile memory of a memory device. In addition to enabling key modification firmware, these attributes may also have additional uses. Depending on whether the memory device is configured by the manufacturer or by the customer, different options for memory device operation may be implemented by changing these values. For example, the JEDEC standard currently defines an attribute (e.g., an "original equipment manufacturer (OEM) string attribute") whose default value includes a predefined vendor name that uniquely identifies the OEM. However, the OEM may change this default value by writing different values to the corresponding area of the non-volatile memory. The method according to the example embodiment enables and disables the key modification firmware based on the value that has been written for the OEM string attribute. Similarly, the OEM string attribute may be used to enable other custom firmware on the memory device.
[0104] Figure 8 An example state transition diagram 800 of the memory controller 105 for controlling when and under what conditions the key erase firmware is enabled is shown. Figure 8 In some embodiments, a memory device (eg, memory device 100 ( Figure 1 )) can be provided to a customer (e.g., a mobile device manufacturer) in an initial state 805, where, for example: operational metrics do not satisfy the enabling lock conditions; the configuration is not locked (e.g., configuration execution is permitted); the value of the configuration setting is empty (or in a default state or an unwritten state); and the key modification firmware is disabled, which at least means that the security keys on the memory device 100 cannot be erased.
[0105] As previously described, the security key may be set by the memory device manufacturer or OEM / customer at an earlier time period. The key modification firmware may consist of one function in a set of firmware binary codes (e.g., which may contain other unrelated functions), or the key modification firmware may consist of a separate dedicated firmware binary code without other unrelated functions.
[0106] The customer can change the memory device from state 805 to state 810 (e.g., "enabled state") by writing a value (e.g., a security key modification value) to a configuration setting. Because the operation metric (e.g., a write counter) does not meet the lock condition (e.g., the operation metric of the write counter is below a threshold), and the configuration setting is set to the security key modification value, the key modification firmware is enabled. Once the key modification firmware is enabled, the user can submit a request to the key modification firmware to erase the security key, replace the security key, or in some instances, include both operations. In some embodiments, the memory device can be manufactured (and provided to the customer) by the memory manufacturer in state 810 instead of state 805. The security key modification value can be specified by the customer or manufacturer of the memory device. When the security key modification value is kept confidential, external parties can be prevented from enabling the key modification firmware to change the security key and access the protected memory. In some instances, when the value of the configuration setting is set to a specific value (e.g., state 815), other customer-specific firmware features can be enabled. For example, the security key modification value can be specific to the OEM and used to enable OEM-specific features. In other instances, after the security key modification value, other values can be set to the configuration setting to enable specific features.
[0107] The memory device may migrate from state 805 to state 815 (e.g., a "used state"), for example, by utilizing the memory device such that an operational metric satisfies a lock condition (e.g., by writing data to the memory device such that the number of bytes written is greater than zero), by writing a value other than a security key modification value to a configuration setting, or by performing both operations. Other configuration operations may be performed on the memory device while the memory device is in state 815. However, the key modification firmware may remain disabled.
[0108] If the memory device 100 is in state 810, the memory device can migrate to state 820 (e.g., a "manufacturing state") by performing operations, such as by performing operations that cause an operation metric to satisfy a lock condition, such as writing data to the memory device 100 such that the number of bytes written exceeds a threshold. State 820 is similar to state 815, but the key modification firmware (and / or other custom firmware in some embodiments) remains enabled in state 820.
[0109] If the memory device is in state 815, and the value of the configuration setting changes (either maliciously by an external actor, or by a customer), then the memory device changes to a "deployed state" 825, in which the key modifying firmware is deactivated. This occurs even if the configuration value changes to a secure key modifying value, because the operational metrics satisfy the lock condition (e.g., total bytes written > a given threshold) when the configuration value changes to a secure key modifying value. This prevents the key modifying firmware from being enabled after the memory device is shipped, even for customers who do not lock the configuration after the mobile device is shipped. In state 825, the configuration can be locked or unlocked.
[0110] If the memory device is in state 820, and the value of the configuration setting is changed (either maliciously by an external actor, or by a customer), then the memory device changes to state 815, and the key modification firmware is disabled. If the memory device is in state 820, and the configuration of the memory device is locked, then the memory device enters state 830 ("deployed state"). Deployed state 830 differs from deployed state 825 in that the key modification firmware remains enabled and allows changes to security keys. In other instances, state 830 may disable the key modification firmware in response to a lock of the configuration or in response to an operational metric satisfying a lock condition. In still other instances, once the configuration is locked, the key modification firmware may deny any operation that changes the security key.
[0111] like Figure 8 As shown in , in order to enable the key modifying firmware, the configuration setting must be set to a secure key modifying value before the operational metric exceeds the threshold. Once the key modifying firmware is enabled, the user can modify the security keys until the key modifying firmware is disabled by changing the configuration setting. Figure 8 A plurality of state transitions are shown, but those skilled in the art will appreciate that other transitions and / or states may be possible, such as transitions between states 810 and 815, and so on.
[0112] As used herein, the term operation metric may include one or more metrics of a memory device. Example metrics may include the number of bytes written, the number of bytes read, the number of read operations performed, the number of write operations performed, the number of power cycles, and the like. Example lock conditions may include a threshold number of read or write operations; a threshold number of bytes read or written, and the like. In one example, the operation metric may be the number of bytes written, and the lock condition may be the number of bytes written being greater than zero. Thus, once data is written to the memory device, the operation metric satisfies the condition (because the number of bytes written exceeds zero), and if the key replacement firmware has not already been enabled, the firmware cannot be enabled again.
[0113] Fig. 9A flow chart of a method 900 for enabling key modification firmware according to some examples of the present disclosure is shown. At operation 910, a memory device may receive a request to set a configuration setting to a first value. In some examples, the configuration setting may be an OEM string. At operation 915, it is determined whether the configuration of the device is locked. If at operation 915, the configuration is locked, the process ends and the configuration remains unchanged. If the configuration is not locked, then at operation 920, the configuration setting is set to the first value. At operation 925, it is determined whether the operation metric meets the locking condition. For example, whether the number of bits or bytes read or written meets or exceeds a threshold. In one example, the threshold may be zero. That is, once data is written to the memory device, the ability to enable the key modification firmware is terminated (if not previously completed). In other examples, the operation metric is the number of reads, the number of writes, or other operations. If the operation metric meets the locking condition, the process ends and the key modification firmware is not enabled.
[0114] If the operational metric does not satisfy the lock condition, then the memory device checks to determine if the first value is a security key modification value at operation 927. If not, then the process terminates and the key modification firmware is not enabled. If the first value is a security key modification value, then at operation 930, the key modification firmware is enabled and modification of the security key is enabled. Although Fig. 9 Operation 925 is shown to be performed before operation 927 , but in other examples, operation 927 may be performed before operation 925 .
[0115] Fig.10 A flow chart illustrating a method 1000 for updating a security key of a protected portion of a memory device using a configuration value according to some examples of the present disclosure. Prior to performing method 1000, key modification firmware is loaded into a memory device using an FFU process. At operation 1010, the memory device receives a request to modify one or more security keys. At operation 1015, the memory device may determine whether the key modification firmware is enabled. For example, according to method 900. The key modification firmware may be enabled at Figure 8 is enabled in states 810, 820, and 830.
[0116] If the key modification firmware is enabled, then the one or more security keys may be modified at 1020. This may include erasing the security keys 1030 and / or replacing the security keys 1025. If the key modification firmware is not enabled, then at operation 1022, the security keys are not modified. This may include denying the request or taking no action on the request. In some examples, one or more operations in method 1000 are performed by key modification firmware and / or operating firmware.
[0117] Fig.11A block diagram of an example machine 1100 is shown that can perform any one or more of the techniques (e.g., methods) discussed herein. The machine 1100 or one or more components of the machine 1100 can implement one or more memory devices or components of memory devices described herein. For example, the machine 1100 or one or more components of the machine 1100 can implement the memory device 100. In some examples, the machine 1100 can be a host device 135. In some examples, the main memory 1104, the static memory 1106, and / or the mass storage device 1121 can be implemented by a memory, such as described herein with respect to Figure 1-10 The memories discussed.
[0118] In alternative embodiments, the machine 1100 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 1100 may operate in the capacity of a memory device, a host device, a server machine, a client machine, or a server-client network environment. In an example, the machine 1100 may act as a peer-to-peer machine in a peer-to-peer (P2P) (or other distributed) network environment. The machine 1100 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile phone, a network appliance, an IoT device, an automotive system, a host device, or any machine capable of executing (sequentially or otherwise) instructions specifying actions to be taken by the machine. In addition, although only a single machine is shown, the term "machine" will also be deemed to include any machine collection that executes a set of instructions (or multiple sets) individually or collectively to perform any one or more of the methods discussed herein (e.g., cloud computing, software as a service (SaaS), other computer cluster configurations).
[0119] As described herein, an instance may include logic or multiple components, modules or mechanisms (hereinafter referred to as "modules") or may operate on them. A module is a tangible entity (e.g., hardware) that is capable of performing a specified operation and may be configured or arranged in a certain manner. In an example, a circuit may be arranged as a module in a specified manner (e.g., internally or relative to an external entity such as other circuits). In an example, all or part of one or more computer systems (e.g., independent, client or server computer systems) or one or more hardware processors may be configured as a module for performing a specified operation by firmware or software (e.g., instructions, application parts or applications). In an example, the software may reside on a machine-readable medium. In an example, when executed by the underlying hardware of the module, the software causes the hardware to perform the specified operation.
[0120] Thus, the term "module" is understood to encompass a tangible entity, referring to an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., provisionally) configured (e.g., programmed) to operate in a particular manner or to perform part or all of any operations described herein. In view of instances of temporarily configuring modules, each module need not be instantiated at any time. For example, where a module includes a general-purpose hardware processor configured using software, the general-purpose hardware processor can be configured into corresponding different modules at different times. The software can configure the hardware processor accordingly, for example, to constitute a particular module at one time and to constitute another module at a different time.
[0121] The machine (e.g., computer system) 1100 (e.g., host device 135, managed memory device 100, etc.) may include a hardware processor 1102 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof, etc.), a main memory 1504, and a static memory 1106, some or all of which may communicate with each other via an interconnection link (e.g., a bus) 1108. The machine 1100 may further include a display unit 1110, an alphanumeric input device 1112 (e.g., a keyboard), and a user interface (UI) navigation device 1114 (e.g., a mouse). In an example, the display unit 1110, the input device 1112, and the UI navigation device 1114 may be a touch screen display. The machine 1100 may additionally include a storage device (e.g., a mass storage device 1121), a signal generating device 1118 (e.g., a speaker), a network interface device 1120, and one or more sensors 1116, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. The machine 1100 may include an output controller 1128, such as a serial (e.g., Universal Serial Bus (USB), parallel or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, a card reader, etc.).
[0122] The storage device 1121 may include a machine-readable medium 1122 on which one or more sets of data structures or instructions 1124 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein are stored. The instructions 1124 may also reside, completely or at least partially, within the main memory 1104, within the static memory 1106, or within the hardware processor 1102 during execution thereof by the machine 1100. In an example, one or any combination of the hardware processor 1102, the main memory 1104, the static memory 1106, or the storage device 1121 may constitute the machine-readable medium 1122.
[0123] Although machine-readable medium 1122 is shown as a single medium, the term “machine-readable medium” may include a single medium or multiple media (eg, a centralized or distributed database, or associated caches and servers) configured to store one or more instructions 1124 .
[0124] The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions for execution by the machine 1100 and causing the machine 1100 to perform any one or more of the techniques of the present invention, or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memory and optical and magnetic media. In an example, a centralized machine-readable medium includes a machine-readable medium having a plurality of particles, the particles having a constant (e.g., stationary) mass. Therefore, a centralized machine-readable medium is a non-transitory propagating signal. Specific examples of centralized machine-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
[0125] Instructions 1124 (e.g., software, programs, operating systems (OS), etc.) or other data are stored on storage device 1121 and can be accessed by memory 1104 for use by processor 1102. Memory 1104 (e.g., DRAM) is typically fast but volatile, and is therefore a different type of storage than storage device 1121 (e.g., SSD), which is suitable for long-term storage, including long-term storage when in a "disconnected" condition. Instructions 1124 or data in use by a user or machine 1100 are typically loaded into memory 1104 for use by processor 1102. When memory 1104 is full, virtual space from storage device 1121 can be allocated to supplement memory 1104; however, because storage device 1121 is typically slower than memory 1104, and write speeds are typically at least twice slower than read speeds, the use of virtual memory can greatly reduce the user experience due to storage device latency (compared to memory 1104, such as DRAM). Furthermore, the use of storage device 1121 for virtual memory may significantly reduce the usable useful life of storage device 1121 .
[0126] Compared to virtual memory, virtual memory compression (e.g. The kernel feature "ZRAM") uses portions of memory as compressed block storage to avoid paging to storage 1121. Paging occurs in compressed blocks until the data must be written to storage 1121. Virtual memory compression increases the available size of memory 1104 while reducing wear on storage 1121.
[0127] Storage devices optimized for mobile electronic devices or mobile storage traditionally include MMC solid-state storage devices (e.g., micro Secure Digital (microSD TM ) card, etc.). MMC devices include several parallel interfaces (e.g., 8-bit parallel interfaces) with the host device and are often components that are removable and detachable from the host device. In contrast, eMMC TM The device is attached to the circuit board and is seen as a component of the host device, with read speeds comparable to Serial ATA-based TM (Serial Advanced Technology (AT) Attachment, or SATA) SSD devices. However, the demand for mobile device performance continues to increase in order to fully realize virtual or augmented reality devices, take advantage of increased network speeds, etc. In response to this demand, storage devices have moved from parallel to serial communication interfaces. Universal Flash Storage (UFS) devices, which include a controller and firmware, use a low voltage differential signaling (LVDS) serial interface with a dedicated read / write path to communicate with the host device, further promoting higher read / write speeds.
[0128] The instructions 1124 may further be transmitted or received over a communication network 1126 using a transmission medium via the network interface device 1120 using any of a number of transmission protocols (e.g., frame relay, Internet Protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, and a wireless data network (e.g., a wireless network known as a wireless network). The Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, known as 16 family of standards), IEEE 802.15.4 family of standards, peer-to-peer (P2P) networks, and other networks. In an example, network interface device 1520 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to communication network 1126. In an example, network interface device 1120 may include multiple antennas to communicate wirelessly using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology. The term "transmission media" should be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by machine 1100, and includes digital or analog communication signals or other intangible media used to facilitate communication of such software.
[0129] The above detailed description includes reference to the accompanying drawings, which form part of the detailed description. The accompanying drawings show specific embodiments by way of illustration, in which the present invention can be practiced. These embodiments are also referred to herein as "examples". Such examples may include elements other than those shown or described. However, the inventors also contemplate examples in which only those elements shown or described are provided. In addition, the inventors of the present invention also contemplate examples (or one or more aspects thereof) of any combination or arrangement of those elements shown or described relative to a specific example (or one or more aspects thereof) or relative to other examples (or one or more aspects thereof) shown or described herein.
[0130] In this document, the term "one" is used as commonly used in patent documents to include one or more than one, independent of any other examples or uses of "at least one" or "one or more". In this document, the term "or" is used to refer to a non-exclusive or, so that unless otherwise indicated, "A or B" may include "A but not B", "B but not A" and "A and B". In the appended claims, the terms "including" and "in which" are used as colloquial equivalents of the corresponding terms "including" and "wherein". In addition, in the appended claims, the terms "including" and "comprising" are open-ended, that is, systems, devices, articles or processes containing elements other than those listed after this term in the claims are still considered to be within the scope of the claims. In addition, in the appended claims, the terms "first", "second" and "third" etc. are used only as labels and are not intended to impose numerical requirements on their objects.
[0131] In various examples, the components, controllers, processors, units, engines, or tables described herein may include, among other things, physical circuitry or firmware stored on a physical device. As used herein, "processor" means any type of computing circuit, such as, but not limited to, a microprocessor, a microcontroller, a graphics processor, a digital signal processor (DSP), or any other type of processor or processing circuit, including a group of processors or a multi-core device.
[0132] Various embodiments according to the present invention and described herein include memories using vertical structures of memory cells (e.g., NAND strings of memory cells). As used herein, directional adjectives will be employed relative to the surface of the substrate on which the memory cells are formed (i.e., a vertical structure will be considered to extend away from the substrate surface, a bottom end of the vertical structure will be considered to be the end closest to the substrate surface, and a top end of the vertical structure will be considered to be the end farthest from the substrate surface).
[0133] As used herein, directional adjectives, such as horizontal, vertical, normal, parallel, perpendicular, etc., may refer to relative directions and are not intended to require strict adherence to specific geometric properties unless otherwise specified. For example, as used herein, a vertical structure need not be strictly perpendicular to the surface of a substrate, but may be generally perpendicular to the surface of the substrate and may form an acute angle (e.g., between 60 and 120 degrees, etc.) with the surface of the substrate.
[0134] In some embodiments described herein, different doping configurations may be applied to a source side select gate (SGS), a control gate (CG), and a drain side select gate (SGD), each of which may be formed of or at least include polysilicon in this instance, with the result that these layers (e.g., polysilicon, etc.) may have different etching rates when exposed to an etching solution. For example, during the formation of a monolithic pillar in a 3D semiconductor device, the SGS and CG may form a recess, while the SGD may remain less recessed or even not recessed. Thus, these doping configurations may enable selective etching of different layers (e.g., SGS, CG, and SGD) in a 3D semiconductor device using an etching solution (e.g., tetramethylammonium hydroxide (TMCH)).
[0135] As used herein, operating a memory cell includes reading from the memory cell, writing to the memory cell, or erasing the memory cell. The operation of placing a memory cell in a given state is referred to herein as "programming" and may include writing to or erasing from a memory cell (e.g., a memory cell may be programmed to an erased state).
[0136] According to one or more embodiments of the present invention, a memory controller (e.g., a processor, controller, firmware, etc.) located inside or outside a memory device is capable of determining (e.g., selecting, setting, adjusting, calculating, changing, clearing, transferring, adapting, deriving, defining, utilizing, modifying, applying, etc.) the number of wear cycles, or a wear state (e.g., recording wear cycles, counting operations of the memory device as they occur, tracking the operations of the memory device from which they were initiated, evaluating memory device characteristics corresponding to the wear state, etc.).
[0137] According to one or more embodiments of the present invention, a memory access device may be configured to provide wear cycle information to a memory device with respect to each memory operation. The memory device control circuitry (e.g., control logic) may be programmed to compensate for memory device performance changes corresponding to the wear cycle information. The memory device may receive the wear cycle information and determine one or more operating parameters (e.g., values, characteristics) in response to the wear cycle information.
[0138] It will be understood that when an element is referred to as being "on," "connected to," or "coupled to" another element, it may be directly on, directly connected or coupled to, or there may be intervening elements. In contrast, when an element is referred to as being "directly on," "directly connected to," or "directly coupled to" another element, there are no intervening elements or layers. If two elements are shown in a drawing as being connected by a line, the two elements may be coupled, or directly coupled, unless otherwise specified.
[0139] The method examples described herein may be implemented at least in part by a machine or computer. Some examples may include a computer-readable medium or machine-readable medium encoded with instructions, which are operable to configure an electronic device to perform a method as described in the above examples. Implementations of such methods may include code, such as microcode, assembly language code, high-level language code, and the like. Such code may include computer-readable instructions for performing various methods. The code may form part of a computer program product. In addition, the code may be tangibly stored on one or more volatile or non-volatile tangible computer-readable media, such as during execution or at other times. Examples of these tangible computer-readable media may include, but are not limited to: hard disks, removable disks, removable optical disks (e.g., compact disks and digital video disks), cassettes, memory cards or sticks, random access memory (RAM), read-only memory (ROM), solid-state drives (SSD), universal flash storage (UFS) devices, embedded MMC (eMMC) devices, and the like.
[0140] The above description is intended to be illustrative and not restrictive. For example, the above examples (or one or more aspects thereof) can be used in combination with each other. For example, a person skilled in the art can use other embodiments after consulting the above description. The abstract is submitted with the following understanding: it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the above specific embodiments, various features can be grouped together to simplify the present invention. This situation should not be interpreted as an expectation that the unclaimed public features are necessary for any claim. In fact, the title of the present invention may be less than all the features of a specific disclosed embodiment. Therefore, the attached claims are hereby incorporated into the specific embodiments, wherein each claim exists independently as a separate embodiment, and it is expected that these embodiments can be combined with each other in various combinations or arrangements. The scope of the present invention should be determined by reference to the attached claims and the full scope of equivalents granted by the claims.
[0141] Other Notes and Examples
[0142] Example 1 is a memory device, the memory device comprising: a memory array, the memory array comprising a plurality of memory cells, a portion of the memory array being a protected portion accessed using a security key; a controller, the controller being configured to perform operations including: receiving a request to set a configuration setting of the memory device to a first value; setting the configuration setting of the memory device to the first value; determining whether an operation metric is below a threshold; in response to setting the configuration setting of the memory device to the first value and determining that the operation metric is below the threshold, enabling a security key modification feature; receiving a request to modify the security key of the protected portion; in response to receiving the request, determining whether the security key modification feature is enabled; and in response to determining that the security key modification feature is enabled, modifying the security key of the protected portion.
[0143] In example 2, the subject matter of example 1 includes wherein the configuration setting is an original equipment manufacturer string attribute.
[0144] In Example 3, the subject matter of Examples 1-2 includes, wherein the protected portion includes a replay protected memory block (RPMB), and wherein the operation further includes: after modifying the security key, receiving a request to perform a memory operation at a location of the RPMB, the request including a secret value; determining whether the secret value is an expected secret value based on the request and the modified security key; and in response to determining that the secret value is the expected secret value, performing the memory operation at the location of the RPMB.
[0145] In Example 4, the subject matter of Examples 1-3 includes wherein the operations further comprise: in response to determining that the security key modification feature is not enabled, not modifying the security key of the protected portion.
[0146] In Example 5, the subject matter according to Examples 1-4 includes, wherein the operation further includes: receiving a request to set a configuration setting of the memory device to a second value; setting the configuration setting of the memory device to the second value; determining whether the operation metric is below the threshold; in response to determining that the operation metric is not below the threshold and the configuration setting is set to the second value, disabling the security key modification feature; receiving a second request to modify the security key of the protected portion; in response to receiving the second request, determining whether the security key modification feature is enabled; and in response to determining that the security key modification feature is disabled, prohibiting modification of the security key of the protected portion.
[0147] In Example 6, the subject matter of Examples 1-5 includes, wherein the operations further include: receiving a request to lock a configuration of the memory device; locking the configuration of the memory device; receiving a request to modify the configuration setting to a second value different from the first value; determining whether the configuration of the memory device is locked; and in response to determining that the configuration of the memory device is locked, prohibiting the first value of the configuration setting from being changed to the second value.
[0148] In Example 7, the subject matter of Examples 1-6 includes wherein the plurality of memory cells are NAND memory cells.
[0149] Example 8 is a method comprising: at a memory device: receiving a request to set a configuration setting of the memory device to a first value; setting the configuration setting of the memory device to the first value; determining whether an operating metric is below a threshold; in response to setting the configuration setting of the memory device to the first value and determining that the operating metric is below the threshold, enabling a security key modification feature; receiving a request to modify a security key of a protected portion of a memory array of the memory device; in response to receiving the request, determining whether the security key modification feature is enabled; and in response to determining that the security key modification feature is enabled, modifying the security key of the protected portion.
[0150] In example 9, the subject matter of example 8 includes wherein the configuration setting is an original equipment manufacturer string attribute.
[0151] In Example 10, the subject matter of Examples 8-9 includes, wherein the protected portion includes a replay protected memory block (RPMB), and wherein the operation further includes: after modifying the security key, receiving a request to perform a memory operation at a location of the RPMB, the request including a secret value; determining whether the secret value is an expected secret value based on the request and the modified security key; and in response to determining that the secret value is the expected secret value, performing the memory operation at the location of the RPMB.
[0152] In Example 11, the subject matter of Examples 8-10 includes wherein the operations further comprise: in response to determining that the security key modification feature is not enabled, not modifying the security key of the protected portion.
[0153] In Example 12, the subject matter of Examples 8-11 includes, wherein the operation further includes: receiving a request to set a configuration setting of the memory device to a second value; setting the configuration setting of the memory device to the second value; determining whether the operating metric is below the threshold; in response to determining that the operating metric is not below the threshold and the configuration setting is set to the second value, disabling the security key modification feature; receiving a second request to modify the security key of the protected portion; in response to receiving the second request, determining whether the security key modification feature is enabled; and in response to determining that the security key modification feature is disabled, prohibiting modification of the security key of the protected portion.
[0154] In Example 13, the subject matter of Examples 8-12 includes, wherein the operation further includes: receiving a request to lock the configuration of the memory device; locking the configuration of the memory device; receiving a request to modify the configuration setting to a second value different from the first value; determining whether the configuration of the memory device is locked; and in response to determining that the configuration of the memory device is locked, prohibiting the first value of the configuration setting from being changed to the second value.
[0155] In Example 14, the subject matter of Examples 8-13 includes wherein the plurality of memory cells are NAND memory cells.
[0156] Example 15 is a non-transitory machine-readable medium storing instructions that, when executed by a controller of a memory device, cause the memory device to perform operations including: receiving a request to set a configuration setting of the memory device to a first value; setting the configuration setting of the memory device to the first value; determining whether an operating metric is below a threshold; in response to setting the configuration setting of the memory device to the first value and determining that the operating metric is below the threshold, enabling a security key modification feature; receiving a request to modify a security key of a protected portion of a memory array of the memory device; in response to receiving the request, determining whether the security key modification feature is enabled; and in response to determining that the security key modification feature is enabled, modifying the security key of the protected portion.
[0157] In Example 16, the subject matter of Example 15 includes wherein the configuration setting is an original equipment manufacturer string attribute.
[0158] In Example 17, the subject matter of Examples 15-16 includes, wherein the protected portion includes a replay protected memory block (RPMB), and wherein the operation further includes: after modifying the security key, receiving a request to perform a memory operation at a location of the RPMB, the request including a secret value; determining whether the secret value is an expected secret value based on the request and the modified security key; and in response to determining that the secret value is the expected secret value, performing the memory operation at the location of the RPMB.
[0159] In Example 18, the subject matter of Examples 15-17 includes wherein the operations further comprise: in response to determining that the security key modification feature is not enabled, not modifying the security key of the protected portion.
[0160] In Example 19, the subject matter of Examples 15-18 includes, wherein the operation further includes: receiving a request to set a configuration setting of the memory device to a second value; setting the configuration setting of the memory device to the second value; determining whether the operating metric is below the threshold; in response to determining that the operating metric is not below the threshold and the configuration setting is set to the second value, disabling the security key modification feature; receiving a second request to modify the security key of the protected portion; in response to receiving the second request, determining whether the security key modification feature is enabled; and in response to determining that the security key modification feature is disabled, prohibiting modification of the security key of the protected portion.
[0161] In Example 20, the subject matter of Examples 15-19 includes wherein the operations further include: receiving a request to lock the configuration of the memory device; locking the configuration of the memory device; receiving a request to modify the configuration setting to a second value different from the first value; determining whether the configuration of the memory device is locked; and in response to determining that the configuration of the memory device is locked, prohibiting the first value of the configuration setting from being changed to the second value.
[0162] In Example 21, the subject matter of Examples 15-20 includes wherein the plurality of memory cells are NAND memory cells.
[0163] Example 22 is a memory device, the memory device comprising: a memory array, the memory array comprising a plurality of memory cells, a portion of the memory array being a protected portion accessed using a security key; a controller, the controller being configured to perform operations including the following: a component for receiving a request to set a configuration setting of the memory device to a first value; a component for setting the configuration setting of the memory device to the first value; a component for determining whether an operating metric is below a threshold; a component for enabling a security key modification feature in response to setting the configuration setting of the memory device to the first value and determining that the operating metric is below the threshold; a component for receiving a request to modify the security key of the protected portion; a component for determining whether the security key modification feature is enabled in response to receiving the request; and a component for modifying the security key of the protected portion in response to determining that the security key modification feature is enabled.
[0164] In Example 23, the subject matter of Example 22 includes wherein the configuration setting is an original equipment manufacturer string attribute.
[0165] In Example 24, the subject matter of Examples 22-23 includes, wherein the protected portion includes a replay protected memory block (RPMB), and wherein the operation further includes: a component for receiving a request to perform a memory operation at a location of the RPMB after modifying the security key, the request including a secret value; a component for determining whether the secret value is an expected secret value based on the request and the modified security key; and a component for performing the memory operation at the location of the RPMB in response to determining that the secret value is the expected secret value.
[0166] In Example 25, the subject matter of Examples 22-24 includes wherein the operations further comprise: means for not modifying the security key of the protected portion in response to determining that the security key modification feature is not enabled.
[0167] In Example 26, the subject matter of Examples 22-25 includes, wherein the operation further includes: a component for receiving a request to set a configuration setting of the memory device to a second value; a component for setting the configuration setting of the memory device to the second value; a component for determining whether the operating metric is below the threshold; a component for disabling the security key modification feature in response to determining that the operating metric is not below the threshold and the configuration setting is set to the second value; a component for receiving a second request to modify the security key of the protected portion; a component for determining whether the security key modification feature is enabled in response to receiving the second request; and a component for prohibiting modification of the security key of the protected portion in response to determining that the security key modification feature is disabled.
[0168] In Example 27, the subject matter of Examples 22-26 includes, wherein the operation further includes: a component for receiving a request to lock the configuration of the memory device; a component for locking the configuration of the memory device; a component for receiving a request to modify the configuration setting to a second value different from the first value; a component for determining whether the configuration of the memory device is locked; and a component for prohibiting the first value of the configuration setting from being changed to the second value in response to determining that the configuration of the memory device is locked.
[0169] In Example 28, the subject matter of Examples 22-27 includes wherein the plurality of memory cells are NAND memory cells.
[0170] Example 29 is at least one machine-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement any of Examples 1-28.
[0171] Example 30 is an apparatus comprising means for implementing any of Examples 1-28.
[0172] Example 31 is a system for implementing any one of Examples 1-28.
[0173] Example 32 is a method of implementing any of Examples 1-28.
Claims
1. A memory device, the memory device include: a memory array comprising a plurality of memory cells, a portion of the memory array being a protected portion accessed using a security key; A controller configured to perform operations including: receiving a request to set a configuration setting of the memory device to a first value; setting the configuration setting of the memory device to the first value; determining whether an operational metric of the memory device is below a threshold; in response to setting the configuration setting of the memory device to the first value and determining that the operational metric is below the threshold, enabling a security key modification feature; receiving a request to modify the security key of the protected portion; In response to receiving the request, determining whether the security key modification feature is enabled; as well as In response to determining that the security key modification feature is enabled, the security key of the protected portion is modified.
2. The memory device of claim 1, wherein the configuration setting is an original equipment manufacturer string attribute.
3. The memory device of claim 1 , wherein the protected portion comprises a replay protected memory block RPMB, and wherein the operation further comprises: include: After modifying the security key, receiving a request to perform a memory operation at a location of the RPMB, the request including a secret value; determining, based on the request and the modified security key, whether the secret value is an expected secret value; as well as In response to determining that the secret value is the expected secret value, performing the memory operation at the location of the RPMB.
4. The memory device of claim 1, wherein the operation further include: In response to determining that the security key modification feature is not enabled, the security key of the protected portion is not modified.
5. The memory device of claim 1, wherein the operation further include: receiving a request to set a configuration setting of the memory device to a second value; setting the configuration setting of the memory device to the second value; determining whether the operational metric is below the threshold; responsive to determining that the operational metric is not below the threshold and the configuration setting is set to the second value, deactivating the security key modification feature; receiving a second request to modify the security key of the protected portion; in response to receiving the second request, determining whether the security key modification feature is enabled; as well as In response to determining that the security key modification feature is disabled, modifying the security key of the protected portion is prohibited.
6. The memory device of claim 1, wherein the operation further include: receiving a request to lock a configuration of the memory device; locking the configuration of the memory device; receiving a request to modify the configuration setting to a second value different from the first value; determining whether the configuration of the memory device is locked; as well as Responsive to determining that the configuration of the memory device is locked, changing the first value of the configuration setting to the second value is prohibited.
7. The memory device of claim 1, wherein the plurality of memory cells are NAND memory cells.
8. A method of operating a memory device, wherein include: At the memory device: receiving a request to set a configuration setting of the memory device to a first value; setting the configuration setting of the memory device to the first value; determining whether an operational metric of the memory device is below a threshold; in response to setting the configuration setting of the memory device to the first value and determining that the operational metric is below the threshold, enabling a security key modification feature; receiving a request to modify a security key of a protected portion of a memory array of the memory device; In response to receiving the request, determining whether the security key modification feature is enabled; as well as In response to determining that the security key modification feature is enabled, the security key of the protected portion is modified.
9. The method of claim 8, wherein the configuration setting is an original equipment manufacturer string attribute.
10. The method of claim 8, wherein the protected portion comprises a replay protected memory block RPMB, and wherein the operation further include: After modifying the security key, receiving a request to perform a memory operation at a location of the RPMB, the request including a secret value; determining, based on the request and the modified security key, whether the secret value is an expected secret value; as well as In response to determining that the secret value is the expected secret value, performing the memory operation at the location of the RPMB.
11. The method of claim 8, wherein the operation further comprises: include: In response to determining that the security key modification feature is not enabled, the security key of the protected portion is not modified.
12. The method of claim 8, wherein the operation further comprises: include: receiving a request to set a configuration setting of the memory device to a second value; setting the configuration setting of the memory device to the second value; determining whether the operational metric is below the threshold; responsive to determining that the operational metric is not below the threshold and the configuration setting is set to the second value, deactivating the security key modification feature; receiving a second request to modify the security key of the protected portion; in response to receiving the second request, determining whether the security key modification feature is enabled; as well as In response to determining that the security key modification feature is disabled, modifying the security key of the protected portion is prohibited.
13. The method of claim 8, wherein the operation further comprises: include: receiving a request to lock a configuration of the memory device; locking the configuration of the memory device; receiving a request to modify the configuration setting to a second value different from the first value; determining whether the configuration of the memory device is locked; as well as Responsive to determining that the configuration of the memory device is locked, changing the first value of the configuration setting to the second value is prohibited.
14. The method of claim 8, wherein the plurality of memory cells are NAND memory cells.
15. A non-transitory machine-readable medium storing instructions that, when executed by a controller of a memory device, cause the memory device to perform operations comprising: receiving a request to set a configuration setting of the memory device to a first value; setting the configuration setting of the memory device to the first value; determining whether an operational metric of the memory device is below a threshold; in response to setting the configuration setting of the memory device to the first value and determining that the operational metric is below the threshold, enabling a security key modification feature; receiving a request to modify a security key of a protected portion of a memory array of the memory device; In response to receiving the request, determining whether the security key modification feature is enabled; as well as In response to determining that the security key modification feature is enabled, the security key of the protected portion is modified.
16. The non-transitory machine-readable medium of claim 15, wherein the configuration setting is an original equipment manufacturer string attribute.
17. The non-transitory machine-readable medium of claim 15, wherein the protected portion comprises a replay protected memory block RPMB, and wherein the operation further include: After modifying the security key, receiving a request to perform a memory operation at a location of the RPMB, the request including a secret value; determining, based on the request and the modified security key, whether the secret value is an expected secret value; as well as In response to determining that the secret value is the expected secret value, performing the memory operation at the location of the RPMB.
18. The non-transitory machine-readable medium of claim 15, wherein the operations further include: In response to determining that the security key modification feature is not enabled, the security key of the protected portion is not modified.
19. The non-transitory machine-readable medium of claim 15, wherein the operations further include: receiving a request to set a configuration setting of the memory device to a second value; setting the configuration setting of the memory device to the second value; determining whether the operational metric is below the threshold; responsive to determining that the operational metric is not below the threshold and the configuration setting is set to the second value, deactivating the security key modification feature; receiving a second request to modify the security key of the protected portion; in response to receiving the second request, determining whether the security key modification feature is enabled; as well as In response to determining that the security key modification feature is disabled, modifying the security key of the protected portion is prohibited.
20. The non-transitory machine-readable medium of claim 15, wherein the operations further include: receiving a request to lock a configuration of the memory device; locking the configuration of the memory device; receiving a request to modify the configuration setting to a second value different from the first value; determining whether the configuration of the memory device is locked; as well as Responsive to determining that the configuration of the memory device is locked, changing the first value of the configuration setting to the second value is prohibited.
