Controller and method for accessing a memory device via multiple modes

By dynamically switching between a central controller and multiple media controllers, and employing chip-hunting and non-chip-hunting protocols, the misalignment problem during memory device access is solved, improving the reliability and efficiency of the memory system and supporting high-speed communication.

CN117420945BActive Publication Date: 2026-11-17MICRON TECHNOLOGY INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310764088.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2022-07-19
Filing Date
2023-06-27
Publication Date
2026-11-17
Estimated Expiration
2043-06-27

AI Technical Summary

Technical Problem

In the prior art, memory devices are prone to misalignment when accessed by a separate media controller, leading to significant latency and single point of failure risk. This is especially true in data protection schemes, where the reliability and efficiency of the memory system are affected.

Method used

It employs a central controller and multiple media controllers, dynamically enabling/disabling different media controller groups to access memory devices by switching between chip-killing and non-chip-killing protocols, achieving data alignment and fault tolerance, and supporting high-speed communication of the CXL protocol.

Benefits of technology

It improves the reliability and efficiency of memory systems, reduces the risk of single points of failure, supports high-speed data transmission and fault recovery, and reduces system complexity and cost.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117420945B_ABST
    Figure CN117420945B_ABST
Patent Text Reader

Abstract

This disclosure relates to a controller and method for accessing a memory device via multiple modes. The memory controller may include media controllers respectively coupled to the memory device. A first set of media controllers may be enabled during a first operating mode of the memory controller, and a second set of media controllers may be enabled during a second operating mode of the memory controller, during which certain features, such as low-power features, may be disabled. Data accessed by each media controller in the first set of media controllers may be aligned before further transmission to other circuitry of the memory controller, such as those dedicated to the low-power features.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure generally relates to semiconductor memories and methods, and more specifically, to apparatus, systems and methods for accessing memory devices via multiple modes. Background Technology

[0002] Memory devices are typically provided as internal components of computers or other electronic systems, in semiconductors, or integrated circuits. Many different types of memory exist, including volatile and non-volatile memory. Volatile memory may require power to maintain its data (e.g., host data, erroneous data, etc.) and includes Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Synchronous Dynamic Random Access Memory (SDRAM), and Thyristor Random Access Memory (TRAM), among others. Non-volatile memory provides persistent data by retaining the stored data when no power is supplied and includes NAND flash memory, NOR flash memory, ferroelectric random access memory (FeRAM), and resistive variable memory such as phase-change random access memory (PCRAM), resistive random access memory (RRAM), and magnetoresistive random access memory (MRAM), such as spin torque transfer random access memory (STT RAM), etc.

[0003] A memory device may be coupled to a host computer (e.g., a host computing device) to store data, commands, and / or instructions for use by the host computer or electronic system during operation. For example, data, commands, and / or instructions may be transferred between the host computer and the memory device during operation of the computing or other electronic system. A controller may be used to manage the transfer of data, commands, and / or instructions between the host computer and the memory device. Summary of the Invention

[0004] Embodiments of this disclosure provide a method for accessing a memory device via multiple modes, comprising: accessing the plurality of memory devices in a first mode using a central controller and a first set of media controllers, each coupled to a corresponding set of memory devices in the central controller and the plurality of memory devices; and accessing the plurality of memory devices in a second mode using the central controller and a second set of media controllers, each coupled to a corresponding set of memory devices in the central controller and the plurality of memory devices.

[0005] Another embodiment of this disclosure provides an apparatus for accessing memory devices via multiple modes, comprising: a first set of media controllers among a plurality of media controllers, the first set of media controllers being coupled to the plurality of memory devices and configured to access the plurality of memory devices according to a chip-hunting protocol; a second set of media controllers among the plurality of media controllers, the second set of media controllers being coupled to the plurality of memory devices and configured to access the plurality of memory devices according to a non-chip-hunting protocol; and a controller coupled to the plurality of media controllers, the controller being configured to enable the first set of media controllers to access the plurality of memory devices according to the chip-hunting protocol when the second set of media controllers is deactivated.

[0006] Another embodiment of this disclosure provides a method for accessing memory devices via multiple modes, comprising: enabling a first set of media controllers using a central controller according to a chip-hunting protocol for accessing the multiple memory devices by: coupling the first set of media controllers to the multiple memory devices; and decoupling a second set of media controllers from the multiple memory devices; and enabling the second set of media controllers using the central controller according to a non-chip-hunting protocol for accessing the multiple memory devices by: coupling the second set of media controllers to the multiple memory devices; and decoupling the first set of media controllers from the multiple memory devices.

[0007] Another embodiment of this disclosure provides an apparatus for accessing memory devices via multiple modes, comprising: a plurality of memory devices; a first portion of a memory controller including: a plurality of physical memory interfaces; a plurality of media controllers including: a first set of media controllers coupled to at least a portion of the plurality of memory devices via a portion of the plurality of physical memory interfaces; a second set of media controllers coupled to the plurality of memory devices via the plurality of physical memory interfaces; and a switching circuit system coupled between the plurality of media controllers and the plurality of physical memory interfaces; and a second portion of the memory controller coupled to the first portion of the memory controller, the second portion of the memory controller being configured to control the switching circuit system to: couple the first set of media controllers to the portion of the plurality of physical memory interfaces to allow the first set of media controllers to access at least the portion of the plurality of memory devices according to a chip-hunting protocol; and couple the second set of media controllers to the plurality of physical memory interfaces to allow the second set of media controllers to access the plurality of memory devices according to a non-chip-hunting protocol. Attached Figure Description

[0008] Figure 1This is a functional block diagram of a computing system including a memory controller according to several embodiments of the present disclosure.

[0009] Figure 2 This is a functional block diagram of a memory controller according to several embodiments of the present disclosure.

[0010] Figure 3 This is a functional block diagram of a memory controller according to several embodiments of the present disclosure.

[0011] Figure 4 This is a functional block diagram illustrating a portion of a memory controller including a central controller portion and a back-end portion according to several embodiments of the present disclosure.

[0012] Figure 5 This is a flowchart of a method for accessing a memory device in different operating modes according to several embodiments of the present disclosure.

[0013] Figure 6 This is a flowchart of a method for accessing a memory device in different operating modes according to several embodiments of the present disclosure. Detailed Implementation

[0014] This describes systems, apparatus, and methods related to accessing memory devices via multiple modes. In some cases, subsets of data distributed across multiple memory devices often need to be processed together at various circuit systems / components (e.g., circuit systems dedicated to data protection schemes). When accessing a particular memory device via a separate media controller, misaligned accesses to the memory device and / or the data subset can occur. This often poses significant risks, such as requiring a refresh to restart the reading of the data subset, which can significantly increase the latency associated with processing the data subset.

[0015] The various embodiments described herein are directed to providing a controller (e.g., a memory controller) comprising a group of media controllers configured to access memory devices according to different operating modes. For example, each media controller in a first group of media controllers may be configured to manage / access multiple memory devices for various purposes, such as data protection schemes, for a subset of data that needs to be processed together. A data protection scheme can be provided through “chip hunting,” where the memory system can recover data even if a member chip (e.g., a memory device) is damaged or otherwise unavailable; thus, preventing one of the chips from becoming a single point of failure (SPOF) in the memory system.

[0016] The accessed subset can be aligned at the corresponding media controller in the first group of media controllers before being transmitted to other circuitry, such as those dedicated to data protection schemes. Instead of the first group, a second group of media controllers can be activated to access data stored in the memory device, eliminating the need for alignment at the corresponding controller in the second group if data alignment is not required due to the data protection scheme being disabled. Embodiments of this disclosure can dynamically enable / disable those controller groups to switch between different modes of accessing the memory device.

[0017] In some embodiments, the memory system may be a compute fast link (CXL) compatible memory system. The host interface can be managed using the CXL protocol and coupled to the host via an interface configured for the peripheral component high-speed interconnect (PCIe) protocol. CXL is a high-speed central processing unit (CPU) to device and CPU to memory interconnect designed to enhance the performance of next-generation data centers. CXL technology maintains memory coherence between the CPU memory space and the memory on the attached device, allowing resource sharing to achieve higher performance, reduced software stack complexity, and lower overall system cost. With the increasing use of accelerators to supplement CPUs to support emerging applications such as artificial intelligence and machine learning, CXL is designed as an industry-open standard interface for high-speed communication. CXL technology is built on the PCIe infrastructure, utilizing PCIe physical and electrical interfaces to provide advanced protocols in areas such as input / output (I / O) protocols, memory protocols (e.g., initially allowing the host to share memory with the accelerator), and coherence interfaces.

[0018] As used herein, unless expressly indicated otherwise, the singular forms “a / an” and “the” include both singular and plural references. Furthermore, the word “may” is used throughout this application in a permissive sense (i.e., possible, able) rather than in a mandatory sense (i.e., must). The term “comprising” and its derivatives mean “including but not limited to”. The term “coupled” means a direct or indirect connection. It should be understood that data can be transmitted, received, or exchanged via electronic signals (e.g., current, voltage, etc.), and the phrase “signal indicating [data]” refers to the data itself being transmitted, received, or exchanged in a physical medium.

[0019] The figures in this document follow a numbering rule, where the first one or more digits correspond to the figure number, and the remaining digits identify elements or components in the figure. Similar elements or components between different figures can be identified by using similar digits. For example, 110 could represent... Figure 1 Component "10" in the text, and similar components can be found in the text. Figure 2 The symbol is represented as 210. Hyphens and additional numbers or letters can be used to refer to similar elements within the diagram. See, for example... Figure 1Elements 126-1, 126-2, and 126-M are used in the drawings. Such similar elements can generally be represented without hyphens and additional numbers or letters. For example, elements 126-1, 126-2, and 126-M can be collectively referred to as 126. As used herein, the designations “M,” “N,” “Q,” “P,” “S,” and “L,” especially with respect to the reference numerals in the drawings, indicate that several specific features so specified may be included. It should be understood that elements shown in the various embodiments herein may be added, interchanged, and / or removed to provide multiple additional embodiments of this disclosure. Furthermore, it should be understood that the scale and relative dimensions of the elements provided in the drawings are intended to illustrate certain embodiments of the invention and should not be construed as limiting.

[0020] Figure 1 This is a functional block diagram of a computing system 101 including a memory controller 100 according to several embodiments of the present disclosure. The memory controller 100 may include a front-end portion 104, a central controller portion 110 (e.g., alternatively referred to as a "central controller"), and a back-end portion 119. The computing system 101 may include a host 103 and memory devices 126-1, ..., 126-N coupled to the memory controller 100. In some embodiments, the memory controller 100 may act as a system controller for a memory system.

[0021] The front-end portion 104 includes interfaces and interface management circuitry for coupling the memory controller 100 to the host 103 via input / output (I / O) channels 102-1, 102-2, ..., 102-M, and circuitry for managing the I / O channels 102. Any number of I / O channels 102 may exist, such as eight, sixteen, or another number. In some embodiments, the I / O channel 102 may be configured as a single port. In at least one embodiment, the interface between the memory controller 100 and the host 103 may be a PCIe physical and electrical interface operating according to the CXL protocol.

[0022] The central controller section 110 may include and / or be referred to as a data management circuitry. The central controller section 110 may control the execution of memory operations in response to a request received from the host 103. Examples of memory operations include read operations for reading data from the memory device 122 or write operations for writing data to the memory device 122.

[0023] The central controller section 110 can generate error detection information and / or error correction information based on data received from the host 103. The central controller section 110 can perform error detection operations and / or error correction operations on data received from the host 103 or from the memory device 122.

[0024] Back-end portion 119 may include a media controller and a physical (PHY) layer coupling memory controller 100 to memory device 126. As used herein, the term "PHY layer" generally refers to the physical layer in the Open Systems Interconnection (OSI) model of a computing system. The PHY layer may be the first (e.g., lowest) layer of the OSI model and may be used to transmit data via a physical data transmission medium. The physical data transmission medium may include channels 125-1, ..., 125-N. In some embodiments, channel 125 may, for example, include a sixteen-pin data bus and a two-pin data mask inversion (DMI) bus, as well as other possible buses. Back-end portion 119 may exchange (e.g., transmit or receive) data with memory device 126 via data pins and exchange error detection information and / or error correction information with memory device 126 via DMI pins. The exchange of error detection information and / or error correction information may occur simultaneously with data exchange.

[0025] An example of memory device 126 is a dynamic random access memory (DRAM) operating according to a protocol such as Low Power Double Data Rate (LPDDRx), which may be referred to herein as an LPDDRx DRAM device, LPDDRx memory, etc. The "x" in LPDDRx refers to any generation of the protocol (e.g., LPDDR5). In at least one embodiment, at least one of memory devices 126-1 operates as an LPDDRx DRAM device with low-power features enabled, and at least one of memory devices 126-N operates as an LPDDRx DRAM device with at least one low-power feature disabled. In some embodiments, although memory device 126 is an LPDDRx memory device, memory device 126 does not include circuitry configured to provide low-power functionality to memory device 126, such as a Dynamic Voltage Frequency Scaling Core (DVFSC), a Subthreshold Current Reduction Circuit (SCRC), or other circuitry providing low-power functionality. Providing an LPDDRx memory device 126 without such circuitry can advantageously reduce the cost, size, and / or complexity of the LPDDRx memory device 126. By way of example, the LPDDRx memory device 126, which has a circuit system that provides reduced low-power functionality, can be used in applications other than mobile applications (e.g., if the memory is not intended for use in a mobile application, then some or all of the low-power functionality can be sacrificed to reduce the cost of producing the memory).

[0026] Back-end section 119 may include a switching circuit system (e.g., Figure 2 The switching circuit system 207 described herein may include one or more switches, such as multiplexers / demultiplexers (e.g., ...). Figure 3(Multiplexers / demultiplexers 335 and 337 as described herein). The central controller section 110 can control the switching circuitry to selectively allow (e.g., enable) a portion of the media controller in the back-end section 119 to access the memory device 126 via channel 125, while preventing (e.g., disabling) another portion of the media controller from accessing the memory device 126. The media controller group can be configured for different operating modes. Thus, by selectively allowing different portions of the media controller to access the memory device 126, the memory controller 100 can operate according to different operating modes (e.g., configurations).

[0027] In one operating mode, memory device 126 can be accessed in a manner that allows chip-hunting operations to be performed on data accessed from memory device 126. In different operating modes, memory device 126 may not necessarily be accessed in a manner that provides chip-hunting capabilities. The chip-hunting provided herein can protect the memory system (e.g., Figure 1 The memory system 101 shown is designed to prevent any single memory device 126 (chip) from failing and any multi-bit errors from any part of a single memory chip.

[0028] In some embodiments, the memory controller 100 may include a management unit 105 to initialize, configure, and / or monitor the characteristics of the memory controller 100. The management unit 105 may include an I / O bus for managing out-of-band data and / or commands, a management unit controller for executing instructions associated with initializing, configuring, and / or monitoring the characteristics of the memory controller, and a management unit memory for storing data associated with initializing, configuring, and / or monitoring the characteristics of the memory controller 100. As used herein, the term "out-of-band" generally refers to a transmission medium different from the primary transmission medium of the network. For example, out-of-band data and / or commands may be data and / or commands transmitted to the network using a transmission medium different from the transmission medium used to transmit data within the network.

[0029] Figure 2 This is a functional block diagram of a memory controller 200 according to several embodiments of the present disclosure. For example... Figure 2 As shown, the front-end portion 204 may include: an interface 206 comprising a plurality of I / O lanes 202-1, 202-2, ..., 202-M; and an interface management circuitry 208 for managing the interface 206. An example of the interface 206 is a Peripheral Component Interconnect (PCIe) 5.0 interface. In some embodiments, the memory controller 200 may receive access requests relating to at least one of cache memory 212 and memory devices 226-1, 226-2, ..., 226-(N-1), 226-N via the interface 206 according to the CXL protocol. The interface 206 may receive requests from the host (e.g., ...) via I / O lanes 202. Figure 1The host 103 shown receives data. The interface management circuitry 208 can use the CXL protocol to manage the interface 206 and can be referred to as the CXL interface management circuitry 208. The CXL interface management circuitry 208 can be coupled to the host via the PCIe interface 206.

[0030] The central controller section 210 (e.g., alternatively referred to as the "central controller") may be coupled to the interface management circuitry 208. The central controller section 210 may be configured to perform memory operations.

[0031] The central controller section 210 may include a security component 215 for encrypting data before it is stored in the storage device 226, and / or a cache memory 212. Examples of the security component may include, but are not limited to, software and circuitry configured to implement data encryption, data hashing, data masking, and data tokenization. In some embodiments, data may be encrypted using Advanced Encryption Standard (AES) encryption before it is stored in the cache memory 212.

[0032] Cache memory 212 can be configured to store data associated with the execution of memory operations, error detection information, error correction information, and / or metadata. An example of cache memory 212 is a thirty-two (32) path-associative cache containing multiple cache lines. The cache line size can be equal to or greater than the access granularity of memory controller 200 (e.g., 64 bytes for the CXL protocol). For example, each cache line can contain 256 bytes of data. In another example, each cache line can contain 512 bytes of data. The size of read and write requests in the CXL memory system can be 64 bytes. Therefore, data items in cache memory 212 can have 64 bytes of data. Each cache line can include 256 bytes. Therefore, multiple 64-byte requests can be stored in each cache line. In response to a request from the host, memory controller 200 can write 256 bytes of data to memory device 226. In some embodiments, the 256 bytes of data can be written in 64-byte blocks. Using cache memory 212 to store data associated with read or write operations improves the speed and / or efficiency of data access because cache memory 212 can prefetch data and store it in multiple 64-byte blocks in case of a cache miss. Instead of searching a separate memory device in case of a cache miss, data can be read from cache memory 212. Less time and energy are used to access prefetched data compared to the time and energy required when the memory system must search for data before accessing it.

[0033] Central controller section 210 may include error correction code (ECC) circuitry 216, which may be based on a slave device (e.g., Figure 1 The host 103 described herein receives data that generates error correction information and / or error detection information. In some embodiments, the generated error correction information and error detection information may be stored in various locations of the memory device 226. The ECC circuit system 216 may additionally use the error correction information and / or error detection information to perform error correction operations and / or error detection operations. The ECC circuit system 216 may be coupled to any one of the cache memory 212, the LPCK circuit system 214, or the security component 215.

[0034] Examples of error correction information can be parity check data used to correct for and / or detect the number of bit errors in data. For example, error correction information can correct for single errors and detect two-bit errors in data. Examples of error detection information can be cyclic redundancy check (CRC) data. Error detection operations using CRC data can be referred to as algebraic error detection. Error detection operations can involve using a check value generated by algebraic calculations of the data to be protected. Error detection operations can detect unintended changes to data by comparing a check value stored in association with the data with a check value calculated based on the data.

[0035] In some embodiments, error correction information and error detection information previously generated (at the central controller section 210) based on data later stored in a memory device 226 may be stored in the same memory device 226. When data is read from the memory device 226, the error correction information and / or error detection information may also be read, allowing the information to be used to correct and / or detect one or more bit errors in the data.

[0036] The central controller section 210 may include a low-power chip kill (LPCK) circuitry 214 coupled between cache memory 212 and ECC circuitry 216. The LPCK circuitry 214 may be configured to generate error correction information (e.g., LPCK parity) about data received from the host and store the LPCK parity in various / dedicated locations in memory device 226. Data sharing the same LPCK parity (e.g., used together to generate the LPCK parity) may be referred to as being striped together. The LPCK circuitry 214 may additionally use the LPCK parity to perform chip kill operations on the data. The LPCK circuitry 214 can be used to provide increased data reliability and correct errors in the data.

[0037] An example chip-based implementation for a memory controller 200, comprising eleven channels 225 and a 176-bit bus width coupled to eleven memory devices 226, may include writing data to eight of the eleven memory devices 226 and writing parity data to three of the eleven memory devices 226. Four codewords may be written, each consisting of eleven four-bit symbols, where each symbol belongs to a different memory device 226. A first codeword may include the first four-bit symbol of each memory device 226, a second codeword may include the second four-bit symbol of each memory device 226, a third codeword may include the third four-bit symbol of each memory device 226, and a fourth codeword may include the fourth four-bit symbol of each memory device 226. Multi-bit symbols (e.g., four-bit symbols) may be non-binary symbols. For example, a non-binary symbol with N bits may be a finite Galois field of 2... N One of the elements.

[0038] Three parity symbols allow the LPCK circuitry 214 to correct at most one symbol error and detect at most two symbol errors in each codeword. If only two parity symbols are added instead of three, the LPCK circuitry 214 can correct at most one symbol error but detect only one. In some embodiments, data symbols and parity symbols can be written to or read from memory device 226 in parallel. If every bit symbol in the die fails, only the bit symbols from that memory device 226 in the codeword will fail. This allows memory contents to be reconstructed even if one memory device 226 fails completely. LPCK is considered "real-time correction" because it corrects data without impacting performance by performing a repair operation.

[0039] The LPCK circuitry system 214 can be selectively enabled / disabled based on the operating mode of the memory controller 200 (e.g., via the central controller section 210). For example, if the memory controller 200 operates in LPCK mode, the central controller section 210 can disable the LPCK circuitry system 214; conversely, if the memory controller 200 operates in non-LPCK mode, the central controller section 210 can enable the LPCK circuitry system 214. Therefore, when the memory controller 200 operates in non-LPCK mode and when LPCK mode is disabled, data accessed from the memory device 226 can be provided to the front-end section 204 without performing LPCK on the data.

[0040] like Figure 2As shown, the memory controller 200 may include a back-end portion 219, which includes a media control circuitry 220 coupled to the data management circuitry 210. The media control circuitry 220 may include media controllers 221-1 and 221-2. The back-end portion 219 may include a physical (PHY) layer 222 having PHY memory interfaces 224-1, 224-2, ..., 224-(N-1), 224-N. Each PHY memory interface 224 is configured to couple to a corresponding memory device 226.

[0041] PHY layer 222 may be an LPDDRx memory interface. In some embodiments, each of the PHY memory interfaces 224 may include data and DMI pins. For example, each PHY memory interface 224 may include sixteen data pins and two DMI pins. Media control circuitry 220 may be configured to exchange data with the corresponding memory device 226 via the data pins. Media control circuitry 220 may be configured to exchange error correction information, error detection information, and / or metadata via the DMI pins, rather than exchanging such information via the data pins. The DMI pins can provide multiple functions, such as data masking, data bus transposition, and parity checking for read operations, by setting a mode register. The DMI bus uses bidirectional signaling. In some cases, each transmitted byte of data has a corresponding signal sent via the DMI pins for data selection. In at least one embodiment, data may be exchanged simultaneously with error correction information and / or error detection information. For example, 64 bytes of data may be exchanged (transmitted or received) via the data pins, while 35 bits of error detection information (and metadata) and 21 bits of error correction information may be exchanged via the DMI pins. Such embodiments reduce the overhead that would otherwise be present on the data input / output (e.g., also referred to in the field as "DQ") bus, in order to transmit error correction information, error detection information, and / or metadata.

[0042] Back-end portion 219 may couple PHY layer portion 222 to corresponding memory devices 226-1, 226-2, ..., 226-(N-1), 226-N. Each memory device 226 includes at least one array of memory cells. In some embodiments, memory device 226 may be a group of memory dies, some of which are coupled to corresponding channels to transmit data stored in memory device 226. For example, memory device 226 may include four memory dies, two of which are coupled to corresponding channels 225 so that data stored in the memory dies of memory device 226 can be transmitted through those two memory dies.

[0043] In some embodiments, memory device 226 may be a different type of memory. Media control circuitry 220 may be configured to control at least two different types of memory. For example, memory devices 226-1 and 226-2 may be LPDDRx memories operating according to a first protocol, and memory devices 226-(N-1) and 226-N may be LPDDRx memories operating according to a second protocol different from the first protocol. In such an example, a first media controller 221-1 may be configured to control memory devices 226-1 and 226-2 of a first subgroup according to the first protocol, and a second media controller 221-2 may be configured to control memory devices 226-(N-1) and 226-N of a second subgroup according to the second protocol. In a particular example, memory devices 226-1 and 226-2 may have an onboard error correction circuitry system.

[0044] Back-end section 219 may include a switching circuit system 207. The switching circuit system 207 may include several switches, such as several multiplexers and / or demultiplexers coupled between the media control circuit system 220 and the PHY layer 222 and / or between the ECC circuit system 216 (e.g., Figure 3 (Multiplexers / demultiplexers 335 and 337 as described herein). In an example, the central controller section 210 controls the multiplexers and demultiplexers of each group of the switching circuitry system 207 to couple the first group of media controllers 221 to the PHY memory interface 224 for operation in a first operating mode (e.g., LPCK mode), and to couple the second (e.g., a different) group of media controllers 221 to the PHY memory interface 224 for operation of the computing system 101 in a second operating mode (e.g., non-LPCK mode).

[0045] In LPCK mode, each media controller 221 (configured to access memory device 226 in LPCK mode) accesses striped data and parity symbols (e.g., symbols to be processed together for LPCK) from multiple memory devices together and aligns those symbols before transmitting (e.g., providing) them together to the central controller section 210 (e.g., ECC circuitry 216). Alternatively, the media controller 221 waits to receive all the data and parity symbols from memory device 226 before transmitting them to the central controller section 210.

[0046] In non-LPCK mode, each media controller 221 (configured to access memory device 226 according to non-LPCK mode) accesses one or more memory devices and additionally transmits the accessed data to the central controller section 210 (e.g., ECC circuitry 216) in the order of its reception without having to wait to receive all the data striped together and distributed across multiple memory devices.

[0047] The memory controller 200 may include a management unit 205 configured to initialize, configure, and / or monitor the characteristics of the memory controller 200. In some embodiments, the management unit 205 includes a system management (SM) bus 238. The SM bus 238 may manage out-of-band data and / or commands. The SM bus 238 may be a serial presence detection portion. In some embodiments, the SM bus 238 may be a single-ended simple two-wire bus for lightweight communication purposes. The management unit 205 may include a CPU subsystem 240, which may act as a controller for the management unit to execute instructions associated with initializing, configuring, and / or monitoring the characteristics of the memory controller 200. The management unit 205 may include a hybrid circuit system 242, such as local memory storing code and / or data associated with managing and / or monitoring the characteristics of the memory controller 200. The endpoints of the management unit 205 may be exposed to a host system (e.g., Figure 1 The host 103 shown in the figure manages the data. In some embodiments, the characteristics monitored by the management unit 205 may include the voltage supplied to the memory controller 200 and / or the temperature measured by an external sensor. The management unit 205 may include interconnects 236, such as an Advanced High Performance Bus (AHB), to couple different components of the management unit 205.

[0048] Management unit 205 may include circuitry for managing in-band data (e.g., data transmitted over a primary transmit medium within a network (e.g., a local area network (LAN))). In some embodiments, CPU subsystem 240 may be compliant with Joint Test Action Group (JTAG) standards and inter-integrated circuit (IIC) protocols. 2 C or I 3 C) Controllers for protocol and auxiliary I / O circuitry systems. JTAG generally refers to an industry standard used for verifying and testing printed circuit boards after manufacturing. 2 C typically refers to a serial protocol used for two-wire interfaces to connect low-speed devices such as microcontrollers, I / O interfaces, and other similar peripherals in embedded systems. In some embodiments, an auxiliary I / O circuitry may couple the management unit 205 to the memory controller 200. Furthermore, firmware for operating the management unit may be stored in the hybrid circuitry 242. In some embodiments, the hybrid circuitry 242 may be a flash memory, such as flash NOR memory or other persistent flash memory devices.

[0049] Figure 3 This is a functional block diagram of a portion of a memory controller 300 according to several embodiments of the present disclosure. The memory controller 300 may include a front-end portion 304, a central controller portion 310 (e.g., alternatively referred to as a "central controller"), and a back-end portion 319. The front-end portion 304 may include: an interface 306 having a plurality of I / O channels 302-1, 302-2, ..., 302-M; and an interface management circuitry 308 for managing the interface 306. The central controller portion 310 may include a security component 315, a cache memory 312, LPCK encoders 341-1, ..., 341-L, and LPCK decoders 343-1, ..., 343-L. The LPCK encoder 341 may be configured for LPCK encoding, and the LPCK decoder 343 may be configured for LPCK decoding. LPCK encoding refers to encoding data by adding LPCK parity data (e.g., parity symbols to data). LPCK decoding refers to performing a chip-hunting operation on the data using the LPCK parity data.

[0050] The LPCK encoder 341 and decoder 343 can be Figure 2 The LPCK circuitry 214 described herein can be selectively enabled / disabled, for example, based on the operating mode under which the memory controller 300 operates. For instance, the LPCK encoder 341 and decoder 343 can be disabled when the memory controller 300 operates in a non-LPCK mode and enabled when the memory controller 300 operates in LPCK mode. The central controller section 310 may additionally include... Figure 2 The ECC encoder / decoder 318-1, ..., 318-S and 318-(S+1) of the ECC circuit system 216 described herein.

[0051] The back-end section 319 may include a media control circuitry system 320 and a PHY layer 322. The media control circuitry system 320 may include media controllers 331-1, ..., 331-3 and 333-1, ..., 333-Q-(P+1) similar to media controller 221. PHY layer 322 may include PHY memory interfaces 324-1-1, ..., 324-1-P, 324-2-1, ..., 324-2-P, 324-Q-1, ..., 324-QP and 324-Q-(P+1), which are configured to be coupled via channels 325-1-1, ..., 325-1-P, 325-2-1, ..., 325-2-P, 325-Q-1, ..., 325-QP and 325-Q-(P+1), collectively referred to as channel 325, to memory devices 326-1-1, ..., 326-1-P, 326-2-1, ..., 326-2-P, 326-Q-1, ..., 326-QP and 326-Q-(P+1), collectively referred to as memory devices 326. Although one memory device 326 is shown per channel 325, each memory device 326 may include, for example, multiple memory dies per channel 325.

[0052] Channels 325 may consist of a corresponding number of data lines (DQs) (also referred to as pins or pads). For example, each channel 325 may contain 16 DQs. As an example, each memory device 326 may include two x8 memory dies (e.g., a memory die with 8 DQs), each of which contributes 8 bits to fill the x16 channel 325.

[0053] The back-end section 319 may also include several switches. Figure 3 Each switch described in the document ( Figure 3 The “Mux / DeMux” shown may be a multiplexer or a demultiplexer, or both. In various embodiments, a switch may be coupled between the PHY memory interface 324 and media controllers 331 and 333. The back-end portion 319 may additionally include a switch 337 coupled between the ECC encoder / decoder 318 and media controllers 331 and 333. In some embodiments, switches 335 and / or 337 may include a Double Data Rate (DDR) Physical Interface (DFI) multiplexer or demultiplexer.

[0054] Media controllers 331 and 333 can be configured to access memory device 326 according to different protocols. For example, media controller 331 can be configured to access according to a protocol corresponding to LPCK mode (e.g., the LPCK protocol), and media controller 333 can be configured to access according to a protocol corresponding to non-LPCK mode. ECC encoder / decoder 318 and memory device 326 (e.g., memory devices 326-1-1, ..., 326-QP) can be coupled to only one set of media controllers based on the current operating mode of memory controller 300. For example, when LPCK mode is enabled so that memory controller 300 operates according to LPCK mode, media controller 331 can be coupled to ECC encoder / decoder 318 and memory device 326 (e.g., via switches 335 and 337), while media controller 333 is decoupled from ECC encoder / decoder 318 and memory device 326. Similarly, when the non-LPCK mode is enabled so that the memory controller 300 operates in the non-LPCK mode, the media controller 333 can be coupled to the ECC encoder / decoder 318 and the memory device 326 (e.g., via switches 335 and 337), while the media controller 331 is decoupled from the ECC encoder / decoder 318 and the memory device 326.

[0055] In the LPCK, the media controller 331 can be configured to access memory devices 326 that are configured for striping data and parity symbols together. Figure 3 In the embodiments described herein, memory devices 326-1-1, ..., 326-1-P are configured for a dataset and parity symbols to be striped together, memory devices 326-2-1, ..., 326-2-P are configured for different datasets and parity symbols to be striped together, and memory devices 326-Q-1, ..., 326-QP are configured for another different dataset and parity symbols to be striped together. In this example, media controller 331-1 may be configured to access memory devices 326-1-1, ..., 326-1-P according to the LPCK protocol, media controller 331-1 may be configured to access memory devices 326-2-1, ..., 326-2-P according to the LPCK protocol, and media controller 331-1 may be configured to access memory devices 326-Q-1, ..., 326-QP according to the LPCK protocol. Data and parity symbols stored together as units can be aligned at the corresponding media controller 331 and then further transmitted to the central controller section 310.

[0056] In non-LPCK mode, media controllers 333-1-1, ..., 333-1-P can be configured to access memory devices 326-1-1, ..., 326-1-P respectively; media controllers 333-2-1, ..., 333-2-P can be configured to access memory devices 326-2-1, ..., 326-2-P respectively; media controllers 333-Q-1, ..., 333-QP can be configured to access memory devices 326-Q-1, ..., 326-QP respectively; and media controller 333-Q-(P+1) can be configured to access memory device 326-Q-(P+1). Figure 3 In the embodiments described herein, there is a 1:1:1 dependency between the ECC encoder / decoder 318, the media controller 333, and the memory device 326. The PHY memory interface 324-Q-(P+1) and the ECC encoder / decoder 318-(S+1) are coupled only to the media controller 333-Q-(P+1) and not to the switch 335 so as to be configured for use in only one operating mode (e.g., non-LPCK mode).

[0057] Memory device 326 can be configured for multiple LPCK channels. As used herein, an LPCK channel refers to a group of memory devices / memory dies that store striped data and parity symbols together. For example, in LPCK mode, memory device 326 can be configured for three separate LPCK channels (a first LPCK channel containing a set of memory devices 326-1-1, ..., 326-1-P, a second LPCK channel containing a set of memory devices 326-2-1, ..., 326-2-P, and a third LPCK channel containing a set of memory devices 326-3-1, ..., 326-3-P), where each LPCK channel contains five memory devices, and each LPCK channel is 80 bits wide (e.g., each channel 325 is 16 bits wide). In non-LPCK mode, each memory device 326 can be configured for a channel (e.g., a non-LPCK channel).

[0058] In a non-limiting instance, the device may include multiple media controllers (e.g., Figure 2 The first group of media controllers (e.g., in the media controller 221 described herein) Figure 3 and Figure 4 Media controllers 331 and 431 as described herein. The first group can be coupled to multiple memory devices (e.g., respectively in...). Figure 1 , Figure 2 , Figure 3 and Figure 4 The memory devices 126, 226, 326, 426 described herein are configured to access the plurality of memory devices in accordance with a chip hunting protocol.

[0059] The device may additionally include a second set of media controllers from the plurality of media controllers (e.g., respectively in...). Figure 3 and Figure 4 The media controllers 333 and 433 described herein, the second group being coupled to multiple memory devices and configured to access multiple memory devices according to a non-chip-hunting protocol. (e.g., in...) Figure 1 , Figure 2 , Figure 3 and Figure 4 The central controller sections 110, 210, 310, and 410 described herein are coupled to multiple media controllers.

[0060] The controller can be configured to enable the first set of media controllers to access multiple memory devices according to a chip-hunting protocol when the second set of media controllers is disabled. The controller can be further configured to enable the second set of media controllers to access multiple memory devices according to a non-chip-hunting protocol when the first set of media controllers is disabled.

[0061] Each media controller in the first group of media controllers may be coupled to a corresponding set of memory devices in a plurality of memory devices. Each media controller in the first group of media controllers may be configured to access a striped subset of data from the corresponding set of memory devices for chip kill operations. In this example, each media controller in the first group of media controllers may be configured to align the data subset and wait until each data subset is received from each of the corresponding set of memory devices before providing the data subset to the controller.

[0062] The media controllers for the first and second groups can be connected via one or more multiplexers or one or more multiplexers or both (e.g., ...). Figure 3 The multiplexer / demultiplexer 335 described herein is coupled to a plurality of memory devices. In this example, the controller may be configured to couple a first set of media controllers, rather than a second set of media controllers, to a plurality of memory devices using one or more multiplexers or one or more multiplexers or both, to access the plurality of memory devices according to a chip-hunting protocol. Alternatively, the controller may be configured to couple a second set of media controllers, rather than a first set of media controllers, to a plurality of memory devices using one or more multiplexers or one or more multiplexers or both, to access the plurality of memory devices according to a non-chip-hunting protocol. In some embodiments, the plurality of memory devices may include one or more additional memory devices not coupled to the first set of media controllers (e.g., ...). Figure 3 The memory device 326-Q-(P+1) described herein or Figure 4 The memory devices 426-16 described herein.

[0063] In another non-limiting example, a device may include a plurality of memory devices (e.g., respectively in...). Figure 1 , Figure 2 , Figure 3 and Figure 4 The memory devices 126, 226, 326, 426 described herein and the memory controller (e.g., respectively in...) Figure 1 , Figure 2 , Figure 3 and Figure 4 The memory controllers 100, 200, 300, and 400 described herein. The first part of the memory controller (e.g., in...) Figure 1 , Figure 2 , Figure 3 and Figure 4 The back-end portions 119, 219, 319, and 419 described herein may include multiple physical memory interfaces (e.g., respectively in...). Figure 2 , Figure 3 and Figure 4 The PHY memory interfaces 224, 324, and 434 described herein and multiple media controllers (e.g., Figure 2 Media controller 221 as described herein). Multiple media controllers may include a first set of media controllers (e.g., in [location not specified]) that can be coupled to at least a portion of multiple memory devices via a portion of a multiple physical memory interface. Figure 3 and Figure 4 The media controllers 331 and 431 described herein, and a second set of media controllers (e.g., in [location not specified]) that can be coupled to multiple memory devices via multiple physical memory interfaces. Figure 3 and Figure 4 Media controllers 333 and 433 as described herein). The first part of the memory controller may additionally include one or more switches coupled between the multiple media controllers and multiple physical memory interfaces (e.g., Figure 3 Switches 335 and 337 are described in the document.

[0064] The second part of the memory controller (e.g., in...) Figure 1 , Figure 2 , Figure 3 and Figure 4The central controller portions 110, 210, 310, and 410 described herein are coupled to a first portion of the memory controller. A second portion of the memory controller may be configured to control one or more switches to couple portions of the first set of media controllers to multiple physical memory interfaces, allowing the first set of media controllers to access at least a portion of the multiple memory devices according to a chip-hunting protocol. The second portion of the memory controller may be further configured to couple a second set of media controllers to the multiple physical memory interfaces, allowing the second set of media controllers to access the multiple memory devices according to a non-chip-hunting protocol.

[0065] In other words, the second part of the memory controller can be configured to control one or more switches to decouple the second set of media controllers from the multiple physical memory interfaces, allowing the first set of media controllers to access at least a portion of the multiple memory devices according to a chip-hunting protocol. The second part of the memory controller can be further configured to control one or more switches to partially decouple the first set of media controllers from the multiple physical memory interfaces, allowing the first set of media controllers to access at least a portion of the multiple memory devices according to a non-chip-hunting protocol.

[0066] One or more switches may be the first group of switches (e.g., Figure 3 The switch 335 described herein), and the first part of the memory controller further includes a second set of switches coupled between a plurality of media controllers and a second part of the memory controller (e.g., Figure 3 (Switch 337 as described herein). In this example, the second portion of the memory controller can be configured to control the second set of switches to couple the first set of media controllers to the second portion of the memory controller, allowing the first set of media controllers to access at least a portion of a plurality of memory devices according to a chip-hunting protocol. Alternatively, in this example, the second portion of the memory controller can be configured to control the second set of switches to couple the second set of media controllers to the second portion of the memory controller, allowing the second set of media controllers to access at least a portion of a plurality of memory devices according to a non-chip-hunting protocol. In some embodiments, one or more switches include a Double Data Rate (DDR) Physical Interface (DFI) multiplexer or demultiplexer.

[0067] In some embodiments, the respective media controllers in the first group of media controllers (e.g., respectively in...) Figure 3 and Figure 4 The media controllers 331 and 431 described herein can be configured to receive a subset of data from a respective memory device of at least a portion of the plurality of memory devices and to receive parity data from a respective memory device of at least a portion of the plurality of memory devices. In this example, the second portion of the memory controller (e.g., respectively in...) Figure 1 , Figure 2 , Figure 3and Figure 4 The central controller sections 110, 210, 310, and 410 described herein can be configured to receive data subsets and parity data from the respective media controllers and perform a chip-hunting operation on the data subsets using the parity data. Additionally, in this example, the respective media controllers in the first group of media controllers can be configured to prevent subsets of data from being provided to the second part of the memory controller unless each subset of the data subset is received at the respective media controller in the first group of media controllers.

[0068] Figure 4 This is a functional block diagram illustrating a portion of a memory controller 400 comprising a central controller portion 410 (e.g., alternatively referred to as "central controller") and a back-end portion 419 according to several embodiments of the present disclosure. The central controller portion 410 may include an LPCK circuitry system 414 and an ECC encoder / decoder 418-1, ..., 418-8. The back-end portion 419 may include PHY memory interfaces 424-1, ..., 424-16 and memory devices 426-1, ..., 426-16 coupled to the respective PHY memory interfaces 424 via corresponding channels 425-1, ..., 425-16 (collectively referred to as channel 425). As described herein, memory devices 426-1, ..., 426-16 (collectively referred to as memory device 426) may include a number of memory dies, wherein at least some (e.g., two) of the memory dies are coupled to the respective channels 425 for exchanging data stored in memory device 426.

[0069] Media controllers 431-1, 431-2, and 431-3 can be similar to Figure 3 The media controller 331 described herein is configured to access the memory device 426 according to the LPCK protocol when LPCK mode is enabled. Additionally, media controllers 433-1, ..., 433-8 may be similar to... Figure 3 The media controller 333 described herein is configured to access the memory device 426 according to the non-LPCK protocol when non-LPCK mode is enabled.

[0070] When LPCK mode is enabled, media controller 331 can be coupled to the corresponding ECC encoder / decoder 318 and PHY media interface 424. Conversely, when non-LPCK mode is enabled (disabling LPCK mode), media controller 331 can be coupled to ECC encoder / decoder 318 and PHY media interface 424. Media controllers 431 and 433 can be coupled via one or more multiplexers / demultiplexers 435 (…). Figure 4 The "Mux / DeMux" shown is coupled to the corresponding PHY memory interface 424, and the multiplexer / demultiplexer 435 may include Figure 3 The document describes several switches 335.

[0071] exist Figure 4 In the embodiments described herein, media controller 431 may be coupled to a set of PHY memory interfaces 424, each of which is further coupled to a corresponding memory device 426 configured for striped data and parity symbols. For example, when LPCK mode is enabled, media controller 431-1 may be coupled to PHY memory interfaces 424-1, ..., 424-5 (which are further coupled to memory devices 426-1, ..., 426-5), media controller 431-2 may be coupled to PHY memory interfaces 424-6, ..., 424-10 (which are further coupled to memory devices 426-6, ..., 426-10), and media controller 431-3 may be coupled to PHY memory interfaces 424-11, ..., 424-15 (which are further coupled to memory devices 426-11, ..., 426-15).

[0072] Data accessed by each media controller 431 may be aligned at the respective media controller 431 before being transmitted to the central controller section 410. For example, data accessed from memory devices 431-1 to 431-5 may be aligned at media controller 431-1 before being transmitted to the central controller section 410, data accessed from memory devices 431-6 to 431-10 may be aligned at media controller 431-2 before being transmitted to the central controller section 410, and data accessed from memory devices 431-11 to 431-15 may be aligned at media controller 431-3 before being transmitted to the central controller section 410.

[0073] In addition, Figure 4In the embodiments described herein, the media controller 433 may be coupled to different sets of PHY memory interfaces 424. For example, when non-LPCK mode is enabled, media controller 433-1 can be coupled to PHY memory interfaces 424-1 and 424-2, media controller 433-2 can be coupled to PHY memory interfaces 424-3 and 424-4, media controller 433-3 can be coupled to PHY memory interfaces 424-5 and 424-6, media controller 433-4 can be coupled to PHY memory interfaces 424-7 and 424-8, media controller 433-5 can be coupled to PHY memory interfaces 424-9 and 424-10, media controller 433-6 can be coupled to PHY memory interfaces 424-11 and 424-12, media controller 433-7 can be coupled to PHY memory interfaces 424-13 and 424-14, and media controller 433-8 can be coupled to PHY memory interfaces 424-15 and 424-16. The data accessed by each media controller 433 may not be aligned at the corresponding media controller 433, but may be transmitted to the central controller section 410, for example, in the order of reception.

[0074] exist Figure 4 In the embodiments described herein, in LPCK mode, memory devices 426-1, ..., 426-5 may be configured for a first LPCK channel, memory devices 426-1, ..., 426-5 may be configured for a second LPCK channel, and memory devices 426-1, ..., 426-5 may be configured for a third LPCK channel. In non-LPCK mode, each memory device 426 may be configured for a channel (e.g., a non-LPCK channel) such that memory device 426 is configured for sixteen non-LPCK channels.

[0075] Figure 5 This is a flowchart of a method 550 for accessing a memory device in different operating modes according to several embodiments of the present disclosure. The method 550 may be executed by processing logic, which may include hardware (e.g., processing device, circuit system, dedicated logic, programmable logic, microcode, device hardware, integrated circuit, etc.), software (e.g., instructions that run or execute on the processing device), or a combination thereof. In some embodiments, the method 550 is executed by processing logic in different operating modes. Figure 1 , Figure 2 , Figure 3 and Figure 4The memory controllers 100, 200, 300, and 400 described herein execute the procedures. Although shown in a specific order or sequence, the order of the processes may be modified unless otherwise specified. Therefore, it should be understood that the illustrated embodiments are merely examples, and the illustrated processes may be performed in different orders, and some processes may be performed in parallel. Furthermore, one or more processes may be omitted in various embodiments. Therefore, not all processes are required in every embodiment. Other process flows are also possible.

[0076] At position 552, a central controller can be used (e.g., separately in...). Figure 1 , Figure 2 , Figure 3 and Figure 4 The central controller portions 110, 210, 310, and 410 described herein, and the first set of media controllers (e.g., respectively coupled to the central controller and the respective sets of memory devices in the plurality of memory devices) are coupled to the central controller and the plurality of memory devices. Figure 3 and Figure 4 The media controllers 331 and 431 described herein access multiple memory devices (e.g., in different modes) in a first mode (e.g., LPCK mode). Figure 1 , Figure 2 , Figure 3 and Figure 4 (Memory devices 126, 226, 326, 426 as described herein). For example, in order to access multiple memory devices in a first mode, the first set of media controllers can be enabled by coupling a first set of media controllers, rather than a second set of media controllers, to the multiple memory devices.

[0077] At position 554, a central controller and a second set of media controllers, each coupled to a corresponding memory device in the central controller and multiple memory devices, can be used (e.g., respectively in...). Figure 3 and Figure 4 The media controllers 333 and 433 described herein access multiple memory devices in a second mode (e.g., non-LPCK mode). For example, in order to access multiple memory devices in the second mode, the first set of media controllers can be enabled by coupling the second set of media controllers, instead of the first set of media controllers, to the multiple memory devices.

[0078] When accessing multiple memory devices in LPCK mode (alternatively referred to as chip-hunting mode), a striped subset of data can be received from multiple memory devices. This data subset can then be aligned at a corresponding media controller in a first set of media controllers before being provided to the controller.

[0079] When accessing multiple memory devices in a non-LPCK mode (alternatively referred to as non-chip hunter mode), each media controller in the second set of media controllers may receive a subset of data from one or more of the memory devices. Subsequently, the data subsets may be provided to the controller in the order in which they are received at the respective media controller in the second set of media controllers.

[0080] Figure 6 This is a flowchart of a method 660 for accessing a memory device in different operating modes according to several embodiments of the present disclosure. The method 660 can be executed by processing logic, which may include hardware (e.g., processing device, circuit system, dedicated logic, programmable logic, microcode, device hardware, integrated circuit, etc.), software (e.g., instructions that run or execute on the processing device), or a combination thereof. In some embodiments, the method 660 is executed by... Figure 1 , Figure 2 , Figure 3 and Figure 4 The memory controllers 100, 200, 300, and 400 described herein execute the procedures. Although shown in a specific order or sequence, the order of the processes may be modified unless otherwise specified. Therefore, it should be understood that the illustrated embodiments are merely examples, and the illustrated processes may be performed in different orders, and some processes may be performed in parallel. Furthermore, one or more processes may be omitted in various embodiments. Therefore, not all processes are required in every embodiment. Other process flows are also possible.

[0081] At position 662, the first group of media controllers can be enabled (e.g., respectively in...). Figure 3 and Figure 4 The media controllers 331 and 431 described herein are used to utilize a central controller (e.g., respectively in...). Figure 1 , Figure 2 , Figure 3 and Figure 4 The central controller sections 110, 210, 310, and 410 described herein access multiple memory devices (e.g., respectively in...) according to the chip hunting protocol. Figure 1 , Figure 2 , Figure 3 and Figure 4 The memory devices 126, 226, 326, and 426 described herein can be used to enable the first set of media controllers by coupling the first set of media controllers to the multiple memory devices and decoupling the second set of media controllers from the multiple memory devices.

[0082] At position 664, a second set of media controllers can be enabled (e.g., separately in...). Figure 3 and Figure 4The media controllers 333 and 433 described herein are used to access multiple memory devices using a central controller and according to a non-chip-hunting protocol. The second set of media controllers can be enabled by coupling a second set of media controllers to the multiple memory devices and decoupling the first set of media controllers from the multiple memory devices.

[0083] In some embodiments, each of the plurality of memory devices may be coupled to a corresponding switch, which is further coupled to a corresponding media controller in a first group of media controllers and a corresponding media controller in a second group of media controllers. In this example, method 660 may additionally include (for accessing the plurality of memory devices by coupling according to a chip-hunting protocol) using a corresponding switch to couple a corresponding media controller in the first group of media controllers to a memory device in the plurality of memory devices and using a corresponding switch to decouple a corresponding media controller in the second group of media controllers from a memory device in the plurality of memory devices.

[0084] In some embodiments, each media controller in the first group of media controllers, when enabled, may be coupled to a corresponding set of memory devices in a plurality of memory devices storing a striped subset of data together. In this example, method 660 may include accessing a subset of data from the corresponding set of memory devices.

[0085] In some embodiments, each media controller in the first group of media controllers may be further coupled to the controller when enabled. In this example, method 660 may additionally include preventing at least one subset of the data subset or parity data from being provided to the controller unless a subset of data is received and aligned at the respective media controller.

[0086] While specific embodiments have been shown and described herein, those skilled in the art will understand that arrangements calculated to achieve the same results may replace the specific embodiments shown. This disclosure is intended to cover modifications or variations of one or more embodiments of this disclosure. It should be understood that the above description has been carried out illustratively and not restrictively. Combinations of the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art upon review of the above description. The scope of one or more embodiments of this disclosure includes other applications in which the above structures and processes are used. Therefore, the scope of one or more embodiments of this disclosure should be determined with reference to the appended claims together with the full scope of the equivalents given by such claims.

[0087] In the foregoing detailed embodiments, some features are grouped together in a single embodiment for the purpose of simplifying this disclosure. This approach of the disclosure should not be construed as reflecting an intention that the disclosed embodiments must use more features than expressly stated in each claim. In fact, as reflected in the appended claims, the subject matter of the invention lies in less than all the features of a single disclosed embodiment. Therefore, the appended claims are hereby incorporated into the detailed embodiments, wherein each claim is, in itself, a separate embodiment.

Claims

1. A method comprising: Using a central controller and a first set of media controllers, each coupled to a set of corresponding memory devices in the central controller and the plurality of memory devices, access the plurality of memory devices in a first mode, wherein the first mode corresponds to a chip hunting mode; and Using the central controller and a second set of media controllers different from the first set of media controllers, the plurality of memory devices are accessed in the second mode by the following operations: A subset of data is received from one or more of the plurality of memory devices through each of the media controllers in the second group of media controllers; and The data subsets are provided to the controller in the order in which they are received at the respective media controllers in the second group of media controllers, wherein each media controller in the second group is coupled to the central controller and a respective memory device in the plurality of memory devices.

2. The method of claim 1, further comprising enabling the first set of media controllers in order to access the plurality of memory devices in the first mode by coupling the first set of media controllers to the plurality of memory devices instead of coupling the second set of media controllers to the plurality of memory devices.

3. The method of claim 1, further comprising enabling the first set of media controllers by coupling the second set of media controllers to the plurality of memory devices instead of the first set of media controllers to the plurality of memory devices in order to access the plurality of memory devices in the second mode.

4. The method according to claim 1, wherein: Accessing the plurality of memory devices in the first mode using the first set of media controllers includes: Receive a striped subset of data from multiple memory devices among the plurality of memory devices; and Before providing the data subset to the controller, the data subset is aligned at the corresponding media controller in the first group of media controllers.

5. The method according to claim 1, wherein: The second mode is the non-chip hunting mode.

6. An apparatus comprising: A first group of media controllers in a plurality of media controllers, the first group of media controllers being coupled to a plurality of memory devices and configured to access the plurality of memory devices in accordance with a chip hunting protocol; The second group of media controllers in the plurality of media controllers, the second group of media controllers being coupled to the plurality of memory devices and configured to access the plurality of memory devices in accordance with a non-chip hunting protocol; and A controller coupled to the plurality of media controllers, the controller being configured to enable the first group of media controllers to access the plurality of memory devices in accordance with the chip hunting protocol when the second group of media controllers is deactivated.

7. The device of claim 6, wherein the controller is configured to enable the second set of media controllers to access the plurality of memory devices in accordance with the non-chip-hunting protocol when the first set of media controllers is deactivated.

8. The device according to claim 6, wherein: When each media controller in the first group of media controllers is coupled to a corresponding set of memory devices in the plurality of memory devices, each media controller in the first group of media controllers is configured to access a striped subset of data from the corresponding set of memory devices for chip hunting operations.

9. The device of claim 8, wherein each media controller in the first set of media controllers is configured to align with the data subset and wait until each of the data subset is received from each of the respective sets of memory devices before further providing the data subset to the controller.

10. The device according to claim 6, wherein: The first group of media controllers and the second group of media controllers may be coupled to the plurality of memory devices via one or more multiplexers or one or more multiplexers or both.

11. The device of claim 10, wherein the controller is configured to couple the first set of media controllers, rather than the second set of media controllers, to the plurality of memory devices using the one or more multiplexers or one or more multiplexers or both, to access the plurality of memory devices in accordance with the chip-hunting protocol.

12. The device of claim 10, wherein the controller is configured to couple the second set of media controllers, rather than the first set of media controllers, to the plurality of memory devices using the one or more multiplexers or one or more multiplexers or both, to access the plurality of memory devices in accordance with the non-chip-hunting protocol.

13. The device of claim 6, wherein the plurality of memory devices further includes one or more additional memory devices not coupled to the first set of media controllers.

14. The device of claim 6, wherein the device includes a memory controller coupled to a host, and wherein the memory controller includes the controller and the first and second sets of media controllers.

15. A method comprising: To access multiple memory devices, the central controller enables the first group of media controllers according to the chip hunting protocol by performing the following operations: Couple the first group of media controllers to the plurality of memory devices; and Discouple the second group of media controllers from the plurality of memory devices; In order to access the plurality of memory devices, the central controller is used to enable the second group of media controllers according to a non-chip-hunting protocol by the following operations: Couple the second set of media controllers to the plurality of memory devices; and The first group of media controllers is disconnected from the plurality of memory devices.

16. The method of claim 15, wherein each of the plurality of memory devices is coupled to a corresponding switch, the switch being further coupled to a corresponding media controller in the first group of media controllers and a corresponding media controller in the second group of media controllers, and wherein the method further comprises, for accessing the plurality of memory devices, according to the chip hunting protocol: The corresponding media controller in the first group of media controllers is coupled to the memory device in the plurality of memory devices using the corresponding switch; and The corresponding switch is used to disconnect the corresponding media controller in the second group of media controllers from the memory device in the plurality of memory devices.

17. The method of claim 15, wherein: When enabled, each media controller in the first group of media controllers is coupled to a corresponding set of memory devices in the plurality of memory devices that store a striped subset of data together, and the method further includes accessing the data subset from the corresponding set of memory devices.

18. The method of claim 17, wherein each media controller in the first group of media controllers is further coupled to a controller when enabled, and the method further includes preventing at least one subset of the data subset or parity data from being provided to the controller unless a data subset is received and aligned at the respective media controller.

19. An apparatus comprising: Multiple memory devices; The first part of the memory controller includes: Multiple physical memory interfaces; Multiple media controllers, including: A first set of media controllers, which can be coupled to at least a portion of the plurality of memory devices via a portion of the plurality of physical memory interfaces; and A second set of media controllers, which can be coupled to the plurality of memory devices via the plurality of physical memory interfaces; and A switching circuit system coupled between the plurality of media controllers and the plurality of physical memory interfaces; and A second portion of the memory controller, coupled to the first portion of the memory controller, is configured to control the switching circuit system to perform the following operations: Couple the first set of media controllers to portions of the plurality of physical memory interfaces to allow the first set of media controllers to access at least portions of the plurality of memory devices according to a chip-hunting protocol; and The second set of media controllers is coupled to the plurality of physical memory interfaces to allow the second set of media controllers to access the plurality of memory devices according to a non-chip-hunting protocol.

20. The device of claim 19, wherein the second portion of the memory controller is configured to control the switching circuit system to perform the following operations: Disconnect the second group of media controllers from the plurality of physical memory interfaces to allow the first group of media controllers to access at least a portion of the plurality of memory devices according to the chip hunting protocol; and The first set of media controllers is decoupled from the portions of the plurality of physical memory interfaces to allow the first set of media controllers to access at least the portions of the plurality of memory devices according to the non-chip-hunting protocol.

21. The apparatus according to claim 19, wherein: The switching circuit system is a first set of switches, and the first part of the memory controller further includes a second set of switches coupled between the plurality of media controllers and the second part of the memory controller.

22. The device of claim 21, wherein the second portion of the memory controller is configured to control the second set of switches to perform the following operations: Couple the first set of media controllers to the second portion of the memory controller to allow the first set of media controllers to access at least said portions of the plurality of memory devices according to the chip-hunting protocol; and The second set of media controllers is coupled to the second portion of the memory controller to allow the second set of media controllers to access at least the portions of the plurality of memory devices in accordance with the non-chip-hunting protocol.

23. The device according to claim 19, wherein: The corresponding media controller in the first group of media controllers is configured to receive: A subset of data from at least the respective portions of the plurality of memory devices; and Parity check data from at least the portions of the plurality of memory devices.

24. The device of claim 23, wherein the second portion of the memory controller is configured to: Receive the data subset and the parity data from the corresponding media controller; and The parity data is used to perform a chip-hunting operation on the subset of data.

25. The device of claim 23, wherein the respective media controller in the first group of media controllers is configured to prevent a subset of the data subset from being provided to the second portion of the memory controller unless each subset of the data subset is received at the respective media controller in the first group of media controllers.

26. The device of claim 19, wherein the switching circuit comprises a Double Data Rate (DDR) Physical Interface (DFI) multiplexer or demultiplexer.

Citation Information

Patent Citations

  • Crypto-ransomware compromise detection

    CN110709843A

  • Non-volatile memory die data mirroring

    WO2017007487A1