Detection and isolation of failed hold-up capacitors using hardware circuitry within a data storage device
Hardware circuitry in data storage devices addresses the inefficiencies of detecting and isolating failed hold-up capacitors, ensuring rapid fault detection and isolation to prevent data loss and maintain device functionality.
Patent Information
- Application Number
- JP2024529323
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-06-28
- Filing Date
- 2023-05-04
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2043-05-04
AI Technical Summary
Existing data storage devices face issues with failed hold-up capacitors leading to unexpected power loss, which can render the device non-functional, and current methods for detecting and isolating such failures are inefficient, often requiring excessive CPU bandwidth and causing delays.
Implementing hardware circuitry within the data storage device to detect and isolate failed hold-up capacitors without firmware intervention, using detection and isolation circuits to identify short-circuit faults and disconnect faulty capacitors from the power supply.
This approach ensures rapid detection and isolation of failed capacitors, reducing the risk of data loss and maintaining device functionality by minimizing CPU usage and eliminating long detection delays.
Smart Images

Figure 2024542461000001_ABST
Abstract
Description
[Technical field]
[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Non-provisional Application No. 17 / 852,103, filed June 28, 2022, entitled “DETECTION AND ISOLATION OF FAILED HOLD-UP CAPACITORS USING HARDWARE CIRCUITRY IN A DATA STORAGE DEVICE,” the entire contents of which are incorporated by reference into this application for all purposes. [Background technology]
[0002] Storage devices allow users to store and retrieve data. Examples of storage devices include non-volatile memory devices. Non-volatile memory generally retains data after a power cycle. One example of non-volatile memory is flash memory, which may include an array(s) of NAND cells on one or more dies. Flash memory may be found in Solid-State Drives (SSD), Secure Digital (SD) cards, and the like. Flash storage devices may store control information associated with data. For example, flash storage devices may maintain control tables that include mappings of logical addresses to physical addresses. These control tables may be used to track the physical locations of logical sectors or blocks within the flash memory. The control tables may be stored in the non-volatile memory to enable access to the stored data after a power cycle.
[0003] Enterprise SSDs may include a capacitor bank to protect against unexpected power loss in order to safeguard user data. If one or more capacitors in the capacitor bank fail during the life of the drive, this may lead to a situation in which the drive can no longer function and the user cannot read information stored on the drive. It is therefore important to detect any capacitor failure as early as possible, isolate the faulty capacitor as quickly as possible, and / or take any corrective action as necessary.
[0004] The statements provided in the "Background" section should not be assumed to be prior art merely because they are mentioned in or associated with the "Background" section. The Background section may include information that describes one or more aspects of the subject technology, and the statements in this section are not intended to limit the invention. [Brief description of the drawings]
[0005] The detailed description will now be made with reference to the accompanying drawings. [Figure 1] FIG. 1 is a block diagram illustrating components of an exemplary data storage system in accordance with one or more embodiments. [Figure 2A] 1 illustrates an example capacitor bank circuit for providing power loss protection in a solid-state drive (SSD) in accordance with one or more embodiments. [Figure 2B] 1 illustrates example electronic components, including exemplary circuitry, that may be used to detect and isolate any failed capacitors in a power bank used to provide backup power to a data storage device, in accordance with one or more embodiments. [Figure 2C] FIG. 1 illustrates another example of electronic components including exemplary circuitry that may be used to detect and isolate any failed capacitors in a power bank used to provide backup power to a data storage device, in accordance with one or more embodiments. [Diagram 3]5 is a flowchart illustrating an exemplary process for detecting and isolating a failed hold-up capacitor using hardware circuitry in a data storage device in accordance with one or more embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0006] The detailed description set forth below is intended as a description of various configurations of the subject technology, and is not intended to represent the only configurations in which the subject technology may be practiced. The accompanying drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a thorough understanding of the subject technology. However, the subject technology may be practiced without these specific details. In some instances, structures and components are represented in block diagram form to avoid obscuring the concepts of the subject technology. For ease of understanding, similar components are labeled with the same element numbers.
[0007] This description relates generally to data storage systems and methods, and more particularly, for example but not limited to, detection and isolation of failed hold-up capacitors using hardware circuitry within a data storage device.
[0008] One or more implementations of the subject technology provide several performance benefits that improve the functionality of a computer. User data can be protected by using hardware circuitry within the data storage device to detect and isolate failed hold-up capacitors and take corrective action as necessary. In turn, a host computer coupled to the data storage device also benefits from the improved performance and security of the data storage device.
[0009] FIG. 1 is a block diagram illustrating components of an exemplary data storage system in accordance with aspects of the subject technology. A data storage system may also be referred to as a system, a data storage device, a storage device, a solid-state drive, a drive, or a device. As shown in FIG. 1, in some aspects, a data storage system 100 (e.g., a solid-state drive (SSD)) comprises a data storage controller 101, a storage medium 102, and a flash memory array including one or more flash memories 103. The data storage controller 101 may also be referred to as a controller 101. The controller 101 may use the storage medium 102 for temporary storage of data and information used to manage the data storage system 100. The controller 101 may include several internal components (not shown), such as read-only memory, other types of memory, a flash component interface (e.g., a multiplexer that manages command and data transfer along a serial connection to the flash memory 103), an input / output (I / O) interface, error correction circuitry, etc. In some aspects, the elements of the controller 101 may be integrated into a single chip. In other aspects, these elements may be separated onto their own Personal Computer (PC) boards.
[0010] In some implementations, aspects of the present disclosure may be implemented in data storage system 100. For example, aspects of the present disclosure may be integrated with the functionality of data storage controller 101 or may be implemented as a separate component for use with data storage controller 101.
[0011] The controller 101 may also include a processor that may be configured to execute code or instructions to perform the operations and functions described herein, manage request flow and address mapping, perform calculations, and generate commands. The processor of the controller 101 may be configured to monitor and / or control the operation of components within the data storage controller 101. The processor may be a general-purpose microprocessor, a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gate logic, discrete hardware components, or a combination thereof. One or more sequences of instructions may be stored as firmware on a Read-Only-Memory (ROM) within the controller 101 and / or its processor. The one or more sequences of instructions may be software stored in and read from the storage medium 102, the flash memory 103, or received from the host device 104 (e.g., via the host interface 105). The ROM, the storage medium 102, and the flash memory 103 represent examples of machine or computer readable media on which instructions / code executable by the controller 101 and / or its processor may be stored. A machine or computer readable medium may generally refer to any one or more media used to provide instructions to the controller 101 and / or its processor, including volatile media such as dynamic memory used for buffers in the storage medium 102 or the controller 101, and non-volatile media such as electronic, optical, and magnetic media.
[0012] In some aspects, the controller 101 may be configured to store data received from the host device 104 in the flash memory 103 in response to a write command from the host device 104. The controller 101 is further configured to read the data stored in the flash memory 103 in response to a read command from the host device 104 and transfer the read data to the host device 104. The host device 104 may also be referred to as a host, a host system, or a host computer.
[0013] Host device 104 represents any device coupled to data storage system 100 and configured to store data in data storage system 100. Host device 104 may be a computing system such as a personal computer, a server, a workstation, a laptop computer, a personal digital assistant (PDA), a smartphone, etc. Alternatively, host device 104 may be an electronic device such as a digital camera, a digital audio player, a digital video recorder, etc.
[0014] In some aspects, the storage medium 102 represents a volatile memory used to temporarily store data and information used to manage the data storage system 100. In accordance with aspects of the subject technology, the storage medium 102 is a Random Access Memory (RAM), such as Double Data Rate (DDR) RAM. Other types of RAM may be used to implement the storage medium 102. The memory 102 may be implemented using a single RAM module or multiple RAM modules. Although the storage medium 102 is shown as being separate from the controller 101, one skilled in the art will recognize that the storage medium 102 may be incorporated into the controller 101 without departing from the scope of the subject technology. Alternatively, the storage medium 102 may be a non-volatile memory, such as a magnetic disk, flash memory, peripheral SSD, etc.
[0015] As further shown in FIG. 1 , the data storage system 100 may also include a host interface 105. The host interface 105 may be configured to be operatively coupled (e.g., via a wired or wireless connection) to the host device 104 to receive data from the host device 104 and transmit data to the host device 104. The host interface 105 may include electrical and physical connections or wireless connections to operatively couple the host device 104 to the controller 101 (e.g., via an I / O interface of the controller 101). The host interface 105 may be configured to communicate data, address, and control signals between the host device 104 and the controller 101. Alternatively, the I / O interface of the controller 101 may comprise the host interface 105 and / or may be combined with the host interface 105. The host interface 105 may be configured to implement a standard interface such as Small Computer System Interface (SCSI), Serial Attached SCSI (SAS), a Fibre Channel interface, Peripheral Component Interconnect Express (PCIe), Serial Advanced Technology Attachment (SATA), Universal Serial Bus (USB), etc. The host interface 105 may be configured to implement only one interface. Alternatively, the host interface 105 (and / or the I / O interfaces of the controller 101) may be configured to implement multiple interfaces, which may be individually selectable using configuration parameters selected by a user or programmed at assembly. The host interface 105 may include one or more buffers for buffering transmissions between the host device 104 and the controller 101.
[0016] Flash memory 103 may represent a non-volatile memory device for storing data. In accordance with aspects of the subject technology, flash memory 103 includes, for example, a NAND flash memory. Flash memory 503 may include a single flash memory device or chip, or may include multiple flash memory devices or chips arranged in multiple channels (as shown in FIG. 1). The capacity and configuration of flash memory 103 are not particularly limited. For example, the number of physical blocks, the number of physical pages per physical block, the number of sectors per physical page, and the size of the sectors may vary within the scope of the subject technology.
[0017] Flash memories may have a standard interface specification so that chips from multiple manufacturers can be used interchangeably (at least for the most part). The interface hides the internal operation of the flash and returns only the bit values detected internally for the data. In aspects, the interface of the flash memory 103 is used to access one or more internal registers 106 and an internal flash controller 107 for communication by an external device (e.g., controller 101). In some aspects, the registers 106 may include address registers, command registers, and / or data registers to internally retrieve and output required data to and from the NAND memory cell array 108. The NAND memory cell array 108 may also be referred to as a NAND array, memory array, or NAND. For example, the data registers may contain data to be stored in the memory array 108 or data after fetching from the memory array 108, may be used for temporary data storage, and / or may act like a buffer. The address registers may store the memory address where data is fetched to the host device 104, or the address where data is sent and stored. In some aspects, command registers are included to control parity, interrupt control, etc. In some aspects, the internal flash controller 107 is accessible via control registers to control the general behavior of the flash memory 103. The internal flash controller 107 and / or the control registers may control the number of stop bits, word length, receiver clock source, addressing mode switching, paging control, co-processor control, etc.
[0018] In some aspects, the registers 106 may include test registers. The test registers may be accessed by specific address and / or data combinations provided at the interface of the flash memory 103 (e.g., by dedicated software provided by the manufacturer to perform various tests on the internal components of the flash memory). In further aspects, the test registers may be used to access and / or modify other internal registers, such as command and / or control registers. In some aspects, test modes accessible via the test registers may be used to enter or modify specific programming conditions (e.g., read levels) of the flash memory 103 to dynamically change how data is read from the memory cells of the memory array 108. The registers 106 may also include one or more data latches coupled to the flash memory 103.
[0019] It should be understood that in all cases, the data is not necessarily the result of a command received from and / or returned to the host 104. In some aspects, the controller 101 may be configured to perform a read operation independent of the host 104 (e.g., to verify a read level or BER). As used herein, the terms "configured to," "operable to," and "programmed to" do not imply any particular tangible or intangible modification of the subject matter and are intended to be used interchangeably. For example, a processor configured to monitor and control an operation or component may also mean that the processor is programmed to monitor and control the operation or that the processor is operable to monitor and control the operation. Similarly, a processor configured to execute code may be interpreted as a processor programmed to execute code or operable to execute code.
[0020] FIG. 2A illustrates an example capacitor bank 200 for providing power loss protection in a data storage device, such as an enterprise solid-state drive (SSD), in accordance with one or more embodiments.
[0021] In this example, capacitors C1, C2, ..., C10 are connected in parallel. The number of capacitors and / or the capacitance values of the capacitors may be determined based on the data storage device (e.g., the number of flash memories, the capacity of the data storage device) and / or the amount of power backup required for the device.
[0022] In some systems, firmware running on the SSD may periodically check the health of the capacitor bank 200. The frequency of the health checks may be adjusted. However, if these health checks are performed too frequently, an excessive amount of Central Processing Unit (CPU) bandwidth may be required. This, in turn, may impact the throughput of the drive.
[0023] In one or more aspects, embodiments of the subject technology are directed to hardware circuits that can obviate one or more problems due to the aforementioned limitations and other shortcomings. In one or more aspects, implementations of the subject technology can be used to detect and isolate faulty capacitors using hardware without firmware intervention. In one or more examples, the type of capacitor failure may be a short circuit failure.
[0024] FIG. 2B illustrates example electronic components, including an exemplary circuit 204, that may be used to detect and isolate any failed capacitors in a power bank used to provide backup power to a data storage device, in accordance with one or more embodiments.
[0025] In some aspects, a data storage device (e.g., data storage device 100 or enterprise solid-state drive) may include a non-volatile memory (e.g., flash memory 103) configured to store data and hardware circuitry (e.g., 204, including 204-2 and 204-4) coupled to a controller 202. Controller 202 may also be referred to as a microcontroller.
[0026] In one example, a controller (e.g., 101) of Figure 1 may include some portions or all of controller 202 or perform some or all of the functionality of controller 202. In another example, a controller (e.g., 101 and / or 107) of Figure 1 may include some or all of controller 202 or perform some or all of the functionality of controller 202. In yet another example, some or all of the hardware circuitry (e.g., 204) may be external to the controller (e.g., 101 and / or 107) of Figure 1 but within data storage device 100. These are examples, and the subject technology is not limited to these examples.
[0027] The hardware circuit (e.g., 204, including 204-2 and 204-4) may be configured to provide backup power to a non-volatile memory (e.g., a non-volatile memory die) and a microcontroller. The hardware circuit may include multiple circuit components (e.g., 204-2 and 204-4). Each of the circuit components may include a hold-up capacitor (e.g., capacitor 206-2 or 206-4). In one or more examples, the hold-up capacitor may be a capacitor to hold a charge or to provide a backup power source for a data storage device in the event of an unexpected power loss to allow the device to shut down gracefully. In one or more examples, the hold-up capacitor may be a capacitor that is charged from the output of the rectifier through a low resistance and alternating current (AC) line of the rectifier. Each of the multiple circuit components may also include detection and isolation circuitry (e.g., 210-2, 208-2, 212-2, and 216-2, or 210-4, 208-4, 212-4, and 216-4) configured to detect whether the hold-up capacitor has failed and to isolate the hold-up capacitor when the hold-up capacitor has failed.
[0028] The controller 202 may be configured to control a non-volatile memory (e.g., flash memory 103) and communicate with a host. The controller 202 may be configured to obtain a status of an interface (e.g., a general purpose I / O interface, interfaces 218-2, 218-4) coupled to the plurality of circuit components. The controller 202 may also be configured to determine a status of the plurality of circuit components based on the status of the interface. The controller 202 may be configured to execute a corrective action for the data storage device according to a determination that the status of the plurality of circuit components corresponds to one or more failed hold-up capacitors.
[0029] In some aspects, each detection and isolation circuit may be configured to detect that its hold-up capacitor is faulty and to isolate the faulty hold-up capacitor without receiving any commands from a host or controller (e.g., independent of the host and controller) to detect or isolate the faulty hold-up capacitor. In some aspects, the detection and isolation circuit may be configured to perform any of these steps in real time without being repeated with any periodicity, with a predetermined delay scheme, and / or automatically without any software or firmware instructions.
[0030] In some aspects, each detection and isolation circuit may include a sense circuit (e.g., 212-2, 210-2 and 212-2, 212-4, or 210-4 and 212-4) configured to detect if a hold-up capacitor (e.g., C1 206-2 or C2 206-4) has failed and generate an output based on detecting if the hold-up capacitor has failed. The detection and isolation circuit may also include a comparator circuit (e.g., 216-2 or 216-4) coupled to the sense circuit and configured to receive an output of the sense circuit, compare the output of the sense circuit to a trigger threshold, and generate an output of the comparator circuit based on comparing the output of the sense circuit to the trigger threshold. For example, the trigger threshold may be lower than the operating voltage range. If the expected voltage range is X volts + / - 5%, the threshold may be less than the X-5% level. The value of X may be based on an expected current, where the current is based on an expected capacitance. The detection and isolation circuit may also include a switch circuit (e.g., 208-2 or 208-4) coupled to the comparator circuit and the hold-up capacitor and configured to be turned on or off based on the output of the comparator circuit. In some aspects, if a short circuit fault or defect occurs in the hold-up capacitor, the sense circuit detects that the hold-up capacitor has failed.
[0031] In some aspects, the sensing circuit may include a current sensing component. For example, the current sensing component may include a resistor (e.g., R1 210-2 or R2 210-4) connected to a current sensor (e.g., 212-2 or 212-4). The current sensing component (e.g., R1 210-2 or R2 210-4) may be connected in series with a corresponding hold-up capacitor (e.g., C1 206-2 or C2 206-4). For example, a capacitor (e.g., 206-2) is connected to a current sensing component (e.g., R1 210-2) coupled to a current sensor (e.g., 212-2). In a further example, a capacitor (e.g., 206-4) is connected to a current sensing component (e.g., R2 210-4) coupled to a current sensor (e.g., 212-4).
[0032] In some aspects, if a short circuit fault occurs in the hold-up capacitor, the current flowing through the current sense component is greater than a threshold current value, which causes the output of the sense circuit (e.g., 212-2 or 212-4) to be greater than a trigger threshold, and the output of the sense circuit causes the output of the comparator circuit (e.g., 216-2 or 216-4) to turn off a switch circuit (e.g., 208-2 or 2084), which in turn isolates the hold-up capacitor (e.g., C1 206-2 or C2 206-4).
[0033] In some aspects, the switch circuit is coupled between the hold-up capacitor and the ground node. For example, in the example circuit shown in FIG. 2B, switch 208-2 is coupled between capacitor 206-2 and ground node 214-2, and switch 208-4 is coupled between capacitor 206-4 and ground node 214-4. The ground node may be referred to as a low power supply node or a first power supply node. The ground node may be configured to be connected to a ground, a low power supply voltage, or a first end of a power supply.
[0034] When the output of the sense circuit is greater than the trigger threshold, the output of the comparator circuit causes the switch circuit to turn off. When the switch circuit is turned off, the hold-up capacitor is disconnected from the ground node. In some aspects, when the output of the sense circuit is less than the trigger threshold, the output of the comparator circuit causes the switch circuit to remain on. When the switch circuit remains on, the hold-up capacitor is not isolated and is coupled to the ground node through the switch circuit.
[0035] In some aspects, multiple circuit components may be connected in parallel and the hold-up capacitors of multiple circuit components may be connected in parallel.
[0036] In some aspects, the detection and isolation circuitry comprises a current sense circuit (e.g., 212-2, or 210-2 and 212-2) coupled to a hold-up capacitor (e.g., capacitor 206-2), a voltage comparator circuit (e.g., voltage comparator 216-2) coupled to the current sense circuit, and a switch circuit (e.g., switch 208-2) connected to the voltage comparator circuit and the hold-up capacitor. If the hold-up capacitor does not fail, the output of the current sense circuit is below a trigger threshold of the voltage comparator circuit, and the output of the voltage comparator circuit allows the switch circuit to remain in the on position. If a short circuit fault occurs in the hold-up capacitor, the current flowing through the current sense circuit (or at least a portion of the current sense circuit) is greater than a threshold current value, and the output of the current sense circuit is greater than a trigger threshold of the voltage comparator circuit, and the output of the voltage comparator circuit allows the switch circuit to turn off, further isolating the hold-up capacitor.
[0037] In some aspects, the current sense circuit comprises a current sense resistor (e.g., resistor 210-2) and a current sensor (e.g., current sensor 212-2). A first end of the current sense resistor may be connected in series with a hold-up capacitor (e.g., one end of resistor 210-2 is connected in series with capacitor 206-2). A second end of the current sense resistor may be connected to a power supply node (e.g., 213-2), and the current sensor may be connected in parallel with the current sense resistor (e.g., resistor 210-2 is connected in parallel with current sensor 212-2). A first node of the current sensor may be coupled to a first end of the current sense resistor, and a second node of the current sensor may be coupled to a second end of the current sense resistor. For example, for current sensor 212-2, a node labeled +in is connected to one end of resistor 210-2, and a node labeled -in is connected to the other end of resistor 210-2. The power supply node (e.g., 213-2 or 213-4) may be referred to as a high power supply node or a second power supply node. The power supply node may be configured to be connected to a high power supply voltage or a second end of a power supply.
[0038] In some aspects, the data storage device may further comprise a host interface (e.g., interface 105) for coupling the data storage device to a host (e.g., host 104). The controller 202 may be configured to communicate the status of the plurality of circuit components to the host using the host interface.
[0039] 2C illustrates a second example of electronic components, including an exemplary circuit 204, that may be used to detect and isolate any failed capacitors in a power bank used to provide backup power to a data storage device, according to one or more embodiments. Some of the components illustrated in FIG. 2C (e.g., 204 and 202) may be the same or substantially the same as components illustrated in FIG. 2B having the same element numbers, and therefore, for the sake of brevity, repeated descriptions thereof may be omitted.
[0040] In the example shown in FIG. 2C, the data storage device (e.g., data storage device 100 or enterprise solid-state drive) may further include a digital I / O expander 220 coupled between the plurality of circuit components and the controller 202. The digital I / O expander may be configured to generate an interrupt (asynchronous signal) (e.g., shown as an input change notification interrupt 222) to the controller 202 when a status of one of the plurality of circuit components changes. The controller 202 may be configured to check a status of an interface between the digital I / O expander 220 and the controller 202 to determine which hold-up capacitor has failed. In some aspects, the interface may include I / O nodes, and the controller 202 may be configured to store the status of the hold-up capacitors and compare the status of the I / O nodes to the stored status. Each of the statuses of the hold-up capacitors may correspond to a respective one of the hold-up capacitors. Each of the statuses of the I / O nodes may correspond to a respective one of the I / O nodes.
[0041] 2B and 2C, in some aspects, the circuit components may be configured to have a number of hold-up capacitors based on at least one of the capacity of the data storage device and the type of the data storage device. For example, a Triple-Level Cell (TLC) or Quad-Level Cell (QLC) data storage device may have a capacity of 1 Terabyte (TB), 2 TB, 4 TB, 8 TB, 16 TB, or 32 TB, and the number of hold-up capacitors may be determined based on the capacity and / or type of the data storage device (e.g., TLC vs. QLC). The storage memory type, including the data path design, may dictate how much energy is needed to ensure that in-flight data and other vulnerable data (including control information) are protected.
[0042] In some aspects, the corrective action may include ceasing to receive write commands (e.g., ceasing processing of future commands but completing in-progress write commands) but continuing to receive read commands from the host. Exemplary write commands include any type of Non-Volatile Memory express (NVMe) write protocol command, such as an NVMe Write command, an NVMe Write Zero command, or an NVMe Fuse command.
[0043] 2B and 2C, the capacitors (e.g., C1 206-2 and C2 206-4) may be connected in parallel. The current sense components (e.g., R1 210-2 and R2 210-4) may be precision current sense resistors. The output of the current sense circuit, which includes the resistors and the current sensors (e.g., 210-2 and 212-2, or 210-4 and 212-4), may be connected to a voltage comparator (e.g., 216-2 or 216-4). The output of the voltage comparator may be connected to a switch (e.g., 208-2 or 208-4) connected in series with the capacitors (e.g., C1 206-2 or C2 206-4). When the capacitors (e.g., C1 206-2 or C2 206-4) are healthy and operating properly, the output of the current sense circuit may be below the trigger threshold of the voltage comparator. Therefore, the output of the voltage comparator is high and the switch remains in the on position. If a short circuit fault occurs in the capacitor, a large current may flow through the current sense circuit. The output of the current sense circuit may be higher than the trigger threshold of the voltage comparator. Therefore, the output of the voltage comparator is low and the switch is turned off. In this way, the faulty capacitor may be isolated.
[0044] In some aspects, the output of the voltage comparator may be connected to a General Purpose Input / Output (GPIO) pin of the controller 202. Firmware running on the controller may read the status of these GPIO pins and determine the status of the health of the capacitor banks (e.g., 206-2 and 206-4). If a failed capacitor is detected, the firmware may report the status of the data storage device to the host for appropriate action to be taken. In conventional systems, if capacitor health checks are not performed frequently, there may be a long period of delay before a failed capacitor is detected. The firmware may detect a problem with the capacitor bank. However, if the delay is long, the data storage device may lose power due to lack of sufficient capacity. This may lead to loss of user data and, in some cases, the data storage device may not function even after power-up. The techniques and circuits described above may be used to address one or more of such issues.
[0045] It may be beneficial to explain the structures shown in FIGS. 1, 2B, and 2C with respect to FIG. 3, which is a flowchart illustrating an exemplary process 300 for detecting and isolating a failed hold-up capacitor using hardware circuitry in a data storage device, in accordance with one or more embodiments.
[0046] 1, 2B, 2C, and 3, a data storage system device (e.g., data storage device 100) may include a non-volatile memory (e.g., flash memory 103), a controller (e.g., controller 202), and hardware circuits (e.g., 204 including 204-2 and 204-4) coupled to the non-volatile memory and the controller. The hardware circuits are configured to provide backup power to the data storage device, which may include the non-volatile memory and the controller. (See process 302). The hardware circuits may also be configured to detect and isolate failed hold-up capacitor(s) used to provide the backup power. (See process 304). Examples of hardware circuits are described above with reference to FIGS. 2B and 2C, in accordance with one or more embodiments. Process 300 may also include obtaining, by or for a controller (e.g., 202, 101, or 107), a status of an interface coupled to the hardware circuit (see process 306), determining a status of the hardware circuit based on the status of the interface (see process 308), and performing corrective action for the data storage device in accordance with a determination that the status of the hardware circuit corresponds to one or more failed hold-up capacitors (see process 310).
[0047] 3 may be implemented in hardware, e.g., performed in or by hardware circuitry (e.g., 204, 204-2, 204-4 or components thereof). In one or more examples, process 302 may be performed in or by hardware hold-up capacitors (e.g., 206-2 and 206-4), for example. In one or more examples, process 304 may be performed in or by detection and isolation circuitry (e.g., 210-2, 208-2, 212-2 and 216-2, or 210-4, 208-4, 212-4 and 216-4), for example.
[0048] In one or more aspects, process 302 is performed without the use of a host (e.g., 104) or controller (e.g., 202, 101, or 107), without intervention or interruption by a host (e.g., 104) or controller (e.g., 202, 101, or 107), independently of a host (e.g., 104), and / or independently of a controller (e.g., 202, 101, or 107). In one or more aspects, process 302 is performed without the use of software, firmware, or instructions. In one or more aspects, process 302 is performed solely by hardware. In one or more aspects, process 302 is performed without receiving instructions or commands. In one or more aspects, process 302 is performed without a delay or wait period.
[0049] In one or more aspects, process 304 is performed without the use of a host (e.g., 104) or controller (e.g., 202, 101, or 107), without intervention or interruption by a host (e.g., 104) or controller (e.g., 202, 101, or 107), independently of a host (e.g., 104), and / or independently of a controller (e.g., 202, 101, or 107). In one or more aspects, process 304 is performed without the use of software, firmware, or instructions. In one or more aspects, process 304 is performed solely by hardware. In one or more aspects, process 304 is performed without receiving instructions or commands. In one or more aspects, process 304 is performed without a delay or wait period.
[0050] A controller (e.g., 202, 101, and / or 107) may execute some of the processes 300 (e.g., 306, 308, and 310) of Figure 3. The controller (e.g., 202, 101, and / or 107) may generate some of the processes 300 (e.g., 306, 308, and 310), or the controller (e.g., 202, 101, and / or 107) may provide instructions to the controller 107 (and registers 106) that cause or facilitate some of the processes 300 (e.g., 306, 308, and 310).
[0051] A non-transitory machine-readable medium (e.g., memory in 102, 106, or 101) may contain machine-executable instructions that, when executed by a computer, machine, or processor (e.g., 202, 101, or 107), perform some of the processes (e.g., 306, 308, and 310) of Figure 3. Some of the processes 300 (e.g., 306, 308, and 310) may be implemented as hardware, firmware, software, or a combination thereof.
[0052] 2B and 2C, the hardware circuit (e.g., 204) comprises two circuit components (e.g., 204-2 and 204-4). Note that in other examples, the hardware circuit may comprise one circuit component rather than two. In yet other examples, the hardware circuit may comprise three or more circuit components.
[0053] In one example, a hardware circuit (eg, 204) is implemented using only hardware components without the use of firmware or software.
[0054] Various examples of aspects of the present disclosure are described below, which are provided as examples and not as limitations of the subject technology.
[0055] One or more aspects of the subject technology provide a data storage device that may include a non-volatile memory configured to store data, a hardware circuit, and a controller. The hardware circuit may be coupled to the controller and configured to provide backup power to the non-volatile memory and the controller. The hardware circuit may include a plurality of circuit components. Each of the plurality of circuit components may include a hold-up capacitor and a detection and isolation circuit that may be configured to detect whether the hold-up capacitor has failed and to isolate the hold-up capacitor when the hold-up capacitor has failed. The controller may be configured to control the non-volatile memory and to communicate with a host. The controller may be configured to obtain a status of an interface coupled to the plurality of circuit components, determine a status of the plurality of circuit components based on the status of the interface, and perform a corrective action for the data storage device according to a determination that the status of the plurality of circuit components corresponds to one or more failed hold-up capacitors.
[0056] In another aspect, a method is provided for detecting and isolating a failed hold-up capacitor in a data storage device. According to some aspects, the method may be performed using one or more hardware circuits and / or controllers for one or more data storage devices. The method may include, in a hardware circuit coupled to the controller and the non-volatile memory, providing backup power for the non-volatile memory and the controller, detecting whether a hold-up capacitor of the hardware circuit has failed, and isolating the hold-up capacitor if the hold-up capacitor has failed. The method may include, in the controller, obtaining a status of an interface coupled to the hardware circuit, determining a status of the hardware circuit based on the status of the interface, and performing a corrective action for the data storage device according to a determination that the status of the hardware circuit corresponds to one or more failed hold-up capacitors.
[0057] In a further aspect, the system may include first means for (i) providing backup power for the non-volatile memory and detecting and (ii) isolating a failed hold-up capacitor; second means for obtaining a status of an interface coupled to the first means; third means for determining a status of the first means based on the status of the interface; and fourth means for performing corrective action in accordance with a determination that the status of the first means corresponds to one or more failed hold-up capacitors.
[0058] A system and method for detecting and isolating a failed hold-up capacitor in a data storage device is disclosed. The described method and system thus provide performance benefits that improve the functionality of the storage device.
[0059] It is understood that other configurations of the subject technology will be readily apparent to those skilled in the art from the detailed description herein, in which various configurations of the subject technology are shown and described by way of illustration. As will be understood, the subject technology is capable of other different configurations, and its several details are capable of modification in various other respects, all without departing from the scope of the subject technology. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature, and not as restrictive.
[0060] Those skilled in the art will appreciate that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein may be implemented as electronic hardware, computer software, or a combination of both. To illustrate this interchangeability of hardware and software, the various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application. The various components and blocks may be arranged differently (e.g., arranged in a different order or partitioned in a different way), all without departing from the scope of the subject technology.
[0061] It is understood that the specific order or hierarchy of steps in the processes disclosed is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sample order, and are not intended to be limited to the specific order or hierarchy presented.
[0062] The foregoing description is provided to enable those skilled in the art to practice the various aspects described herein. The foregoing description provides various examples of the subject technology, and the subject technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects set forth herein, but are to be accorded the full scope consistent with the language of the claims, and references to elements in the singular do not mean "only one" unless specifically so stated, but rather "one or more." The term "some" refers to one or more, unless otherwise specified. Includes masculine pronouns (e.g., his), feminine and neuter (e.g., her and its), and vice versa. Headings and subheadings, if any, are used for convenience only and are not intended to limit the subject technology.
[0063] A phrase such as "aspect" does not imply that such aspect is essential to the subject technology or that such aspect applies to all configurations of the subject technology. A disclosure of an aspect may apply to all configurations, or one or more configurations. An aspect may provide one or more examples. A phrase such as an aspect may refer to one or more aspects, and vice versa. A phrase such as "embodiment" does not imply that such embodiment is essential to the subject technology or that such embodiment applies to all configurations of the subject technology. A disclosure of an embodiment may apply to all embodiments, or one or more embodiments. An embodiment may provide one or more examples. A phrase such as "embodiment" may refer to one or more embodiments, and vice versa. A phrase such as "configuration" does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology. A disclosure of an embodiment may apply to all configurations, or one or more configurations. An embodiment may provide one or more examples. A phrase such as "configuration" may refer to one or more configurations, and vice versa.
[0064] The word "exemplary" is used herein to mean "serving as an example or illustration." Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs.
[0065] The phrase "a first element," "a second element," and / or "a third element" should be understood as one of the first, second, and third elements, or a combination of any or all of the first, second, and third elements. As an example, A, B, and / or C can refer to A only, B only, C only, any or some combination of A, B, and C, or all of A, B, and C.
[0066] The term "at least one" should be understood to include any and all combinations of one or more of the associated listed items. For example, "at least one of the first, second, and third items" means not only any one of the first, second, or third items, but also any combination of two or more of the first, second, and third items.
[0067] When an element is "connected" or "coupled" to another element, the element may be directly connected or coupled to the other element, or, unless otherwise specified, indirectly connected or coupled to the other element through one or more intervening elements disposed or interposed between the elements.
[0068] All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or that later become known to those skilled in the art are intended to be expressly incorporated herein by reference and encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. Unless an element is expressly recited using the phrase "means for" or, in the case of a method claim, an element is recited using the phrase "step for", that element is not to be construed under the provisions of 35 USC § 112, sixth paragraph. Moreover, to the extent that terms such as "include", "have", and the like are used in this specification or in the claims, such terms are intended to be inclusive in the same manner as "comprise" is construed when "comprise" is used as a transitional phrase in the claims.
Claims
1. a non-volatile memory configured to store data; a hardware circuit coupled to a controller and configured to provide backup power to the non-volatile memory and the controller, the hardware circuit comprising a plurality of circuit components, each of the plurality of circuit components comprising: A hold-up capacitor; a detection and isolation circuit configured to detect whether the hold-up capacitor has failed and configured to isolate the hold-up capacitor when the hold-up capacitor has failed; The controller is configured to control the non-volatile memory and to communicate with a host, the controller comprising: Obtaining a status of an interface coupled to the plurality of circuit components; determining a status of the plurality of circuit components based on the status of the interface; and executing a corrective action for the data storage device in accordance with a determination that the status of the plurality of circuit components corresponds to one or more failed hold-up capacitors.
2. 2. The data storage device of claim 1, wherein the detection and isolation circuitry is configured to detect that the hold-up capacitor has failed and to isolate the failed hold-up capacitor without receiving any command from the host or the controller to detect or isolate the failed hold-up capacitor.
3. The detection and isolation circuitry includes: a sensing circuit configured to detect whether the hold-up capacitor has failed and to generate an output based on detecting whether the hold-up capacitor has failed; a comparator circuit coupled to the sensing circuit, the comparator circuit configured to receive the output of the sensing circuit, compare the output of the sensing circuit to a trigger threshold, and generate an output of the comparator circuit based on comparing the output of the sensing circuit to the trigger threshold; 2. The data storage device of claim 1, further comprising: a switch circuit coupled to the comparator circuit and the hold-up capacitor, the switch circuit configured to be turned on or off based on the output of the comparator circuit.
4. The data storage device of claim 3 , wherein the sense circuit is configured to detect that the hold-up capacitor has failed when a short circuit fault occurs in the hold-up capacitor.
5. the sensing circuit comprises a current sensing component; the current sensing component is connected in series with the hold-up capacitor; 4. The data storage device of claim 3, wherein when a short circuit fault occurs in the hold-up capacitor, a current flowing through the current sensing component is greater than a threshold current value, which causes the output of the sensing circuit to be greater than the trigger threshold, which causes the output of the sensing circuit to turn off the switch circuit, and the turned-off switch circuit isolates the hold-up capacitor.
6. the switch circuit is coupled between the hold-up capacitor and a first power supply node; when the output of the sense circuit is greater than the trigger threshold, the output of the comparator circuit causes the switch circuit to turn off; 4. The data storage device of claim 3, wherein when the switch circuit is turned off, the hold-up capacitor is disconnected from the first power supply node.
7. the switch circuit is coupled between the hold-up capacitor and a first power supply node; when the output of the sense circuit is less than the trigger threshold, the output of the comparator circuit causes the switch circuit to remain on; 4. The data storage device of claim 3, wherein when said switch circuit remains on, said hold-up capacitor is not isolated but is coupled to said first power supply node through said switch circuit.
8. the plurality of circuit components are connected in parallel; The data storage device of claim 1 , wherein the hold-up capacitors of the plurality of circuit components are connected in parallel.
9. The detection and isolation circuitry includes: a current sense circuit coupled to the hold-up capacitor; a voltage comparator circuit coupled to the current sensing circuit; 2. The data storage device of claim 1, further comprising: a switch circuit connected to said voltage comparator circuit and said hold-up capacitor.
10. when the hold-up capacitor has not failed, an output of the current sense circuit is below a trigger threshold of the voltage comparator circuit, and the output of the voltage comparator circuit allows the switch circuit to remain in an on position; 10. The data storage device of claim 9, wherein when a short circuit fault occurs in the hold-up capacitor, the current through the current sense circuit is greater than a threshold current value, causing the output of the current sense circuit to be greater than the trigger threshold of the voltage comparator circuit, and causing the output of the voltage comparator circuit to turn off the switch circuit, isolating the hold-up capacitor.
11. the current sensing circuit comprises a current sensing resistor and a current sensor; a first end of the current sense resistor connected in series with the hold-up capacitor; a second end of the current sense resistor coupled to a second power supply node; 10. The data storage device of claim 9, wherein the current sensor is connected in parallel to the current sensing resistor, a first node of the current sensor being coupled to the first end of the current sensing resistor, and a second node of the current sensor being coupled to the second end of the current sensing resistor.
12. a host interface for coupling the data storage device to the host; 2. The data storage device of claim 1, wherein the controller configured to perform the corrective action comprises the controller configured to communicate the status of the plurality of circuit components to the host using the host interface.
13. 2. The data storage device of claim 1, further comprising: a digital I / O expander connected between the plurality of circuit components and the controller, the digital I / O expander configured to generate an interrupt to the controller when a status of one of the plurality of circuit components changes, and the controller configured to check a status of an interface between the digital I / O expander and the controller to determine which of the hold-up capacitors has failed.
14. the interface comprises an I / O node; the controller is configured to store a status of the hold-up capacitor and compare a status of the I / O node to the stored status; each of the states of the hold-up capacitors corresponds to a respective one of the hold-up capacitors; 14. The data storage device of claim 13, wherein each of the statuses of the I / O nodes corresponds to a respective one of the I / O nodes.
15. The data storage device of claim 1 , wherein the plurality of circuit components are configured to have a number of hold-up capacitors based on at least one of a capacity of the data storage device and a type of the data storage device.
16. The data storage device of claim 1 , wherein the corrective action comprises stopping receiving write commands from the host but continuing to receive read commands.
17. 1. A method for detecting and isolating a failed hold-up capacitor in a data storage device, comprising: a hardware circuit coupled to the controller and the non-volatile memory, providing backup power to the non-volatile memory and the controller; Detecting whether a hold-up capacitor of the hardware circuit has failed, and isolating the hold-up capacitor if the hold-up capacitor has failed; In the controller, obtaining a status of an interface coupled to the hardware circuit; determining a status of the hardware circuit based on the status of the interface; and performing corrective action for the data storage device in accordance with a determination that the status of the hardware circuitry corresponds to one or more failed hold-up capacitors.
18. 20. The method of claim 17, wherein the hardware circuitry detects that the hold-up capacitor has failed and isolates the failed hold-up capacitor without receiving any command from the controller or a host coupled to the data storage device.
19. 20. The method of claim 17, wherein the corrective action comprises stopping receiving write commands from a host coupled to the data storage device, but continuing to receive read commands.
20. a first means for providing backup power for the non-volatile memory and for detecting and isolating a failed hold-up capacitor; second means for obtaining a status of an interface coupled to the first means; third means for determining a status of the first means based on the status of the interface; and fourth means for implementing corrective action in accordance with a determination that the status of the first means corresponds to one or more failed hold-up capacitors.
Citation Information
Patent Citations
Storage device including protection circuit for secondary power source and method of controlling secondary power source
KR102374076B1
Method of managing power and performance of an electronic device including a plurality of capacitors for supplying auxiliary power
US20180059761A1
Fault tolerance for power loss imminent circuitry failure
US20190041938A1
