Memory programming providing corruption protection

• US 9,971,659 B1
• Filed: 06/24/2015
• Issued: 05/15/2018
• Est. Priority Date: 06/24/2015
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: Western Digital Technologies Incorporated (Western Digital Corporation)
• Inventors: McCabe, Timothy J., Barnes, Edwin D., Webster, Michael W., Bricketto, Paul, Kwong, Hee, Tam, Karman, Klett, Michael F., Lin, Tino, Nguyen, Mark, Quan, John Minh Hon
• Primary Examiner(s): McCarthy, Christopher
• Application Number:
  US14/748,616
• Time in Patent Office: 1,056 Days
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 11/1441 Resetting or repowering
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57

Abstract

Systems and methods are disclosed for programming non-volatile storage. Methods involve identifying boot loader code stored in a first partition of a non-volatile storage, the boot loader code being marked as active, executing the boot loader code using one or more processors of the computing system, loading a firmware image to a second partition of the non-volatile storage, the second partition being separate from the first partition, and marking the firmware image as active. Methods further involve detecting a power loss event and, following a power cycle, determining that the firmware image is stored in the second partition and has been marked as active, and, in response to said determination, making a copy of the firmware image and storing the copy in the first partition.

Claims

1. A method of programming firmware in a computing system, the method comprising:

loading boot loader code to a first partition of a non-volatile storage, the boot loader code comprising instructions for loading a firmware image that is separate from the boot loader code to the non-volatile storage;

marking the boot loader code as active;

in response to a system start-up, executing the boot loader code using one or more processors of the computing system; and

as directed by the boot loader code;

loading the firmware image from a location separate from the non-volatile storage to a second partition of the non-volatile storage, the second partition being separate from the first partition;

marking the firmware image as active;

following a power cycle, determining that the firmware image is stored in the second partition and has been marked as active; and

in response to said determination, making a copy of the firmware image and storing the copy of the firmware image in the first partition, thereby overwriting the boot loader code in the first partition with the copy of the firmware image;

wherein the method is performed at least in part by the one or more processors of the computing system.

2. The method of claim 1, further comprising:

following a separate power cycle, determining that an active copy of the firmware image is not stored in the non-volatile storage; and

in response to said determination that an active copy of the firmware image is not stored in the non-volatile storage, executing the boot loader code from the first partition.

3. The method of claim 1, wherein the non-volatile storage and the one or more processors are components of a data storage drive.

4. The method of claim 1, wherein the non-volatile storage is a flash memory communicatively coupled to an interface bridge module of the computing system.

5. The method of claim 4, wherein said loading the firmware image to the second partition is performed at least in part using a host interface communicatively coupled to the interface bridge module.

6. The method of claim 1, wherein said marking the firmware image as active comprises setting metadata associated with the firmware image to a first value.

7. The method of claim 1, further comprising:

making an additional copy of the firmware image; and

storing the additional copy in the non-volatile storage.

8. The method of claim 1, wherein:

the firmware image is loaded from a second non-volatile storage of a data storage drive; and

the non-volatile storage is a component of the data storage drive.

9. A computing system comprising:

a device controller comprising one or more processors; and

a non-volatile storage having boot loader code stored in a first partition thereof, the boot loader code being marked as active and comprising instructions for loading a firmware image that is separate from the boot loader code to the non-volatile storage;

wherein the device controller is configured to;

in response to a system start-up, execute the boot loader code using the one or more processors;

load the firmware image from a location separate from the non-volatile storage to a second partition of the non-volatile storage, the second partition being separate from the first partition;

mark the firmware image as active;

following a power cycle, determine that the firmware image is stored in the second partition and has been marked as active; and

in response to said determination, make a copy of the firmware image and store the copy of the firmware image in the first partition, thereby overwriting the boot loader code in the first partition with the copy of the firmware image.

10. The computing system of claim 9, wherein the device controller is further configured to:

following a separate power cycle, determine that an active copy of the firmware image is not stored in the non-volatile storage; and

in response to said determination that an active copy of the firmware image is not stored in the non-volatile storage, execute the boot loader code from the first partition.

11. The computing system of claim 9, wherein the computing system is a data storage drive.

12. The computing system of claim 9, wherein the non-volatile storage is a flash memory communicatively coupled to an interface bridge module of the computing system.

13. The computing system of claim 12, wherein the device controller is further configured to receive the firmware image over a host interface communicatively coupled to the interface bridge module.

14. The computing system of claim 9, wherein the device controller is configured to mark the firmware image as active at least in part by setting metadata associated with the firmware image to a first value.

15. The computing system of claim 9, wherein the device controller is further configured to:

make an additional copy of the firmware image; and

store the additional copy in the non-volatile storage.

16. The computing system of claim 9, wherein:

the device controller is further configured to load the firmware image from a second non-volatile storage of a data storage drive; and

the non-volatile storage is a component of the data storage drive.