Memory controller, memory device, and operating method of memory device

CN119025016APending Publication Date: 2024-11-26SK HYNIX INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311758870.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-24
Filing Date
2023-12-20
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In existing storage systems, the host has difficulty obtaining detailed self-test results during self-test operations, resulting in incomplete error information and affecting system diagnostic efficiency.

Method used

A self-test manager and response generator are introduced into the memory controller to generate additional header segments containing the results of the self-test operation, which are transmitted to the host via Protocol Message Unit (PIU) to report the results of the self-test operation in detail.

Benefits of technology

This enables the host to obtain detailed results of self-test operations, improving the efficiency and accuracy of system diagnosis, simplifying the result information transmission process, and reducing the probability of errors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025016A_ABST
    Figure CN119025016A_ABST
Patent Text Reader

Abstract

The invention relates to a memory controller. The memory controller includes: a host interface configured to receive, from a host, a diagnostic command for requesting execution of a self-test operation; and a processor configured to perform a self-test operation on the memory device and generate a response corresponding to the diagnostic command, where the host interface is configured to transmit the response to the host, the response comprising: a base header segment collectively included in a protocol information unit transmitted / received between the memory controller and the host; and an additional header segment including result information indicating a result of the self-test operation.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Korean Patent Application No. 10-2023-0066801, filed on May 24, 2023, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] Embodiments of the present disclosure generally relate to an electronic device, and more particularly, to a memory controller, a memory device, and an operating method of the memory device. Background Art

[0004] The storage system includes a host and a storage device. The storage device may include a memory controller and a memory device. The storage device may also be implemented using only the memory device. The host and the storage device in the storage system are interconnected by at least one of a plurality of interface standards or protocols such as Universal Flash Storage (UFS), Serial ATA (SATA), Small Computer System Interface (SCSI), Serial SCSI (SAS), Embedded MMC (eMMC) and Non-Volatile Memory Express (NVMe). Summary of the invention

[0005] Embodiments of the present disclosure provide a memory controller, a memory device, and an operating method of the memory device capable of effectively performing a self-test operation.

[0006] According to one aspect of the present disclosure, a memory controller is provided, comprising: a host interface configured to receive a diagnostic command for requesting to perform a self-test operation from a host; and a processor configured to perform a self-test operation on a memory device and generate a response corresponding to the diagnostic command, wherein the host interface is configured to transmit the response to the host, the response comprising: a basic header segment commonly included in a protocol information unit sent / received between the memory controller and the host; and an additional header segment including result information indicating a result of the self-test operation.

[0007] According to another aspect of the present disclosure, a storage device is provided, comprising: a memory device configured to store data; and a memory controller configured to receive a diagnostic command for requesting to perform a self-test operation from an external device, perform the self-test operation in response to the diagnostic command, and provide a response corresponding to the diagnostic command to the external device, wherein the response comprises: a basic header segment, commonly included in a protocol information unit sent / received between the external device and a host; and an additional header segment, including result information indicating a result of the self-test operation.

[0008] According to another aspect of the present disclosure, a method for operating a storage device is provided, comprising: receiving a diagnostic command from an external device for requesting to perform a self-test operation; performing the self-test operation in response to the diagnostic command; and generating a response including result information about the self-test operation, wherein the response includes: a basic header segment, commonly included in a protocol information unit sent / received between the storage device and the external device; and an additional header segment, including result information indicating a result of the self-test operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Embodiments of the present disclosure will now be described more fully below with reference to the accompanying drawings; however, the embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be thorough and complete and will convey the scope of the embodiments to those skilled in the art.

[0010] In the accompanying drawings, dimensions may be exaggerated for clarity of illustration. It will be understood that when an element is referred to as being "between" two elements, it may be the only element between the two elements, or one or more intermediate elements may be present. Throughout, the same reference numerals refer to the same elements.

[0011] Figure 1 is a diagram illustrating a storage system according to an embodiment of the present disclosure.

[0012] Figure 2 It is shown Figure 1 A diagram of an example of a memory controller is shown.

[0013] Figure 3 It is shown Figure 1 A diagram of another example of a memory controller is shown.

[0014] Figure 4 is a diagram illustrating the structure of a data unit used for communication between a host and a memory controller.

[0015] Figure 5 is a diagram showing the structure of a basic header segment of a protocol information unit (PIU).

[0016] Figure 6 is a diagram showing the structure of a command descriptor block included in a transaction specific field of a PIU.

[0017] Figure 7 is a diagram showing the structure of an additional header segment of a PIU.

[0018] Figure 8 is a diagram illustrating a PIU structure of a diagnostic command according to an embodiment of the present disclosure.

[0019] Fig. 9is a diagram illustrating a structure of a command descriptor block included in a transaction-specific field of a diagnostic command according to an embodiment of the present disclosure.

[0020] Fig.10 is a table illustrating a self-test operation according to information included in a transaction-specific field of a diagnostic command according to an embodiment of the present disclosure.

[0021] Fig.11 is a diagram illustrating a PIU structure of a response to a diagnosis command according to an embodiment of the present disclosure.

[0022] Fig.12 is a diagram illustrating a structure of an additional header segment of a response according to an embodiment of the present disclosure.

[0023] Fig.13 is a sequence diagram illustrating an operation method of a storage device according to an embodiment of the present disclosure.

[0024] Fig.14 is a sequence diagram illustrating an operation method of a storage device according to an embodiment of the present disclosure.

[0025] Fig.15 is a block diagram illustrating a solid state drive (SSD) system to which a storage device is applied according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0026] For the purpose of describing the embodiments according to the concept of the present disclosure, the specific structural or functional descriptions disclosed herein are merely illustrative. The embodiments according to the concept of the present disclosure can be implemented in various forms and should not be interpreted as being limited to the embodiments set forth herein.

[0027] Figure 1 is a diagram illustrating a storage system according to an embodiment of the present disclosure.

[0028] Reference Figure 1 , the storage system may include a host (i.e., an external device) 400 and a storage device 50. The storage device 50 may include a memory device 100 and a memory controller 200. The storage device 50 may be a device that stores data under the control of a host 400 such as a mobile 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. Alternatively, the storage device 50 may be a device for storing data under the control of a host 400, which is used to store high-capacity data in one place, such as a server or a data center. The storage device 50 may be manufactured as any of various types of storage devices according to a host interface, which is a communication scheme with the host 400. Further, the storage device 50 may be manufactured as any of various packaging types.

[0029] The memory device 100 may store data. The memory device 100 may operate under the control of the memory controller 200. The memory device 100 may include a memory cell array including a plurality of memory cells for storing data.

[0030] Each of the memory cells may be configured as any one of 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, and a quad-level cell (QLC) storing four data bits.

[0031] The memory cell array may include a plurality of memory blocks. Each memory block may include a plurality of memory cells. Each memory block may include a plurality of pages. In an embodiment, a page may be a unit for writing (programming) data in the memory device 100 or reading data stored in the memory device 100. A memory block may be a unit for erasing data.

[0032] In an embodiment, the memory device 100 may be, for example, a volatile memory device or a nonvolatile memory device. In the present disclosure, for convenience of description, the case where the memory device 100 is a NAND flash memory is described.

[0033] The memory device 100 may receive a command and an address from the memory controller 200, and access an area selected by the address in the memory cell array. The memory device 100 may perform an operation indicated by the command on the area selected by the address. For example, the memory device 100 may perform a write operation (programming operation), a read operation, and an erase operation. In a programming operation, the memory device 100 may program data in an area selected by the address. In a read operation, the memory device 100 may read data from an area selected by the address. In an erase operation, the memory device 100 may erase data stored in an area selected by the address.

[0034] The memory controller 200 may control the operation of the memory device 50 .

[0035] The memory controller 200 may run firmware (FW) when power is applied to the memory device 50. When the memory device 100 is a flash memory device, the memory controller 200 may run FW such as a flash translation layer (FTL) for controlling communication between the host 400 and the memory device 100.

[0036] In an embodiment, the memory controller 200 may receive data and a logical block address (LA) from the host 400 and convert the LA into a physical block address (PA) representing an address of a memory cell included in the memory device 100 where data is to be stored.

[0037] The memory controller 200 may control the memory device 100 to perform a program operation, a read operation, an erase operation, etc. according to a request from the host 400. In a program operation, the memory controller 200 may provide a program command, a PA, and data to the memory device 100. In a read operation, the memory controller 200 may provide a read command and a PA to the memory device 100. In an erase operation, the memory controller 200 may provide an erase command and a PA to the memory device 100.

[0038] In an embodiment, the memory controller 200 may autonomously generate commands, addresses, and data regardless of a request from the host 400, and transmit the commands, addresses, and data to the memory device 100. For example, the memory controller 200 may provide the memory device 100 with commands, addresses, and data for performing read operations and program operations accompanying when performing wear leveling, read recycling, garbage collection, etc.

[0039] In an embodiment, the memory controller 200 may control at least two memory devices according to an interleaving scheme to improve operation performance. The interleaving scheme may be a scheme for controlling operations on at least two memory devices to overlap with each other. Further, the interleaving scheme may be a scheme for controlling operations of a plurality of groups divided in one memory device to overlap with each other. The group may be at least one memory die unit or at least one memory plane unit.

[0040] Further, the memory controller 200 may receive a diagnostic command for requesting the memory controller 200 to perform a self-test operation from the host 400, and perform the self-test operation in response to the diagnostic command. In one embodiment, the memory controller 200 may perform a self-test operation on the memory device 100 or the memory controller 200 itself. In another embodiment, the memory controller 200 may perform a self-test operation on the entire memory device 50.

[0041] The host 400 may communicate with the storage device 50 using at least one of various interface protocols or standards such as: Universal Serial Bus (USB), Serial AT Attachment (SATA), Serial SCSI (SAS), High Speed ​​Inter-Chip (HSIC), Small Computer System Interface (SCSI), FireWire, Peripheral Component Interconnect (PCI), PCI Express (PCIe), Non-Volatile Memory Express (NVMe), Universal Flash Storage (UFS), Secure Digital (SD), MultiMedia Card (MMC), Embedded MMC (eMMC), Dual In-line Memory Module (DIMM), Registered DIMM (RDIMM), and Load Reduced DIMM (LRDIMM).

[0042] In the present disclosure, for the convenience of description, a case is described in which the storage device 50 and the host 400 perform data communication according to the UFS interface, but the embodiments of the present disclosure are not limited to performing data communication according to the UFS interface. Specifically, the storage device 50 and the host 400 may perform data communication using a command defined as a protocol information unit (hereinafter referred to as a PIU). The PIU may be a data packet generated according to a predetermined protocol. Therefore, in the present disclosure, the PIU is only a form of command sent / received between the storage device 50 and the host 400, so the command and the PIU may have substantially the same meaning.

[0043] The command can be used for the host 400 or the storage device 50 to request, instruct or respond to perform any operation. In an embodiment, various commands can be defined according to the use and purpose. For example, commands, responses, data outputs, query requests, data inputs, preparations for transmission, etc. can all be referred to as commands. In one embodiment, these commands can be transmitted in the form of the above-mentioned PIU. The minimum size of the PIU can be 32 bytes, and the maximum size of the PIU can be 65600 bytes. The format of the PIU can have different sizes depending on its type.

[0044] In an embodiment, when the command is provided in the form of a PIU, a diagnostic command for requesting to perform a self-test operation may be provided in the form of a command PIU. Further, a response to the diagnostic command may be provided in the form of a response PIU.

[0045] The host 400 may generate a command related to a self-test operation to be performed by the memory device 50, and provide the command to the memory controller 200. Further, the host 400 may receive a response to the command from the memory controller 200.

[0046] For example, the command related to the self-test operation may be a diagnostic command (SENDDIAGNOSTIC CMD) for requesting execution of the self-test operation, a diagnostic result receiving command (RECEIVEDIAGNOSTIC RESULT CMD) for requesting a result of the self-test operation, and the like.

[0047] Figure 2 It is shown Figure 1 A diagram of an example of a memory controller is shown.

[0048] Reference Figure 1 and Figure 2 , the memory controller 200 may include a self-test manager 210 and a response generator 220 .

[0049] The self-test manager 210 may receive a diagnostic command SENDDIAGNOSTIC CMD for requesting to perform a self-test operation from the host 400. The diagnostic command SENDDIAGNOSTIC CMD may be provided in the form of a PIU. The diagnostic command SENDDIAGNOSTIC CMD may include information about a self-test operation to be performed by the memory device 50.

[0050] The self-test manager 210 may perform a self-test operation in response to the received diagnostic command SEND DIAGNOSTIC CMD. In one embodiment, the self-test manager 210 may perform a self-test operation on the memory controller 200 itself. In another embodiment, the self-test manager 210 may provide a self-test command SELF-TESTCMD to the memory device 100 to control the memory device 100 to perform a self-test operation. Therefore, the self-test manager 210 may receive a result obtained by performing the self-test operation from the memory device 100. In yet another embodiment, the self-test manager 210 may perform a self-test operation on the entire memory device 50.

[0051] The self-test manager 210 may provide the result of the self-test operation, SELF-TEST RESULT, to the response generator 220. The response generator 220 may generate a response including result information, which indicates the result of the self-test operation. The response generated by the response generator 220 may be a response to a diagnostic command, SENDDIAGNOSTIC RESPONSE. In an embodiment, the response generator 220 may generate a response in the form of a PIU. In an embodiment, the result information indicating the result of the self-test operation may be included in an extra header segment of the response PIU. The result information indicating the result of the self-test operation may include information about whether an error occurs in the self-test operation, the detailed cause of the error, the location of the error, etc.

[0052] The response generator 220 may provide the response SEND DIAGNOSTIC RESPONSE to the diagnostic command to the host 400, and the host 400 may obtain the result of the self-test operation performed by the storage device 50 based on the result information included in the response. In an embodiment, the host 400 may check the additional header segment of the response SEND DIAGNOSTIC RESPONSE to the diagnostic command to obtain the result of the self-test operation.

[0053] Figure 3 It is shown Figure 1 A diagram of another example of a memory controller is shown.

[0054] Reference Figure 3 , the memory controller 1000 may include a processor 1010 , an internal memory 1020 , an error correction code (ECC) circuit 1030 , a host interface 1040 , a buffer memory interface 1050 , and a memory interface 1060 .

[0055] The processor 1010 may perform various calculations for controlling the memory device 100 and generate various commands. When the processor 1010 receives a request from the host 400, the processor 1010 may generate a command according to the received request and transmit the generated command to the queue controller. In an embodiment, the processor 1010 may perform a self-test operation in response to a diagnostic command received from the host 400. In the present disclosure, the request or command provided by the host 400 to the memory device 50 may mean that the request and the command are the same. The request or command provided by the host 400 to the memory device 50 may be distinguished from the command provided by the memory controller 200 to the memory device 100. Further, the processor 1010 may generate a response corresponding to the diagnostic command. The processor 1010 may generate a response corresponding to the diagnostic command so that the result of the self-test operation is included in the response. In an embodiment, the processor 1010 may generate a response in the form of a PIU, which includes a basic header segment and an additional header segment. In an embodiment, result information indicating the result of the self-test operation may be included in the additional header segment.

[0056] The internal memory 1020 may store various information for the operation of the memory controller 1000. For example, the internal memory 1020 may include a logical address mapping table and a physical address mapping table. The internal memory 1020 may be configured by at least one of a random access memory (RAM), a dynamic RAM (DRAM), a static RAM (SRAM), and a tightly coupled memory (TCM). In an embodiment, information related to a self-test operation may be stored in the internal memory 1020. However, the present disclosure is not limited thereto, and information related to a self-test operation may be stored in a separate memory distinct from the memory controller 1000.

[0057] The ECC circuit 1030 is configured to detect and correct errors in data received from the memory device 100 by using an error correction code (ECC). The processor 1010 may adjust a read voltage according to an error detection result of the ECC circuit 1030, and control the memory device 100 to perform a re-read. In an embodiment, the error correction block may be provided as a component of the memory controller 1000.

[0058] The host interface 1040 may transfer requests (or commands), addresses, data, etc. between the memory controller 1000 and the host 400. For example, the host interface 1040 may receive commands, addresses, data, etc. from the host 400, and send data read from the memory device 100, responses to commands, etc. to the host 400. The host interface 1040 may communicate with the host 400 using at least one of various interface protocols or standards such as Universal Serial Bus (USB), Serial AT Attachment (SATA), Serial 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), Load Reduced DIMM (LRDIMM), Enhanced Small Form Factor Memory Disk Interface (ESDI), and Electronic Integrated Drive IDE. In an embodiment, the host interface 1040 may receive a diagnostic command from the host 400 and send a response to the diagnostic command generated by the processor 1010 to the host 400 .

[0059] The buffer memory interface 1050 can transfer data between the processor 1010 and the buffer memory. The buffer memory can be used as a working memory or a cache memory of the memory controller 1000, and stores data used in the storage device 50. The buffer memory can be used as a read buffer, a write buffer, a mapping buffer, etc. by the processor 1010. In some embodiments, the buffer memory may include a double data rate synchronous dynamic random access memory (DDR SDRAM), a fourth generation low power double data rate (LPDDR4) SDRAM, a graphic double data rate (GDDR) SDRAM, a low power DDR (LPDDR) or a Rambus dynamic access memory (RDRAM). The buffer memory can be independently located outside the memory controller 1000. When the buffer memory is included in the memory controller 1000, the buffer memory interface 1050 can be omitted.

[0060] The memory interface 1060 may transfer commands, addresses, data, etc. between the memory controller 1000 and the memory device 100. For example, the memory interface 1060 may send commands, addresses, data, etc. to the memory device 100 through a channel, and receive data, etc. from the memory device 100. In an embodiment, the memory interface 1060 may provide the memory device 100 with a self-test command for a self-test operation performed by the processor 1010. Further, the memory interface 1060 may receive a result of the self-test operation performed by the memory device 100 from the memory device 100.

[0061] Figure 4 is a diagram showing the structure of a data unit (or data packet) used for communication between the host 400 and the memory controller 200 .

[0062] Reference Figure 1 and Figure 4 , the host 400 and the memory controller 200 may communicate with each other using a data packet called a protocol information unit (hereinafter, referred to as a PIU). In terms of the interface connection between the host 400 and the storage device 50, one device may transmit the PIU to the other device. The device that generates the PIU may be referred to as an initiating device, and the device that receives the generated PIU may be referred to as a target device. That is, the PIU is not a data packet that one of the host 400 and the storage device 50 transmits unilaterally to the other device, but may be a data packet transmitted between the two devices.

[0063] According to an operation to be performed by the host 400 or the memory controller 200, the PIU may include an inquiry request PIU, a command PIU, a response PIU, a data output PIU, a data input PIU, and or a prepare transfer PIU.

[0064] The query request PIU may provide the storage device 50 with a device descriptor including several parameters of the storage device 50 .

[0065] The command PIU may be a protocol information unit transmitted when the host 400 transmits a command to the storage device 50 .

[0066] The response PIU may be a protocol information unit transmitted when the storage device 50 provides a response to a command provided by the host 400 .

[0067] The data output PIU may be a protocol information unit transmitted when the host 400 provides data to the storage device 50 .

[0068] The data input PIU may be a protocol information unit transmitted when the storage device 50 provides data to the host 400 .

[0069] The ready to transfer PIU may be a protocol information unit transmitted when the storage device 50 notifies that the storage device 50 is ready to receive a data output PIU from the host 400. When the storage device 50 has enough buffer space to store data provided by the host 400, the ready to transfer PIU may be transmitted.

[0070] The minimum size of a PIU may be 32 bytes, and the maximum size of a PIU may be 65600 bytes. The format of a PIU may have different sizes depending on its type.

[0071] In an embodiment, the PIU may include a basic header segment 61 , a transaction-specific field 62 , an additional header segment 63 , and a data segment 64 .

[0072] The basic header segment 61 may have a size of 12 bytes. The basic header segment 61 may be commonly included in all PIUs. The basic header segment 61 may include basic setting information related to the PIU.

[0073] The transaction specific field 62 may be included in the PIU at byte addresses 12 to 31. Depending on the type of PIU, the transaction specific field 62 may include a specific transaction code.

[0074] When the Total EHS Length field of the basic header segment 61 has a non-zero value, the additional header segment 63 may be defined. The additional header segment 63 may start from the byte address 32 of the PIU. When the basic header segment 61 does not include sufficient information, the additional header segment 63 may be an area capable of additionally storing data.

[0075] The data segment 64 may be included in the data-out PIU or the data-in PIU.

[0076] In an embodiment, the additional header segment 63 and the data segment 64 may not be included in all PIUs, but may be included only in specific PIUs.

[0077] Figure 5 is a diagram showing the structure of a basic header segment of a PIU.

[0078] Reference Figure 5 The basic header segment 61 may include transaction type, flag, logical unit number (LUN), task tag, initiator ID, command set type, query function / task management function (Query Function, TaskManag.Function), response, status, total extra header segment length (Total EHS Length), device information and data segment length.

[0079] The transaction type may be a field having a unique value according to the type of PIU. Examples of transaction types according to the type of PIU are shown in Table 1 below.

[0080] Table 1

[0081]

[0082]

[0083] The flag may be a field having different values ​​according to the transaction type. The logical unit number (LUN) may be a field indicating the number of the logical unit on which the operation is to be performed among a plurality of logical units included in the object on which the operation is to be performed. Figure 1 Each of the described host 400 and storage device 50 may include a plurality of logical units, and a logical unit number (LUN) of a basic header segment 61 included in the PIU may indicate a specific logical unit among the plurality of logical units.

[0084] Depending on the issue type, task tags can correspond to fields with different values.

[0085] The initiator ID (IID) may be a field for identifying who is the initiator of the request operation. Therefore, the initiator ID may have different values ​​when the host 400 generates the PIU and when the storage device 50 generates the PIU.

[0086] The command set type may be a field included in the command PIU and the response PIU. The command set type may be a field indicating which interface supports a command, such as whether the command is a SCSI command, a UFS command, or a manufacturer-defined command.

[0087] Query Function / Task Management Function (Query Function, Task Manag. Function) may be a field input to the PIU, such as a query request, a query response, or a task management request.

[0088] The response may be a field indicating whether the performance of the requested operation succeeded or failed.

[0089] Status may be a field indicating the SCSI status.

[0090] The total extra header segment length (Total EHS Length) may be a field indicating the size of the extra header segment in units of 32 bits. When the PIU includes an extra header segment, the total extra header segment length (Total EHS Length) may be used. The length of the extra header segment may be in units of 4 bytes. The maximum size of the extra header segment may be 1024 bytes. When the extra header segment is not used, the value of the total extra header segment length (Total EHS Length) may be 0.

[0091] The device information may include information used only when performing a specific function.

[0092] The data segment length may be a field indicating the length of the data segment of the PIU. When the PIU does not include the data segment, the data segment length may be 0.

[0093] Figure 6 is a diagram showing the structure of a command descriptor block (CDB) included in the transaction specific field 62 of the PIU.

[0094] Reference Figure 4 and Figure 6 , the command descriptor block may be included in the transaction-specific field 62 of the PIU. The area of ​​the transaction-specific field 62 including the command descriptor block may be designated as a CDB field. The CDB field may be an array of 16 bytes including the command descriptor block.

[0095] although Figure 6 A 6-byte command descriptor block format is shown, but the size of the command descriptor block may be different therefrom. For example, a maximum of 16-byte command descriptor blocks may be used in the UFS interface.

[0096] In an example, the command descriptor block may include zeroth to fifth bytes, and each byte may include zeroth to seventh bits.

[0097] The 0th to 7th bits of the 0th byte of the command descriptor block may indicate an operation code. For example, the operation codes of various SCSI commands used in the UFS interface are shown in Table 2 below.

[0098] Table 2

[0099]

[0100]

[0101] The 0th to 7th bits of the first to fifth bytes of the command descriptor block may include miscellaneous CDB information. The miscellaneous CDB information may be defined by the standards of each command. In an embodiment, the miscellaneous CDB information may include information about the operation to be performed by each command.

[0102] The 0th to 7th bits of the sixth byte of the command descriptor block may be defined as a control byte, but the control byte may not be used in the UFS interface.

[0103] Figure 7 is a diagram showing the structure of the additional header segment 63 of the PIU.

[0104] Reference Figure 5 and Figure 7 , when the total length of the additional header segments (Total EHS Length) of the basic header segment 61 is not 0, the additional header segment 63 may exist. That is, in the PIU, the additional header segment 63 may not exist, or at least one additional header segment 63 may exist. In an embodiment, the additional header segment 63 may start from the byte address 32 of the PIU. The length of the additional header segment 63 may be a multiple of 32 bytes. When the basic header segment 61 does not include enough information, the additional header segment 63 may be an area capable of storing additional data.

[0105] In an embodiment, the additional header segment 63 may include a header area 63a and a data area 63b. The header area 63a may include an EHS length (bLength) indicating the size of the additional header segment 63. The EHS length (bLength) may indicate the size of the additional header segment 63 in units of 32 bytes.

[0106] The header area 63a may further include an EHS type (bEHSType) indicating the type of data included in the additional header segment 63. For example, when the EHS type (bEHSType) has a value of 01h, the data included in the additional header segment 63 may be data related to advanced RPMB operations. The header area 63a may further include an EHS subtype (bEHSSubType) indicating the subtype of the data included in the additional header segment 63.

[0107] The data area 63b may include EHS data transmitted using the additional header segment 63. The type of the EHS data may be determined by the values ​​of the EHS type (bEHSType) and the EHS subtype (bEHSSubType).

[0108] Figure 8 is a diagram illustrating a PIU structure of a diagnostic command according to an embodiment of the present disclosure.

[0109] Reference Figure 1 and Figure 8 , a diagnostic command (SEND DIAGNOSTIC CMD) may be provided from the host 400. The PIU of the diagnostic command (SEND DIAGNOSTIC CMD) may include a basic header segment 61 and a transaction-specific field 62.

[0110] In an embodiment, since the diagnostic command (SENDDIAGNOSTIC CMD) is a type of command, the diagnostic command (SENDDIAGNOSTIC CMD) may be provided in a PIU form from the host 400 to the storage device 50. Therefore, the transaction type included in the basic header segment 61 of the diagnostic command (SENDDIAGNOSTIC CMD) may be represented as xx00 0001b, as described in Table 1 above.

[0111] In one embodiment, the total extra header segment length (Total EHS Length) included in the basic header segment 61 of the diagnostic command (SENDDIAGNOSTIC CMD) may have a value of 0. The PIU of the diagnostic command (SENDDIAGNOSTIC CMD) may not include any extra header segment. However, the present disclosure is not limited to this. In another embodiment, the total extra header segment length (Total EHS Length) included in the basic header segment 61 of the diagnostic command (SENDDIAGNOSTIC CMD) may have a value other than 0. The PIU of the diagnostic command (SEND DIAGNOSTIC CMD) may include an extra header segment, and the extra header segment may additionally include information related to the self-test operation to be performed by the diagnostic command (SENDDIAGNOSTIC CMD).

[0112] In an embodiment, the data segment length included in the basic header segment 61 of the diagnostic command (SENDDIAGNOSTIC CMD) may have a value of 0. The PIU of the diagnostic command (SEND DIAGNOSTIC CMD) may not include any data segment, but the present disclosure is not limited thereto.

[0113] The transaction specific field 62 of the diagnostic command (SENDDIAGNOSTIC CMD) may include an expected data transfer length. The expected data transfer length may indicate the number of bytes to be transferred to complete the command as indicated by the command descriptor block included in the PIU.

[0114] Further, the transaction-specific field 62 of the diagnostic command (SENDDIAGNOSTIC CMD) may include a CDB field, and a command descriptor block related to the self-test operation to be performed by the diagnostic command (SENDDIAGNOSTIC CMD) may be included in the CDB field. Fig. 9 The command descriptor block included in the transaction-specific field 62 of the diagnostic command (SENDDIAGNOSTIC CMD) is described in more detail.

[0115] Fig. 9is a diagram illustrating a structure of a command descriptor block included in a transaction-specific field of a diagnostic command according to an embodiment of the present disclosure.

[0116] Reference Fig. 9 , a diagnostic command descriptor block included in the transaction-specific field of the diagnostic command may indicate an operation code indicated by the zeroth byte, and the operation code indicated by the diagnostic command descriptor block may be represented as 1Dh, as described in Table 2 above.

[0117] The fifth to seventh bits of the first byte in the diagnostic command descriptor block may indicate a self-test code. The self-test code may indicate the type of self-test operation to be performed. For example, self-test code 001b may represent a background short self-test operation, and accordingly, the storage device may perform a short self-test operation in a background mode.

[0118] The self-test code 010 b may indicate a background extended self-test operation, and thus, the memory device may perform the extended self-test operation in a background mode.

[0119] The self-test code 100b may indicate to abort the background self-test, and accordingly, the storage device performing the self-test operation in the background mode may abort the self-test operation. When the storage device performs the self-test operation in the foreground mode, the storage device may end the command in the CHECK CONDITION state, in which the sense key is set to ILLEGAL REQUEST and the additional sense code is set to INVALID FIELD IN CDB. In the present disclosure, the command ends with a specific status may refer to the storage device providing a response corresponding to the command to the host, and the status of the response indicates a specific status.

[0120] The self-test code 101 b may indicate a foreground short self-test operation, and accordingly, the storage device may perform the short self-test operation in a foreground mode.

[0121] The self-test code 110 b may indicate a foreground extended self-test operation, and accordingly, the storage device may perform the extended self-test operation in a foreground mode.

[0122] In an embodiment, a short self-test operation may refer to a self-test operation that includes one or more segments and is completed within two minutes. An extended self-test operation may refer to a self-test operation that includes one or more segments and is completed at a separately defined time. For each manufacturer, the tests performed in segments may be different. Examples of segments may be electrical segments, search / servo segments, read / verify segments, etc. In the case of electrical segments, the logic unit may test its own electronic devices and perform, for example, buffer RAM tests, read / write circuit tests, read / write head tests, etc. In the case of search / servo segments, the storage device may test search capabilities and servo capabilities. In the case of read / verify segments, the storage device may perform a read scan on a portion or the entire surface of the medium.

[0123] When the storage device performs a self-test operation in the foreground mode, the storage device may end all commands except the query command, the report LUNS command, and the request sensing command in the CHECK CONDITION state.

[0124] When the storage device performs a self-test operation in the background mode, the storage device may complete the command in a GOOD state, initialize the next self-test result log parameter in the self-test result log page, and then perform the self-test operation.

[0125] The fourth bit of the first byte in the diagnostic command descriptor block may indicate a page format (PF) bit. The page format (PF) bit may specify the format of a parameter list sent by the host through a diagnostic command.

[0126] The second bit of the first byte in the diagnostic command descriptor block may indicate a self-test (SELFTEST) bit. The self-test (SELFTEST) bit may indicate whether the self-test operation to be performed by the storage device is a default self-test operation. In an embodiment, when the self-test (SELFTEST) bit indicates 1, the storage device may perform a default self-test operation. When the storage device performs the default self-test operation, the storage device may end all commands except the query command, the report LUNS command, and the request sensing command in the CHECK CONDITION state. In the CHECK CONDITION state, the sensing key may be set to NOTREADY, and the additional sensing code may be set to UNIT NOT READY and SELF-TEST IN PROGRESS. When no error is sensed during the default self-test operation, the storage device may end the command in the GOOD state. When an error is sensed during the default self-test operation, the storage device may end the command in the set CHECK CONDITION state so that the sensing key is set to HARDWARE ERROR and the additional sensing code indicates the cause of the error.

[0127] The first bit of the first byte in the diagnostic command descriptor block may indicate a device offline (DEVOFFL) bit. When the device offline (DEVOFFL) bit is set to 1, this may mean that the default self-test operation performed by the storage device has an impact on the logical units in the storage device. When the device offline (DEVOFFL) bit is set to 9, this may mean that after the storage device completes the default self-test operation, no impact caused by the diagnostic command processing will be generated in any logical unit. When the self-test (SELFTEST) bit is set to 0, the device offline (DEVOFFL) bit can be ignored.

[0128] The zeroth position of the first byte in the diagnostic command descriptor block can indicate the unit offline (UNITOFFL) position. When the unit offline (UNITOFFL) position is set to 1, this can refer to the default self-test operation has an impact on the user-accessible medium in the logical unit. When the unit offline (UNITOFFL) position is set to 1, this can refer to that after the storage device completes the default self-test operation, any impact caused by the diagnostic command processing will not be generated in the user-accessible medium. When the self-test (SELFTEST) position is set to 0, the unit offline (UNITOFFL) position can be ignored.

[0129] At least a portion of the third byte and the fourth byte in the diagnostic command descriptor block may indicate a parameter list length. The parameter list length may be the length of the parameter list to be transmitted from the host to the storage device, expressed in bytes. When the parameter list length is 0, this may mean that there is no data to be transmitted.

[0130] Fig.10 is a table illustrating a self-test operation according to information included in a transaction-specific field of a diagnostic command according to an embodiment of the present disclosure.

[0131] Reference Fig.10 , the self-test operation to be performed according to the combination of the values ​​of the self-test code, the page format (PF) bit, the self-test (SELFTEST) bit and the parameter list length can be determined.

[0132] In case 1, the self-test code, PF bit, self-test bit, and parameter list length may all be 0. In case 1, the storage device may complete the command in a GOOD state.

[0133] In case 2, the self-test code, PF bit, and self-test bit may be 0, and the parameter list length may not be 0. In case 2, the storage device may receive a parameter list from the host to perform a self-test operation. When the storage device receives a diagnostic result receive command (RECEIVE DIAGNOSTIC RESULT CMD), the storage device may provide parameter data to the host. However, in the case of the UFS interface, the diagnostic result receive command (RECEIVE DIAGNOTIC RESULTCMD) is not separately defined, which is problematic.

[0134] In case 3, the self-test code, PF bit, parameter list length may be 0, and the self-test bit may be 1. In case 3, the storage device may perform a default self-test operation. When the default self-test operation is performed normally, the storage device may end the command in the GOOD state. When the default self-test operation fails, the storage device may end the command in the set CHECKCONDITION state, so that the sense key is set to HARDWARE ERROR and the additional sense code indicates the cause of the error.

[0135] In case 4, the self-test code and the PF bit may be 0, the self-test bit may be 1, and the parameter list length may not be 0. In case 4, the storage device may end the command in the CHECK CONDITION state, in which the sense key is set to ILLEGAL REQUEST and the additional sense code is set to INVALID FIELD INCDB.

[0136] In case 5, the self-test code, self-test bit, parameter list length can be 0, and the PF bit can be 1. In case 5, when the storage device receives the diagnostic result receiving command (RECEIVE DIAGNOSTIC RESULT CMD), the storage device can provide the host with a diagnostic page or parameter data according to whether the PF bit is supported. However, in the case of the UFS interface, the diagnostic result receiving command (RECEIVE DIAGNOTIC RESULT CMD) is not separately defined, which is problematic.

[0137] In case 6, the self-test code and the self-test bit may be 0, the PF bit may be 1, and the parameter list length may not be 0. In case 6, the storage device may receive a parameter list from the host to perform a self-test operation. When the storage device receives a diagnostic result receive command (RECEIVE DIAGNOSTIC RESULT CMD), the storage device may provide a diagnostic page or parameter data to the host depending on whether the PF bit is supported. However, in the case of the UFS interface, the diagnostic result receive command (RECEIVE DIAGNOTIC RESULT CMD) is not separately defined, which is problematic.

[0138] In case 7, the self test code may be 0, and the PF bit and the self test bit may be 1. In case 7, the memory device may end the command in a CHECK CONDITION state in which the sense key is set to ILLEGAL REQUEST and the additional sense code is set to INVALID FIELD IN CDB.

[0139] In case 8, the self-test code may not be 0, and the PF bit, the self-test bit, and the parameter list length may be 0. In case 8, the storage device may perform a self-test operation based on the self-test code. That is, the storage device may perform a background short self-test operation when the self-test code is 001b, a background extended self-test operation when the self-test code is 010b, an abort background self-test operation when the self-test code is 100b, a foreground short self-test operation when the self-test code is 101b, and a foreground extended self-test operation when the self-test code is 110b.

[0140] In case 9, the self-test code may not be 0, the PF bit and the self-test bit may be 0, and the parameter list length may not be 0. In addition, in case 10, the self-test code may not be 0, the PF bit may be 0, and the self-test bit may be 1. In cases 9 and 10, the storage device may end the command in the CHECK CONDITION state, in which the sense key is set to ILLEGAL REQUEST and the additional sense code is set to INVALID FIELD IN CDB.

[0141] In case 11, the self-test code may not be 0, the PF bit may be 1, the self-test bit may be 0, and the parameter list length may not be 0. In case 11, similar to case 8, the storage device may perform a self-test operation based on the self-test code. In addition, when the storage device receives a diagnostic result receive command (RECEIVE DIAGNOSTIC RESULT CMD), the storage device may provide a diagnostic page or parameter data to the host depending on whether the PF bit is supported. However, in the case of the UFS interface, the diagnostic result receive command (RECEIVE DIAGNOTIC RESULT CMD) is not separately defined, which is problematic.

[0142] In case 12, the self-test code may not be 0, the PF bit may be 1, the self-test bit may be 0, and the parameter list length may not be 0. In case 13, the self-test code may not be 0, the PF bit may be 1, and the self-test bit may be 1. In cases 12 and 13, the storage device may end the command in the CHECK CONDITION state, in which the sense key is set to ILLEGAL REQUEST and the additional sense code is set to INVALID FIELD INCDB.

[0143] Fig.11 is a diagram illustrating a PIU structure of a response to a diagnosis command according to an embodiment of the present disclosure.

[0144] Reference Figure 1 and Fig.11 , the memory controller 200 sends a response to the diagnostic command to the host 400. The PIU of the response to the diagnostic command may include a basic header segment 61, a transaction-specific field 62, and an additional header segment 63. The PIU of the response may further include a data segment 64, optionally.

[0145] In an embodiment, a response to the diagnostic command (SENDDIAGNOSTIC CMD) may be provided in the form of a PIU from the storage device 50 to the host 400. Therefore, the transaction type included in the basic header segment 61 of the PIU of the response may be represented as xx00 0001b, as described in Table 1 above.

[0146] In an embodiment, the total extra header segment length (Total EHSLength) included in the basic header segment 61 of the PIU of the response may not have a value of 0. Therefore, the PIU of the response may include the extra header segment.

[0147] In an embodiment, the basic header segment 61 of the PIU of the response may include a response field. The response field may indicate whether the requested operation can succeed. For example, when the response field has a value of 00h, the response field may indicate that the target is successful. When the response field has a value of 00h, the response field may indicate that the target fails.

[0148] In an embodiment, the basic header segment 61 of the PIU of the response may include a status field. The status field may indicate the status of the command provided from the host 400.

[0149] The GOOD state in the command status may indicate that the storage device has completed the command without any errors. The CHECK CONDITION state in the command status may indicate that the storage device has completed the command but with errors, or requesting another operation to process the result. When the CHECK CONDITION state occurs, valid sense data about the last processed command may be returned as a response.

[0150] In one embodiment, the data segment length (Total EHS Length) included in the basic header segment 61 of the PIU of the response may not have a value of 0. Therefore, the PIU of the response may include the data segment 64. In another embodiment, the data segment length (Total EHS Length) included in the basic header segment 61 of the PIU of the response may have a value of 0. Therefore, the PIU of the response does not include the data segment 64.

[0151] In an embodiment, the data segment 64 may include bytes storing the sensing data length and the sensing data.

[0152] The sense data may include additional information about the error state. Therefore, when the command is successfully executed, there is no need to provide the sense data to the host 400. Therefore, the response of the PIU may not include the data segment 64, and therefore, the data segment length may have a value of 0.

[0153] The sensing data length may indicate the number of bytes of valid sensing data. In an embodiment, when the SCSI command set is used, the sensing data length may have a value of 18.

[0154] The sensing data may be provided in a fixed format, and the sensing data format may include a response code, a sensing key, sensing information, an additional sensing length, an additional sensing code (ASC), an additional sensing code qualifier (ASCQ), and the like.

[0155] The sense key can provide general information indicating that a command was not successful based on the occurrence of an error or abnormal situation. Therefore, the sense key can indicate the specific type of error. The additional sense code (ASC) can provide more detailed information about the error. In addition, the additional sense code qualifier (ASCQ) can further break down the error information.

[0156] The error types according to the value of the sensing key are shown in Table 3 below.

[0157] Table 3

[0158] Sensing key value describe 00h No sensing 01h Recovering from Errors 02h Not ready 03h Medium Error 04h Hardware Error 05h Illegal request 06h Unit Focus 07h Data Protection 08h Blank Check 09h Vendor Specific 0Ah Replication Aborted 0B Abnormal termination command 0Ch reserve 0h Volume overflow 0eH Error comparison 0F reserve

[0159] When the value of the sense key is 04h, this may indicate a HARDWARE ERROR, which means that the storage device has found an unrecoverable hardware error.

[0160] When the value of the sense key is 05h, this may refer to an ILLEGAL REQUEST, which means that an illegal parameter value is included in the command descriptor block or additional parameters.

[0161] In the existing UFS interface, the diagnostic result receiving command (RECEIVE DIAGNOSTIC RESULTCMD) is not defined. Therefore, when the self-test operation is performed according to the diagnostic command (SEND DIAGNOSTIC CMD), the storage device 50 can provide the result of the self-test operation using only the responsive status information and the sensing data.

[0162] When the self-test operation according to the diagnostic command is successfully performed, the storage device can end the command by providing a response including status information indicating a GOOD state. When the storage device 50 is not ready to receive the diagnostic command, the storage device 50 can provide a response including status information indicating a BUSY state to the host 400.

[0163] When a failure occurs in a self-test operation according to a diagnostic command, the storage device 50 may include status information indicating CHECKCONDITION, and the sensing key may provide a response including values ​​indicating ILLEGAL REQUEST, MEDIUMERROR, HARDWARE ERROR, UNIT ATTENTION, etc. to the host 400.

[0164] When an error is found through the self-test operation, a response of 04h in which the sense key is set to indicate HARDWARE ERROR may be provided from the storage device 50 to the host 400. Therefore, the host 400 only obtains information indicating that an error is found through the self-test operation, and it is difficult for the host 400 to obtain detailed information about the error, which is problematic.

[0165] The PIU of the response to the diagnostic command provided by the memory controller 200 according to an embodiment of the present disclosure may solve this problem using the additional header segment 63 .

[0166] The PIU of the response may include result information indicating the result of the self-test operation. The result information indicating the result of the self-test operation may include information on whether an error occurs in the self-test operation, a detailed reason for the error, a location where the error occurs, and the like.

[0167] Therefore, the memory controller 200 according to an embodiment of the present disclosure may provide the result of the self-test operation to the host 400 in more detail without receiving any separate command except the diagnostic command (SENDDIAGNOSTIC CMD) from the host 400 .

[0168] Fig.12 is a diagram showing the structure of an additional header segment 63 of a response according to an embodiment of the present disclosure.

[0169] Reference Fig.12 , the additional header segment 63 may include a header area 63a and a data area 63b. The EHS length bLength included in the header area 63a may be represented as 0x3. Therefore, it can be seen that the additional header segment 63 has a size of 96 bytes. However, Fig.12 The size of the additional header segment 63 shown is illustrative only and may be smaller or larger than 96 bytes.

[0170] The EHS type bEHSType included in the header area 63a may be represented as a value indicating that the EHS data stored in the data area 63b is data related to the self-test operation. For example, the value indicating that the EHS data is data related to the self-test operation may be defined as 02h.

[0171] The EHS subtype bEHSSubType included in the header area 63a of the additional header segment 63 may be represented as a value indicating the type of the self-test operation. For example, the EHS subtype bEHSSubType may include a value selected from the reference Fig. 9 and Fig.10The information included in the EHS subtype bEHSSubType may indicate the type of self-test operation performed in the storage device 50 by combining information including a self-test (SELFTEST) code, a page format (PF) bit, a self-test (SELFTEST) bit, a parameter list length, etc.

[0172] Result information indicating the result of the self-test operation may be included in the data area 63b of the additional header segment 63. The result information may be information defined for each manufacturer. For example, as described above, the result information may include information about whether an error occurred in the self-test operation, the detailed reason for the error, the location where the error occurred, etc.

[0173] Fig.13 is a sequence diagram illustrating an operation method of a storage device according to a comparative example of the present disclosure.

[0174] Reference Fig.13 In operation S1301, the host 400 may provide a diagnostic command (SENDDIAGNOSTIC CMD) to the storage device 50. Thus, the storage device 50 may perform a self-test operation. In operation S1303, the storage device 50 may provide a response (SENDDIAGNOSTIC Response) to the diagnostic command to the host 400.

[0175] Thereafter, in operation S1305, the host 400 may provide a RECEIVE DIAGNOSTIC RESULT CMD to the storage device 50 to obtain result information about the self-test operation. Therefore, in operation S1307, the storage device 50 may provide the host 400 with result information about the self-test operation through a DATA IN data packet.

[0176] When providing the result information is completed, the storage device 50 may provide a response (RECEIVE DIAGNOSTIC RESULT Response) to the diagnosis result receiving command to the host 400 in operation S1309 .

[0177] In an example, the commands, responses, data packets, etc. described above may be provided in the form of a PIU.

[0178] However, since the diagnostic result receiving command (RECEIVE DIAGNOSTICRESULT CMD) is not defined in the UFS interface, the storage device 50 cannot provide result information to the host 400, which is problematic. Fig.13 As shown, the storage device 50 using the UFS interface cannot provide result information through the data input (DATA IN) PIU, but can only provide limited information using a response to a diagnostic command (SENDDIAGNOSTIC Response).

[0179] Fig.14 is a sequence diagram illustrating an operation method of a storage device according to an embodiment of the present disclosure.

[0180] Reference Fig.14 In operation S1401, the host 400 may provide a diagnostic command (SENDDIAGNOSTIC CMD) to the storage device 50. Therefore, the storage device 50 may perform a self-test operation.

[0181] Thereafter, in operation S1403, the storage device 50 may provide a response (SENDDIAGNOSTIC Response) to the diagnostic command to the host 400. The response (SENDDIAGNOSTIC Response) to the diagnostic command may include an additional header segment. The additional header segment may include result information on the self-test operation.

[0182] That is, the storage device 50 according to an embodiment of the present disclosure can generate a response with an additional header segment, in which the result information about the self-test operation is included. Therefore, the storage device can provide the host 400 with more detailed result information about the self-test operation without receiving any separate diagnostic result receiving command (RECEIVEDIAGNOSTIC RESULT CMD).

[0183] In addition, Fig.13 Compared with the case where the storage device 50 uses the diagnostic result receiving command (RECEIVE DIAGNOSTICRESULT CMD) to provide result information to the host 400, Fig.14 In the case shown, the result information transmission process is further simplified. Therefore, the result information transmission operation speed can be increased, and the probability of errors occurring in the result information transmission can be reduced.

[0184] Fig.15 is a block diagram illustrating a solid state drive (SSD) system to which a storage device is applied according to an embodiment of the present disclosure.

[0185] Reference Fig.15, the SSD system 3000 includes a host 3100 and an SSD 3200. The SSD 3200 may receive / send signals from / to the host 3100 through a signal connector 3001 and receive power 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 3230, and a buffer memory 3240.

[0186] According to an embodiment of the present disclosure, the SSD controller 3210 may be used as a reference Figures 1 to 3 The memory controller 200 or 1000 is described.

[0187] The SSD controller 3210 may control the plurality of flash memories 3221 to 322n in response to a signal received from the host 3100. The signal may be a signal based on an interface between the host 3100 and the SSD 3200. For example, the signal may be a signal defined by at least one of an interface protocol or standard such as Universal Serial Bus (USB), Multimedia Card (MMC), Embedded MMC (eMMC), Peripheral Component Interconnect (PCI), PCI Express (PCIe), Advanced Technology Attachment (ATA), Serial ATA (SATA), Parallel ATA (PATA), Small Computer System Interface (SCSI), Enhanced Small Disk Interface (ESDI), Integrated Drive Electronics (IDE), FireWire, Universal Flash Storage (UFS), WI-FI, Bluetooth, and NVMe.

[0188] In an embodiment, the SSD controller 3210 may receive a diagnostic command (SENDDIAGNOSTICCMD) from the host 3100, and perform a self-test operation on the SSD 3200 in response to the diagnostic command. Further, the SSD controller 3210 may generate a response to the diagnostic command (SENDDIAGNOSTIC Response). The response to the diagnostic command may include an additional header segment, and the additional header segment may include result information of the self-test operation. The SSD controller 3210 may provide the generated response to the host 3100.

[0189] The auxiliary power supply 3230 is connected to the host 3100 through the power connector 3002. The auxiliary power supply 3230 can receive the power PWR input from the host 3100 and be charged with the power PWR. When the power supply from the host 3100 is not stable, the auxiliary power supply 3230 can provide power to the SSD 3200. The auxiliary power supply 3230 can be located in the SSD 3200, or located outside the SSD 3200. For example, the auxiliary power supply 3230 can be located on the mainboard and provide auxiliary power to the SSD 3200.

[0190] 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 temporarily store metadata (e.g., a mapping table) of the flash memories 3221 to 322n. The buffer memory 3240 may include at least one volatile memory such as DRAM, SDRAM, DDR SDRAM, LPDDR SDRAM, and GRAM, or may include at least one nonvolatile memory such as FRAM, ReRAM, STT-MRAM, and PRAM.

[0191] According to an embodiment of the present disclosure, a memory controller, a memory device, and an operating method of the memory device may be provided, which are capable of performing a self-test operation more efficiently.

[0192] Although the present disclosure has been shown and described with reference to certain embodiments of the present disclosure, it will be understood by those skilled in the art that various changes in form and details may be made in the present disclosure without departing from the concept and scope of the present disclosure as defined by the appended claims and their equivalents. Therefore, the scope of the present disclosure should not be limited to the above-mentioned embodiments, but should be determined not only by the appended claims but also by their equivalents.

[0193] In the above-described embodiments, all operations or some operations may be selectively performed and some operations may be omitted. In each embodiment, operations may not necessarily be performed in the order described and operations may be rearranged. The embodiments disclosed in this specification and the accompanying drawings are merely examples to facilitate understanding of the present disclosure, and the present disclosure is not limited thereto. That is, it should be apparent to those skilled in the art that various modifications may be made based on the technical scope of the present disclosure.

[0194] On the other hand, embodiments of the present disclosure have been described in the drawings and the specification. Although specific terms are used here, these are only for describing embodiments of the present disclosure. Therefore, the present disclosure is not limited to the above-mentioned embodiments and there may be many variations within the scope of the present disclosure. It should be apparent to those skilled in the art that, in addition to the embodiments of the present disclosure herein, various modifications may be made based on the technical scope of the present disclosure. In addition, the embodiments may be combined to form additional embodiments.

Claims

1. A memory controller, comprising: a host interface for receiving a diagnostic command from a host requesting execution of a self-test operation; as well as a processor that performs the self-test operation on the memory device and generates a response corresponding to the diagnostic command, The host interface transmits the response to the host, and the response includes: a basic header segment commonly included in a protocol information unit transmitted / received between the memory controller and the host; and An additional header segment includes result information indicating a result of the self-test operation.

2. The memory controller according to claim 1, wherein: The basic header segment includes a total additional header segment length field indicating a length of the additional header segment.

3. The memory controller according to claim 2, wherein: The Total Extra Header Segments Length field has a value other than 0.

4. The memory controller according to claim 1, wherein: The additional header segment includes: a header area, comprising length information indicating a length of the additional header segment and type information indicating that the additional header segment is related to the self-test operation; and The data area includes the result information.

5. The memory controller according to claim 4, wherein: The header area further includes subtype information indicating a type of the self-test operation.

6. The memory controller according to claim 5, wherein: The subtype information includes at least one item of information selected from the group consisting of: A self-test code indicating the type of the self-test operation; a page format bit indicating the format of the parameter list transmitted from the host; A self-test bit, indicating whether the self-test operation is a default self-test operation; and Parameter list length, indicating the length of the parameter list.

7. The memory controller according to claim 1, wherein: The diagnostic command includes: a basic header segment commonly included in a protocol information unit transmitted / received between the memory controller and the host; and A transaction-specific field comprising information about the self-test operation.

8. The memory controller according to claim 7, wherein: The transaction-specific field includes a data packet, and the data packet includes: A self-test code indicating the type of the self-test operation; a page format bit indicating the format of the parameter list transmitted from the host; A self-test bit, indicating whether the self-test operation is a default self-test operation; and Parameter list length, indicating the length of the parameter list.

9. A storage device, comprising: A memory device for storing data; as well as a memory controller that receives a diagnostic command requesting execution of a self-test operation from an external device, executes the self-test operation in response to the diagnostic command, and provides a response corresponding to the diagnostic command to the external device, The response includes: a basic header segment commonly included in a protocol information unit transmitted / received between the external device and the memory controller; and An additional header segment includes result information indicating a result of the self-test operation.

10. The storage device according to claim 9, wherein: The additional header segment includes: a header area, comprising length information indicating a length of the additional header segment and type information indicating that the additional header segment is related to the self-test operation; and The data area includes the result information.

11. The storage device according to claim 10, wherein: The header area further includes subtype information indicating a type of the self-test operation.

12. The storage device according to claim 11, wherein: The subtype information includes at least one item of information selected from the group consisting of: A self-test code indicating the type of the self-test operation; A page format bit, indicating the format of the parameter list transmitted from the external device; A self-test bit, indicating whether the self-test operation is a default self-test operation; and Parameter list length, indicating the length of the parameter list.

13. The storage device according to claim 9, wherein: The diagnostic command includes: a basic header segment commonly included in a protocol information unit transmitted / received between the memory controller and the external part; and A transaction-specific field comprising information about the self-test operation.

14. The storage device according to claim 13, wherein: The transaction-specific field includes a data packet, and the data packet includes: A self-test code indicating the type of the self-test operation; A page format bit, indicating the format of the parameter list transmitted from the external device; A self-test bit, indicating whether the self-test operation is a default self-test operation; and Parameter list length, indicating the length of the parameter list.

15. A method of operating a storage device, comprising: receiving a diagnostic command requesting execution of a self-test operation from an external device; performing the self-test operation in response to the diagnostic command; as well as generating a response including information regarding the results of said self-test operation, The response includes: a basic header segment commonly included in a protocol information unit transmitted / received between the storage device and the outside; and An additional header segment includes result information indicating a result of the self-test operation.

16. The method according to claim 15, wherein: The additional header segment includes: a header area, comprising length information indicating a length of the additional header segment, type information indicating that the additional header segment is related to the self-test operation, and sub-type information indicating a type of the self-test operation; and The data area includes the result information.

17. The method according to claim 16, wherein: The subtype information includes at least one item of information selected from the group consisting of: A self-test code indicating the type of the self-test operation; A page format bit, indicating the format of the parameter list transmitted from the external device; A self-test bit, indicating whether the self-test operation is a default self-test operation; and Parameter list length, indicating the length of the parameter list.

18. The method according to claim 15, wherein: The diagnostic command includes: a basic header segment commonly included in a protocol information unit transmitted / received between the storage device and the outside; and A transaction-specific field comprising information about the self-test operation.

19. The method according to claim 18, wherein: The transaction-specific field includes a data packet, and the data packet includes: A self-test code indicating the type of the self-test operation; A page format bit, indicating the format of the parameter list transmitted from the external device; A self-test bit, indicating whether the self-test operation is a default self-test operation; and Parameter list length, indicating the length of the parameter list.

20. The method according to claim 19, wherein: When the self-test operation is performed, an operation determined based on the data packet is performed.