Dual software images with fall-back

• US 6,564,371 B1
• Filed: 08/26/1999
• Issued: 05/13/2003
• Est. Priority Date: 08/26/1998
• Status: Expired due to Term

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Uhlemann, Henrik, Goldman, Tomasz
• Primary Examiner(s): Chaki, Kakali
• Assistant Examiner(s): Chavis, John Q.
• Application Number:
  US09/383,810
• Time in Patent Office: 1,356 Days
• Field of Search: 717/11, 717/127, 714/2, 714/6, 714/7, 714/19, 714/46
• US Class Current: 717/127
• CPC Class Codes: G06F 11/1433 during software upgrading

Abstract

A method and system to enable a user to store a known and operational version of software and a new version of software (possibly not operational) in a memory on a network device. The user can test the new software and have an automatic fallback mechanism which loads the old version of software in the device if the new version fails to operate.

Claims

1. A method for testing software in a device, comprising:

initializing the device;

storing at least two software images in a memory in the device;

providing status information to indicate a state of each software image in said memory, the state of each software image being one of current, not-current or a test version;

selecting one of the software images for execution if the state indicates the one of the software images is said test version;

changing the status information for the selected software image prior to execution of the selected software image to a state of not-current if the selected software image is the test version; and

executing the selected software image without an automatic reboot if the selected software image fails.

2. The method of claim 1 wherein selecting one of the software images for execution comprises selecting another of the software images for execution if the status information indicates none of the software images are a test version and the another of the software images is a current version.

3. The method of claim 1 further comprising:

determining whether the device is operating properly.

4. The method of claim 3 further comprising:

changing the status information of the selected software image from indicating that the selected software image is not-current to status information that indicates that the selected software image is current if the device is operating properly, and changing the status information of a second of the software images to a status information indicating that the second software image is not-current.

5. The method of claim 3 further comprising:

maintaining the status information of the selected software image if the device is not operating properly; and

reinitializing the device.

6. The method of claim 1 wherein the software images and status information are stored in a non-volatile memory, the non-volatile memory comprising a plurality of bit value locations, the bit value locations being independently addressable when changing state between a first state value and a second state value, and the bit value locations being addressable members of an interdependent plurality of locations when changing state between the second state value and the first state value.

7. The method of claim 4 wherein the software images and status information are stored in a non-volatile memory, the non-volatile memory comprising a plurality of bit value locations, the bit value locations being independently addressable when changing state between a first state value and a second state value, and the bit value locations being addressable members of an interdependent plurality of locations when changing state between the second state value and the first state value.

8. The method of claim 7 wherein changing the status information comprises altering a bit value location between the first state value and the second state value.

9. A method of managing images of software in a device, comprising:

storing at least two images of software in a memory in the device;

storing status records in the memory, wherein the status records indicate the operating mode of the software, including whether one of the software images is a test image;

selecting the test image for execution;

altering the status records to indicate an attempt to establish device operation with the selected image of software and to indicate that the selected image is no longer designated as a test image; and

executing the selected image without an automatic reboot if the selected image fails.

10. The method of claim 9 further comprising:

establishing device operation;

indicating whether the operational image of software is to be accepted;

selectively altering any status records necessary to indicate whether the selected version is to be accepted.

11. A computer program residing on a computer-readable medium comprising instructions for causing a computer to

store at least two images of software in a memory in the device;

store a status record for each image in the memory, wherein the status records indicate the operating mode of the associated software image, including that one of the software images is a test image;

select the test image for execution;

alter the status records to indicate an attempt to establish device operation with the selected image of software and to indicate that the selected image is no longer designated a test image; and

execute the selected image without an automatic reboot if the selected image fails.

12. The computer program of claim 11 further comprising instructions to:

establish device operation;

indicate whether the operational image of software is to be accepted; and

selectively alter status records to indicate whether the selected image is to be accepted.