Booting and initialization techniques for stacked memory architectures
By receiving commands at the common logic block of the memory system and performing initialization and evaluation operations through the interface block, the problem of inefficiency in initialization and evaluation in the stacked memory architecture is solved, and more efficient memory system performance is achieved.
Patent Information
- Application Number
- CN202410677246.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-05-22
- Filing Date
- 2024-05-29
- Publication Date
- 2024-12-03
AI Technical Summary
The prior art has problems of inefficiency and insufficient performance in the initialization and evaluation of stacked memory architectures, especially in terms of interface coordination between multi-layer semiconductor dies and correct operation of memory arrays.
Insuring the memory system's initialization or evaluation commands are performed by receiving initialization or evaluation commands at a common logical block of the memory system and accessing the memory array in corresponding channels through multiple interface blocks, initialization or evaluation operations, including row repair, column repair and TSV repair, to ensure the memory system's Efficient initialization and evaluation.
It improves the initialization and evaluation efficiency of the stacked memory architecture, improves system performance, ensures the correct operation and repair of the memory array, and improves the stability and reliability of the overall system.
Smart Images

Figure CN119068931A_ABST
Abstract
Description
[0001] Cross Reference
[0002] This patent application claims priority to U.S. Patent Application No. 18 / 671,485 (DAS Code: 6879) filed by ECKEL on May 22, 2024, entitled “BOOT AND INITIALIZATION TECHNIQUES FOR STACKED MEMORY ARCHITECTURES” and U.S. Provisional Patent Application No. 63 / 470,683 filed by ECKEL on June 2, 2023, entitled “BOOT AND INITIALIZATION TECHNIQUES FOR STACKED MEMORY ARCHITECTURES”, each of which is assigned to its assignee and the entire contents of each of which are expressly incorporated herein by reference.
[0003] The technical field relates to boot and initialization techniques for stacked memory architectures. Background Art
[0004] Memory devices are widely used to store information in devices such as computers, user devices, wireless communication devices, cameras, digital displays, and others. Information is stored by programming memory cells within the memory device to various states. For example, a binary memory cell is programmable to one of two supported states, typically represented by a logical 1 or a logical 0. In some instances, a single memory cell may support more than two states, either of which may be stored. To access stored information, a memory device may read (e.g., sense, detect, retrieve, determine) a state from a memory cell. To store information, a memory device may write (e.g., program, set, assign) a state to a memory cell.
[0005] There are various types of memory devices, including magnetic hard disks, random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), self-selection memory, chalcogenide memory technology, NOR and NAND memory devices, and others. Memory cells can be described in terms of volatile configurations or non-volatile configurations. Memory cells in non-volatile configurations can maintain a stored logic state for a long time, even in the absence of external power. Memory cells in volatile configurations lose their stored state when disconnected from external power. Summary of the invention
[0006] A method is described. The method may include: receiving an initialization command at a common logic block of a first semiconductor die of a memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access one or more respective memory arrays of one or more second semiconductor die of the memory system via a set of respective one or more channels; outputting an indication of an instruction for each of the plurality of interface blocks based on receiving the initialization command; receiving the instruction by each of the plurality of interface blocks based on the indication; and performing one or more respective initialization operations by each of the plurality of interface blocks based on the interface block receiving the instruction.
[0007] An apparatus is described. The apparatus may include: a first semiconductor die of a memory system, the first semiconductor die including: a common logic block; and a plurality of first interface blocks coupled to the common logic block; and one or more second semiconductor dies of the memory system coupled to the first semiconductor die and including: a plurality of second interface blocks, each second interface block coupled to a respective one of the plurality of first interface blocks via a set of respective one or more channels; and a plurality of memory arrays, each memory array coupled to one of the plurality of second interface blocks, wherein the common logic block includes logic circuitry operable to initiate initialization of the plurality of first interface blocks.
[0008] A method is described. The method may include: receiving an evaluation command at a common logic block of a first semiconductor die of a memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access one or more respective memory arrays of one or more second semiconductor die of the memory system via a set of respective one or more channels; outputting an indication of an evaluation operation to each of the plurality of interface blocks based on receiving the evaluation command, the evaluation operation associated with evaluating an access operation associated with the one or more respective memory arrays; receiving, by each of the plurality of interface blocks, an instruction for the evaluation operation based on the indication; and initiating, by each of the plurality of interface blocks, a portion of the evaluation operation based on receiving the instruction.
[0009] A method is described. The method may include: determining to initialize a memory system at a common logic block of a first semiconductor die of a memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access one or more respective memory arrays of one or more second semiconductor die of the memory system; outputting an indication of one or more instructions associated with initializing the memory system to each of the plurality of interface blocks based on determining to initialize the memory system; receiving the one or more instructions by each of the plurality of interface blocks based on outputting the indication; and initiating a portion of the one or more instructions by each of the plurality of interface blocks based on receiving the one or more instructions. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 An example of a system supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown.
[0011] Figure 2 An example of a system supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown.
[0012] Figure 3 An example of a system supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown.
[0013] Figure 4 An example of a process flow supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown.
[0014] Figure 5 An example of a process flow supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown.
[0015] Figure 6 A block diagram of a memory system supporting boot and initialization techniques for a stacked memory architecture is shown according to examples disclosed herein.
[0016] Figures 7 to 9 A flow chart illustrating a method of supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown. DETAILED DESCRIPTION
[0017] Some memory systems may include a semiconductor die stack that includes one or more memory dies above a logic die that is operable to access a set of memory arrays distributed across the one or more memory dies. The logic die may include one or more interface blocks (e.g., memory interface blocks (MIBs), interface circuitry), which may each be operable to access a respective subset of the set of memory arrays (e.g., via a set of respective one or more channels). This architecture may be implemented as part of a tightly coupled dynamic random access memory (TCDRAM) system, and may support solutions for memory-centric logic, such as a graphics processing unit (GPU), and other implementations. In some examples, the TCDRAM system may be tightly coupled (e.g., physically coupled, electrically coupled) to a processor (e.g., a GPU or other host) as part of a physical memory map accessible to the processor. This coupling may include one or more processors implemented in the same semiconductor die as at least a portion of the TCDRAM system (e.g., the same die as the one or more interface blocks, as part of the logic die) or a processor implemented in a die that is directly coupled (e.g., fused) to another die that includes at least a portion of the TCDRAM system. Unlike cache-based memory, TCDRAM cannot be backed by an external memory hierarchy with the same physical address. For example, TCDRAM may be associated with and located within a dedicated base address, where each portion of the TCDRAM may not overlap within the address.
[0018] According to examples disclosed herein, a memory system (e.g., a TCDRAM system) may include a common logic block (e.g., a logic circuit system) that is operable to output an indication to each of a set of multiple interface blocks to perform an initialization procedure, an evaluation procedure, or both. For example, the common logic block may receive a command to initialize or evaluate an operation associated with one or more memory arrays of the memory system (e.g., from a host system, from an external device). The common logic block may output an indication of a set of instructions (e.g., one or more programs) associated with the initialization or evaluation. The interface block may use the received indication (e.g., from a non-volatile storage device of the memory system) to obtain the instruction and perform (e.g., start) one or more operations associated with the obtained instruction. In some examples, the common logic block may output an indication in response to identifying a power-on condition (e.g., as part of a boot protocol). In some cases, the one or more operations may include evaluating the interface block, the memory array, or both for correct operation, for establishing a trim setting (e.g., for accessing a memory cell of the memory array), for determining whether to repair a component of the memory system (e.g., row repair, column repair, through silicon via (TSV) repair), or any combination thereof. Such techniques may support efficient initialization and evaluation of a memory system (eg, of an interface block), which may improve performance of the memory system or a system including the memory system (eg, in conjunction with a host system).
[0019] First, in reference Figures 1 to 5 Features of the present disclosure are described in the context of systems, dies, and process flows. Figures 6 to 9 These and other features of the present disclosure are further illustrated and described in the context of the device diagrams and flow diagrams of the present invention.
[0020] Figure 1 An example of a system 100 that supports boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is illustrated. The system 100 may include a portion of an electronic device, such as a computing device, a mobile computing device, a wireless communication device, a graphics processing device, a vehicle, or other system. The system 100 includes a host system 105, a memory system 110, and one or more channels 115 (e.g., for providing a communicative coupling) coupling the host system 105 and the memory system 110. The system 100 may include one or more memory systems 110, but aspects of the one or more memory systems 110 may be described in the context of a single memory system 110.
[0021] The host system 105 may be an example of a processor (e.g., circuitry, processing circuitry, processing component) that uses memory to perform processes, such as a processing system of a computing device, a mobile computing device, a wireless communication device, a graphics processing device, a wearable device, an Internet connection device, a vehicle controller, a single chip system (SoC), or other fixed or portable electronic device, among other examples. The host system 105 may include one or more of an external memory controller 120, a processor 125, a basic input / output system (BIOS) component 130, or other components (e.g., peripheral components, input / output controllers not shown). The components of the host system 105 may be coupled to each other using a bus 135.
[0022] The external memory controller 120 may be configured to enable information (e.g., data, commands, control information, configuration information) communication between components of the system 100 (e.g., between components of the host system 105 (e.g., the processor 125) and the memory system 110). The external memory controller 120 may process (e.g., convert, translate) communications exchanged between the host system 105 and the memory system 110. In some examples, the external memory controller 120 or other components of the system 100 or associated functionality described herein may be implemented by or be part of the processor 125. For example, the external memory controller 120 may be hardware, firmware, or software (e.g., instructions), or some combination thereof, implemented by the processor 125 or other components of the system 100 or the host system 105. Although the external memory controller 120 is illustrated as being external to the memory system 110, in some examples, the external memory controller 120 or its functionality described herein may be implemented by one or more components of the memory system 110 (e.g., the memory system controller 155, the local memory controller 165), or vice versa. In various examples, the host system 105 or the external memory controller 120 may be referred to as a host.
[0023] Processor 125 is operable to provide functionality (e.g., control functionality) for system 100 or host system 105. Processor 125 may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. In some examples, processor 125 may be an example of a central processing unit (CPU), a graphics processing unit (GPU), a general purpose GPU (GPGPU), or a SoC, among other examples.
[0024] In some examples, the system 100 or the host system 105 may include an input component, an output component, or a combination thereof. The input component may include a sensor, a microphone, a keyboard, another processor (e.g., on a printed circuit board), an interface (e.g., a user interface, an interface between other devices), or a peripheral device that interfaces with the system 100 via one or more peripheral components, as well as other examples. The output component may include a display, an audio speaker, a printing device, another processor on a printed circuit board, or a peripheral device that interfaces with the system 100 via one or more peripheral components, as well as other examples.
[0025] The memory system 110 may be a component of the system 100 operable to provide physical memory locations (e.g., addresses) that may be used or referenced by the system 100. The memory system 110 may include a memory system controller 155 and one or more memory dies 160 (e.g., memory chips) for supporting data storage capacity. The memory system 110 may be configured to cooperate with one or more different types of host systems 105, and may respond to and execute commands provided by the host system 105 (e.g., via the external memory controller 120). For example, the memory system 110 (e.g., the memory system controller 155) may receive a write command indicating that the memory system 110 will store data received from the host system 105, or receive a read command indicating that the memory system 110 will provide data stored in the memory die 160 to the host system 105, or receive a refresh command indicating that the memory system 110 will refresh data stored in the memory die 160, as well as other types of commands and operations.
[0026] The memory system controller 155 may include components (e.g., circuitry, logic) operable to control the operation of the memory system 110. The memory system controller 155 may include hardware, firmware, or instructions that enable the memory system 110 to perform various operations, and may be operable to receive, transmit, or execute commands, data, or control information related to the operation of the memory system 110. The memory system controller 155 may be operable to communicate with one or more of the external memory controller 120, one or more memory dies 160, or the processor 125. In some examples, the memory system controller 155 may cooperate with the local memory controller 165 of the memory die 160 to control the operation of the memory system 110.
[0027] Each memory die 160 may include a local memory controller 165 and a memory array 170. The memory array 170 may be a collection of memory cells, each of which may be operable to store one or more bits of data. The memory die 160 may include a two-dimensional (2D) array of memory cells or a three-dimensional (3D) array of memory cells. In some examples, a 2D memory die 160 may include a single memory array 170. In some examples, a 3D memory die 160 may include two or more memory arrays 170, which may be stacked or positioned next to each other (e.g., relative to a substrate).
[0028] The local memory controller 165 may include components (e.g., circuitry, logic) operable to control the operation of the memory die 160. In some examples, the local memory controller 165 may be operable to communicate (e.g., receive or transmit data or commands or both) with the memory system controller 155. In some examples, the memory system 110 may not include a memory system controller 155 and a local memory controller 165, or an external memory controller 120 may perform the various functions described herein. Thus, the local memory controller 165 may be operable to communicate with the memory system controller 155, with other local memory controllers 165, or directly with the external memory controller 120 or processor 125, or any combination thereof. Examples of components that may be included in the memory system controller 155 or the local memory controller 165 or both may include a receiver for receiving signals (e.g., from the external memory controller 120), a transmitter for transmitting signals (e.g., to the external memory controller 120), a decoder for decoding or demodulating received signals, an encoder for encoding or modulating signals to be transmitted, a sensing component for sensing the state of memory cells of the memory array 170, a writing component for writing the state to the memory cells of the memory array 170, or various other components operable to support the described operations of the memory system 110.
[0029] The host system 105 (e.g., external memory controller 120) and the memory system 110 (e.g., memory system controller 155) may communicate information (e.g., data, commands, control information, configuration information) using one or more channels 115. Each channel 115 may be an example of a transmission medium that carries information, and each channel 115 may include one or more signal paths (e.g., transmission media, electrical conductors, conductive paths) between terminals associated with components of the system 100. For example, a channel 115 may be associated with a first terminal (e.g., including one or more pins, including one or more pads) at the host system 105 and a second terminal at the memory system 110. A terminal may be an example of a conductive input or output point of a device of the system 100, and a terminal may be operable to serve as part of a channel 115. In some implementations, at least the channel 115 between the host system 105 and the memory system 110 may include or be referred to as a host interface (e.g., a physical host interface). In some implementations, the host interface may include or be associated with interface circuitry (e.g., signal drivers, signal latches) at the host system 105 (e.g., at the external memory controller 120) or at the memory system 110 (e.g., at the memory system controller 155), or both.
[0030] In some examples, channels 115 (e.g., associated signal paths and terminals) may be dedicated to conveying one or more types of information. For example, channels 115 may include one or more command and address channels, one or more clock signal channels, one or more data channels, and other channels or combinations thereof. In some examples, signaling may be conveyed via channels 115 using single data rate (SDR) signaling or double data rate (DDR) signaling. In SDR signaling, one modulation symbol (e.g., signal level) of a signal may be recorded for each clock cycle (e.g., on either a rising or falling edge of a clock signal). In DDR signaling, two modulation symbols of a signal may be recorded for each clock cycle (e.g., on both a rising edge and a falling edge of a clock signal).
[0031] In some examples, at least a portion of system 100 may implement a stacked die architecture in which multiple semiconductor dies are physically and communicatively coupled. In some implementations, one or more semiconductor dies may include multiple instances of interface circuitry (e.g., memory system 110, memory interface block), each associated with accessing a set of one or more corresponding memory arrays of one or more other semiconductor dies. The interface circuitry may perform operations such as initialization operations, evaluation operations, configuration operations, access operations, or other operations based on information (e.g., instructions, parameters, configuration information) stored at memory system 110.
[0032] According to examples disclosed herein, the memory system 110 may include a common logic block (e.g., logic circuitry) operable to output an indication to each of a set of multiple interface blocks to perform an initialization procedure, an evaluation procedure, or both. For example, the common logic block may receive a command to initialize or evaluate operations associated with one or more memory arrays 170 of the memory system 110 (e.g., from the host system 105, from an external device). The common logic block may output an indication of a set of instructions (e.g., a program) associated with the initialization or evaluation. The interface block may use the received indication (e.g., from a non-volatile storage device of the memory system 110) to obtain the instruction and perform one or more operations associated with the instruction. In some examples, the common logic block may output the indication in response to identifying a power-on condition (e.g., as part of a boot protocol). In some cases, one or more operations may include evaluating the interface block or associated memory array 170 for proper operation, for establishing trim settings (e.g., for accessing memory cells of memory array 170), for determining whether to repair components of memory system 110 (e.g., row repair, column repair, TSV repair), or any combination thereof. Such techniques may support efficient initialization and evaluation of memory system 110, which may improve performance of system 100.
[0033] In addition to being applied to the systems described herein, boot and initialization techniques for stacked memory architectures may also be implemented generally to support artificial intelligence applications. As the use of artificial intelligence increases to support machine learning, analysis, decision making, or other related applications, electronic devices that support artificial intelligence applications and processes may be desirable. For example, artificial intelligence applications may be associated with accessing relatively large amounts of data for analytical purposes and may benefit from memory systems that can effectively and efficiently store relatively large amounts of data or access stored data relatively quickly. Implementation of the techniques described herein may support artificial intelligence or machine learning techniques by supporting efficient initialization and testing of high-bandwidth memory systems, including coordinated initialization and testing of relatively large numbers of interfaces (e.g., channels, data paths, supporting stacks) between a host and a memory array of one or more semiconductor dies stacked on a logic die, and other benefits.
[0034] Figure 2An example of a system 200 (e.g., a semiconductor system, a system of coupled semiconductor dies) supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is illustrated. The system 200 illustrates an example of a die 205 (e.g., a semiconductor die, a host die, a processor die, a logic die) coupled with one or more dies 240 (e.g., dies 240-a-1 and 240-a-2, a semiconductor die, a memory die, an array die). The die 205 or die 240 may be formed using a respective semiconductor substrate (e.g., a crystalline semiconductor material substrate such as silicon, germanium, silicon-germanium, gallium arsenide, or gallium nitride) or a silicon-on-insulator (SOI) substrate (e.g., silicon on glass (SOG), silicon on sapphire (SOS)), or an epitaxial semiconductor material formed on another substrate, among other examples. Although the illustrated example of the system 200 includes two dies 240, the system 200 according to the described techniques may include any number of one or more dies 240 coupled with the die 205. Furthermore, although the non-limiting examples of system 200 herein are generally described in terms of application to a memory system, memory subsystem, memory device, or combination thereof, examples of system 200 are not limited thereto. For example, aspects of the present disclosure may be equally applicable to any computing system, computing subsystem, processing system, processing subsystem, component, device, structure, or other type of system or subsystem used for applications such as data collection, data processing, data storage, networking, communication, power, artificial intelligence, single chip system, control, telemetry, sensing and monitoring, digital entertainment, or any combination thereof.
[0035] System 200 illustrates an example of an interface circuit system implemented in (e.g., distributed between) multiple semiconductor dies (e.g., a stack of directly coupled dies) between a host and a memory (e.g., via a host interface, via a physical host interface). For example, die 205 may include a set of one or more interface blocks 220 (e.g., interface blocks 220-a-1 and 220-a-2, memory interface blocks), and each die 240 may include a set of one or more interface blocks 245 and one or more memory arrays 250 (e.g., die 240-a-1 includes interface block 245-a-1 coupled to a set of one or more memory arrays 250-a-1, and die 240-a-2 includes interface block 245-a-2 coupled to a set of one or more memory arrays 250-a-2). In some implementations, die 205 may also include a host processor 210. However, in some other implementations, host processor 210 may be external to die 205, such as in another semiconductor die or other component that is coupled (e.g., communicatively coupled, directly coupled, bonded) to die 205 via one or more contacts 212. Although the example of system 200 is illustrated as including one interface block 245 in each die 240, die 240 in accordance with the described techniques may include any number of one or more interface blocks 245 that are each coupled to a set of respective one or more memory arrays 250 and each coupled to a respective interface block 220 of die 205. Thus, interface circuitry of system 200 may include one or more interface blocks 220 of die 205, with each interface block 220 coupled (e.g., in communication) to a corresponding interface block 245 of die 240 (e.g., external to die 205). In some examples, the coupled combination of interface block 220 and interface block 245 (e.g., coupled via a bus associated with one or more channels, such as one or more data channels, one or more control channels, one or more clock channels, or a combination thereof) may include or be referred to as a data path associated with a set of corresponding one or more memory arrays 250.
[0036] The host processor 210 may be an example of the host system 105 or a portion thereof (e.g., the processor 125, the external memory controller 120, or both). The host processor 210 may be configured to perform operations to implement storage of the memory array 250. For example, the host processor 210 may receive data read from the memory array 250 or may transmit data written to the memory array 250, or both (e.g., according to an application or other operation of the host processor 210). The memory array 250 may be an example of the memory array 170 and may include memory cells of various architectures, such as RAM, DRAM, SDRAM, SRAM, FeRAM, MRAM, RRAM, PCM, chalcogenide, NOR or NAND memory cells, or any combination thereof.
[0037] The host processor 210 may be configured to perform signaling communication (eg, transmission, reception) with the interface block 220 via the host interface 213 (eg, physical host interface). The host interface 213 may implement reference Figure 1 For example, the host processor 210 may be configured to transmit access signaling (e.g., control signaling, access command signaling, configuration signaling) via the host interface 213, which may be received by the interface block 220 to support access operations (e.g., read operations, write operations) to the memory array 250.
[0038] The host interface 213 may include a set of one or more corresponding signal paths for each interface block 220, so that the host processor 210 can communicate with each interface block 220 via a corresponding set of signal paths (e.g., according to the selection of a corresponding set for performing access operations via the interface block 220 selected by the host processor 210). Additionally or alternatively, the host interface 213 may include one or more signal paths shared between multiple interface blocks 220, and the interface blocks 220 or the host processor 210 or both may interpret, ignore, respond to, or suppress response signaling via the shared signal paths of the host interface 213 based on a logic indication (e.g., an addressing indication associated with the interface block 220 or an interface enable signal, which may be provided by the host processor 210 or the corresponding interface block 220, depending on the signaling direction). In some examples, the host interface 213 may include one or more instances of control circuitry (e.g., memory controller circuitry) that may be associated with implementing aspects of the external memory controller 120. In some other examples, such control circuitry may be included in the host processor 210.
[0039] The die 205 may also include a logic block 230 (e.g., a shared logic block, a central logic block, a common logic circuit system) that may be configured to communicate (e.g., transmit, receive) signaling with the interface block 220 of the die 205. In some cases, the logic block 230 may be configured to transmit information that may include commands, instructions, data, or other information to the interface block 220 to facilitate the operation of the interface block 220. For example, the logic block 230 may be configured to transmit initialization or other configuration signaling that may be received by the interface block 220 to support initialization or other configuration of the interface block 220 or other aspects of operating the die 240 (e.g., via a corresponding interface block 245). The logic block 230 may be coupled to each interface block 220 via a corresponding bus 231 (e.g., bus 231-a-1 associated with interface block 220-a-1, bus 231-a-2 associated with interface block 220-a-2). In some examples, the respective buses 231 may each include a set of respective one or more signal paths so that the logic block 230 can communicate with each interface block 220 via a respective set of signal paths. Additionally or alternatively, the respective buses 231 may include one or more signal paths (not shown) shared between multiple interface blocks 220.
[0040] In some implementations, logic block 230 may be configured to perform signaling communications (e.g., transmit, receive) with host processor 210 (e.g., via bus 232, via contacts 212 of host processor 210 external to die 205) such that logic block 230 may support an interface between interface block 220 and host processor 210. For example, host processor 210 may be configured to transmit initialization signaling (e.g., boot commands) or other configuration or operational signaling, which may be received by logic block 230 to support initialization, configuration, or other operations of interface block 220. Additionally or alternatively, in some implementations, logic block 230 may be configured to perform signaling communications (e.g., transmit, receive) with components external to system 200 (e.g., via contacts 233) such that logic block 230 may support an interface that bypasses host processor 210. In some examples, such implementations may support evaluation, configuration, or other operations of system 200 during manufacturing, assembly, validation, or other operations associated with system 200 (e.g., prior to coupling with host processor 210, without implementing host processor 210, for operations independent of the host processor), via contacts 233 accessible at a physical interface of the system.
[0041] Each interface block 220 may be coupled to at least one respective bus 221 of die 205 and a respective bus 246 of die 240, the respective bus 246 being configured to communicate signaling with the corresponding interface block 245 (e.g., via one or more associated signal paths). For example, interface block 220-a-1 may be coupled to interface block 245-a-1 via bus 221-a-1 and bus 246-a-1, and interface block 220-a-2 may be coupled to interface block 245-a-2 via bus 221-a-2 and bus 246-a-2. In some examples, die 240 may include a bus, such as bus 255, that bypasses the operational circuitry of die 240 (e.g., bypasses the interface block 245 of a given die 240). For example, interface block 220-a-2 may be coupled to interface block 245-a-2 of die 240-a-2 via bus 255-a-1 of die 240-a-1, which may bypass interface block 245 of die 240-a-1. Such techniques may be extended for interconnection between more than two dies 240 (e.g., for interconnection via respective buses 255 of multiple dies 240).
[0042] The respective signal paths of buses 221, 246, and 255 may be coupled to one another from one die to another via various arrangements of contacts at the surfaces of the interfacing dies. For example, bus 221-a-1 may be coupled to bus 246-a-1 via contacts 222-a-1 of die 205 (e.g., at the surface of die 205) and contacts 247-a-1 of die 240-a-1, bus 221-a-2 may be coupled to bus 255-a-1 via contacts 222-a-2 of die 205 and contacts 256-a-1 of die 240-a-1, bus 255-a-1 may be coupled to bus 246-a-2 via contacts 257-a-1 of die 240-a-1 and contacts 247-a-2 of die 240-a-2, and so on. Although each respective bus is illustrated with a single line coupled via a singular contact, it should be understood that each signal path of a given bus may be associated with a respective contact to support separate communication coupling of each signal path via the given bus. In some examples, bus 255 may traverse a portion of die 240 (e.g., in an in-plane direction, along a direction different from the thickness direction, in a waterfall arrangement), which may support an arrangement of contacts 222 along a surface of die 205 coupled to an interface block 245 of a different die 240 along a stacking direction (e.g., via respective contacts 256 and 257 that do not overlap when viewed along the thickness direction).
[0043] The interconnection of the interfacing contacts may be supported by a variety of techniques. For example, in a hybrid bonding implementation, the interfacing contacts may be coupled by fusion of the conductive material (e.g., electrically conductive material) of the interfacing contacts (e.g., without solder or other intervening material between the contacts). For example, in an assembled condition, the coupling of die 205 to die 240-a-1 may include fusion of the conductive material of contact 222-a-2 to the conductive material of contact 256-a-1, and the coupling of die 240-a-1 to die 240-a-2 may include fusion of the conductive material of contact 257-a-1 to the conductive material of contact 247-a-2, and so on. In some examples, such coupling may include inoperable fusion of contacts (e.g., non-communicative coupling, physical coupling), such as fusion of contact 260-a-1 and contact 256-a-2, both of which are not coupled to the operable circuitry of die 240-a-1 or 240-a-2. In some examples, such techniques may be implemented to improve coupling strength or uniformity (e.g., implementing contact 260 that is not operable to couple with interface block 245 or interface block 220), or such coupling may be a byproduct of duplication of components that may be operable or inoperable in various configurations. (For example, where for a die 240 having contacts 256 and 257 arranged together, contacts 256-a-1 and 257-a-1 provide a communication path between interface block 245-a-2 and interface block 220-a-2, but contacts 256-a-2 and 257-a-2 do not provide a communication path between interface block 245 and interface block 220).
[0044] In some examples, the fusion of conductive material between the dies (e.g., between contacts) may be accompanied by fusion of other materials at one or more surfaces of the interfacing dies. For example, in an assembled condition, the coupling of die 205 with die 240-a-1 may include fusion of dielectric material 207 (e.g., non-conductive material) of die 205 with dielectric material 242 of die 240-a-1, and the coupling of die 240-a-1 with die 240-a-2 may include fusion of dielectric material 242 of die 240-a-1 with dielectric material 242 of die 240-a-2. In some examples, such dielectric materials may include oxides, nitrides, carbides, oxide-nitrides, oxide-carbides, or other conversions or doping of semiconductor materials of die 205 or die 240, as well as other materials that may support such fusion. However, the coupling between die 205 and die 240 may be implemented according to other techniques, which may implement solder, adhesives, thermal interface materials, and other intervening materials.
[0045] In some examples, the dies 240 may be coupled into a stack (e.g., forming a "cube" or other arrangement of dies 240), and the stack may subsequently be coupled to the die 205. In some examples, a group of respective one or more dies 240 may be coupled to each die 205 of the plurality of dies 205 formed in a wafer (e.g., in a chip-to-wafer bonding arrangement, before dicing the wafer of dies 205), and the dies 205 coupled to their respective groups of dies 240 may be separated from each other (e.g., by dicing at least the wafer of dies 205). In some other examples, a group of respective one or more dies 240 may be coupled to the respective dies 205 after the dies 205 are separated from the wafer of dies 205 (e.g., in a chip-to-chip bonding arrangement).
[0046] The buses 221, 246, and 255 may be configured to provide configuration signaling (e.g., coordination signaling, logic signaling, modulation signaling, digital signaling) between the interface block 220 and the corresponding interface block 245, which may involve various modulation or coding techniques through the transmission interface block (e.g., via the driver component of the transmission interface block). In some examples, this signaling may be supported (e.g., accompanied) by clock signaling communicated (e.g., coordinated with the signal transmission) via the corresponding bus. For example, the bus may be configured to pass one or more clock signals transmitted by the interface block 220 for reception by the interface block 245 (e.g., for triggering a latch or other receiving component of the interface block 245 to receive a signal, for supporting the timing control operation of the interface block 245). Additionally or alternatively, the bus may be configured to pass one or more clock signals transmitted by the interface block 245 for reception by the interface block 220 (e.g., for triggering a latch or other receiving component of the interface block 220 to receive a signal, for supporting the timing control operation of the interface block 220). Such clock signals may be associated with communication (e.g., unidirectional communication, bidirectional communication) of various signaling (e.g., control signaling, command signaling, data signaling, or any combination thereof). For example, a bus may include one or more signal paths for a data bus (e.g., one or more data lanes, a DQ bus, via a data interface of an interface block) to communicate according to one or more corresponding clock signals (e.g., a data clock signal) or one or more signal paths for a control bus (e.g., a command / address (C / A) bus, via a command interface of an interface block) to communicate according to one or more clock signals (e.g., a control clock signal), or any combination thereof.
[0047] Interface block 220, interface block 245, and logic block 230 may each include circuitry (signaling circuitry, multiplexing circuitry, processing circuitry, controller circuitry) in various configurations (e.g., hardware configurations, logic configurations, software or instruction configurations) that support functionality assigned to the respective blocks for accessing or otherwise operating a set of corresponding memory arrays 250. For example, interface block 220 may include circuitry configured to perform a first subset of operations supporting access of memory arrays 250, and interface block 245 may include circuitry configured to support a second subset of operations supporting access of memory arrays 250. In some examples, interface blocks 220 and 245 may support functional partitioning or distribution of functionality associated with memory system controller 155, local memory controller 165, or both across multiple dies (e.g., die 205 and at least one die 240). In some implementations, logic block 230 may be configured to coordinate or configure aspects of the operation of interface block 220, interface block 245, or both. Such operations or subsets of operations may include operations performed in response to commands from the host processor 210 or operations performed without commands from the host processor 210 (e.g., operations determined or initiated by the interface block 220, operations determined or initiated by the interface block 245, operations determined or initiated by the logic block 230), or various combinations thereof.
[0048] In some examples, the circuitry of interface block 220, interface block 245, or logic block 230, or any combination thereof, may include components (e.g., transistors) formed at least in part from doped portions of a substrate of a respective die. In some examples, the substrate of die 205 may have characteristics that differ from characteristics of a substrate of die 240. Additionally or alternatively, in some examples, transistors formed from the substrate of die 205 may have characteristics that differ from transistors formed from the substrate of die 240 (e.g., according to different transistor architectures).
[0049] The die 240 may include one or more cells 265 (e.g., modules) separated from a semiconductor wafer having a pattern (e.g., a two-dimensional pattern) of cells 265. Although each die 240 of the system 200 is illustrated as having a single cell 265 (e.g., cell 265-a-1 of die 240-a-1, cell 265-a-2 of die 240-a-2), a die 240 according to the described technology may include any number of cells 265 that may be arranged in various patterns (groups of one or more cells 265 along a row direction, groups of one or more cells 265 along a column direction, and other patterns). Each cell 265 may include at least the circuitry of a corresponding interface block 245 and a memory array 250, a bus 251, a bus 246, and one or more contacts 247 corresponding to the corresponding interface block 245. In some instances, each unit 265 may also appropriately include one or more buses 255, contacts 256, contacts 257, or contacts 260 (e.g., associated with corresponding interface blocks 245 of units 265 of different dies 240), which may support various degrees of stackability or modularity between units 265 of other dies 240 or via units 265 of other dies 240.
[0050] In some examples, the interface block 220 may include circuitry configured to receive first access command signaling from the host processor 210 (e.g., via the host interface 213, from the host processor 210 external to the die 205 via one or more contacts 212) and transmit second access command signaling to a corresponding (e.g., coupled) interface block 245 based on (e.g., in response to) the received first access command signaling. The interface block 245 may thus include circuitry configured to receive second access command signaling from the corresponding interface block 220 and access a corresponding set of one or more memory arrays 250 based on (e.g., in response to) the received second access command signaling. In various examples, the first access command signaling may include an access command associated with an operation type (e.g., a read operation, a write operation, a refresh operation, a memory management operation), which may be associated with an indication of an address (e.g., a logical address, a physical address) of the one or more memory arrays 250. In some examples, the first access command signaling may include an indication of a logical address associated with the memory array 250, and the circuit system of the interface block 220 may be configured to generate a second access command signaling to indicate a physical address associated with the memory array 250 (e.g., a row address, a column address, using a logical-to-physical (L2P) table or other mapping or calculation functionality of the interface block 220).
[0051] In some examples, to support write operations of the system 200, the circuitry of the interface block 220 may be configured to receive first data signaling associated with the first access command signaling (e.g., from the host processor 210 via the host interface 213, from the host processor 210 external to the die 205 via one or more contacts 212) and transmit second data signaling (e.g., associated with the second access command signaling) based on the received first access command signaling and the first data signaling. The interface block 245 may therefore be configured to receive the second data signaling and write data to the one or more memory arrays 250 based on the received second access command signaling and the second data signaling (e.g., according to the indicated address associated with the first access command signaling). In some instances, interface block 220 may include error control functionality (e.g., error detection circuitry, error correction circuitry, error correction code (ECC) logic, an ECC engine) that supports interface block 220 in performing error control operations (e.g., detecting or correcting errors in the first data signaling, determining one or more parity bits conveyed in the second data signaling and written with the data) to generate a second data signaling based on using the received first data signaling.
[0052] In some examples, to support read operations of system 200, the circuitry of interface block 245 may be configured to read data from memory array 250 based on received second access command signaling and transmit first data signaling based on the read data. Interface block 220 may thus be configured to receive first data signaling and transmit second data signaling based on the received first data signaling (e.g., to host processor 210 via host interface 213, to host processor 210 external to die 205 via one or more contacts 212). In some examples, interface block 220 may include error control functionality that enables interface block 220 to generate second data signaling based on performing error control operations using received first data signaling (e.g., detecting or correcting errors in the first data signaling, which may include calculations involving one or more parity bits received with the first data signaling).
[0053] In some examples, access command signaling transmitted by the interface block 220 to the interface block 245 may be generated (e.g., based on access command signaling received from the host processor 210, based on initiation signaling received from the host processor 210, without receiving signaling from the host processor 210, or otherwise independent of signaling from the host processor 210) according to various determination or generation techniques configured at the interface block 220 (e.g., based on a configuration modified at the interface block 220 for accessing the memory array 250). Such techniques may enable the interface block 220 to configure aspects of access operations performed by the corresponding interface block 245 on the memory array 250.
[0054] In some implementations, the operation of logic block 230, interface block 220, interface block 245, or memory array 250, or any combination thereof, may be supported by information stored at system 200. For example, system 200 may include one or more storage locations, such as non-volatile (NV) array 270, that may be configured to store such information and output information to one or more components of system 200 to support related operations. Such storage locations may be configured in various arrangements in system 200. For example, NV array 270 may be located in die 205 or one or more die 240, or any combination thereof (e.g., in both die 205 and one or more die 240). Information may be written to one or more NV arrays 270 during system 200 manufacturing, during system 200 operation (e.g., based on the operation of system 200), or both. In some examples, NV array 270 may be implemented as a read-only memory (ROM) array.
[0055] In some implementations, the logic block 230 may be configured to communicate signaling with one or more of the NV arrays 270 of the system 200 (e.g., with supporting circuitry associated with the operation of the NV arrays 270). For example, the logic block 230 may be suitably coupled to the one or more NV arrays 270 via one or more buses 271 and corresponding contacts 272 and 273, which may each include one or more signal paths operable to communicate signaling (e.g., command signaling, data signaling) between the logic block 230 and the one or more NV arrays 270. In some examples, the interface block 220 may be configured to communicate signaling with the one or more NV arrays 270, such that each interface block 220 may be coupled to the one or more NV arrays 270 via the logic block 230 (e.g., via a corresponding bus 231) or directly via one or more signal paths (not shown).
[0056] In some examples, logic block 230 may receive a command to initialize or evaluate operations associated with memory array 250, interface block 245, interface block 220, or a combination thereof (e.g., from host system 105, from host processor 210, from a device external to system 200 via contact 212 or contact 233). Logic block 230 may output an indication of a set of instructions (e.g., a program) associated with initialization or evaluation (or both) to interface block 220, which may obtain the instructions (e.g., from NV array 270) and perform (e.g., initiate) one or more operations associated with the instructions. In some examples, logic block 230 may output the indication in response to identifying a power-on condition (e.g., as part of a boot protocol). In some cases, one or more operations may include evaluating the interface block 220, the interface block 245, the memory array 250, or any combination thereof for proper operation, for establishing trim settings (e.g., for accessing memory cells of the memory array 250), for determining whether to implement a repair solution (e.g., row repair, column repair, TSV repair) of the system 200, or a combination thereof. Such techniques may support efficient initialization and evaluation of the system 200, which may further improve overall system performance.
[0057] Figure 3 An example of a system 300 that supports boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown. System 300 may illustrate implementations of aspects of system 100, system 200, or both. For example, system 300 may include a die 205-b having one or more interface blocks 220-b (e.g., interface blocks 220-b-1 to 220-bn) coupled to a logic block 230-b (e.g., a common logic block). Die 205-b may be coupled to a die 205-b having a corresponding interface block 220-b (e.g., as described in reference Figure 2 20-b). In some examples, logic block 230-b may use broadcast command circuitry 325-a to communicate with one or more interface blocks 220-b for signaling, and each interface block 220-b may include respective broadcast command circuitry 325-b. Broadcast command circuitry 325 may be associated with one or more channels (e.g., buses, bridges) between logic block 230-b and each of interface blocks 220-b.
[0058] As part of the operating system 300, the logic block 230-b, one or more interface blocks 220-b, or a combination thereof, may be operable to execute one or more programs (e.g., one or more sets of instructions), such as one or more initialization operations of the system 300, one or more evaluation operations of the system 300, or a combination thereof. For example, the logic block 230-b may be operable to initialize the interface controller 305 of each interface block 220-b. In some examples, each interface controller 305 may be operable to perform testing and repair operations of the corresponding interface block 220-b and the components of the memory array 250 associated therewith. For example, the interface controller 305 may be operable to execute a program to detect errors (e.g., failures, mechanical defects) in one or more rows or one or more columns (or both) of the associated memory array 250, detect errors associated with TSVs between dies (e.g., between die 205 and die 240, between die 240, associated with bus 221, 246, or 255), perform calibration operations on components associated with operating the corresponding memory array 250 (e.g., components of the corresponding interface block 245), or a combination thereof. In some cases, the interface controller 305 may support the execution of repair operations (e.g., in cooperation with the repair controller 375) to attempt to repair one or more detected errors.
[0059] In some examples, the system 300 may be operable to communicate with another system (e.g., the host system 105) or an evaluation probe, or both. To support such communication, the system 300 may include an evaluation interface 310 that is operable to translate or otherwise respond to signaling (e.g., signaling from an external system) received via one or more contacts (e.g., contacts 233) associated with the evaluation interface 310 by generating control signaling to operate with the logic block 230-b. For example, the host system 105 or other device coupled to the evaluation interface 310 may transmit control signaling to the evaluation interface 310 to invoke an evaluation protocol (e.g., configuration settings, data modes, access modes, registers), which may be associated with instructions stored at the evaluation interface 310. Such protocols may be invoked to initiate various of one or more procedures, such as initialization operations of the system 300, evaluation operations of the system 300, or both. In some examples, the evaluation interface 310 may provide external access to the system 300, such as an IEEE 1500 interface or other dedicated access logic.
[0060] The system 300 may store one or more programs in the NV array 270-b. In some implementations, the NV array 270-b may include an array of one-time programmable (OTP) elements 330, which may be examples of fuses, antifuses, or other read-only memory elements. The OTP memory elements 330 may be configured to store information and accessed by the interface blocks 220-b using the command channel controller 360 of each of the interface blocks 220-b. For example, the command channel controller 360 may be configured to communicate information from the OTP memory elements 330 to the interface controller 305 (e.g., via the command channel 340). Although illustrated as being included in the die 205-b (e.g., in the logic block 230-b), the NV array 270-b may be separate from the logic block 230-b (e.g., external to the logic block 230-b). For example, one or more NV arrays 270 associated with system 300 may be included in one or more other portions of die 240 or die 205, or any combination thereof.
[0061] In some cases, multiple programs may be programmed (e.g., stored, written) to NV array 270-b. For example, as part of manufacturing or assembly, one or more initialization programs, one or more evaluation programs, or both may be programmed to NV array 270-b. Additionally or alternatively, one or more programs may be programmed to NV array 270-b during operation of system 300 (e.g., by an external device, such as host system 105). Such programs may include programs that configure system 300 to perform repair operations, programs that configure system 300 to perform MBIST operations, or both.
[0062] The interface block 220-b may also include a number of array controllers 350-a and 350-b that may be coupled to the interface controller 305. The array controllers 350-a and 350-b may be configured to facilitate the operation of the one or more memory arrays 250, for example, by communicating information of the operation of the one or more memory arrays 250 (e.g., to the memory arrays 250, to the corresponding interface block 245) using data channels 345-a and data channels 345-b, respectively. In some examples, the data channels 345 may be included in or otherwise associated with the bus 221. A repair controller 375 may also be coupled to the interface controller 305 and may be configured to store repair information (e.g., column repair information, row repair information, redundancy information) of the one or more memory arrays 250.
[0063] The logic block 230-b may be operable to launch one or more programs as part of a power-on sequence of the system 300 or as part of a power-on sequence of a coupled host system 105, or both. For example, the logic block 230-b may receive a command from the host system 105 coupled to the system 300, such as an initialization command to initialize the system 300 or an evaluation command to evaluate aspects of the system 300. In some cases, the logic block 230-b may receive the command using the evaluation interface 310.
[0064] The logic block 230-b may generate or obtain an indication of a program (e.g., an initialization program, an evaluation program) using the received command. In some cases, the logic block 230-b may obtain the indication from a non-volatile storage device (e.g., a boot ROM 320) associated with the logic block 230-b. For example, the command may include one or more fields that identify the program, and the logic block 230-b may decode the command to obtain an indication of the program stored in the boot ROM 320. Additionally or alternatively, the logic block 230-b may determine to initialize the system 300 in response to identifying a power-on condition (e.g., application or availability of power, signaling indicating a power-on condition). For example, the logic block 230-b may determine to initialize the system 300 as part of a power-on sequence, as part of a reset sequence, or both.
[0065] After receiving and, in some cases, decoding the command or after determining to initialize the system 300, the logic block 230-b may output an indication to each of the interface blocks 220-b using the broadcast command circuitry 325-a. The broadcast command circuitry 325-a may be an example of or may implement aspects of a configuration and status loop (CRS) interface between the logic block 230-b and the interface block 220-b. In some examples, the logic block 230-b may broadcast the indication to each of the interface blocks 220-b (e.g., concurrently).
[0066] Additionally or alternatively, the logic block 230-b may continuously output indications to the interface block 220-b. For example, the interface blocks 220-b may be arranged in a ring or star configuration, wherein each interface block 220-b (e.g., the broadcast command circuitry 325-b of each interface block 220-b) is communicatively coupled to one or more other interface blocks 220-b (e.g., one or more adjacent interface blocks 220-b). The logic block 230-b may output indications to a first interface block 220-b, which may output indications to a second interface block 220-b communicatively coupled to the first interface block 220-b, and so on, such that each interface block 220-b may receive indications from the logic block 230-b or from an adjacent interface block 220-b.
[0067] Each interface block 220-b may receive an indication (e.g., via a broadcast command circuitry 325-b) and issue an indication to an interface controller 305. The interface controller 305 of the interface block 220-b may be an example of a processor operable to perform evaluation operations, such as test operations, repair operations, or other aspects of a memory built-in self-test (MBIST) program of a memory array coupled to the interface block 220-b. Additionally, the interface controller 305 may be operable to execute a general purpose program (e.g., instructions, code), such as a program stored in a volatile storage device 365 coupled to the interface controller 305. The volatile storage device 365 may act as a random access memory (RAM) for the interface controller 305 and may be implemented using various memory architectures, such as DRAM, SRAM, or other volatile memory architectures.
[0068] In response to receiving the indication, the interface controller 305 may obtain the program (e.g., one or more instructions corresponding to the program, code corresponding to the program) from the NV array 270-b. For example, the interface controller 305 may use the command channel controller 360 to issue a read command to the NV array 270-b via the command channel 340. The read command may include information included in the indication, such as the starting address of the program (e.g., the starting address within the NV array 270-b), the size of the program (e.g., the number of bits of the program), or both. The NV array 270-b may process the read command and output the program to the interface controller 305 via the command channel 340. In some cases, the NV array 270-b may include or may be associated with a command queue or other circuit system that can manage multiple incoming access commands (e.g., read commands from the interface controller 305 of multiple interface blocks 220-b).
[0069] After receiving the program, the interface controller 305 may store the program to the volatile storage device 365 and may begin executing the program. After completing the program, the interface controller 305 may store an indication that the program has been completed (e.g., one or more values associated with the status or results of the program) to one or more status registers of the interface block 220-b. For example, if the program includes a repair operation (e.g., an operation for repairing a row or column of a memory array associated with the interface block 220-b or an operation for repairing a TSV associated with the interface block 220-b), the interface controller 305 may store an indication of the repaired component (e.g., an identifier of the component, an address of the component) to a status register of the repair controller 375. Additionally, if the program fails to repair the component, the interface controller 305 may store an indication of the component and an indication that the component is inoperable (e.g., faulty or otherwise defective).
[0070] The one or more status registers may each include one or more volatile memory cells (e.g., SRAM cells, flip-flop circuits) and may be accessed by logic block 230-b, via coupled host system 105, or both. For example, the one or more status registers may be communicatively coupled with broadcast command circuitry 325-b, and logic block 230-b, host system 105, or both may read values stored in the one or more status registers via broadcast command circuitry 325-a.
[0071] As part of initializing or evaluating the system 300, each interface controller 305 of the interface block 220-b of the system 300 may begin executing a program concurrently. However, because operating conditions may vary across different interface blocks 220-b, each interface block 220-b may complete the program at a different time or may execute a different program associated with the program, or both. For example, if the program includes a repair operation, the first interface controller 305 of the first interface block 220-b may identify and attempt to repair one or more errors or faults associated with the first interface block 220-b, while the second interface controller 305 may not identify the error and therefore may not attempt a repair operation. Therefore, the second interface controller 305 may complete the program before the first interface controller 305.
[0072] In some cases, the logic block 230-b, the host system, or both may wait until each interface block 220-b has completed a program (e.g., until each interface block 220-b has stored a value in one or more status registers indicating that the interface block 220-b has completed a program) or until a threshold number of interface blocks 220-b have completed a program. After reading the one or more status registers and determining that the interface block 220-b has completed a program, the coupled host system 105 may transmit a second command indicating a second program to the logic block 230-b (e.g., via the evaluation interface 310). The logic block 230-b may output an indication of the second command to the interface block 220-b, and the interface blocks 220-b may each retrieve the second program from the NV array 270-b and begin executing the second program.
[0073] Additionally or alternatively, the interface controller 305 may retrieve and begin executing the second program with an indication from the logic block 230-b (e.g., without transmitting the second command via the coupled host system 105). For example, the program may include an indication of the second program (e.g., may include a starting address of the second program, a size of the second program, or both). After completing the program, the interface controller 305 may issue a read command to the NV array 270-b using the indication included in the program (e.g., using the command channel controller 360). The NV array 270-b may output the second program to the interface controller 305, and the interface controller 305 may begin executing the second program. In some cases, including an indication of the second program within a program may be referred to as "linking" the programs together.
[0074] Figure 4 An example of a process flow 400 supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown. The process flow 400 may be implemented by aspects of the system 100, the system 200, the system 300, or a combination thereof. For example, aspects of the process flow 400 may be implemented by the logic block 230, one or more interface blocks 220 (e.g., one or more interface controllers 305 of the interface block 220), the host system 105, or a combination thereof. In the following description of the process flow 400, the operations may be performed in an order different from that shown. Additionally, one or more operations may be omitted from the process flow 400, and one or more operations may be added to the process flow 400.
[0075] The process flow 400 may illustrate an example of an initialization method of a memory system 110 having a first semiconductor die (e.g., die 205) including a logic block 230 and one or more interface blocks 220 operable to access one or more memory arrays (e.g., one or more memory arrays 250, via corresponding interface blocks 245) of one or more second semiconductor dies (e.g., die 240) of the memory system 110. In some cases, the logic block 230 may include a non-volatile storage device (e.g., boot ROM 320) operable to store instructions (e.g., code, program) configured to implement aspects of the process flow 400. In some examples, each interface block 220 may include an interface controller 305 operable to read instructions (e.g., initialization procedures, repair procedures, training procedures, calibration procedures, or any combination thereof) from one or more NV arrays 270 of the memory system 110. In some examples, aspects of the process flow 400 may be performed as part of a power-on sequence of the memory system 110.
[0076] At 405, the memory system 110 may be powered on. As part of the power-on sequence of the memory system 110, the logic block 230 may determine to initialize the memory system 110. In some cases, the logic block 230 may determine to initialize the memory system 110 in response to receiving one or more signals from the host system 105, such as a signal for transitioning into a default state, a reset signal, one or more clock signals, or a combination thereof.
[0077] Additionally or alternatively, the memory system 110 may determine to initialize the memory system 110 in response to a command from the host system 105. For example, at 410, the logic block 230 may receive an initialization command from the host system 105, which may indicate a set of instructions (e.g., an initialization program) stored in one or more NV arrays 270. In some cases, the host system 105 may transmit the initialization command using an evaluation interface (e.g., evaluation interface 310).
[0078] After receiving the initialization command, logic block 230 may output an indication of the instruction group (e.g., an address associated with one or more NV arrays 270 where the instruction group may be stored, a size of the instruction group) to each interface controller 305 of interface block 220 at 415. In some cases, logic block 230 may transmit the indication using broadcast command circuitry 325-b, and each interface block 220 may receive the indication using corresponding broadcast command circuitry 325-b.
[0079] The broadcast command circuitry 325-b may issue an indication to the interface controller 305, and the interface controller 305 may read the instruction group from the one or more NV arrays 270 using the command channel controller 360 and the associated command channel 340 at 420. After receiving the instruction group, the interface controller 305 may store the instruction group to the volatile storage device 365 and may begin executing the instructions at 425. In some examples, a single interface block 220 may be coupled to multiple memory arrays 250 using multiple data channels 345 (e.g., 8 data channels). In such a case, the interface controller 305 may execute the instruction group independently for each data channel 345. For example, the interface controller 305 may execute the instruction group for the first data channel 345, then may execute the instruction group for the second data channel 345, and so on (e.g., the interface controller 305 may "cycle" through each data channel 345).
[0080] In some cases, the instruction group may include one or more evaluation operations for a component associated with a data channel 345 of the interface block 220 (e.g., one or more rows of memory cells of a memory array coupled to a data channel 345 of the interface block 220, one or more columns of memory cells of a memory array coupled to a data channel 345 of the interface block 220, one or more TSVs associated with the interface block 220 (e.g., TSVs between memory array layers coupled to the interface block 220), or a combination thereof). For example, at 430, the interface controller 305 may determine whether the component passes the one or more evaluation operations. As described herein, a component may “pass” an evaluation operation if the evaluation operation does not detect or identify a fault or defect associated with the component.
[0081] If the component passes the evaluation operation, the process flow 400 may return to (e.g., may loop back to) 430 and the interface controller 305 may perform the evaluation operation on the subsequent channel. Alternatively, if the component does not pass the evaluation operation, the interface controller 305 determines at 435 whether the component is repairable. For example, the interface controller 305 may execute code included in the instruction group to diagnose the component. If the interface controller 305 determines that the component is not repairable, the interface controller 305 may determine at 440 that the component of the data channel 345 has failed. In some cases, the interface controller 305 may store a value indicating the failed component to a register (e.g., a status register of the repair controller 375). In addition, the interface controller 305 may disable one or more memory cells associated with the failed component (e.g., one or more memory cells of a failed row may be disabled, one or more memory arrays 250 of a failed column may be disabled).
[0082] Alternatively, if the interface controller 305 determines that the component is repairable, the interface controller 305 may perform a repair operation at 450 to repair the identified defect of the component. In some examples, the repair operation may be included in the instruction set. Additionally or alternatively, the repair operation may not be included in the instruction set. In such cases, the instruction set may include an indication of the repair operation, such as an address of a set of additional instructions that include the repair operation. The interface controller 305 may use the indication at 445 to read the additional instruction set from one or more NV arrays 270.
[0083] In some examples, after completing the repair operation, the interface controller 305 can store a value indicating the repair component (e.g., within a status register of the repair controller 375). Additionally, the process flow 400 can return to (e.g., can loop back to) 430, and the interface controller 305 can perform an evaluation operation on the subsequent data channel 345.
[0084] Figure 5 An example of a process flow 500 supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown. The process flow 500 may be implemented by aspects of the system 100, the system 200, the system 300, or a combination thereof. For example, aspects of the process flow 500 may be implemented by the logic block 230, one or more interface blocks 220 (e.g., one or more interface controllers 305 of the interface block 220), the host system 105, or a combination thereof. In the following description of the process flow 500, the operations may be performed in an order different from that shown. Additionally, one or more operations may be omitted from the process flow 500, and one or more operations may be added to the process flow 500.
[0085] The process flow 500 may illustrate an example of a method for identifying and storing one or more operating parameters of a memory system 110 of a first semiconductor die (e.g., die 205) having one or more interface blocks 220 including a logic block 230 and one or more memory arrays (e.g., one or more memory arrays 250, via corresponding interface blocks 245) of one or more second semiconductor dies (e.g., die 240) of the memory system 110. In some cases, the logic block 230 may include a non-volatile storage device (e.g., boot ROM 320) operable to store instructions (e.g., code, program) configured to implement aspects of the process flow 500. Additionally, each interface block 220 may include an interface controller 305 operable to read instructions (e.g., initialization program, repair program, training program, calibration program, or any combination thereof) from one or more NV arrays 270 of the memory system 110. In some examples, aspects of the process flow 500 may be performed as part of manufacturing operations of the memory system 110.
[0086] At 505, the memory system 110 may be powered on. As part of the power-on sequence of the memory system 110, the logic block 230 may determine to initialize the memory system 110. In some cases, the logic block 230 may determine to initialize the memory system 110 in response to receiving one or more signals from the host system 105, such as a signal for transitioning into a default state, a reset signal, one or more clock signals, or a combination thereof.
[0087] At 510, one or more sets of instructions may be programmed to one or more NV arrays 270. The one or more sets of instructions may include an initialization procedure, an evaluation procedure, a training procedure, or a combination thereof. In some cases, the manufacturing system may program one or more sets of instructions to one or more NV arrays 270. Additionally or alternatively, the host system 105 may transmit one or more commands to the logic block 230, which may cause the logic block 230 to program one or more instructions to the one or more NV arrays 270. In the example of the NV array 270 including an array of OTP storage elements, programming the NV array 270 may include "burning" or otherwise setting one or more of the OTP elements.
[0088] Additionally or alternatively, the memory system 110 may determine to initialize the memory system 110 in response to a command from a coupled host system 105. For example, at 510, the logic block 230 may receive an initialization command from the host system 105, which may indicate a set of instructions (e.g., an initialization program) stored in one or more NV arrays 270. In some cases, the host system 105 may transmit the initialization command using an evaluation interface (e.g., evaluation interface 310).
[0089] As part of the manufacturing operation, each interface controller 305 may perform one or more training procedures to determine one or more operating parameters, such as access voltages, voltage timings, TSV resistances, or combinations thereof, for accessing the memory array 250 coupled to each interface controller 305. To perform the training procedures, the logic block 230 may output an indication of a set of instructions including the training procedures to each interface controller 305 of the interface blocks 220 at 515. In some cases, the logic block 230 may transmit the indication using broadcast command circuitry 325-b, and each interface block 220 may receive the indication using respective broadcast command circuitry 325-b.
[0090] The broadcast command circuitry 325-b may issue an indication to the interface controller 305, and the interface controller 305 may read the instruction group from the one or more NV arrays 270 using the command channel controller 360 and the associated command channel 340 at 520. After receiving the instruction group, the interface controller 305 may store the instruction group to the volatile storage device 365 and may begin executing the instructions at 525. In some examples, a single interface block 220 may be coupled to multiple memory arrays 250 using multiple data channels 345 (e.g., 8 data channels). In such a case, the interface controller 305 may execute the instruction group independently for each data channel 345. For example, the interface controller 305 may execute the instruction group for the first data channel 345, then may execute the instruction group for the second data channel 345, and so on (e.g., the interface controller 305 may "cycle" through each data channel 345).
[0091] In some cases, the training procedure may include identifying at 530 whether an aspect of the channel's TSV is operable to be modified (e.g., whether the TSV is "trainable"). If the interface controller 305 determines that the TSV is not trainable, the interface controller 305 may determine at 535 that the TSV of the data channel 345 has failed. In some cases, the interface controller 305 may store a value indicating the failed TSV to a register (e.g., a status register of the repair controller 375). Additionally, the interface controller 305 may disable one or more memory cells associated with the failed TSV.
[0092] Alternatively, if the interface controller 305 determines that the TSV is trainable, the interface controller 305 may perform a training procedure (e.g., by calibrating the TSV) at 540. After completing the training procedure, the interface controller 305 may store the operating parameters resulting from the training procedure (e.g., the configuration determined using the calibration). Additionally, the process flow 500 may return to (e.g., may loop back to) 530, and the interface controller 305 may perform the training procedure on subsequent data lanes 345.
[0093] In some examples, after completing the training procedure for the data channel 345, the interface controller 305 may perform one or more evaluation operations on the data channel 345 at 545. In such cases, the process flow 500 may include aspects of the process flow 400. For example, the process flow 500 may continue to operation 425 of the process flow 400, and the interface controller 305 may perform one or more evaluation operations associated with the data channel 345.
[0094] Figure 6 A block diagram 600 is shown of a memory system 620 that supports boot and initialization techniques for a stacked memory architecture according to examples disclosed herein. The memory system 620 may be a reference Figures 1 to 5 Memory system 620 or its various components may be examples of means for performing various aspects of boot and initialization techniques for stacked memory architectures, as described herein. For example, memory system 620 may include command receiving component 625, interface block output component 630, interface block receiving component 635, instruction execution component 640, initialization control component 645, instruction storage component 650, instruction control component 655, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).
[0095] The command receiving component 625 may be configured as or otherwise support means for receiving an initialization command at a common logic block of a first semiconductor die of the memory system 620, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, each of the plurality of interface blocks being operable to access (e.g., via a set of corresponding one or more channels) one or more corresponding memory arrays of one or more second semiconductor dies of the memory system 620. The interface block output component 630 may be configured as or otherwise support means for outputting an indication of an instruction for each of the plurality of interface blocks based on receiving the initialization command. The interface block receiving component 635 may be configured as or otherwise support means for receiving the instruction by each of the plurality of interface blocks based on the indication. The instruction executing component 640 may be configured as or otherwise support means for executing (e.g., initiating) one or more corresponding operations (e.g., initialization operations) by each of the plurality of interface blocks based on the interface block receiving the instruction.
[0096] In some examples, the instruction storage component 650 may be configured as or otherwise support means for storing received instructions by each of the plurality of interface blocks to a corresponding volatile storage component associated with the interface block, and each interface block may perform one or more corresponding initialization operations based on each interface block storing the received instructions.
[0097] In some examples, instruction control component 655 may be configured or otherwise support means for storing an indication associated with completion of an interface block to a register based on an interface block completion instruction in the plurality of interface blocks.
[0098] In some examples, the interface block receiving component 635 may be configured or otherwise support a means for receiving a second instruction based on a second indication including the instruction. In some examples, the instruction execution component 640 may be configured or otherwise support a means for executing (e.g., starting) one or more corresponding second operations based on receiving the second instruction.
[0099] In some examples, to support receiving instructions, interface block receiving component 635 may be configured or otherwise support means for reading instructions from non-volatile storage of memory system 620 using a respective command channel of each of the plurality of interface blocks.
[0100] In some examples, outputting the indication may be based on receiving the indication from a second non-volatile storage device of the common logic block.
[0101] In some examples, each interface block of the plurality of interface blocks may be associated with a respective plurality of data channels between the interface block and one or more respective memory arrays.
[0102] In some examples, non-volatile storage devices may include one or more one-time programmable memory elements.
[0103] In some examples, to support receiving the initialization command, the command receiving component 625 can be configured or otherwise support means for receiving the initialization command from the host system using the evaluation interface of the common logic block.
[0104] In some examples, the instruction execution component 640 may be configured to or otherwise support means for determining by each of the plurality of interface blocks whether to apply row repair, column repair, or through silicon via repair to access one or more respective memory arrays based on performing one or more respective initialization operations.
[0105] In some examples, the command receiving component 625 may be configured or otherwise support means for receiving an evaluation command at a common logic block of a first semiconductor die of the memory system 620, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, each of the plurality of interface blocks being operable to access (e.g., via a set of corresponding one or more channels) one or more corresponding memory arrays of one or more second semiconductor dies of the memory system 620. In some examples, the interface block output component 630 may be configured or otherwise support means for outputting an indication of an evaluation operation to each of the plurality of interface blocks based on receiving the evaluation command, the evaluation operation being associated with evaluating an access operation associated with the one or more corresponding memory arrays. In some examples, the interface block receiving component 635 may be configured or otherwise support means for receiving, by each of the plurality of interface blocks, an instruction to evaluate the operation based on the indication. In some examples, instruction execution component 640 may be configured or otherwise support means for executing, by each of the plurality of interface blocks, one or more operations (eg, a portion of an instruction that initiates an evaluation operation) based on receiving an instruction.
[0106] In some examples, the interface block receiving component 635 may be configured or otherwise support means for receiving, by an interface block of the plurality of interface blocks, an indication of a second evaluation operation based on an instruction to perform the evaluation operation. In some examples, the instruction execution component 640 may be configured or otherwise support means for executing (e.g., initiating) a portion of the second evaluation operation by the interface block based on receiving the second evaluation operation.
[0107] In some examples, instruction control component 655 may be configured or otherwise support means for storing a value to a register associated with an interface block of the plurality of interface blocks, the value indicating that the interface block has completed an evaluation operation.
[0108] In some examples, the command receiving component 625 may be configured or otherwise support means for receiving a second evaluation command at the common logic block and after storing the value. In some examples, the interface block output component 630 may be configured or otherwise support means for outputting a second indication of a second evaluation operation to each of the plurality of interface blocks based on receiving the second evaluation command. In some examples, the interface block receiving component 635 may be configured or otherwise support means for receiving a second evaluation operation based on the output indication by each of the plurality of interface blocks. In some examples, the instruction execution component 640 may be configured or otherwise support means for initiating a portion of a second evaluation operation based on receiving the second evaluation operation by each of the plurality of interface blocks.
[0109] In some examples, the evaluation operation may be written to a non-volatile storage device of the memory system 620, and receiving the evaluation operation may include reading the evaluation operation from the non-volatile storage device using a respective command channel of each of the plurality of interface blocks.
[0110] In some examples, outputting the indication may be based on receiving the indication from a second non-volatile storage device of the common logic block.
[0111] In some examples, each interface block of the plurality of interface blocks includes a respective plurality of data channels between the interface block and one or more respective memory arrays.
[0112] In some examples, the evaluation operations include repair operations for one or more columns of memory cells associated with a memory array in one or more respective memory arrays, test operations for one or more through-silicon vias (TSVs) of the memory system 620, operations associated with disabling one or more memory cells of the one or more respective memory arrays, or a combination thereof.
[0113] The initialization control component 645 may be configured to or otherwise support means for determining to initialize the memory system 620 at a common logic block of a first semiconductor die of the memory system 620, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, each of the plurality of interface blocks being operable to access one or more corresponding memory arrays of one or more second semiconductor dies of the memory system 620. In some examples, the interface block output component 630 may be configured to or otherwise support means for outputting an indication of one or more instructions associated with initializing the memory system 620 to each of the plurality of interface blocks based on the determination to initialize the memory system 620. In some examples, the interface block receiving component 635 may be configured to or otherwise support means for receiving the one or more instructions by each of the plurality of interface blocks based on the output indication. In some examples, the instruction execution component 640 may be configured to or otherwise support means for executing (e.g., launching) the one or more instructions by each of the plurality of interface blocks based on receiving the one or more instructions.
[0114] In some examples, determining to initialize memory system 620 can be based on identifying a power-on condition of memory system 620 .
[0115] In some examples, command receiving component 625 may be configured or otherwise support means for receiving an initialization command at a common logic block. In some examples, interface block output component 630 may be configured or otherwise support means for outputting an indication based on receiving an initialization command.
[0116] Figure 7A flowchart illustrating a method 700 for supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown. The operations of the method 700 may be implemented by a memory system or components thereof described herein. For example, the operations of the method 700 may be implemented by reference to Figures 1 to 6 The memory system described herein performs. In some examples, the memory system may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the memory system may use dedicated hardware to perform aspects of the described functions.
[0117] At 705, the method may include receiving an initialization command at a common logic block of a first semiconductor die of a memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access (e.g., via a set of respective one or more channels) one or more respective memory arrays of one or more second semiconductor dies of the memory system. Operation 705 may be performed according to examples disclosed herein. For example, the memory system may include a logic block 230 that receives signaling from a host device (e.g., using the evaluation interface 310).
[0118] At 710, the method may include outputting an indication of instructions for each interface block in the plurality of interface blocks based on receiving the initialization command. Operation 710 may be performed according to examples disclosed herein. For example, logic block 230 may include broadcast command circuitry 325 that outputs an indication to interface block 220.
[0119] At 715, the method may include receiving, by each of the plurality of interface blocks, an instruction based on the indication. Operation 715 may be performed according to examples disclosed herein. For example, the interface block 220 may include a command channel controller 360 that receives instructions from one or more NV arrays 270.
[0120] At 720, the method may include performing, by each of the plurality of interface blocks, one or more respective initialization operations based on the interface block receiving the instruction. Operation 720 may be performed according to examples disclosed herein. For example, the interface block 220 may include an interface controller 305 that executes the instruction.
[0121] In some examples, the apparatus described herein may perform one or several methods, such as method 700. The apparatus may include features, circuitry, logic, means, or instructions (such as a non-transitory computer-readable medium storing instructions executable by a processor) for performing the following aspects of the present disclosure, or any combination thereof:
[0122] Aspect 1: A method, apparatus, or non-transitory computer-readable medium, comprising operations, features, circuit systems, logic, means, or instructions, or any combination thereof, for: receiving an initialization command at a common logic block of a first semiconductor die of a memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access (e.g., via a set of corresponding one or more channels) one or more corresponding memory arrays of one or more second semiconductor die of the memory system; outputting an indication of an instruction for each of the plurality of interface blocks based on receiving the initialization command; receiving the instruction by each of the plurality of interface blocks based on the indication; and performing one or more corresponding initialization operations by each of the plurality of interface blocks based on the interface block receiving the instruction.
[0123] Aspect 2: The method, apparatus or non-transitory computer-readable medium according to Aspect 1, further comprising the following operations, features, circuit systems, logic, components or instructions or any combination thereof: each interface block among the multiple interface blocks stores the received instructions to a corresponding volatile storage component associated with the interface block, wherein each interface block performs the one or more corresponding initialization operations based on each interface block storing the received instructions.
[0124] Aspect 3: A method, apparatus or non-temporary computer-readable medium according to any one of Aspects 1 to 2, further comprising operations, features, circuit systems, logic, components or instructions or any combination thereof for: storing an indication associated with the completion of the interface block in a register based on the interface block among the multiple interface blocks completing the one or more corresponding initialization operations.
[0125] Aspect 4: A method, apparatus or non-transitory computer-readable medium according to any one of Aspects 1 to 3, further comprising operations, features, circuit systems, logic, components or instructions or any combination thereof for: receiving a corresponding second instruction by at least one of the multiple interface blocks based on a second indication including the instruction; and performing one or more corresponding second operations based on receiving the second instruction.
[0126] Aspect 5: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 4, wherein receiving the instruction includes operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for reading the instruction from a non-volatile storage device of the memory system using a corresponding command channel of each of the multiple interface blocks.
[0127] Aspect 6: The method, apparatus, or non-transitory computer-readable medium of aspect 5, wherein outputting the indication is based on receiving the indication from a second non-volatile storage device of the common logic block.
[0128] Aspect 7: The method, apparatus, or non-transitory computer-readable medium of any one of Aspects 5 to 6, wherein each interface block of the plurality of interface blocks is associated with a respective plurality of data channels between the interface block and the one or more respective memory arrays.
[0129] Aspect 8: The method, apparatus, or non-transitory computer-readable medium of any one of aspects 5 to 7, wherein the non-volatile storage comprises one or more one-time programmable memory elements.
[0130] Aspect 9: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 8, wherein receiving the initialization command comprises operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for receiving the initialization command from a host system using an evaluation interface of the common logic block.
[0131] Aspect 10: The method, apparatus, or non-transitory computer-readable medium of any one of Aspects 1 to 9, further comprising operations, features, circuit systems, logic, means, or instructions, or any combination thereof, for: determining by each of the plurality of interface blocks whether to apply row repair, column repair, or through-silicon via repair to access the one or more corresponding memory arrays based on performing the one or more corresponding initialization operations.
[0132] Figure 8 A flowchart illustrating a method 800 for supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown. The operations of the method 800 may be implemented by a memory system or components thereof described herein. For example, the operations of the method 800 may be implemented by reference to Figures 1 to 6 The memory system described herein performs. In some examples, the memory system may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the memory system may use dedicated hardware to perform aspects of the described functions.
[0133] At 805, the method may include receiving an evaluation command at a common logic block of a first semiconductor die of a memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access (e.g., via a set of respective one or more channels) one or more respective memory arrays of one or more second semiconductor dies of the memory system. Operation 805 may be performed according to examples disclosed herein. For example, the memory system may include a logic block 230 that receives signaling from a host device (e.g., using the evaluation interface 310).
[0134] At 810, the method may include outputting an indication of an evaluation operation to each of the plurality of interface blocks based on receiving the evaluation command, the evaluation operation being associated with evaluating access operations associated with one or more respective memory arrays. Operation 810 may be performed according to examples disclosed herein. For example, logic block 230 may include broadcast command circuitry 325 that outputs an indication to interface block 220.
[0135] At 815, the method may include receiving, by each of the plurality of interface blocks, an instruction to evaluate an operation based on the indication. Operation 815 may be performed according to examples disclosed herein. For example, the interface block 220 may include a command channel controller 360 that receives instructions from one or more NV arrays 270.
[0136] At 820, the method may include initiating, by each of the plurality of interface blocks, a portion of an evaluation operation based on receiving the instruction. Operation 820 may be performed according to examples disclosed herein. For example, the interface block 220 may include an interface controller 305 that executes the instruction.
[0137] In some examples, the apparatus described herein may perform one or several methods, such as method 800. The apparatus may include features, circuitry, logic, means, or instructions (such as a non-transitory computer-readable medium storing instructions executable by a processor) for performing the following aspects of the present disclosure, or any combination thereof:
[0138] Aspect 11: A method, apparatus, or non-transitory computer-readable medium, comprising operations, features, circuit systems, logic, means, or instructions, or any combination thereof, for: receiving an evaluation command at a common logic block of a first semiconductor die of a memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access (e.g., via a set of corresponding one or more channels) one or more corresponding memory arrays of one or more second semiconductor die of the memory system; outputting an indication of an evaluation operation to each of the plurality of interface blocks based on receiving the evaluation command, the evaluation operation being associated with evaluating an access operation associated with the one or more corresponding memory arrays; receiving, by each of the plurality of interface blocks, an instruction for the evaluation operation based on the indication; and initiating, by each of the plurality of interface blocks, a portion of the instruction for the evaluation operation based on receiving the instruction.
[0139] Aspect 12: The method, apparatus or non-transitory computer-readable medium according to Aspect 11, further comprising the following operations, features, circuit systems, logic, components or instructions or any combination thereof: receiving an indication of a second evaluation operation by an interface block among the multiple interface blocks based on the instruction to perform the evaluation operation; and starting a portion of the second evaluation operation by the interface block based on receiving the second evaluation operation.
[0140] Aspect 13: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 11 to 12, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: storing a value to a register associated with an interface block among the plurality of interface blocks, the value indicating that the interface block has completed the evaluation operation.
[0141] Aspect 14: The method, apparatus or non-transitory computer-readable medium according to Aspect 13, further comprising the following operations, features, circuit systems, logic, components or instructions or any combination thereof: receiving a second evaluation command at the common logic block and after storing the value; outputting a second indication of a second evaluation operation to each of the multiple interface blocks based on receiving the second evaluation command; receiving the second evaluation operation by each of the multiple interface blocks based on outputting the indication; and starting a part of the second evaluation operation by each of the multiple interface blocks based on receiving the second evaluation operation.
[0142] Aspect 15: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 11 to 14, wherein the evaluation operation is written to a non-volatile storage device of the memory system, and receiving the evaluation operation includes reading the evaluation operation from the non-volatile storage device using a corresponding command channel of each interface block of the plurality of interface blocks.
[0143] Aspect 16: The method, apparatus, or non-transitory computer-readable medium of Aspect 15, wherein outputting the indication is based on receiving the indication from a second non-volatile storage device of the common logic block.
[0144] Aspect 17: The method, apparatus, or non-transitory computer-readable medium of any of Aspects 11 to 16, wherein each interface block of the plurality of interface blocks comprises a respective plurality of data channels between the interface block and the one or more respective memory arrays.
[0145] Aspect 18: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 11 to 17, wherein the evaluation operation includes a repair operation for one or more columns of memory cells associated with a memory array in the one or more corresponding memory arrays, a test operation for one or more through-silicon vias (TSVs) of the memory system, an operation associated with disabling one or more memory cells of the one or more corresponding memory arrays, or a combination thereof.
[0146] Fig. 9 A flowchart illustrating a method 900 for supporting boot and initialization techniques for a stacked memory architecture according to examples disclosed herein is shown. The operations of the method 900 may be implemented by a memory system or components thereof described herein. For example, the operations of the method 900 may be implemented by reference to Figures 1 to 6 The memory system described herein performs. In some examples, the memory system may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the memory system may use dedicated hardware to perform aspects of the described functions.
[0147] At 905, the method may include determining, at a common logic block of a first semiconductor die of the memory system, to initialize the memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access (e.g., via a set of corresponding one or more channels) one or more corresponding memory arrays of one or more second semiconductor dies of the memory system. Operation 905 may be performed according to examples disclosed herein. For example, the memory system may include the logic block 230 that determines how to initialize the memory system.
[0148] At 910, the method may include outputting an indication of one or more instructions associated with initializing the memory system to each of the plurality of interface blocks based on determining to initialize the memory system. Operation 910 may be performed according to examples disclosed herein. For example, logic block 230 may include broadcast command circuitry 325 that outputs an indication to interface block 220.
[0149] At 915, the method may include receiving one or more instructions by each of the plurality of interface blocks based on the output indication. Operation 915 may be performed according to examples disclosed herein. For example, the interface block 220 may include a command channel controller 360 that receives instructions from one or more NV arrays 270.
[0150] At 920, the method may include initiating, by each of the plurality of interface blocks, a portion of the one or more instructions based on receiving the one or more instructions. Operation 920 may be performed according to examples disclosed herein. For example, the interface block 220 may include an interface controller 305 that executes the instructions.
[0151] In some examples, the apparatus described herein may perform one or several methods, such as method 900. The apparatus may include features, circuitry, logic, means, or instructions (such as a non-transitory computer-readable medium storing instructions executable by a processor) for performing the following aspects of the present disclosure, or any combination thereof:
[0152] Aspect 19: A method, apparatus, or non-transitory computer-readable medium, comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: determining to initialize a memory system at a common logic block of a first semiconductor die of a memory system, the common logic block being coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each being operable to access (e.g., via a set of corresponding one or more channels) one or more corresponding memory arrays of one or more second semiconductor die of the memory system; outputting an indication of one or more instructions associated with initializing the memory system to each of the plurality of interface blocks based on determining to initialize the memory system; receiving the one or more instructions by each of the plurality of interface blocks based on outputting the indication; and initiating a portion of the one or more instructions by each of the plurality of interface blocks based on receiving the one or more instructions.
[0153] Aspect 20: The method, apparatus, or non-transitory computer-readable medium of aspect 19, wherein determining to initialize the memory system is based on identifying a power-on condition of the memory system.
[0154] Aspect 21: The method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 19 to 20, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: receiving an initialization command at the common logic block; and outputting the indication based on receiving the initialization command.
[0155] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, portions from two or more of the methods may be combined.
[0156] An apparatus is described. The following provides an overview of aspects of the apparatus described herein:
[0157] Aspect 22: An apparatus comprising: a first semiconductor die of a memory system, the first semiconductor die comprising: a common logic block; and a plurality of first interface blocks coupled to the common logic block; and one or more second semiconductor die of the memory system, coupled to the first semiconductor die and comprising: a plurality of second interface blocks, each second interface block coupled to a corresponding one of the plurality of first interface blocks; and a plurality of memory arrays, each memory array coupled to one of the plurality of second interface blocks, wherein the common logic block comprises a logic circuit system operable to initiate initialization of the plurality of first interface blocks.
[0158] Aspect 23: The apparatus of aspect 22, wherein the logic circuitry of the common logic block is further operable to: receive an initialization command from a host device; and initiate the initialization based on the received initialization command.
[0159] Aspect 24: The apparatus of any of aspects 22 to 23, wherein the logic circuitry of the common logic block is further operable to: receive an initialization command via an evaluation interface of the common logic block; and initiate the initialization based on the received initialization command.
[0160] Aspect 25: The apparatus according to any one of aspects 22 to 24, wherein to initiate the initialization, the logic circuit system of the common logic block is operable to: output an indication of an instruction to each first interface block of the plurality of first interface blocks based on initiating the initialization.
[0161] Aspect 26: The apparatus of aspect 25, wherein to output the indication, the logic circuitry of the common logic block is operable to read the indication from a non-volatile storage device of the common logic block.
[0162] Aspect 27: The apparatus of any of Aspects 22-26, wherein each first interface block of the plurality of first interface blocks includes respective logic circuitry operable to receive instructions associated with the initialization.
[0163] Aspect 28: The apparatus of aspect 27, wherein the respective logic circuitry of each first interface block of the plurality of first interface blocks is further operable to: initiate a portion of the instruction based on receiving the instruction.
[0164] Aspect 29: An apparatus according to any one of Aspects 27 to 28, wherein: the one or more second semiconductor dies further include a plurality of one-time programmable memory elements storing information associated with operating the plurality of first interface blocks; and receiving the instruction is based on reading the information from the plurality of one-time programmable memory elements.
[0165] Aspect 30: An apparatus according to any one of Aspects 22 to 29, wherein a second semiconductor die among the one or more second semiconductor die is coupled to the first semiconductor die based on a fusion of a plurality of second conductive contacts of the second semiconductor die and a plurality of first conductive contacts of the first semiconductor die, the fusion electrically coupling each second interface block with the corresponding one of the plurality of first interface blocks.
[0166] The information and signals described herein may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, or signaling symbols that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Some figures may illustrate a signal as a single signal; however, a signal may represent a signal bus, where the bus may have various bit widths.
[0167] The terms "electronic communication," "conductive contact," "connection," and "coupling" may refer to a relationship between components that supports the flow of signals between the components. Components are considered to be in electronic communication (e.g., conductive contact, connection, coupling) with each other if there is any electrical path (e.g., conductive path) between the components that can support the flow of signals (e.g., charge, current, voltage) between the components at any time. At any given time, the conductive path between components that are in electronic communication (e.g., conductive contact, connection, coupling) with each other may be an open circuit or a closed circuit based on the operation of the device that includes the connected components. The conductive path between the connected components may be a direct conductive path between the components, or the conductive path between the connected components may be an indirect conductive path that may include intermediate components (e.g., switches, transistors, or other components). In some examples, the flow of signals between the connected components may be interrupted for a period of time, for example, using one or more intermediate components (e.g., switches or transistors).
[0168] The term "coupled" (e.g., "electrically coupled") may refer to a condition that transitions from an open-circuit relationship between components, where signals cannot currently be communicated between the components (e.g., via conductive paths), to a closed-circuit relationship between the components, where signals can be communicated between the components (e.g., via conductive paths). When a component, such as a controller, couples other components together, the component causes a change that allows signals to flow between the other components via conductive paths that previously did not allow signals to flow.
[0169] The term "isolation" refers to a relationship between components where a signal cannot currently flow between the components. Components are isolated from one another if an open circuit exists between the components. For example, when a switch positioned between two components is opened, the components separated by the switch are isolated from one another. When a controller isolates two components, the controller causes a change that prevents a signal from flowing between the components using a conductive path that previously permitted the signal to flow.
[0170] The description set forth herein describes example configurations in conjunction with the accompanying drawings and does not represent all examples that may be implemented or within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" rather than "preferred" or "superior to other examples". The "Detailed Description" includes specific details for providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some examples, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0171] In the accompanying drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes the similar components. If only the first reference label is used in the specification, the description applies to any of the similar components having the same first reference label, regardless of the second reference label.
[0172] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions (e.g., code) on a computer-readable medium or transmitted via a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination of any of these. Features implementing the functions may also be physically located at various locations, including being distributed so that portions of the functions are implemented at different physical locations.
[0173] For example, the various descriptive blocks and modules described in connection with the present disclosure may be implemented or executed with a processor designed to perform the functions described herein, such as a DSP, ASIC, FPGA, discrete gate logic, discrete transistor logic, discrete hardware components, other programmable logic devices, or any combination thereof. A processor may be an example of a microprocessor, a controller, a microcontroller, a state machine, or any type of processor. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0174] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items preceded by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Moreover, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."
[0175] Computer-readable media include both non-transitory computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available media that can be accessed by a computer. For example, but not limited to, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disk (CD) ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices or any other non-transitory media that can be used to carry or store desired program code components in the form of instructions or data structures and can be accessed by a computer or processor. Moreover, any connection is appropriately referred to as computer-readable media. For example, if the software is transmitted from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave), then coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave) are included in the definition of media. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0176] The description herein is provided to enable one skilled in the art to make or use the present disclosure. Those skilled in the art will appreciate the various modifications of the present disclosure, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method wherein include: receiving an initialization command at a common logic block of a first semiconductor die of a memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access one or more respective memory arrays of one or more second semiconductor die of the memory system via a set of respective one or more channels; outputting an indication of instructions for each of the plurality of interface blocks based on receiving the initialization command; receiving, by each of the plurality of interface blocks, the instruction based on the indication; and One or more respective initialization operations are performed by each interface block of the plurality of interface blocks based on receipt of the instruction by the interface block.
2. The method according to claim 1, further comprising: include: The received instructions are stored by each interface block of the plurality of interface blocks to a respective volatile storage component associated with the interface block, wherein each interface block performs the one or more respective initialization operations based on each interface block storing the received instructions.
3. The method according to claim 1, further comprising: include: Based on an interface block of the plurality of interface blocks completing the one or more respective initialization operations, an indication associated with the completion of the interface block is stored to a register.
4. The method according to claim 1, further comprising: include: receiving, by at least one of the plurality of interface blocks, a corresponding second instruction based on a second indication including the instruction; and One or more corresponding second operations are performed based on receiving the second instruction.
5. The method according to claim 1, wherein receiving the instruction include: The instruction is read from a non-volatile storage device of the memory system using a corresponding command channel of each interface block of the plurality of interface blocks. 6 . The method of claim 5 , wherein outputting the indication is based on receiving the indication from a second non-volatile storage device of the common logic block.
7. The method of claim 5, wherein each interface block of the plurality of interface blocks is associated with a respective plurality of data channels between the interface block and the one or more respective memory arrays.
8. The method of claim 5, wherein the non-volatile storage device comprises one or more one-time programmable memory elements.
9. The method of claim 1, wherein receiving the initialization command include: The initialization command is received from a host system using an evaluation interface of the common logic block.
10. The method according to claim 1, further comprising: include: The one or more respective memory arrays are accessed by each interface block of the plurality of interface blocks based on performing the one or more respective initialization operations to determine whether to apply row repair, column repair, or through silicon via repair.
11. A device, wherein include: A first semiconductor die of a memory system, the first semiconductor die comprising: Common logic blocks; and a plurality of first interface blocks coupled to the common logic block; and one or more second semiconductor dies of the memory system coupled to the first semiconductor die and comprising: a plurality of second interface blocks, each second interface block coupled to a respective one of the plurality of first interface blocks via a respective set of one or more channels; and a plurality of memory arrays, each memory array coupled to one of the plurality of second interface blocks, Wherein the common logic block includes logic circuitry operable to initiate initialization of the plurality of first interface blocks.
12. The apparatus of claim 11, wherein the logic circuitry of the common logic block is further operable to: receiving an initialization command from a host device; and The initialization is initiated based on the received initialization command.
13. The apparatus of claim 11, wherein the logic circuitry of the common logic block is further operable to: receiving an initialization command via an evaluation interface of the common logic block; and The initialization is initiated based on the received initialization command.
14. The apparatus of claim 11, wherein to initiate the initialization, the logic circuitry of the common logic block is operable to: An indication of an instruction is output to each first interface block of the plurality of first interface blocks based on initiating the initialization.
15. The apparatus of claim 14, wherein to output the indication, the logic circuitry of the common logic block is operable to read the indication from a non-volatile storage device of the common logic block.
16. The apparatus of claim 11, wherein each first interface block of the plurality of first interface blocks comprises respective logic circuitry operable to: Instructions associated with the initialization are received.
17. The apparatus of claim 16, wherein the respective logic circuitry of each first interface block of the plurality of first interface blocks is further operable to: One or more initialization operations are performed based on receiving the instruction.
18. The device according to claim 16, in: The one or more second semiconductor dies further include a plurality of one-time programmable memory elements storing information associated with operating the plurality of first interface blocks; and Receiving the instruction is based on reading the information from the plurality of one-time programmable memory elements.
19. The apparatus of claim 11, wherein a second semiconductor die among the one or more second semiconductor die is coupled to the first semiconductor die based on a fusion of a plurality of second conductive contacts of the second semiconductor die and a plurality of first conductive contacts of the first semiconductor die, the fusion electrically coupling each second interface block with the corresponding one of the plurality of first interface blocks.
20. A method wherein include: receiving an evaluation command at a common logic block of a first semiconductor die of a memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access one or more respective memory arrays of one or more second semiconductor die of the memory system via a set of respective one or more channels; outputting, based on receiving the evaluation command, an indication of an evaluation operation to each of the plurality of interface blocks, the evaluation operation associated with evaluating access operations associated with the one or more respective memory arrays; receiving, by each of the plurality of interface blocks, an instruction for the evaluation operation based on the indication; and A portion of the evaluation operation is initiated by each of the plurality of interface blocks based on receiving the instruction.
21. The method according to claim 20, further comprising: include: receiving, by an interface block of the plurality of interface blocks, an indication of a second evaluation operation based on the instruction to perform the evaluation operation; and A portion of the second evaluation operation is initiated by the interface block based on receiving the second evaluation operation.
22. The method according to claim 20, further comprising: include: A value is stored in a register associated with an interface block of the plurality of interface blocks, the value indicating that the interface block has completed the evaluation operation.
23. The method according to claim 22, further comprising: include: receiving, at the common logic block and after storing the value, a second evaluation command; outputting a second indication of a second evaluation operation to each of the plurality of interface blocks based on receiving the second evaluation command; receiving, by each of the plurality of interface blocks, the second evaluation operation based on outputting the indication; and A portion of the second evaluation operation is initiated by each of the plurality of interface blocks based on receiving the second evaluation operation.
24. The method according to claim 20, in: The evaluation operation is written to a non-volatile storage device of the memory system; and Receiving the evaluation operation includes reading the evaluation operation from the non-volatile storage device using a corresponding command channel of each of the plurality of interface blocks.
25. The method of claim 24, wherein outputting the indication is based on receiving the indication from a second non-volatile storage device of the common logic block.
26. The method of claim 20, wherein each interface block of the plurality of interface blocks comprises a respective plurality of data channels between the interface block and the one or more respective memory arrays.
27. The method of claim 20, wherein the evaluation operation comprises a repair operation for one or more columns of memory cells associated with a memory array in the one or more corresponding memory arrays, a test operation for one or more through-silicon vias (TSVs) of the memory system, an operation associated with disabling one or more memory cells of the one or more corresponding memory arrays, or a combination thereof.
28. A method wherein include: determining to initialize the memory system at a common logic block of a first semiconductor die of the memory system, the common logic block coupled to a plurality of interface blocks of the first semiconductor die, the plurality of interface blocks each operable to access one or more respective memory arrays of one or more second semiconductor dies of the memory system via a set of respective one or more channels; outputting, based on determining to initialize the memory system, an indication of one or more instructions associated with initializing the memory system to each of the plurality of interface blocks; receiving, by each of the plurality of interface blocks, the one or more instructions based on outputting the indication; and A portion of the one or more instructions is initiated by each interface block of the plurality of interface blocks based on receiving the one or more instructions.
29. The method of claim 28, wherein determining to initialize the memory system is based on identifying a power-on condition of the memory system.
30. The method of claim 28, further comprising: include: receiving an initialization command at the common logic block; and The indication is output based on receiving the initialization command.
