Method for assuring flash programming integrity

• US 20070112773A1
• Filed: 11/14/2005
• Published: 05/17/2007
• Est. Priority Date: 11/14/2005
• Status: Abandoned Application

• Current Assignee: Ford Motor Company
• Original Assignee: Ford Motor Company
• Inventors: Joyce, John
• Application Number:
  US11/274,108
• Publication Number:
  US 20070112773A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/64 Retargetable
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/654 using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories

Abstract

A method is provided for assuring that only the correct version of a software update is permitted to be installed in a computer controlled module, such as a vehicle controller. Each version of the software is embedded with a unique identifier, and each software update has an embedded list of the identifiers of the software versions which it is authorized to update or replace. A flashloader is used to determine if the identifier of the software in the controller is present in the list embedded in a proposed update, and installs the update if a match is found. Checksums and encryption of the identifiers can be used to enhance reprogramming integrity.

Claims

1. A method for updating software applications in computerized controllers, comprising the steps of:

(A) embedding an identifier in each of the software applications that uniquely identifies the application;

(B) embedding in a software update a list of identifiers for the software applications that the update is authorized to update;

(C) determining whether the identifier of a software application present in a controller is present in the list embedded in a proposed software update; and

,

(D) installing the proposed software update in the controller only if the identifier of the software application to be updated is determined in step (C) to be present in the list embedded in the proposed software update.

2. The method of claim 1, wherein step (C) is performed using a flashloader to compare the identifier of the software application present in a controller with the list embedded in the proposed software update.

3. The method of claim 1, wherein:

the software application to be updated is stored in a flash memory in the controller, and

step (D) is performed using a flashloader.

4. The method of claim 1, further comprising the steps of:

(E) maintaining a count of the number of times step (C) is performed for a proposed software update, and

(F) terminating attempts to install the software update if the count exceeds a preselected value.

5. The method of claim 1, wherein step (C) includes performing a checksum to verify the integrity of the software application present in a controller.

6. The method of claim 1, further comprising the step of encrypting each of the identifiers embedded in the software applications and the identifiers in the list.

7. The method of claim 1, wherein the update installed in step (D) forms only a portion of the software application present in a controller.

8. A method for updating software in a controller, comprising the steps of:

(A) storing a unique identifier in the controller that uniquely identifies the software present in the controller;

(B) storing with update software a list of the unique identifiers for software that the update software is authorized to update;

(C) determining whether the identifier stored in step (A) is present in the list of identifiers stored in step (B); and

,

(D) updating the software in the controller with the update software only if the identifier is determined in step (C) to be present in the list.

9. The method of claim 8, further comprising the step of embedding the identifier in the software, and step (A) includes storing the software containing the embedded identifier in a memory in the controller.

10. The method of claim 9, further comprising the step of encrypting the location of the identifier within the memory.

11. The method of claim 8, wherein steps (C) and (D) are performed using a flashloader.

12. The method of claim 8, further comprising the steps of:

(E) storing a second copy of the unique identifier in the controller;

(F) determining whether the identifier used in the determination made in step (C) identically matches the second copy of the identifier stored in step (E); and

(G) terminating the update if the step (F) does not result in an identical match.

13. The method of claim 8, further comprising the steps of:

(E) maintaining a count of the number of times step (C) is performed for a proposed software update, and

(F) terminating attempts to update the software if the count exceeds a preselected value.

14. The method of claim 8, wherein step (C) includes performing a checksum to verify the integrity of the software in the controller.

15. The method of claim 8, further comprising the step of encrypting the stored identifier and Each of the identifiers in the list.

16. A method of updating a software application in a computerized controller, comprising the steps of:

(A) determining values for identifiers in a configuration stored in the controller;

(B) determining criteria that the identifier values in the configuration must satisfy in order for a software update to be authorized;

(C) determining whether the criteria are satisfied;

(D) if criteria are satisfied, performing a software update; and

,

(E) if criteria are not satisfied, inhibiting the software update.

17. The method of claim 16, wherein the criteria are stored in the computerized controller.

18. The method of claim 16, wherein the criteria are stored in a new software application.

19. The method of claim 16, wherein step (C) is performed by using a flashloader that updates the software application.

20. The method of claim 16, wherein the values for identifiers in the configuration are embedded in the software application, and are embedded in a new software application using a flashloader.