# US 2022/0019443 A1 · Parallel Boot Execution Of Memory Devices

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0019443 A1
- Document ID: US20220019443A1
- Status: Published application
- Kind: A1
- Application number: 16/932,477
- Filed: 2020-07-17
- Published: 2022-01-20
- Earliest claimed: 2020-07-17
- Assignees: Western Digital Technologies, Inc.
- Applicants: Western Digital Technologies, Inc.
- Inventors: Shay BENISTY; Judah Gamliel HAHN; Ariel NAVON
- Web page: https://patentgrep.com/patent/US20220019443A1

## CPC

- G06F 9/4403: {Processor initialisation}
- G06F 3/0611: {in relation to response time}
- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/0673: {Single storage device}
- G06F 9/4408: {Boot device selection}
- G06F 21/575: {Secure boot}
- G06F 9/445: Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57)
- G06F 2221/033: Test or assess software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present disclosure generally relates to reducing boot latency of memory devices in a dual boot system. The boot code is loaded to the data storage device controller in a flexible manner by being able to receive chunks of the boot code from two separate locations, the host memory buffer (HMB) and the memory device, which may be a NAND device. Part of the boot code may be received from the HMB and another part of the boot code may be received from the memory device. If either the HMB or the memory device can deliver the chunks faster than the other, then the controller can receive the chunks from the faster location and periodically confirm the speed of delivery to ensure the boot code latency is optimized.

## Claims

### Claim 1

A data storage device, comprising:
one or more memory devices; and
a controller coupled to the one or more memory devices, wherein the controller is configured to:
receive boot code chunks of a boot code from a host device; and
receive boot code chunks of the boot code from the one or more memory devices.

### Claim 2 (depends on 1)

The data storage device of claim 1, wherein the boot code includes 20 chunks of a predetermined size.

### Claim 3 (depends on 1)

The data storage device of claim 1, wherein the boot code chunks received from the host device are for a first half of the boot code and wherein the boot code chunks received from the one or more memory devices is for a second half of the boot code.

### Claim 4 (depends on 1)

The data storage device of claim 1, wherein a number of boot code chunks received from the host device is different from a number of boot code chunks received from the one or more memory devices.

### Claim 5 (depends on 1)

The data storage device of claim 1, wherein each boot code chunk received has an authentication signature and wherein the controller is configured to determine whether each boot code chunk has a valid authentication signature.

### Claim 6 (depends on 5)

The data storage device of claim 5, wherein, upon determining an authentication signature is invalid for a specific boot code chunk, the controller is configured to receive the specific boot code chunk from the other of either the host device or the one or more memory devices that sent the invalid specific boot code chunk.

### Claim 7 (depends on 5)

The data storage device of claim 5, wherein the controller is configured to determine whether each boot code chunk has a valid authentication signature after loading each boot code chunk.

### Claim 8

A data storage device, comprising:
one or more memory devices; and
a controller coupled to the one or more memory devices, wherein the controller is configured to:
receive boot code chunks of a boot code from both a host device and the one or more memory devices;
confirm that all boot code chunks have been received;
confirm authentication signatures for the boot code;
determine whether a boot code chunk was invalid;
determine whether the invalid boot code chunk was from the host device or the one or more memory devices; and
receive a valid boot code chunk from whichever of the host device and the one or more memory device did not deliver the invalid boot code chunk.

### Claim 9 (depends on 8)

The data storage device of claim 8, wherein the controller is configured to receive multiple copies of one or more boot chunks.

### Claim 10 (depends on 8)

The data storage device of claim 8, wherein the controller is configured to track a number of boot code chunks received on average from both the one or more memory devices and the host device.

### Claim 11 (depends on 10)

The data storage device of claim 10, wherein one additional boot code chunk greater than the average is placed is each of the host device and the one or more memory devices.

### Claim 12 (depends on 8)

The data storage device of claim 8, wherein the controller receives the boot code chunks from the host device and the one or more memory devices in a different order.

### Claim 13 (depends on 8)

The data storage device of claim 8, wherein the controller receives more than half of the boot code chunks from either the host device or the one or more memory devices.

### Claim 14 (depends on 8)

The data storage device of claim 8, wherein the authentication signatures for the boot code are received from both the host device and the one or more memory devices.

### Claim 15

A data storage device, comprising:
one or more memory devices; and
a controller coupled to the one or more memory devices, wherein the controller is configured to:
receive boot code chunks of a boot code from either the one or more memory devices or a host device;
after a predetermined number of data storage device boots, receive boot data chunks from the other of the one or more memory devices or the host device; and
determine whether an average latency for receiving the boot code from the one or more memory devices is different from the average latency for receiving the boot code from the host device.

### Claim 16 (depends on 15)

The data storage device of claim 15, wherein the controller is further configured to receive the boot code chunks from the one or more memory devices and switch to receiving the boot code chunks from the host device.

### Claim 17 (depends on 15)

The data storage device of claim 15, wherein the controller is further configured to receive the boot code chunks from the host device and switch to receiving the boot code chunks from the one or more memory devices.

### Claim 18 (depends on 15)

The data storage device of claim 15, wherein the controller is configured to calculate the average latency for receiving the boot codes for both the one or more memory devices and the host device.

### Claim 19 (depends on 15)

The data storage device of claim 15, wherein the controller is configured to increase an internal counter each time a boot occurs until the predetermined number of data storage device boots has occurred.

### Claim 20 (depends on 15)

The data storage device of claim 15, wherein the controller includes boot logic that processes both the one or more memory device boot code chunks and the host device boot code chunks.
