Method of hardware driver integrity check of memory card controller firmware

• US 7,536,540 B2
• Filed: 11/21/2005
• Issued: 05/19/2009
• Est. Priority Date: 09/14/2005
• Status: Active Grant

• Current Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Original Assignee: SanDisk Corporation (Western Digital Corporation)
• Inventors: Elhamias, Reuven, Holtzman, Michael, Barzilai, Ron, Cohen, Niv
• Primary Examiner(s): SURYAWANSHI, SURESH
• Application Number:
  US11/284,623
• Publication Number:
  US 20070061570A1
• Time in Patent Office: 1,275 Days
• Field of Search: 713/2, 713/176, 713/189
• US Class Current: 713/2
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 21/575 Secure boot

Abstract

A memory system comprises an encryption engine implemented in the hardware of a controller. In starting up the memory system, a boot strapping mechanism is implemented wherein a first portion of firmware when executed pulls in another portion of firmware to be executed. The hardware of the encryption engine is used to verify the integrity of at least the first portion of the firmware. Therefore, only the firmware that is intended to run the system will be executed.

Claims

1. A method for starting operation and operating a memory storage device comprising:

providing firmware of the memory storage device in a mass storage unit of the memory storage device;

passing said firmware through a hardware implemented encryption engine of the memory storage device;

calculating hash values for said firmware with said hardware implemented encryption engine;

comparing the calculated hash values with stored hash values; and

executing said firmware if said computed hash values match said stored hash values.

5. The method of claim 1, wherein providing the firmware comprises providing a plurality of firmware overlays.

6. The method of claim 5, further comprising, storing, within each overlay of the plurality, a hash value expected to equal a calculated hash value of a quantity of the firmware that includes the overlay containing the hash.

7. The method of claim 6, wherein the calculated hash value of the quantity being read will only correspond to expected hash value when a sector containing the expected hash value is read.

8. The method of claim 6 further comprising disregarding false positive matches on a sector block or page other than the sector block or page containing the expected hash value.

9. The method of claim 1, wherein calculating hash values comprises calculating a MAC value for a block (i), but wherein the resulting MAC value covers blocks 0 to (i), such that MAC [0. . .(i)]=MAC[MAC[0. . .(i-1)], block (i)].

10. The method of claim 9, further comprising storing the calculated MAC value for block (i) in a register of a memory controller of the memory storage device, said register not in the mass storage unit.

11. The method of claim 9, wherein calculating the hash value for a block (i), wherein the resulting MAC value covers blocks 0 to (i), such that MAC [0. . . (i)]=MAC[MAC[0. . .(i-1)], block (i)]is done for a boot loader of the firmware.

12. The method of claim 9, wherein calculating the hash value for a block (i), wherein the resulting MAC value covers blocks 0 to (i), such that MAC [0. . . (i)]=MAC[MAC[0. . .(i-1)], block (i)]is done for a boot loader of the firmware, but not the entire firmware.

13. The method of claim 9, wherein calculating the hash value for a block (i), wherein the resulting MAC value covers blocks 0 to (i), such that MAC [0. . . (i)]=MAC[MAC[0. . .(i-1)], block (i)]is done for the entire firmware.

2. A method for starting operation of a memory storage device, comprising:

providing firmware in a mass storage unit of the memory storage device, the firmware controlling operation of the memory storage device;

executing a first set of instructions in a read only memory that copy the firmware from the mass storage unit of the memory storage device to a random access memory of the memory storage device;

verifying the integrity of the firmware as it passes from the mass storage unit through a hardware implemented encryption engine in a memory controller of the memory storage device; and

after the integrity is verified, executing the firmware from a random access memory with a microprocessor.

3. The method of claim 2, wherein said firmware contains instructions to fetch additional firmware from the mass storage unit.

4. The method of claim 3, wherein the method further comprises executing the additional firmware.