Complete and compatible function

• US 9,384,084 B2
• Filed: 03/23/2012
• Issued: 07/05/2016
• Est. Priority Date: 03/23/2011
• Status: Active Grant

• Current Assignee: Volvo Car Corporation (AB Volvo)
• Original Assignee: Volvo Car Corporation (AB Volvo)
• Inventors: Persson, Magnus, Johansson, Thomas
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): KABIR, MOHAMMAD H
• Application Number:
  US13/428,876
• Publication Number:
  US 20120246615A1
• Time in Patent Office: 1,565 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1004 to protect a block of data words, e.g. CRC or checksum G06F11/1076 takes precedence; security arrangements for protecting computers or computer systems against unauthorized activity G06F21/00
• CPC Class Codes: G06F 9/44 Arrangements for executing specific programs
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers

Abstract

An arrangement for verifying the completeness and compatibility of software components in an electronic control unit includes a bootloader and a CompleteCompatible verification component. The bootloader is arranged to, upon start-up of the electronic control unit, verify the completeness and compatibility of the CompleteCompatible verification component, and upon such verification being positive initiate the CompleteCompatible verification component. The CompleteCompatible verification component is arranged to, upon performance thereof, verify the completeness and compatibility of further software components in the electronic control unit.

Claims

1. An apparatus for verifying the completeness and compatibility of software components, the arrangement comprising:

an electronic control unit (ECU) having memory comprising a memory circuit;

a bootloader stored in the memory circuit; and

a CompleteCompatible verification component stored in the memory,

where the bootloader is arranged to, upon start-up of the ECU, verify the completeness and compatibility of the CompleteCompatible verification component;

wherein, to verify the completeness and compatibility of the CompleteCompatible verification component, the bootloader is arranged to

read a StartCompleteCompatibleSignature;

check if the StartCompleteCompatibleSignature is valid;

if the StartCompleteCompatibleSignature is found valid, read an EndCompleteCompatibleSignatureAddress;

read an EndCompleteCompatibleSignature; and

check if the EndCompleteCompatibleSignature is valid, and upon such verification being positive initiate the CompleteCompatible verification component,

where the CompleteCompatible verification component is arranged to, upon performance thereof, check that a respective start and stop address as well as a version number for a further software component in the ECU is correct or calculate a checksum for the further software component and compare the calculated checksum with a reference value stored in associated memory in order to verify the completeness and compatibility of the further software component in the ECU before the further software component exercises control of the ECU;

wherein the bootloader is arranged for verification of the CompleteCompatible verification component, and the CompleteCompatible verification component is arranged for verification of the further software component in the ECU without involvement of the bootloader in the verification of the further software component.

2. The arrangement according to claim 1 wherein the CompleteCompatible verification component further is arranged to return a value to the bootloader indicative of whether all software components in the electronic control unit are complete and compatible such that the electronic control unit may be started with full operational functionality or not.

3. The arrangement according to claim 1 wherein the CompleteCompatible verification component, upon verification that the further software components are complete and compatible, is arranged to read an application start address from the associated memory and jump to the application start address for execution of the further software components in the electronic control unit.

4. An electronic control unit (ECU) for a motor vehicle, the ECU comprising:

memory comprising a memory circuit; and

an arrangement for verifying the completeness and compatibility of software components in the ECU, the arrangement including a bootloader stored in the memory circuit and a CompleteCompatible verification component stored in the memory,

where the bootloader is arranged to, upon start-up of the electronic control unit, verify the completeness and compatibility of the CompleteCompatible verification component

wherein, to verify the completeness and compatibility of the CompleteCompatible verification component, the bootloader is arranged to

read a StartCompleteCompatibleSignature;

check if the StartCompleteCompatibleSignature is valid;

if the StartCompleteCompatibleSignature is found valid, read an EndCompleteCompatibleSignatureAddress;

read an EndCompleteCompatibleSignature; and

check if the EndCompleteCompatibleSignature is valid, and upon such verification being positive initiate the CompleteCompatible verification component,

where the CompleteCompatible verification component is arranged to, upon performance thereof, check that a respective start and stop address as well as a version number for a further software component in the ECU is correct or calculate a checksum for the further software component and compare the calculated checksum with a reference value stored in associated memory in order to verify the completeness and compatibility of the further software components in the ECU before the further software component exercises control of the ECU;

wherein the bootloader is arranged for verification of the CompleteCompatible verification component, and the CompleteCompatible verification component is arranged for verification of the further software component in the ECU without involvement of the bootloader in the verification of the further software component.

5. A method for verifying the completeness and compatibility of software components in an electronic control unit (ECU), the method comprising:

verifying, via a bootloader upon start-up of the ECU, the completeness and compatibility of a CompleteCompatible verification component through

reading a StartCompleteCompatibleSignature;

checking if the StartCompleteCompatibleSignature is valid;

if the StartCompleteCompatibleSignature is found valid, reading an EndCompleteCompatibleSignatureAddress;

reading an EndCompleteCompatibleSignature; and

checking if the EndCompleteCompatibleSignature is valid, and

upon such verification being positive initiating the CompleteCompatible verification component for verifying the completeness and compatibility of a further software component in the ECU, before the further software component exercises control of the ECU, through at least one of

checking that a respective start and stop address as well as a version number for each further software component is correct;

calculating a checksum for each respective further software component and comparing the calculated checksum with a reference value stored in associated memory;

wherein the bootloader is arranged for verification of the CompleteCompatible verification component, and the CompleteCompatible verification component is arranged for verification of the further software component in the ECU without involvement of the bootloader in the verification of the further software component.

6. The method according to claim 5 further comprising:

returning a value indicative of whether all software components in the electronic control unit are complete and compatible.

7. The method according to claim 5 further comprising:

upon verification that the further software components are complete and compatible, reading an application start address from an associated memory and jumping to the application start address for execution of the further software components in the electronic control unit.