Storage device and operation method thereof
By using the ready-busy pin and ODT flag generator in the storage device to perform ODT operations, the hardware burden and performance reduction caused by ODT operations in the prior art is solved, and more efficient data transmission is achieved.
Patent Information
- Application Number
- CN202110614115.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-08-18
- Filing Date
- 2021-06-02
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2041-06-02
AI Technical Summary
When performing an on-die termination (ODT) operation, existing storage devices need to pass through the ODT pin of the memory controller, resulting in increased hardware burden and reduced performance.
By using the ready-busy (RB) pin of the memory device to control ODT operations, reducing dependence on the ODT pin of the memory controller, using the ODT flag generator and the ODT actuator to determine and execute the ODT operation type to achieve non-compliance ODT operation of the target memory device.
It reduces the hardware burden, improves the operating performance of the storage device, avoids direct control of the memory controller by ODT operation, and improves the integrity of data transmission signal.
Smart Images

Figure CN114077390B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to electronic devices, and more particularly to storage devices and operating methods thereof. Background Art
[0002] A storage device is a device that stores data based on a host device such as a computer, a smart phone, or a smart tablet. Storage devices include devices that store data in a magnetic disk such as a hard disk drive (HDD), and devices that store data in a semiconductor memory (especially a non-volatile memory) such as a solid-state drive (SSD) or a memory card.
[0003] The storage device may include a memory device in which data is stored and a memory controller that stores the data in the memory device. The memory device may be classified into a volatile memory and a non-volatile memory. Here, the non-volatile memory includes a read-only memory (ROM), a programmable ROM (PROM), an electrically programmable ROM (EPROM), an electrically erasable programmable ROM (EPM), a flash memory, a phase change RAM (PRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM), a ferroelectric RAM (FRAM), etc. Summary of the invention
[0004] A storage device according to an embodiment of the present disclosure includes: a plurality of memory devices, including a target memory device and a non-target memory device in which an operation is performed; and a memory controller, which is configured to control the plurality of memory devices. Each of the plurality of memory devices includes: an on die termination (ODT) flag generator, which is configured to generate a flag indicating that an ODT operation can be performed on the non-target memory device; and an ODT executor, which is configured to determine whether the ODT operation is an ODT read operation for a read operation or an ODT write operation for a write operation based on the flag, and is configured to generate an enable signal for enabling the ODT read operation or the ODT write operation.
[0005] A method for operating a storage device having multiple memory devices and a memory controller that controls the multiple memory devices according to an embodiment of the present disclosure includes: performing an operation by a target memory device among the multiple memory devices; generating a flag indicating that an on-die termination (ODT) operation can be performed on a non-target memory device; determining whether the ODT operation is an ODT read operation for a read operation or an ODT write operation for a write operation based on the flag; and generating an enable signal by the non-target memory device to enable the ODT read operation or the ODT write operation. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Figure 1is a block diagram illustrating a storage device.
[0007] Figure 2 is an example Figure 1 A diagram of the structure of a memory device.
[0008] Figure 3 is an example Figure 2 FIG. 1 is a diagram of an embodiment of a memory cell array.
[0009] Figure 4 is exemplified by Figure 1 A diagram of an on-die termination (ODT) operation performed by a memory controller.
[0010] Figure 5 is an example Figure 1 A diagram of the pin configuration of the memory device.
[0011] Fig. 6A and Figure 6B It is an example when Figure 1 A diagram of a target memory device and a non-target memory device when the number of memory devices is plural.
[0012] Figure 7 This is a diagram illustrating the process of generating a flag.
[0013] Figure 8 is an example Figure 7 Diagram of the configuration of the ODT logo generator.
[0014] Fig. 9 is a diagram illustrating commands output from a memory controller in order to perform an ODT operation on a non-target memory device.
[0015] Fig.10 A process of performing an ODT operation on a non-target memory based on a flag is illustrated.
[0016] Fig.11 is an example Fig.10 Diagram of the configuration of the ODT actuator.
[0017] Fig.12 is an example Fig.11 Diagram of the RX enable controller configuration.
[0018] Fig.13 is an example Fig.11 Diagram of the configuration of the ODT read enable controller.
[0019] Fig.14 is an example Fig.11 Diagram of the configuration of the ODT write enable controller.
[0020] Fig.15 is a timing diagram illustrating an ODT write operation.
[0021] Fig.16 is a timing diagram illustrating an ODT read operation.
[0022] Fig.17 is a timing diagram illustrating an ODT write operation and an ODT operation.
[0023] Fig.18 is a diagram illustrating the operation of a memory device according to an embodiment of the present disclosure.
[0024] Fig.19 is an example Figure 1 FIG. 1 is a diagram of another embodiment of a memory controller.
[0025] Fig. 20 is a block diagram illustrating a memory card system to which a storage device according to an embodiment of the present disclosure is applied.
[0026] Fig.21 is a block diagram exemplarily illustrating a solid state drive (SSD) system to which a storage device according to an embodiment of the present disclosure is applied.
[0027] Fig. 22 is a block diagram illustrating a user system to which a storage device according to an embodiment of the present disclosure is applied. DETAILED DESCRIPTION
[0028] The specific structural description or functional description of the embodiments of the concepts disclosed in this specification or this application is only exemplified for describing the embodiments of the concepts of the present disclosure. The embodiments of the concepts of the present disclosure can be performed in various forms, and the description is not limited to the embodiments described in this specification or this application.
[0029] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art to which the present disclosure pertains can easily carry out the technical spirit of the present disclosure.
[0030] It will be understood that although the terms "first", "second", "third", etc. are used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. Therefore, without departing from the teachings of the present disclosure, the first element in some embodiments may be referred to as the second element in other embodiments.
[0031] In addition, it will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, or there can be intervening elements. Conversely, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intervening elements.
[0032] Embodiments of the present disclosure provide a storage device and an operating method thereof that controls an on-die termination (ODT) operation without controlling an ODT pin of a memory controller.
[0033] According to the present technology, a memory device controls an on-die termination (ODT) operation by using a ready-busy (RB) pin of the memory device without using an ODT pin of a memory controller, so the memory device can improve the operation performance of the memory device with a reduced number of pins.
[0034] Figure 1 is a block diagram illustrating a storage device.
[0035] Reference Figure 1 , the storage device 50 may include a memory device 100 and a memory controller 200 .
[0036] The storage device 50 may be a device that stores data based on a host 300 such as a cellular phone, a smart phone, an MP3 player, a laptop computer, a desktop computer, a game console, a TV, a tablet PC, or an in-vehicle infotainment system.
[0037] The storage device 50 may be manufactured as one of various types of storage devices according to a host interface as a device for communicating with the host 300. For example, the storage device 50 may be configured as any of various types of storage devices such as SSD, multimedia cards in the form of MMC, eMMC, RS-MMC, and micro MMC, secure digital cards in the form of SD, mini SD, and micro SD, a universal serial bus (USB) storage device, a universal flash memory (UFS) device, a personal computer memory card international association (PCMCIA) card type storage device, a peripheral component interconnect (PCI) card type storage device, a PCI express (PCI-E) card type storage device, a compact flash (CF) card, a smart media card, and a memory stick.
[0038] The storage device 50 may be manufactured as any of various types of packages. For example, the storage device 50 may be manufactured as any of various types of packages such as package-on-package (PoP), system-in-package (SIP), system-on-chip (SOC), multi-chip package (MCP), chip-on-board (COB), wafer-level fabrication package (WFP), or wafer-level stacked package (WSP).
[0039] The memory device 100 may store data. The memory device 100 may operate based on the memory controller 200. The memory device 100 may include a memory cell array having a plurality of memory cells storing data. The memory cell array may include a plurality of memory blocks. Each memory block may include a plurality of memory cells, and the plurality of memory cells may configure a plurality of pages. In an embodiment, a page may be a unit of measure for storing data in the memory device 100 or for reading data stored in the memory device 100. A memory block may be a unit of measure for erasing data.
[0040] In an implementation, the memory device 100 may be a double data rate synchronous dynamic random access memory (DDR SDRAM), a low power double data rate 4 (LPDDR4) SDRAM, a graphic double data rate (GDDR) SDRAM, a low power DDR (LPDDR), a Rambus dynamic random access memory (RDRAM), a NAND flash memory, a vertical NAND flash memory, a NOR flash memory device, a resistive random access memory (RRAM), a phase change memory (PRAM), a magnetoresistive random access memory (MRAM), a ferroelectric random access memory (FRAM), a spin transfer torque random access memory (STT-RAM), etc. In this specification, for ease of description, it is assumed that the memory device 100 is a NAND flash memory.
[0041] The memory device 100 may be implemented as a two-dimensional array structure or a three-dimensional array structure. Hereinafter, the three-dimensional array structure will be described as an embodiment, but the present disclosure is not limited to the three-dimensional array structure. The present disclosure may be applied not only to a flash memory device in which a charge storage layer is configured by a conductive floating gate (FG), but also to a charge trap flash memory (CTF) in which a charge storage layer is configured by an insulating film.
[0042] In an embodiment, the memory device 100 may be operated in a single-level cell (SLC) method of storing one data bit in one memory cell. Alternatively, the memory device 100 may be operated in a method of storing at least two data bits in one memory cell. For example, the memory device 100 may be operated in a multi-level cell (MLC) method of storing two data bits in one memory cell, a triple-level cell (TLC) method of storing three data bits in one memory cell, or a quad-level cell (QLC) method of storing four data bits in one memory cell.
[0043] The memory device 100 is configured to receive commands and addresses from the memory controller 200, and is configured to access the area selected by the address in the memory cell array. That is, the memory device 100 can perform an operation corresponding to the command on the area selected by the address. For example, the memory device 100 can perform a write operation (programming operation), a read operation, or an erase operation based on the received command. For example, when a program command is received, the memory device 100 can program data to the area selected by the address. When a read command is received, the memory device 100 can read data from the area selected by the address. When an erase command is received, the memory device 100 can erase the data stored in the area selected by the address.
[0044] In an embodiment, the memory device 100 may include an ODT flag generator 150. The ODT flag generator 150 may generate a flag FLAG that provides an instruction to perform an on-die termination (ODT) operation on a non-target memory device or a non-target die. The ODT operation may be an operation to improve signal integrity (SI) by minimizing signal reflections, etc., at an interface between the memory controller 200 and the memory device 100. That is, the ODT operation may be an operation to set the size of a termination resistance (RTT) of an input / output terminal of the memory controller 200 or the memory device 100, and the ODT operation may be an operation for impedance matching of a data transmission line.
[0045] Furthermore, the target memory device may be a memory device in a busy state of performing an operation among a plurality of memory devices connected to the memory controller 200, and the target die may be a die in a busy state of performing an operation among a plurality of dies included in one memory device 100. In contrast, the non-target memory device may be a memory device in a ready state of not performing an operation among a plurality of memory devices connected to the memory controller 200, and the non-target die may be a die in a ready state of not performing an operation among a plurality of dies included in one memory device 100.
[0046] In an embodiment, the ODT flag generator 150 may generate a flag based on a read enable signal and an input / output select signal for a target memory device or a target die. Here, the input / output select signal may be a signal indicating that an input / output signal received from a memory controller is valid, and the read enable signal may be a signal enabling output of data.
[0047] In another embodiment, the flag may be generated based on a write enable signal and an input / output strobe signal for a target memory device or a target die. Here, the write enable signal may be a signal that enables input of data.
[0048] In an embodiment, the memory device 100 may include an ODT executor 170. The ODT executor 170 may perform an ODT operation on a non-target memory device or a non-target die based on a flag FLAG received from the memory controller 200. The flag FLAG may indicate that an ODT operation may be performed on a non-target memory device or a non-target die. In addition, a target memory device and a non-target memory device may be distinguished based on the flag FLAG.
[0049] In an embodiment, before performing the ODT operation, the memory device 100 may perform a preparation operation for performing the ODT operation based on a parameter setting command received from the memory controller 200. The preparation operation may include an operation of outputting a strobe signal indicating that the ODT operation is performed on a non-target memory device or a non-target die and a signal indicating that other operations except the ODT operation cannot be performed to the memory controller 200.
[0050] Thereafter, when the ODT executor 170 receives the flag FLAG from the memory controller 200, the ODT executor 170 may generate a signal providing an instruction to perform an ODT write or ODT read operation through a ready / busy signal generated based on the flag FLAG and may output the signal to the memory controller 200. Here, the ODT executor 170 may output a signal to turn on a buffer that temporarily stores data before performing the ODT write or ODT read operation.
[0051] In the conventional art, to perform the ODT operation, the memory controller 200 generates a control signal itself based on a signal output from the memory device 100 and inputs the control signal through an ODT pin in the memory controller 200. Therefore, a termination resistance (RTT) of the memory controller 200 may be set.
[0052] However, in the present disclosure, the ODT operation may be performed based on a signal output from the memory device 100 instead of the ODT control signal of the memory controller 200, thereby reducing the burden on the memory controller 200. In addition, since the ODT operation may be performed by using the ready / busy pin of the memory device 100 instead of using the ODT pin of the memory controller 200, the burden on the hardware may be minimized.
[0053] The memory controller 200 may control overall operations of the storage device 50 .
[0054] The memory controller 200 may execute firmware when a power supply voltage is applied to the storage device 50. When the memory device 100 is a flash memory device 100, the memory controller 200 may operate firmware such as a flash translation layer (FTL) to control communication between the host 300 and the memory device 100.
[0055] In an embodiment, the memory controller 200 may include firmware (not shown) that receives data and a logical block address (LBA) from the host 300 and converts the LBA into a physical block address (PBA) indicating an address of a memory cell in which data included in the memory device 100 is to be stored. In addition, the memory controller 200 may store a logical-physical address mapping table in a buffer memory, the logical-physical address mapping table configuring a mapping relationship between the LBA and the PBA.
[0056] The memory controller 200 may control the memory device 100 to perform a program operation, a read operation, an erase operation, etc. based on a request of the host 300. For example, when a program request is received from the host 300, the memory controller 200 may convert the program request into a program command, and may provide the program command, the PBA, and data to the memory device 100. When a read request together with an LBA is received from the host 300, the memory controller 200 may change the read request into a read command, select a PBA corresponding to the LBA, and then provide the read command and the PBA to the memory device 100. When an erase request together with an LBA is received from the host 300, the memory controller 200 may change the erase request into an erase command, select a PBA corresponding to the LBA, and then provide the erase command and the PBA to the memory device 100.
[0057] In an embodiment, the memory controller 200 may generate and send a program command, address, and data to the memory device 100 without a request from the host 300. For example, the memory controller 200 may provide commands, addresses, and data to the memory device 100 to perform background operations such as a program operation for wear leveling and a program operation for garbage collection.
[0058] In an embodiment, the storage device 50 may further include a buffer memory (not shown). The memory controller 200 may control data exchange between the host 300 and the buffer memory (not shown). Alternatively, the memory controller 200 may temporarily store system data in the buffer memory to control the memory device 100. For example, the memory controller 200 may temporarily store data input from the host 300 in the buffer memory, and then may send the data temporarily stored in the buffer memory to the memory device 100.
[0059] In various embodiments, the buffer memory may be used as an operation memory and a cache memory of the memory controller 200. The buffer memory may store codes or commands executed by the memory controller 200. Alternatively, the buffer memory may store data processed by the memory controller 200.
[0060] In an embodiment, the buffer memory may be implemented as a dynamic random access memory (DRAM) (such as a double data rate synchronous dynamic random access memory (DDR SDRAM), DDR4 SDRAM, low power double data rate 4 (LPDDR4) SDRAM, graphics double data rate (GDDR) SDRAM, low power DDR (LPDDR), or Rambus dynamic random access memory (DRAM)) or a static random access memory (SRAM).
[0061] In various embodiments, the buffer memory may be connected through an external device outside the storage device 50. In this case, a volatile memory device externally connected to the storage device 50 may be used as a buffer memory.
[0062] In an embodiment, the memory controller 200 may control at least two or more memory devices. In this case, the memory controller 200 may control the memory devices based on an interleaving method, thereby improving operation performance.
[0063] The host 300 can communicate with the storage device 50 by using at least one of various communication methods such as universal serial bus (USB), serial AT attachment (SATA), serial attached SCSI (SAS), high-speed inter-chip (HSIC), small computer system interface (SCSI), peripheral component interconnect (PCI), PCI-Express (PCIe), non-volatile memory express (NVMe), universal flash memory (UFS), secure digital (SD), multimedia card (MMC), embedded MMC (eMMC), dual in-line memory module (DIMM), registered DIMM (RDIMM) and light load DIMM (LRDIMM).
[0064] Figure 2 is an example Figure 1 A diagram of the structure of a memory device.
[0065] Reference Figure 2 , the memory device 100 may include a memory cell array 110 , a peripheral circuit 120 , and a control logic 130 .
[0066] The memory cell array 110 may include a plurality of memory blocks BLK1 to BLKz. The plurality of memory blocks BLK1 to BLKz may be connected to a row decoder 121 through a row line RL. The plurality of memory blocks BLK1 to BLKz may be connected to a page buffer group 123 through bit lines BL1 to BLn. Each of the plurality of memory blocks BLK1 to BLKz includes a plurality of memory cells. As an embodiment, the plurality of memory cells are nonvolatile memory cells. The memory cells connected to the same word line may be defined as one page. Therefore, one memory block may include a plurality of pages.
[0067] The row lines RL may include at least one source select line, a plurality of word lines, and at least one drain select line.
[0068] Each memory cell included in the memory cell array 110 may be configured as a single level cell (SLC) storing one data bit, a multi level cell (MLC) storing two data bits, a triple level cell (TLC) storing three data bits, or a quad level cell (QLC) storing four data bits.
[0069] The peripheral circuit 120 may be configured to perform a program operation, a read operation, or an erase operation on a selected region of the memory cell array 110 based on the control of the control logic 130. The peripheral circuit 120 may drive the memory cell array 110. For example, the peripheral circuit 120 may apply various operating voltages to the row lines RL and the bit lines BL1 to BLn or discharge the applied voltages based on the control of the control logic 130.
[0070] The peripheral circuit 120 may include a row decoder 121 , a voltage generator 122 , a page buffer group 123 , a column decoder 124 , an input / output circuit 125 , and a sensing circuit 126 .
[0071] The row decoder 121 may be connected to the memory cell array 110 via a row line RL. The row line RL may include at least one source selection line, a plurality of word lines, and at least one drain selection line. In an embodiment, the word line may include a normal word line and a dummy word line. In an embodiment, the row line RL may further include a pipeline selection line.
[0072] The row decoder 121 may be configured to decode the row address RADD received from the control logic 130. The row decoder 121 may select at least one memory block among the memory blocks BLK1 to BLKz based on the decoded address. In addition, the row decoder 121 may select at least one word line of the memory block selected for applying the voltage generated by the voltage generator 122 to at least one word line WL based on the decoded address.
[0073] For example, during a programming operation, the row decoder 121 may apply a program voltage to a selected word line, and apply a program pass voltage having a level lower than the program voltage to unselected word lines. During a program verification operation, the row decoder 121 may apply a verification voltage to a selected word line, and apply a verification pass voltage higher than the verification voltage to unselected word lines. During a read operation, the row decoder 121 may apply a read voltage to a selected word line, and apply a read pass voltage higher than the read voltage to unselected word lines.
[0074] In an embodiment, the erase operation of the memory device 100 may be performed in units of memory blocks. During the erase operation, the row decoder 121 may select a memory block based on the decoded address. During the erase operation, the row decoder 121 may apply a ground voltage to a word line connected to the selected memory block.
[0075] The voltage generator 122 may operate based on the control of the control logic 130. The voltage generator 122 may be configured to generate a plurality of voltages by using an external power supply voltage supplied to the memory device 100. Specifically, the voltage generator 122 may generate various operation voltages Vop for a program operation, a read operation, and an erase operation based on the operation signal OPSIG. For example, the voltage generator 122 may generate a program voltage, a verification voltage, a pass voltage, a read voltage, an erase voltage, etc. based on the control of the control logic 130.
[0076] As an embodiment, the voltage generator 122 may generate an internal power supply voltage by adjusting an external power supply voltage. The internal power supply voltage generated by the voltage generator 122 is used as an operating voltage of the memory device 100.
[0077] As an embodiment, the voltage generator 122 may generate a plurality of voltages by using an external power supply voltage or an internal power supply voltage.
[0078] For example, the voltage generator 122 may include a plurality of pumping capacitors that receive an internal power supply voltage, and the plurality of pumping capacitors may be selectively activated based on the control logic 130 to generate a plurality of voltages.
[0079] The generated plurality of voltages may be supplied to the memory cell array 110 through the row decoder 121 .
[0080] The page buffer group 123 may include a first page buffer PB1 to an nth page buffer PBn. The first page buffer PB1 to the nth page buffer PBn may be connected to the memory cell array 110 through the first bit line BL1 to the nth bit line BLn, respectively. The first page buffer PB1 to the nth page buffer PBn may operate based on the control logic 130. Specifically, the first page buffer PB1 to the nth page buffer PBn may operate based on the page buffer control signal PBSIGNALS. For example, the first page buffer PB1 to the nth page buffer PBn may temporarily store data received through the first bit line BL1 to the nth bit line BLn, or may sense the voltage or current of the bit lines BL1 to BLn during a read or verification operation.
[0081] Specifically, during a program operation, when a program voltage is applied to a selected word line, the first to n-th page buffers PB1 to PBn may transmit data DATA received through the input / output circuit 125 to the selected memory cells through the first to n-th bit lines BL1 to BLn. The memory cells of the selected page may be programmed based on the transmitted data DATA. During a program verification operation, the first to n-th page buffers PB1 to PBn may read page data by sensing a voltage or current received from the selected memory cells through the first to n-th bit lines BL1 to BLn.
[0082] During a read operation, the first to nth page buffers PB1 to PBn may read data DATA from memory cells of a selected page through the first to nth bit lines BL1 to BLn and may output the read data DATA to the input / output circuit 125 based on the control of the column decoder 124 .
[0083] During an erase operation, the first to nth page buffers PB1 to PBn may float the first to nth bit lines BL1 to BLn or may apply an erase voltage.
[0084] The column decoder 124 may transfer data between the input / output circuit 125 and the page buffer group 123 based on the column address CADD. For example, the column decoder 124 may exchange data with the first to nth page buffers PB1 to PBn through the data lines DL, or may exchange data with the input / output circuit 125 through the column lines CL.
[0085] The input / output circuit 125 can transmit the reference Figure 1 Description Figure 1 The memory controller 200 receives a command CMD and an address ADDR, or may exchange data DATA with the column decoder 124 .
[0086] The sensing circuit 126 may generate a reference current based on the enable bit signal VRYBIT during a read operation or a verification operation, and may compare a sensing voltage VPB received from the page buffer group 123 with a reference voltage generated by the reference current to output a pass signal PASS or a fail signal FAIL.
[0087] The control logic 130 may output an operation signal OPSIG, a row address RADD, a page buffer control signal PBSIGNALS, and an enable bit signal VRYBIT based on the command CMD and the address ADDR to control the peripheral circuit 120. For example, the control logic 130 may control a read operation of a selected memory block based on a sub-block read command and an address. In addition, the control logic 130 may control an erase operation of a selected sub-block included in a selected memory block based on a sub-block erase command and an address. In addition, the control logic 130 may determine whether a verification operation is passed or failed based on a pass signal PASS or a fail signal FAIL.
[0088] Figure 3 is an example Figure 2 FIG. 1 is a diagram of an embodiment of a memory cell array.
[0089] Reference Figure 2 and Figure 3 , Figure 3 It shows Figure 2 1 is a circuit diagram of any one memory block BLKa among a plurality of memory blocks BLK1 to BLKz included in the memory cell array 110.
[0090] The first selection line, the word line, and the second selection line arranged in parallel with each other may be connected to the memory block BLKa. For example, the word line may be arranged in parallel with each other between the first selection line and the second selection line. Here, the first selection line may be a source selection line SSL, and the second selection line may be a drain selection line DSL.
[0091] More specifically, the memory block BLKa may include a plurality of strings connected between the bit lines BL1 to BLn and the source line SL. The bit lines BL1 to BLn may be connected to the strings, respectively, and the source line SL may be connected to the strings in common. Since the strings may be configured to be identical to each other, the string ST connected to the first bit line BL1 will be specifically described as an example.
[0092] The string ST may include a source selection transistor SST, a plurality of memory cells F1 to F16, and a drain selection transistor DST connected in series between a source line SL and a first bit line BL1. One string ST may include at least one or more of the source selection transistor SST and the drain selection transistor DST. However, the present disclosure is not limited thereto, and the string ST may include more or fewer memory cells than the memory cells F1 to F16 shown in the drawings.
[0093] The source of the source select transistor SST may be connected to the source line SL, and the drain of the drain select transistor DST may be connected to the first bit line BL1. The memory cells F1 to F16 may be connected in series between the source select transistor SST and the drain select transistor DST. The gates of the source select transistors SST included in different strings may be connected to the source select line SSL, the gates of the drain select transistors DST may be connected to the drain select line DSL, and the gates of the memory cells F1 to F16 may be connected to a plurality of word lines WL1 to WL16. A group of memory cells connected to the same word line among the memory cells included in different strings may be referred to as a physical page PPG. Therefore, the memory block BLKa may include a physical page PPG of the number of word lines WL1 to WL16.
[0094] One memory cell can store one bit of data. This is generally referred to as a single-level cell (SLC). In this case, one physical page PPG can store one logical page (LPG) of data. One logical page (LPG) of data can include the number of data bits of the memory cells included in one physical page PPG. In addition, one memory cell can store two or more bits of data. This is generally referred to as a multi-level cell (MLC). In this case, one physical page PPG can store two or more logical pages (LPG) of data.
[0095] A memory cell storing two or more bits of data in one memory cell is called a multi-level cell (MLC). However, recently, as the number of data bits stored in one memory cell increases, a multi-level cell (MLC) refers to a memory cell storing two bits of data, a memory cell storing three or more bits of data is called a three-level cell (TLC), and a memory cell storing four or more bits of data is called a quad-level cell (QLC). In addition, a memory cell method for storing multi-bit data has been developed, and a memory cell storing two or more bits of data can be applied to the memory device 100 of the present embodiment.
[0096] In another embodiment, the memory block may have a three-dimensional structure. Each memory block may include a plurality of memory cells stacked on a substrate. Such a plurality of memory cells may be arranged along the +X direction, the +Y direction, and the +Z direction.
[0097] Figure 4 is exemplified by Figure 1 FIG. 5 is a diagram of an ODT operation performed by a memory controller.
[0098] Reference Figure 4 , Figure 4 The memory controller 200 may include an ODT controller 210 and a memory buffer 220. In an embodiment, the ODT operation may be performed by the ODT controller 210. Here, Figure 4 The ODT controller 210 may include at least two or more of an NMOS, a PMOS, and a resistor.
[0099] For example, when the memory device 100 performs a read operation, data DATA read from the memory device 100 may be output to the memory controller 200 through the input / output line DQ. The data DATA output from the memory device 100 may be temporarily stored in the memory buffer 220 and then output to the host (not shown).
[0100] In an embodiment, before performing a read operation, an ODT operation may be performed to match an interface connecting the memory controller 200 and the memory device 100 (ie, impedance seen by the memory controller 200 and impedance of the transmission line). Here, the ODT operation may be performed to improve signal integrity (SI).
[0101] Therefore, before performing the read operation, the ODT controller 210 may perform an ODT operation for impedance matching. For example, the ODT controller 210 may control the transmission line connected to the input / output line DQ to be connected to the power supply VDDQ by turning on or off the switch connected to the power supply VDDQ. Here, the switch may be NMOS and / or PMOS.
[0102] By adjusting the impedance of the data transmission line by turning on or off a switch included in the ODT controller 210 , an ODT operation of matching the impedance seen to the memory controller 200 with the impedance of the transmission line may be performed.
[0103] However, when the ODT operation is performed by the ODT controller 210 as described above, an ODT pin is required for each memory controller 200 or each memory device 100. In addition, there is a concern that in a structure where a storage device includes a plurality of memory devices or in a structure where a plurality of dies are present, an operation performed on each die may be delayed. Therefore, the ODT operation performed by the ODT controller 210 may result in reduced performance due to a burden on hardware.
[0104] Therefore, in the present disclosure, instead of performing the ODT operation by the ODT controller 210 in the memory controller 200, a process of performing the ODT operation based on a signal output from the memory device 100 is proposed. In addition, since the ODT operation can be performed by using the ready / busy pin of the memory device 100 instead of using the switch (ODT pin) in the ODT controller 210, the burden on hardware can be reduced.
[0105] Figure 5 is an example Figure 1 A diagram of the pin configuration of the memory device.
[0106] Reference Figure 5 , Figure 1 The memory device 100 can communicate with an external controller via a plurality of input / output lines. For example, Figure 1 The memory device 100 can communicate with an external controller through a data input / output line DQ and a control signal line having a chip enable line CE#, a write enable line WE#, a read enable line RE#, an address latch enable line ALE, a command latch enable line CLE, a write protection line WP#, and a ready busy line RB.
[0107] Figure 1 The memory device 100 may receive a chip enable signal from an external controller through a chip enable line CE#. Figure 1 The memory device 100 may receive a write enable signal from an external controller through a write enable line WE#. Figure 1 The memory device 100 may receive a read enable signal from an external controller through a read enable line RE#. Figure 1 The memory device 100 may receive an address latch enable signal from an external controller through an address latch enable line ALE. Figure 1 The memory device 100 may receive a command latch enable signal from an external controller through a command latch enable line CLE. Figure 1 The memory device 100 may receive a write protection signal from an external controller through a write protection line WP#.
[0108] In an embodiment, Figure 1 The memory device 100 can send a ready busy line RB to Figure 1 The memory controller 200 provides instructions Figure 1 A ready busy signal indicates whether the memory device 100 is in a ready state or a busy state.
[0109] The chip enable signal can be selected Figure 1 When the chip enable signal is in the "high" state and Figure 1The memory device 100 corresponds to the "ready" state, Figure 1 The memory device 100 may enter a low power standby state.
[0110] The write enable signal can be a control input to Figure 1 The memory device 100 controls commands, addresses, and storage of input data in latches.
[0111] The read enable signal may be a control signal that enables output of serial data.
[0112] The address latch enable signal may be one of control signals used by the host to indicate whether the type of a signal input to the input / output line DQ is a command, an address, or data.
[0113] The command latch enable signal may be one of control signals used by the host to indicate whether the type of a signal input to the input / output line DQ is a command, an address, or data.
[0114] For example, when the command latch enable signal is activated (e.g., logic high), the address latch enable signal is deactivated (e.g., logic low), and the write enable signal is activated (e.g., logic low) and then deactivated (e.g., logic high), Figure 1 The memory device 100 may recognize that a signal input through the input / output line DQ is a command.
[0115] For example, when the command latch enable signal is deactivated (e.g., logic low), the address latch enable signal is activated (e.g., logic high), and the write enable signal is activated (e.g., logic low) and then deactivated (e.g., logic high), Figure 1 The memory device 100 may recognize that a signal input through the input / output line DQ is an address.
[0116] The write protection signal can be Figure 1 The memory device 100 cannot perform a program operation and an erase operation.
[0117] The ready busy signal can be a marker Figure 1 That is, the ready busy signal in the low state may indicate the state of the memory device 100. Figure 1 The memory device 100 is executing at least one operation. A high state of the ready busy signal may indicate Figure 1 The memory device 100 is not performing any operation.
[0118] exist Figure 1 When the memory device 100 performs any one of a programming operation, a read operation, and an erase operation, the ready busy signal may be in a low state. Figure 1Description Figure 1 The memory controller 200 may determine an end time as a time point at which a program operation or an erase operation ends based on the ready busy signal.
[0119] Fig. 6A and Figure 6B It is an example when Figure 1 A diagram of a target memory device and a non-target memory device when the number of memory devices is plural.
[0120] Reference Fig. 6A and Figure 6B , Fig. 6A Shows when Figure 1 When the storage device 50 includes a plurality of memory devices MD1 to MD4, ready / busy signals RB1 to RB4 are output from each memory device, and Figure 6B The state of a ready / busy signal RB corresponding to each memory device and the state READY / BUSY of the memory device corresponding to the ready / busy signal are shown. Fig. 6A The first to fourth memory devices MD1 to MD4 or 100_1 to 100_4 may include a plurality of memory cells storing data.
[0121] exist Fig. 6A and Figure 6B , a structure in which the storage device 50 includes a plurality of memory devices 100_1 to 100_4 is shown, but the present disclosure may be equally applied to a structure in which a plurality of dies are included in one memory device.
[0122] exist Fig. 6A and Figure 6B ,as well as Figure 7 , Fig. 9 and Fig.10 In the embodiment, each of the plurality of memory devices 100_1 to 100_4 includes an ODT flag generator and an ODT executor. For example, the first memory device 100_1 has an ODT flag generator 150_1 and an ODT executor 170_1, the second memory device 100_2 has an ODT flag generator 150_2 and an ODT executor 170_2, the third memory device 100_3 has an ODT flag generator 150_3 and an ODT executor 170_3, and the fourth memory device 100_4 has an ODT flag generator 150_4 and an ODT executor 170_4.
[0123] exist Fig. 6A and Figure 6BIn the embodiment, it is assumed that among the first to fourth memory devices 100_1 to 100_4, only the first to fourth memory devices 100_1 perform an operation and the second to fourth memory devices 100_2 to 100_4 do not perform an operation. At this time, the operation performed by the first memory device 100_1 may be any one of a program operation, a read operation, or an erase operation.
[0124] Therefore, since it is assumed that only the first memory device 100_1 performs an operation, the first memory device 100_1 may be a target memory device, and the second to fourth memory devices 100_2 to 100_4 may be non-target memory devices.
[0125] In an embodiment, the first to fourth memory devices 100_1 to 100_4 may respectively output ready / busy signals RB1 to RB4 based on a status read command received from the memory controller 200. The ready / busy signals RB1 to RB4 may indicate a state in which the memory devices are operating or a standby state before performing an operation.
[0126] Reference Figure 6B , because in Fig. 6A and Figure 6B In the example, it is assumed that only the first memory device 100_1 performs an operation, and thus the first ready / busy signal RB1 output from the first memory device 100_1 may be in a low state ("0") indicating an operation state. In contrast, since it is assumed that the second to fourth memory devices 100_2 to 100_4 are in a standby state in which no operation is performed, the second to fourth ready / busy signals RB2 to RB4 output from the second to fourth memory devices 100_2 to 100_4 may be in a high state ("1") indicating a standby state.
[0127] Therefore, the first memory device 100_1 may be in a busy state BUSY, and the second to fourth memory devices 100_2 to 100_4 may be in a ready state READY.
[0128] In an embodiment, before the first memory device 100_1 is in the busy state BUSY, the first memory device 100_1 may perform an ODT operation. The ODT operation may be an operation performed in an initialization step to improve signal integrity (SI), and may be an operation to minimize signal reflections, etc., at interfaces between the memory controller 200 and the memory devices 100_1 to 100_4.
[0129] In addition, the ODT operation may be an operation of setting the size of a termination resistance (RTT) of an input / output terminal of the memory controller 200 or the plurality of memory devices 100_1 to 100_4 and may be an operation for impedance matching of a data transmission line.
[0130] In an embodiment, the ODT operation may be an ODT read operation or an ODT write operation. For example, the ODT operation performed before the memory device performs a read operation may be an ODT read operation, and the ODT operation performed before the memory device performs a write (program) operation may be an ODT write operation. That is, different impedance matching may be performed based on the operation performed by the memory device.
[0131] However, due to the Fig. 6A and Figure 6B It is assumed that only the first memory device 100_1 performs an operation, so the ODT operation may be performed only on the first memory device 100_1.
[0132] Therefore, in the present disclosure, a method for performing an ODT operation on the remaining second to fourth memory devices 100_2 to 100_4 while the first memory device 100_1 performs an operation is provided. In addition, in the present disclosure, a method for performing an ODT operation by outputting a signal through a ready / busy pin RB# in a memory device without using an ODT pin of an ODT controller in a memory controller 200 is provided.
[0133] As a result, through the present disclosure, an ODT operation can be performed based on a signal output from the memory device. Therefore, the burden on hardware can be reduced, so that the performance of the storage device 50 can be improved.
[0134] Figure 7 This is a diagram illustrating the process of generating a flag.
[0135] Reference Fig. 6A , Figure 6B and Figure 7 , Figure 7 Shows the connection to Fig. 6A and Figure 6B The first memory device 100_1 among the plurality of memory devices 100_1 to 100_4 and the lines of the ODT flag generator 150_1 included in the first memory device 100_1 and the memory controller 200. Similar to Fig. 6A and Figure 6B , Figure 7 The first memory device 100_1 may be a memory device on which an operation is performed, that is, a target memory device. Figure 7, it is assumed that the second to fourth memory devices 100_2 to 100_4 (ie, non-target memory devices on which no operation is performed) are omitted.
[0136] Reference Figure 7 , assuming that the first memory device 100_1 performs a read operation. In another embodiment, the first memory device 100_1 may perform a write (program) operation or an erase operation.
[0137] In an embodiment, when the first memory device 100_1 performs a read operation, the first memory device 100_1 may perform a read operation by Figure 5 The read enable line RE# of the memory device receives a read enable signal RE_N CLK. The read enable signal RE_N CLK may be a signal that enables output of data from the memory device.
[0138] exist Figure 7 In the example, since the first memory device 100_1 is assumed to perform a read operation, an ODT read enable signal providing an instruction to perform an ODT read operation on a non-target memory device may be generated based on the read enable signal RE_N CLK. Here, the ODT read enable signal may be a signal that causes an ODT read operation to be enabled.
[0139] As a result, since it is assumed that the first memory device 100_1 performs a read operation, an ODT read enable signal may be generated based on the read enable signal RE_N CLK.
[0140] In another embodiment, when it is assumed that the first memory device 100_1 performs a write (program) operation, an ODT write enable signal may be generated based on the input / output strobe signal DQS CLK, which provides an instruction to perform an ODT write operation on a non-target memory device. The input / output strobe signal DQS CLK may be a signal indicating that data received from the memory controller 200 is valid, and may be output to the memory controller 200 through an input / output strobe line. In addition, the ODT write enable signal may be a signal that causes an ODT write operation to be enabled.
[0141] As a result, since it is assumed that the first memory device 100_1 performs a write operation, an ODT write enable signal may be generated based on the input / output strobe signal DQS CLK.
[0142] Thereafter, when the first memory device 100_1 performs a read operation, the ODT flag generator 150_1 may output an ODT enable signal ODT_ENABLE based on the ODT read enable signal and the read enable signal RE_N CLK, indicating that an ODT operation may be performed on a non-target memory device. Here, the ODT enable signal ODT_ENABLE may be output to the memory controller 200 in the form of a flag FLAG.
[0143] In an embodiment, when the memory controller 200 receives the flag FLAG from the first memory device 100_1 (target memory device), the memory controller 200 may output the flag FLAG to the second to fourth memory devices 100_2 to 100_4 so that an ODT operation is performed on the second to fourth memory devices 100_2 to 100_4 (non-target memory devices).
[0144] Figure 8 is an example Figure 7 Diagram of the configuration of the ODT logo generator.
[0145] Reference Figure 7 and Figure 8 , Figure 8 Shows Figure 7 The ODT flag generator 150_1 includes an ODT read enable controller 151 , an ODT write enable controller 153 , and an enable signal generator 155 . Figure 8 shows the output Figure 7 The process of the ODT enable signal ODT_ENABLE.
[0146] exist Figure 8 In the embodiment, the ODT read enable controller 151 and the ODT write enable controller 153 can be configured by a D flip-flop, and the enable signal generator 155 can be configured by an OR gate. In another embodiment, the ODT read enable controller 151, the ODT write enable controller 153 and the enable signal generator 155 can be configured in various ways.
[0147] In an embodiment, when the target memory device performs a read operation, the ODT read enable signal ODT_RD_EN may be generated based on the read enable signal RE_NCLK. For example, when the target memory device performs a read operation, the read enable signal RE_N CLK may be enabled, and the ODT read enable signal ODT_RD_EN may be generated based on the enabled read enable signal RE_N CLK.
[0148] In an embodiment, when the target memory device performs a write (program) operation, the ODT write enable signal ODT_WR_EN may be generated based on the input / output select signal DQS CLK. For example, when the target memory device performs a write (program) operation, the input / output select signal DQS CLK may be enabled, and the ODT write enable signal ODT_WR_EN may be generated based on the enabled input / output select signal DQS CLK.
[0149] In an embodiment, the enabled read enable signal RE_N CLK and the ODT read enable signal ODT_RD_EN may be input to the ODT read enable controller 151, and the ODT read enable signal ODT_RD_EN may be output from the ODT read enable controller 151. In addition, the enabled input / output strobe signal DQS CLK and the ODT write enable signal ODT_WR_EN may be input to the ODT write enable controller 153, and the ODT write enable signal ODT_WR_EN may be output from the ODT write enable controller 153.
[0150] The ODT read enable signal ODT_RD_EN and the ODT write enable signal ODT_WR_EN may be input to the enable signal generator 155 , and the enable signal generator 155 may output the ODT enable signal ODT_ENABLE indicating that an ODT operation may be performed on a non-target memory device.
[0151] That is, when the target memory device performs a read operation, an ODT read enable signal ODT_RD_EN may be output from the ODT read enable controller 151, and when the target memory device performs a write operation, an ODT write enable signal ODT_WR_EN may be output from the ODT write enable controller 153. Thereafter, when the enable signal generator 155 receives any one of the ODT read enable signal ODT_RD_EN and the ODT write enable signal ODT_WR_EN, the enable signal generator 155 may output the ODT enable signal ODT_ENABLE so that the ODT operation is performed on the non-target memory device.
[0152] Fig. 9 is a diagram illustrating commands output from a memory controller in order to perform an ODT operation on a non-target memory device.
[0153] Reference Fig. 6A , Figure 6B and Fig. 9 , Fig. 9 Shown with Fig. 6A The configuration of the storage device 50 is the same as that of Fig. 6A and Figure 6B , assuming Fig. 9 That is, it is assumed that among the first to fourth memory devices 100_1 to 100_4, the first memory device 100_1 is a target memory device and the second to fourth memory devices 100_2 to 100_4 are non-target memory devices.
[0154] Fig. 9 It is shown that after the memory controller 200 receives the flag FLAG from the first memory device 100_1, the memory controller 200 may output a parameter setting command SET_FEATURE_CMD to perform an ODT operation on the second memory device 100_2 to the fourth memory device 100_4 (i.e., a non-target memory device). Here, the flag FLAG may indicate that the ODT operation may be performed on the non-target memory device. In addition, the target memory device and the non-target memory device may be distinguished based on the flag FLAG.
[0155] In an embodiment, the memory controller 200 may receive the flag FLAG from the first memory device 100_1 as a target memory device and then output a parameter setting command SET_FEATURE_CMD to the second to fourth memory devices 100_2 to 100_4. The parameter setting command SET_FEATURE_CMD may be a command that provides instructions to the second to fourth memory devices 100_2 to 100_4 to perform only an ODT operation without performing any other operations.
[0156] Therefore, after the memory controller 200 outputs the parameter setting command SET_FEATURE_CMD to the second to fourth memory devices 100_2 to 100_4 , a signal indicating that an ODT operation may be performed on non-target memory devices and a signal setting a parameter value so that other operations except the ODT operation may not be performed may be output.
[0157] Fig.10 A process of performing an ODT operation on a non-target memory based on a flag is illustrated.
[0158] Reference Fig.10 , Fig.10 The memory controller 200 included in the storage device and the second memory device 100_2 as a non-target memory device among the plurality of memory devices 100_1 to 100_4 are shown. In addition to the second memory device 100_2, the content of this figure can be applied to the third memory device 100_3 and the fourth memory device 100_4 which are also non-target memory devices.
[0159] Fig.10 Lines connected to the second memory device 100_2 and the ODT executor 170_2 included in the second memory device 100_2 and the memory controller 200 are shown.
[0160] In an embodiment, the second memory device 100_2 as a non-target memory device can receive a flag FLAG from the memory controller 200 through the ready / busy line RB#. The flag FLAG can indicate that an ODT operation can be performed on a non-target memory device or a non-target die, and further, a target memory device and a non-target memory device can be distinguished based on the flag FLAG.
[0161] When the second memory device 100_2 receives the flag FLAG from the memory controller 200, it may generate an ODT ready / busy signal RB_N_ODT providing an instruction to perform an ODT operation based on the flag FLAG. The ODT executor 170_2 may perform an ODT operation based on the ODT ready / busy signal RB_N_ODT.
[0162] For example, the ODT executor 170_2 may output a buffer enable signal RE_N_RX_ENABLE to operate a memory buffer in which data is temporarily stored based on the ODT ready / busy signal RB_N_ODT and the delay signal DELAY_SIG obtained by delaying the ODT ready / busy signal RB_N_ODT. When the buffer enable signal is transmitted to the memory controller 200 through the read enable line RE#, the memory buffer in which data in the memory controller 200 is temporarily stored may be operated.
[0163] Thereafter, the ODT executor 170_2 may generate an ODT read enable signal ODT_RD_EN based on the ODT ready / busy signal RB_N_ODT, the delay signal DELAY_SIG and the buffer enable signal RE_N_RX_ENABLE for controlling to perform an ODT read operation. Alternatively, an ODT write enable signal ODT_WR_EN may be generated based on the ODT ready / busy signal RB_N_ODT and the ODT read enable signal ODT_RD_EN.
[0164] In an embodiment, when the generated ODT read enable signal ODT_RD_EN or ODT write enable signal ODT_WR_EN is output to the memory controller 200 through the ready / busy line RB#, the memory controller 200 may perform an ODT read operation or an ODT write operation. The ODT read operation may be an ODT operation performed for impedance matching before the memory device performs a read operation, and the ODT write operation may be an ODT operation performed for impedance matching before the memory device performs a write (program) operation. That is, different impedance matching may be performed based on the operation performed by the memory device.
[0165] Fig.11 is an example Fig.10 Diagram of the configuration of the ODT actuator.
[0166] Reference Fig.10 and Fig.11 , Fig.11 Shown included in Fig.10 The signal delayer 171 , the RX enable controller 173 , the ODT read enable controller 175 , and the ODT write enable controller 177 in the ODT executor 170_2 .
[0167] In an embodiment, the RX enable controller 173 and the ODT write enable controller 177 may be configured by an inverter (ie, a NOT gate) and a non-AND (NAND) gate, and the ODT read enable controller 175 may be configured by an exclusive OR (XOR) gate and a D latch (DLAT). In various embodiments, the signal delayer 171, the RX enable controller 173, the ODT read enable controller 175, and the ODT write enable controller 177 may be configured in various ways.
[0168] The ODT executor 170_2 may receive an ODT ready / busy signal RB_N_ODT through a ready / busy line RB#. The received ODT ready / busy signal RB_N_ODT may be a signal providing an instruction to perform an ODT operation. The ODT ready / busy signal RB_N_ODT may be output to all components 171 to 177 included in the ODT executor 170_2.
[0169] In an implementation, the signal delayer 171 may generate a delay signal DELAY_SIG obtained by delaying the ODT ready / busy signal RB_N_ODT. The delay signal DELAY_SIG may be output to the RX enable controller 173 and the ODT read enable controller 175 .
[0170] In an implementation, the RX enable controller 173 may output a buffer enable signal RE_N_RX_ENABLE based on the ODT ready / busy signal RB_N_ODT and the delay signal DELAY_SIG. The buffer enable signal RE_N_RX_ENABLE may enable a memory buffer that temporarily stores data to operate.
[0171] In an embodiment, the ODT read enable controller 175 may generate an ODT read enable signal ODT_RD_EN based on the buffer enable signal RE_N_RX_ENABLE, the delay signal DELAY_SIG, and the ODT ready / busy signal RB_N_ODT output from the RX enable controller 173. That is, after the memory buffer in which data is to be temporarily stored is turned on, the ODT read enable controller 175 may generate an ODT read enable signal ODT_RD_EN that controls to perform an ODT read operation, and send the ODT read enable signal ODT_RD_EN to the RX enable controller 173. Fig.10 The memory controller 200 outputs an ODT read enable signal ODT_RD_EN. The ODT read operation may be an ODT operation performed for impedance matching before the memory device performs a read operation.
[0172] In an embodiment, the ODT write enable controller 177 may generate an ODT write enable signal ODT_WR_EN based on the ODT read enable signal ODT_RD_EN and the ODT ready / busy signal RB_N_ODT output from the ODT read enable controller 175. That is, after the memory buffer in which data is to be temporarily stored is turned on, the ODT write enable controller 177 may generate an ODT write enable signal ODT_WR_EN that controls to perform an ODT write operation, and may send an ODT write enable signal ODT_WR_EN to the memory buffer 175. Fig.10 The memory controller 200 outputs an ODT write enable signal ODT_WR_EN. The ODT write operation may be an ODT operation performed for impedance matching before the memory device performs a write (program) operation.
[0173] In an embodiment, when from Fig.10 When the memory controller 200 receives the flag FLAG, it can generate an ODT write enable signal ODT_WR_EN based on the ODT ready / busy signal RB_N_ODT so that the ODT write operation is performed first. That is, the ODT write enable controller 177 can generate an ODT write enable signal ODT_WR_EN that controls to perform an ODT write operation until an ODT read enable signal ODT_RD_EN that performs an ODT read operation is received from the ODT read enable controller 175.
[0174] Fig.12 is an example Fig.11 Diagram of the RX enable controller configuration.
[0175] Reference Fig.11 and Fig.12 , Fig.12 The RX enable controller 173 may be configured by an inverter 173_1 (ie, NOT gate) and a NAND gate 173_2. The inverter 173_1 may invert and output an input signal, and the NAND gate 173_2 may be a gate that outputs "0" when both input signals are "1".
[0176] In an embodiment, the RX enable controller 173 may output a buffer enable signal RE_N_RX_ENABLE based on the ODT ready / busy signal RB_N_ODT and the delay signal DELAY_SIG. The ODT ready / busy signal RB_N_ODT may be a signal providing an instruction to perform an ODT operation, and the delay signal DELAY_SIG may be a signal obtained by delaying the ODT ready / busy signal RB_N_ODT.
[0177] For example, the delay signal DELAY_SIG may be input to the inverter 173_1. That is, when the delay signal DELAY_SIG is in a high state ("1"), a signal in a low state ("0") may be input to the NAND gate 173_2, and when the delay signal DELAY_SIG is in a low state ("0"), a signal in a high state ("1") may be input to the NAND gate 173_2.
[0178] Thereafter, the ODT ready / busy signal RB_N_ODT and the signal output from the inverter 173_1 may be input to the NAND gate 173_2. Thus, when both the ODT ready / busy signal RB_N_ODT and the delay signal DELAY_SIG are in a low state ('0'), a buffer enable signal RE_N_RX_ENABLE for operating a memory buffer may be output.
[0179] Fig.13 is an example Fig.11 Diagram of the ODT read enable controller configuration.
[0180] Reference Fig.11 and Fig.13 , Fig.13 The ODT read enable controller 175 may be configured by an XOR gate 175_1 and a DLAT 175_2. The XOR gate 175_1 may be a gate that outputs "1" only when two input signals are in different states, and the DLAT 175_2 may be an element that outputs an input signal when it is in an enabled state.
[0181] In an embodiment, the ODT read enable controller 175 may generate an ODT read enable signal ODT_RD_EN based on the buffer enable signal RE_N_RX_ENABLE, the delay signal DELAY_SIG, and the ODT ready / busy signal RB_N_ODT output from the RX enable controller 173. The buffer enable signal RE_N_RX_ENABLE may be a signal that controls to turn on a memory buffer in which data is temporarily stored, the ODT ready / busy signal RB_N_ODT may be a signal that provides an instruction to perform an ODT operation, and the delay signal DELAY_SIG may be a signal obtained by delaying the ODT ready / busy signal RB_N_ODT.
[0182] For example, the ODT ready / busy signal RB_N_ODT and the delay signal DELAY_SIG obtained by delaying the ODT ready / busy signal RB_N_ODT may be input to the XOR gate 175_1. That is, the ODT read enable signal ODT_RD_EN may be generated only when one of the ODT ready / busy signal RB_N_ODT and the delay signal DELAY_SIG is "1".
[0183] When any one of the ODT ready / busy signal RB_N_ODT and the delay signal DELAY_SIG is '1', a signal XOR_SIG output from the XOR gate may be '1', and the signal XOR_SIG may enable the DLAT 175_2 .
[0184] Thereafter, when the DLAT 175_2 is enabled, the ODT read enable controller 175 may output an ODT read enable signal ODT_RD_EN based on the buffer enable signal RE_N_RX_ENABLE.
[0185] As a result, the ODT read operation may be performed only when any one of the ODT ready / busy signal RB_N_ODT and the delay signal DELAY_SIG is '1'.
[0186] Fig.14 is an example Fig.11 Diagram of the configuration of the ODT write enable controller.
[0187] Reference Fig.11 and Fig.14 , Fig.14The ODT write enable controller 177 may be configured by an inverter 177_1 (ie, NOT gate) and a NAND gate 177_2. The inverter 177_1 may invert and output an input signal, and the NAND gate 177_2 may be a gate that outputs "0" when both input signals are "1".
[0188] In an embodiment, the ODT write enable controller 177 may output an ODT write enable signal ODT_WR_EN based on an ODT read enable signal ODT_RD_EN and an ODT ready / busy signal RB_N_ODT outputted from the ODT read enable controller 175. The ODT ready / busy signal RB_N_ODT may be a signal providing an instruction to perform an ODT operation, and the ODT read enable signal ODT_RD_EN may be a signal providing an instruction to perform an ODT read operation, which is performed for impedance matching before the memory device performs a read operation.
[0189] For example, the ODT read enable signal ODT_RD_EN may be input to the inverter 177_1 .
[0190] Since the ODT read enable signal ODT_RD_EN is not generated before the ODT read operation is performed, the ODT write enable signal ODT_WR_EN in a high state (“1”) may be output, so that the ODT write operation may be performed.
[0191] However, when it is determined to perform the ODT read operation, the ODT read enable signal ODT_RD_EN in a low state (“0”) may be input to the inverter 177_1 and the inverted signal may be input to the NAND gate 177_2 . Therefore, the ODT write enable signal ODT_WR_EN may be disabled.
[0192] Fig.15 is a timing diagram illustrating an ODT write operation.
[0193] Reference Fig.15 , Fig.15 1 shows the state of each signal when an ODT write operation is performed on a non-target memory device NON_TARGET. Fig.15 In the ODT write operation, the non-target memory device NON_TARGET may be a memory device or a die that does not perform an operation, and a CE_N signal for selecting a memory device or a die that does not perform an operation may be maintained in a low state during the ODT write operation.
[0194] In the following figures, it is assumed that the target is a target memory device TARGET, and the non-target is a non-target memory device NON_TARGET. In another embodiment, the target may be a target die, and the non-target may be a non-target die.
[0195] In an embodiment, the target memory device TARGET may receive commands 80h and 12h, address ADD, and data DATA-IN through an input / output pin DQ or an input / output line DQ, so that an ODT write operation is performed. In addition, when commands 80h and 12h, address ADD, or data DATA-IN are received, an input / output select signal DQS indicating that the corresponding commands 80h and 12h, address ADD, or data DATA-IN are valid may be in a high state.
[0196] When during a write (program) operation from Figure 1 When the memory controller 200 receives the input / output selection signal DQS (t13) in a low state, the target memory device TARGET may output an ODT enable signal ODT_ENABLE indicating that an ODT operation may be performed on the non-target memory device NON_TARGET. Here, the ODT enable signal ODT_ENABLE may be output to the memory controller 200 in the form of a flag FLAG.
[0197] In an embodiment, since an ODT operation may be performed only while the target memory device TARGET is operating, the ODT enable signal ODT_ENABLE may maintain a high state from time t13 when the input / output strobe signal DQS is in a low state to time t17 when input of data is completed.
[0198] Thereafter, while the target memory device TARGET performs a write (program) operation, the ready / busy signal RB_N of the target memory device TARGET may be in a low state indicating a busy state (time t14 to time t17 ).
[0199] Immediately after the target memory device TARGET starts the operation, the ready / busy signal RB_N of the non-target memory device NON_TARGET may also be in a low state indicating a busy state when the ODT operation is performed (time t15). When the ready / busy signal RB_N of the non-target memory device NON_TARGET is in a low state, the ODT write enable signal ODT_WR_EN providing an instruction to perform the ODT operation on the non-target memory device NON_TARGET may be in a high state, and thus, the ODT write operation may be performed.
[0200] Fig.16 is a timing diagram illustrating an ODT read operation.
[0201] Reference Fig.16 , Fig.16 1 shows the state of each signal when an ODT read operation is performed on a non-target memory device NON_TARGET. Fig.16 In the ODT read operation, the non-target memory device NON_TARGET may be a memory device or die that does not perform an operation, and a CE_N signal that selects the memory device or die that does not perform an operation may be maintained in a low state during the ODT read operation.
[0202] In an embodiment, the target memory device TARGET may receive the command 00h and CMD and the address ADD, and may output data (DATA-OUT) to the memory device through the input / output pin DQ, so that an ODT read operation is performed. In addition, when the command 00h and CMD and the address ADD are received, the RE_N signal may be in a high state.
[0203] When receiving the RE_N signal in a low state for enabling a read operation (time t23), the target memory device TARGET may output an ODT enable signal ODT_ENABLE indicating that an ODT operation may be performed on the non-target memory device NON_TARGET. Here, the ODT enable signal ODT_ENABLE may be output to the memory controller 200 in the form of a flag FLAG.
[0204] In an embodiment, since the ODT operation is performed only while the target memory device TARGET is operating, the ODT enable signal ODT_ENABLE may maintain a high state from time t23 when the RE_N signal becomes a low state to time t27 when the output of data is completed.
[0205] Thereafter, while the target memory device TARGET performs a read operation, the ready / busy signal RB_N of the target memory device TARGET may be in a low state indicating a busy state (time t24 to time t27 ).
[0206] Immediately after the target memory device TARGET starts operating, the ready / busy signal RB_N of the non-target memory device NON_TARGET may also be in a low state indicating a busy state when the ODT operation is performed (time t25). When the ready / busy signal RB_N of the non-target memory device NON_TARGET is in a low state, the ODT read enable signal ODT_RD_EN providing an instruction to perform the ODT operation on the non-target memory device NON_TARGET may be in a high state, and thus, the ODT read operation may be performed.
[0207] Fig.17 is a timing diagram illustrating an ODT write operation and an ODT operation.
[0208] Reference Fig.17 , Fig.17 States of signals output from the target memory device TARGET and the non-target memory device NON_TARGET are shown.
[0209] In an embodiment, when the target memory device TARGET performs an operation, the RB_N signal of the target memory device TARGET may be in a low state (time t31 to time t36 ).
[0210] In the present disclosure, when the target memory device TARGET performs an operation, since an ODT operation is performed on the non-target memory device NON_TARGET, the RB_N signal of the non-target memory device NON_TARGET may also be in a low state (time t32 to time t37) while the ODT operation is performed on the non-target memory device NON_TARGET.
[0211] In an embodiment, when the RB_N signal of the non-target memory device NON_TARGET is in a low state, the ODT operation may be performed. Therefore, at time t34 to time t35, the RE_N_RX_ENABLE signal that enables the memory buffer in which data is to be temporarily stored during the ODT read operation or the ODT write operation may be in a high state.
[0212] Before the target memory device TARGET performs a read operation, the non-target memory device NON_TARGET can Figure 1 After receiving the flag FLAG indicating that the ODT operation can be performed, the memory controller 200 can send Figure 1 The memory controller 200 outputs the ODT write enable signal ODT_WR_EN in a high state to enable the ODT write operation (time t33 ).
[0213] In an embodiment, at time t35 when the target memory device TARGET performs a read operation, an ODT read enable signal ODT_RD_EN in a high state may be output to enable the ODT read operation. In addition, since the ODT write enable signal ODT_WR_EN in a low state is output, the ODT write operation may be disabled. However, when the target memory device TARGET does not perform a read operation, the ODT write enable signal ODT_WR_EN may remain in a high state until the target memory device TARGET completes the write operation (time t33 to time t37).
[0214] Fig.18is a diagram illustrating the operation of a memory device according to an embodiment of the present disclosure.
[0215] Reference Fig.18 In step S1801, the target memory device may perform an operation. The operation performed by the target memory device may be any one of a program operation, a read operation, and an erase operation.
[0216] In step S1803, a flag may be output from the target memory device. The flag may indicate that an ODT operation may be performed on a non-target memory device or a non-target die. In addition, a target memory device and a non-target memory device may be distinguished based on the flag. Here, the target memory device may be a memory device in a busy state in which an operation is performed, and the non-target memory device may be a memory device in a ready state in which no operation is performed.
[0217] In the present disclosure, while an operation is performed on a target memory device, an ODT operation may be performed on a non-target memory device.
[0218] In step S1805, a parameter setting command may be received from the memory controller. At this time, the non-target memory device may receive the parameter setting command from the memory controller. After receiving the parameter setting command, only operations related to the ODT operation may be performed on the non-target memory device, and other operations may not be performed.
[0219] In step S1807 , the memory device may output an ODT write enable signal or an ODT read enable signal.
[0220] In an embodiment, when a target memory device performs a write operation, the memory device may output an ODT write enable signal requesting to perform an ODT write operation on a non-target memory device based on a flag received from a memory controller.
[0221] In addition, when the target memory device performs a read operation, the memory device may output an ODT read enable signal requesting to perform an ODT read operation on a non-target memory device based on a flag received from the memory controller.
[0222] Fig.19 is an example Figure 1 FIG. 1 is a diagram of another embodiment of a memory controller.
[0223] The memory controller 1000 may be connected to a host and a memory device. The memory controller 1000 may be configured to access the memory device based on a request from the host Host. For example, the memory controller 1000 may be configured to control a write operation, a read operation, an erase operation, and a background operation of the memory device. The memory controller 1000 may be configured to provide an interface between the memory device and the host. The memory controller 1000 may be configured to drive firmware to control the memory device.
[0224] Reference Fig.19 , the memory controller 1000 may include a processor 1010 , a memory buffer 1020 , an error correction circuit (ECC) 1030 , a host interface 1040 , a buffer controller (or buffer control circuit) 1050 , a memory interface 1060 , and a bus 1070 .
[0225] The bus 1070 may be configured to provide a channel between components of the memory controller 1000 .
[0226] The processor 1010 may control the overall operation of the memory controller 1000 and may perform a logical operation. The processor 1010 may communicate with an external host through a host interface 1040 and may communicate with a memory device through a memory interface 1060. In addition, the processor 1010 may communicate with a memory buffer 1020 through a buffer controller 1050. The processor 1010 may control the operation of the memory device by using the memory buffer 1020 as an operating memory, a cache memory, or a buffer memory.
[0227] The processor 1010 may perform the function of the FTL. The processor 1010 may convert the LBA provided by the host into the PBA through the FTL. The FTL may receive the LBA and may convert the LBA into the PBA by using a mapping table. The address mapping method of the flash translation layer may include a plurality of mapping methods based on a mapping unit. Representative address mapping methods may include a page mapping method, a block mapping method, and a hybrid mapping method.
[0228] The processor 1010 may be configured to randomize data received from the host. For example, the processor 1010 may randomize data received from the host by using a randomization seed. The randomized data may be provided to the memory device as data to be stored and may be programmed into the memory cell array.
[0229] The processor 1010 may perform randomization and de-randomization through driver software or firmware.
[0230] The memory buffer 1020 may be used as an operation memory, a cache memory, or a buffer memory of the processor 1010. The memory buffer 1020 may store codes and commands executed by the processor 1010. The memory buffer 1020 may store data processed by the processor 1010. The memory buffer 1020 may include a static RAM (SRAM) or a dynamic RAM (DRAM).
[0231] The error correction circuit 1030 may perform error correction. The error correction circuit 1030 may perform error correction encoding (ECC encoding) based on data to be written to the memory device through the memory interface 1060. The error correction encoded data may be transmitted to the memory device through the memory interface 1060. The error correction circuit 1030 may perform error correction decoding (ECC decoding) on data received from the memory device through the memory interface 1060. For example, the error correction circuit 1030 may be included in the memory interface 1060 as a component of the memory interface 1060.
[0232] The host interface 1040 may be configured to communicate with an external host based on the processor 1010. The host interface 1040 may be configured to perform communication by using at least one of various communication methods such as a universal serial bus (USB), a serial AT attachment (SATA), a serial attached SCSI (SAS), a high-speed inter-chip (HSIC), a small computer system interface (SCSI), a peripheral component interconnect (PCI-Express), a non-volatile memory express (NVMe), a universal flash memory (UFS), a secure digital (SD), a multimedia card (MMC), an embedded MMC (eMMC), a dual in-line memory module (DIMM), a registered DIMM (RDIMM), and a lightly loaded DIMM (LRDIMM).
[0233] The buffer controller 1050 may be configured to control the memory buffer 1020 based on the control of the processor 1010 .
[0234] The memory interface 1060 may be configured to communicate with the memory device based on the control of the processor 1010. The memory interface 1060 may communicate commands, addresses, and data with the memory device through a channel.
[0235] For example, the memory controller 1000 may not include the memory buffer 1020 and the buffer controller 1050 .
[0236] For example, the processor 1010 may control the operation of the memory controller 1000 by using the code. The processor 1010 may load the code from a nonvolatile memory device (eg, a read-only memory) provided inside the memory controller 1000. As another example, the processor 1010 may load the code from the memory device through the memory interface 1060.
[0237] For example, the bus 1070 of the memory controller 1000 may be divided into a control bus and a data bus. The data bus may be configured to transmit data within the memory controller 1000, and the control bus may be configured to transmit control information such as commands and addresses within the memory controller 1000. The data bus and the control bus may be separated from each other and may not interfere with or affect each other. The data bus may be connected to the host interface 1040, the buffer controller 1050, the error correction circuit 1030, and the memory interface 1060. The control bus may be connected to the host interface 1040, the processor 1010, the buffer controller 1050, the memory buffer 1020, and the memory interface 1060.
[0238] Fig. 20 is a block diagram illustrating a memory card system to which a storage device according to an embodiment of the present disclosure is applied.
[0239] Reference Fig. 20 , the memory card system 2000 includes a memory controller 2100 , a memory device 2200 , and a connector 2300 .
[0240] The memory controller 2100 may be connected to the memory device 2200. The memory controller 2100 may be configured to access the memory device 2200. For example, the memory controller 2100 may be configured to control a read operation, a write operation, an erase operation, and a background operation of the memory device 2200. The memory controller 2100 may be configured to provide an interface between the memory device 2200 and a host. The memory controller 2100 may be configured to drive firmware to control the memory device 2200. Figure 2 Description Figure 1 The memory device 2200 is implemented by the memory device 100 of the embodiment of the present invention.
[0241] As an example, the memory controller 2100 may include components such as a random access memory (RAM), a processor, a host interface, a memory interface, and an error correction circuit.
[0242] The memory controller 2100 may communicate with an external device through the connector 2300. The memory controller 2100 may communicate with an external device (e.g., a host) based on a specific communication standard. As an example, the memory controller 2100 may be configured to communicate with an external device through at least one of various communication standards such as a universal serial bus (USB), a multimedia card (MMC), an embedded MMC (eMMC), a peripheral component interconnect (PCI), a PCI-Express (PCI-E), an advanced technology attachment (ATA), a serial ATA, a parallel ATA, a small computer system interface (SCSI), an enhanced small disk interface (ESDI), an integrated drive electronics (IDE), FireWire, a universal flash memory (UFS), Wi-Fi, Bluetooth, and NVMe. As an example, the connector 2300 may be defined by at least one of the various communication standards described above.
[0243] As examples, the memory device 2200 may be implemented as various nonvolatile memory elements such as electrically erasable programmable ROM (EEPROM), NAND flash memory, NOR flash memory, phase change RAM (PRAM), resistive RAM (ReRAM), ferroelectric RAM (FRAM), and spin transfer torque magnetic RAM (STT-MRAM).
[0244] The memory controller 2100 and the memory device 2200 may be integrated into one semiconductor device to configure a memory card. For example, the memory controller 2100 and the memory device 2200 may be integrated into one semiconductor device to configure a memory card such as a PC card (Personal Computer Memory Card International Association (PCMCIA)), a Compact Flash card (CF), a Smart Media Card (SM or SMC), a Memory Stick, a Multimedia Card (MMC, RS-MMC, Micro MMC or eMMC), an SD card (SD, Mini SD, Micro SD or SDHC), and a Universal Flash Storage (UFS).
[0245] Fig.21 is a block diagram exemplarily illustrating a solid state drive (SSD) system to which a storage device according to an embodiment of the present disclosure is applied.
[0246] Reference Fig.21 , the SSD system 3000 may include a host 3100 and an SSD 3200. The SSD 3200 may exchange a signal SIG with the host 3100 through a signal connector 3001, and may receive a power supply PWR through a power connector 3002. The SSD 3200 may include an SSD controller 3210, a plurality of flash memories 3221 to 322n, an auxiliary power supply device 3230, and a buffer memory 3240.
[0247] In an embodiment, the SSD controller 3210 may perform a reference Figure 1 Description Figure 1 The functions of the memory controller 200 are as follows.
[0248] The SSD controller 3210 may control the plurality of flash memories 3221 to 322n based on a signal SIG received from the host 3100. As an example, the signal SIG may be a signal based on an interface between the host 3100 and the SSD 3200. For example, the signal SIG may be a signal defined by at least one of interfaces such as a universal serial bus (USB), a multimedia card (MMC), an embedded MMC (eMMC), a peripheral component interconnect (PCI), a PCI-Express (PCI-E), an advanced technology attachment (ATA), a serial ATA, a parallel ATA, a small computer system interface (SCSI), an enhanced small disk interface (ESDI), an integrated drive electronics (IDE), a FireWire, a universal flash memory (UFS), Wi-Fi, Bluetooth, and NVMe.
[0249] The auxiliary power supply device 3230 may be connected to the host 3100 through the power connector 3002. The auxiliary power supply device 3230 may receive power PWR from the host 3100 and may charge the power supply. When the power supply from the host 3100 is not stable, the auxiliary power supply device 3230 may provide power to the SSD 3200. As an example, the auxiliary power supply device 3230 may be located in the SSD 3200 or may be located outside the SSD 3200. For example, the auxiliary power supply device 3230 may be located on the mainboard and may provide auxiliary power to the SSD 3200.
[0250] The buffer memory 3240 may be used as a buffer memory of the SSD 3200. For example, the buffer memory 3240 may temporarily store data received from the host 3100 or data received from the plurality of flash memories 3221 to 322n, or may temporarily store metadata (e.g., a mapping table) of the flash memories 3221 to 322n. The buffer memory 3240 may include a volatile memory such as DRAM, SDRAM, DDRSDRAM, LPDDR SDRAM, and GRAM, or a nonvolatile memory such as FRAM, ReRAM, STT-MRAM, and PRAM.
[0251] Fig. 22 is a block diagram illustrating a user system to which a storage device according to an embodiment of the present disclosure is applied.
[0252] Reference Fig. 22, the user system 4000 includes an application processor 4100 , a memory module 4200 , a network module 4300 , a storage module 4400 and a user interface 4500 .
[0253] The application processor 4100 may drive components included in the user system 4000, an operating system (OS), a user program, etc. For example, the application processor 4100 may include a controller, an interface, a graphic engine, etc. that controls components included in the user system 4000. The application processor 4100 may be provided as a system on chip (SoC).
[0254] The memory module 4200 may operate as a main memory, an operating memory, a buffer memory, or a cache memory of the user system 4000. The memory module 4200 may include a volatile random access memory (such as DRAM, SDRAM, DDR SDRAM, DDR2SDRAM, DDR3SDRAM, LPDDR SDRAM, LPDDR2SDRAM, and LPDDR3SDRAM) or a nonvolatile random access memory (such as PRAM, ReRAM, MRAM, and FRAM). For example, the application processor 4100 and the memory module 4200 may be packaged based on a package-on-package (POP) and provided as one semiconductor package.
[0255] The network module 4300 can communicate with external devices. For example, the network module 4300 can support wireless communications such as code division multiple access (CDMA), global system for mobile communications (GSM), wideband CDMA (WCDMA), CDMA-2000, time division multiple access (TDMA), long term evolution, Wimax, WLAN, UWB, Bluetooth, and WI-FI. For example, the network module 4300 can be included in the application processor 4100.
[0256] The storage module 4400 may store data. For example, the storage module 4400 may store data received from the application processor 4100. Alternatively, the storage module 4400 may send data stored in the storage module 4400 to the application processor 4100. For example, the storage module 4400 may be implemented as a non-volatile semiconductor memory element such as a phase change RAM (PRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM), a NAND flash memory, a NOR flash memory, and a three-dimensional NAND flash memory. For example, the storage module 4400 may be set as an external drive of the user system 4000 and a removable storage device (removable drive) such as a memory card.
[0257] For example, the storage module 4400 may include a plurality of nonvolatile memory devices, and the plurality of nonvolatile memory devices may be associated with the reference Figure 2 and Figure 3 The storage module 4400 may be similar to the storage device described in the reference Figure 1 The described storage device 50 operates identically.
[0258] The user interface 4500 may include an interface for inputting data or instructions to the application processor 4100 or outputting data to an external device. For example, the user interface 4500 may include a user input interface such as a keyboard, a keypad, a button, a touch panel, a touch screen, a touch pad, a touch ball, a camera, a microphone, a gyro sensor, a vibration sensor, and a piezoelectric element. The user interface 4500 may include a user output interface such as a liquid crystal display (LCD), an organic light emitting diode (OLED) display device, an active matrix OLED (AMOLED) display device, an LED, a speaker, and a monitor.
[0259] CROSS-REFERENCE TO RELATED APPLICATIONS
[0260] This application claims the priority of Korean Patent Application No. 10-2020-0103550 filed on August 18, 2020 in the Korean Intellectual Property Office, the disclosure of which is incorporated herein in its entirety by reference.
Claims
1. A storage device, the storage device include: a plurality of memory devices, the plurality of memory devices including a target memory device and a non-target memory device performing an operation; as well as a memory controller configured to control the plurality of memory devices, wherein the target memory device generates and outputs a flag indicating that an on-die termination (ODT) operation can be performed on the non-target memory device, wherein the non-target memory device receives the flag from the target memory device and performs the ODT operation based on the flag, and Wherein, each of the plurality of memory devices comprises: an ODT flag generator configured to generate the flag; and An ODT executor is configured to determine whether the ODT operation is an ODT read operation for a read operation or an ODT write operation for a write operation based on the flag, and is configured to generate an enable signal enabling the ODT read operation or the ODT write operation.
2. The storage device according to claim 1, in, The flag distinguishes between the target memory device and the non-target memory devices.
3. The storage device according to claim 1, in, When the target memory device performs the read operation, the ODT flag generator of the target memory device generates the flag based on a signal enabling the read operation.
4. The storage device according to claim 1, in, When the target memory device performs the write operation, the ODT flag generator of the target memory device generates the flag based on an input / output strobe signal indicating that the data is valid when data corresponding to the write operation is input.
5. The storage device according to claim 1, in, The memory controller distinguishes between the target memory device and the non-target memory device based on the flag, and outputs a parameter setting command to perform the ODT operation on the non-target memory device.
6. The storage device according to claim 5, in, The non-target memory device performs only operations related to performing the ODT operation based on the parameter setting command.
7. The storage device according to claim 1, in, The ODT operation on the non-target memory device is performed on each of a plurality of non-target memory devices.
8. The storage device according to claim 1, in, The ODT executor included in each of a plurality of non-target memory devices receives the flag and then outputs a signal enabling a buffer included in the memory controller to perform the ODT operation.
9. The storage device according to claim 1, in, When the ODT operation is the ODT read operation, the ODT executor included in each of a plurality of non-target memory devices outputs an ODT read enable signal providing an instruction to perform impedance matching for the read operation.
10. The storage device according to claim 1, in, When the ODT operation is the ODT write operation, the ODT executor included in each of a plurality of non-target memory devices outputs an ODT write enable signal providing an instruction to perform impedance matching for the write operation.
11. A method for operating a storage device, the storage device having a plurality of memory devices and a memory controller controlling the plurality of memory devices, the method The following steps are involved: performing an operation by a target memory device among the plurality of memory devices; generating, by the target memory device, a flag indicating that an on-die termination (ODT) operation can be performed on a non-target memory device other than the target memory device among the plurality of memory devices; receiving, by the non-target memory device, the flag; determining, based on the flag, whether the ODT operation is an ODT read operation for a read operation or an ODT write operation for a write operation; as well as An enable signal enabling the ODT read operation or the ODT write operation is generated by the non-target memory device.
12. The method according to claim 11, in, The flag distinguishes between the target memory device and the non-target memory devices.
13. The method according to claim 11, in, When the target memory device performs the read operation, the flag is generated based on a signal enabling the read operation.
14. The method according to claim 11, in, When the target memory device performs the write operation, the flag is generated based on a signal enabling the write operation.
15. The method according to claim 11, further comprising: The following steps are involved: distinguishing between the target memory device and the non-target memory device based on the flag; as well as A parameter setting command is output by the memory controller so that the ODT operation is performed on the non-target memory device.
16. The method according to claim 15, in, The non-target memory device performs only operations related to performing the ODT operation based on the parameter setting command.
17. The method according to claim 11, in, The ODT operation on the non-target memory device is performed on each of a plurality of non-target memory devices.
18. The method according to claim 11, further comprising: The following steps are involved: After receiving the flag, a signal for the ODT operation is output by the non-target memory device, the signal enabling a buffer included in the memory controller.
19. The method according to claim 11, in, In generating the enable signal, when the ODT operation is the ODT read operation, the non-target memory device outputs an ODT read enable signal providing an instruction to perform impedance matching for the read operation.
20. The method according to claim 11, in, In generating the enable signal, when the ODT operation is the ODT write operation, the non-target memory device outputs an ODT write enable signal providing an instruction to perform impedance matching for the write operation.
