Abstract: A data storage device includes a host interface for coupling the data storage device to a host system. The data storage device also includes a device memory for storing or providing data in response to commands receive from the host system. The data storage device also includes a controller comprising a storage subsystem and a security subsystem. The storage subsystem is configured to receive a host command from the host interface, and process the host command for the device memory. The security subsystem includes a device recovery circuit configured to monitor the storage subsystem for an exception state, and reinitialize pending operations for the storage subsystem after the exception state. Methods and systems are also disclosed.

Abstract: A data storage device includes interfaces for coupling the data storage device to a host system and a server system. The data storage device also includes a device memory for storing or providing data. The data storage device also includes a controller comprising a storage subsystem and a security subsystem. The storage subsystem is configured to receive a host command, receive a probe request for an exception state, generate and transmit, to the security subsystem, a report for the exception state. In response to receiving an update from the security subsystem, the storage subsystem restarts at least a portion of the controller. The security subsystem is configured to monitor and transmit a probe request to the storage subsystem, transmit the report to the server system, receive the update from the server system, and transmit the update to the storage subsystem. Methods and systems are also disclosed.

Abstract: Storage devices may be utilized in external devices that communicate with host computing devices over various communication ports and protocols. Traditionally, storage devices utilize boot loading data, such as boot ROMS, to start normal operations of the device. However, many storage devices are unable to change or update boot loading data once the device has been manufactured or deployed. Thus, methods, systems, and devices described herein decouple the boot loading process from the storage device and load boot loading data from an external device. The boot loading data can be loaded via a wireless communication connection from an external device, where it can be updated as needed. Once loaded, the bootloader can begin the process of loading firmware and starting the normal operation of the drive over regular wired communication ports. When the boot loading data or firmware cannot be loaded externally, traditional booting methods can be used utilizing previously stored copies of the required data.

Abstract: A memory device operable in either of a Secure Digital operational mode and an NVMe operational mode includes password conversion logic to enable the memory device user-mode memory blocks to be accessed in the NVMe operational mode after the memory device was locked in the Secure Digital operational mode.

Abstract: A memory device operable in either of a Secure Digital operational mode and an NVMe operational mode includes password conversion logic to enable the memory device user-mode memory blocks to be accessed in the NVMe operational mode after the memory device was locked in the Secure Digital operational mode.

Abstract: The present disclosure describes technologies and techniques for use by a data storage controller—such as a controller for use with a NAND or other non-volatile memory (NVM)—to store crash-dump information in a boot partition following a system crash within the data storage controller. Within illustrative examples described herein, the boot partition may be read by a host device without the host first re-installing valid firmware into the data storage controller following the system crash. In the illustrative examples, the data storage controller is configured for use with versions of Peripheral Component Interconnect (PCI) Express—Non-Volatile Memory express (NVMe) that provide support for boot partitions in the NVM. The illustrative examples additionally describe virtual boot partitions in random access memory (RAM) for storing crash-dump information if the NAND has been corrupted, where the crash-dump information is retrieved from the RAM without power-cycling the RAM.

Abstract: The present disclosure describes technologies and techniques for use by a data storage controller—such as a controller for use with a NAND device or other non-volatile memory (NVM)—to retrieve configuration information from a NAND boot partition during an initialization procedure initiated by a host. Within illustrative examples described herein, the configuration information stored in the NAND boot partition is provided in addition to configuration information stored within physical layer register sets of the data storage controller. In the examples, the data storage controller is configured for use with versions of Peripheral Component Interconnect (PCI) Express—Non-Volatile Memory express (NVMe) that provide support for NAND boot partitions. In these examples, the use of the NAND boot partition allows an NVM device manufacturer to implement at least some new features in firmware or software within an existing NVM card, without modifying the physical layer registers.

Abstract: A method and apparatus for managing storage devices includes a host interface, a plurality of storage device interfaces, and a processor. The host interface is configured to communicatively couple with a host device and the plurality of storage interfaces configured to communicatively couple with storage devices. The processor is communicatively coupled to the host interface and the plurality of storage device interfaces. Further, the processor is configured to receive requests from the host device via the host interface and communicate the requests to the storage devices via the plurality of storage device interfaces. The processor is additionally configured to receive responses from the storage devices via the plurality of storage interfaces and communicate the responses to the host device via the host interface, manage a global submission queue and a global completion queue, and manage a submission queue and a completion queue for each of the storage devices.

Abstract: A method and apparatus for managing storage devices includes a host interface, a plurality of storage device interfaces, and a processor. The host interface is configured to communicatively couple with a host device and the plurality of storage interfaces configured to communicatively couple with storage devices. The processor is communicatively coupled to the host interface and the plurality of storage device interfaces. Further, the processor is configured to receive requests from the host device via the host interface and communicate the requests to the storage devices via the plurality of storage device interfaces. The processor is additionally configured to receive responses from the storage devices via the plurality of storage interfaces and communicate the responses to the host device via the host interface, manage a global submission queue and a global completion queue, and manage a submission queue and a completion queue for each of the storage devices.

Abstract: The present disclosure describes technologies and techniques for use by a data storage controller—such as a controller for use with a NAND device or other non-volatile memory (NVM)—to retrieve configuration information from a NAND boot partition during an initialization procedure initiated by a host. Within illustrative examples described herein, the configuration information stored in the NAND boot partition is provided in addition to configuration information stored within physical layer register sets of the data storage controller. In the examples, the data storage controller is configured for use with versions of Peripheral Component Interconnect (PCI) Express—Non-Volatile Memory express (NVMe) that provide support for NAND boot partitions. In these examples, the use of the NAND boot partition allows an NVM device manufacturer to implement at least some new features in firmware or software within an existing NVM card, without modifying the physical layer registers.

Abstract: The present disclosure describes technologies and techniques for use by a data storage controller—such as a controller for use with a NAND or other non-volatile memory (NVM)—to store crash-dump information in a boot partition following a system crash within the data storage controller. Within illustrative examples described herein, the boot partition may be read by a host device without the host first re-installing valid firmware into the data storage controller following the system crash. In the illustrative examples, the data storage controller is configured for use with versions of Peripheral Component Interconnect (PCI) Express—Non-Volatile Memory express (NVMe) that provide support for boot partitions in the NVM. The illustrative examples additionally describe virtual boot partitions in random access memory (RAM) for storing crash-dump information if the NAND has been corrupted, where the crash-dump information is retrieved from the RAM without power-cycling the RAM.