|Publication number||US6859876 B2|
|Application number||US 09/751,187|
|Publication date||Feb 22, 2005|
|Filing date||Dec 29, 2000|
|Priority date||Dec 29, 2000|
|Also published as||US20020087855|
|Publication number||09751187, 751187, US 6859876 B2, US 6859876B2, US-B2-6859876, US6859876 B2, US6859876B2|
|Inventors||Don A. Dykes, Richmond L. Armstrong|
|Original Assignee||Hewlett-Packard Development Company, L.P.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (7), Referenced by (12), Classifications (6), Legal Events (7)|
|External Links: USPTO, USPTO Assignment, Espacenet|
1. Field of the Invention
The present invention generally relates to a method and system to update or correct the original boot block of a computer system. More particularly, the invention relates to a method and system to substitute a secondary boot block for the original boot block of a computer system, thereby effectively allowing for modification of the original boot block.
2. Background of the Invention
The procedure for starting up or booting up a computer system is fairly common. When powered on, the computer system executes certain startup code to initialize the system. This startup code is often referred to as a boot block. Essentially, the boot block is intended to create a known state in the computer system from which to begin and to initialize and activate all of the system hardware as necessary. In a personal computer, for example, the boot block includes code to initialize the microprocessor's registers, initialize the DRAM, set-up and recognize other available hardware, etc. This code in a personal computer platform is often referred to as BIOS (Basic Input/Output System). The boot block may need to perform different functions depending on the particular system or platform; however, every system requires some sort of startup code. Therefore every system has some type of a boot block.
Because the boot block initializes the system, it is often stored in protected memory to avoid inadvertent or uninformed modification of its contents. For without the boot block, the computer system cannot be started. In addition, for the boot block to perform its function, it must be stored in memory that is available immediately on startup. Accordingly, the boot block is typically stored in hardware-protected ROM (Read Only Memory) that requires no startup initialization by the computer system. For example, the boot block may be stored in a PROM (Programmable Read Only Memory) that requires no initialization and is protected from modification since a programming device separate from the computer system is typically required to change the memory. In fact, some PROMs are one-shot devices, meaning they can only be programmed once. EPROMs (Erasable Programmable Read Only Memory) may also be used since they require no initialization and, although they are erasable, they typically require UV (ultra violet) radiation to erase them. More recently, however, less costly FlashROMs have been used which have at least a portion of their memory hardware-protected, meaning some hardware interference is required to change that portion of the memory.
Having the boot block stored in unalterable or hardware-protected memory does, however, create some difficulties. In particular, it is by design difficult to update or correct the boot block. While it is desirable to protect the boot block from unintentional or uninformed modification of its contents, i.e., by a user of the computer system, there are times when the boot block may need to be modified. For example, when the system designers want to implement an upgrade to the system which requires a modification to the boot block, perhaps because there was a glitch or bug in the original boot block, or to allow the system to handle conditions not foreseen previously. Whatever the reason, there are times when the boot block needs to be modified. In the past, this meant that most boot block ROMs were mounted to a board in the system via a socket. This allowed the boot block to be changed by physically replacing the ROM with a new ROM containing the updated boot block. Sockets, however, have fallen into disfavor for most computer systems. In particular, sockets add cost to the system, both in terms of the additional materials cost as well as the manufacturing costs. Today, most boot block ROMs are now soldered to the board. Although cheaper to manufacture, this means replacement of the board is required in order to replace the ROM. Obviously, neither solution is desirable.
One solution would be to place the boot block in alterable memory (i.e., memory that can be changed by the system). Although this solution would appear to resolve the replacement problem discussed above, unprotecting the boot block creates a risk of inadvertent or uninformed modification of the boot block. In addition, any attempt to modify or update the original boot block presents a real risk of rendering the system inoperable and unrecoverable since the original boot block has not been maintained.
In accordance with the present invention, there is provided a novel method and system for updating or modifying the original boot block in a computer system without endangering the integrity of the system. In particular, the novel method and system of the present invention allows for a secondary boot block to be substituted for the original boot block. The original boot block is not overwritten, however, so the system can always be recovered. This is accomplished by having the original boot block check for a replacement secondary boot block as early in the startup code as is feasible. If a valid secondary boot block is found, the startup process is passed to the secondary boot block. Thus, updates or modifications can be made by implementing a secondary boot block into the system. The original boot block is maintained, however, so the system can always be started even if the secondary boot block becomes defective.
The invention can be more fully understood by referencing the accompanying drawings wherein:
Certain terms are used throughout the following description and claims to refer to particular system components. As one skilled in the art will appreciate, components may be referred to by different names. This document does not intend to distinguish between components that differ in name but not function. In the following discussion and in the claims, the terms “including” and “comprising” are used in an open-ended fashion, and thus should be interpreted to mean “including, but not limited to . . . ”. Also, the term “couple” or “couples” is intended to mean either an indirect or direct electrical connection. Thus, if a first device couples to a second device, that connection may be through a direct electrical connection, or through an indirect electrical connection via other devices and connections. The term computer system is used broadly herein to include any microprocessor-based system or platform.
Referring now to the drawings, wherein like reference characters denote corresponding components or parts:
As shown, the startup memory 12 includes the original boot block 16. The original boot block 16 comprises the startup code for the system 10. The boot block 16 initializes the system components and brings the system 10 up to a known state before passing control to the system software stored in the system memory 13. The system memory 13 requires initialization before it can be used so the system software stored therein cannot be accessed until the initialization of the system 10 is complete. To accommodate the function of the boot block 16, the startup memory 12 is typically FlashROM which requires little or no initialization such that it can be available almost immediately after power up of the system 10, and which can be hardware protected, in whole or in part, to prevent inadvertent modification of the boot block 16. Although FlashROM is used in the current embodiment of the invention, any memory having these capabilities can be used to store the boot block 16.
The system 10 is started by turning on the power supply 14 to provide power to the system 10. After power up, the CPU 11 accesses the startup memory 12 and begins execution of the boot block 16. The boot block 16 performs the necessary system setup and initialization, such as initializing the DRAM of the system memory 13, and then passes control to the system software. The boot block 16 brings the system 10 up to a known level before handing control to the system software and user. Without the boot block 16, the system could not be started. It is important, then, to protect the boot block 16 from any inadvertent or uninformed modifications. Accordingly, the boot block 16 is typically stored in startup memory 12 that can be protected, in whole or in part, from such modification. In addition, the boot block 16 must be available shortly after power up of the system. Therefore, the boot block needs to be stored in memory that requires no active initialization. As noted above, although other types of memory can meet these criteria, such as PROMs or EPROMs, present systems generally use FlashROM since it is currently the most cost effective memory available with these characteristics.
A problem arises, however, when the boot block 16 needs to be modified. The boot block 16 may need to be modified in order to accommodate an update or upgrade of the system 10, or to correct bugs or glitches in the boot block 16. In early systems, the startup memory 12 was installed in the system 10 via a socket or sockets depending on the number of chips comprising the startup memory 12. This allowed the boot block 16 to be modified by physically replacing the startup memory 12. In particular, the chips comprising the startup memory 12 were simply replaced with new chips via the sockets. Sockets, however, have fallen into disfavor for most computer systems. In particular, sockets add cost to the system, both in terms of the additional materials cost as well as the manufacturing costs. Instead, most startup memory 12 today is soldered to a printed circuit board. Now, however, a change in the startup memory 12 requires replacement of the entire board. Thus the need for a more convenient way to modify the boot block 16 arises. Although the problem could be avoided by simply unprotecting the boot block 16 so that it can be rewritten or overwritten, such a solution puts the integrity of the system at jeopardy. In particular, if the boot block 16 is inadvertently or incorrectly modified, there may be no way to boot up the system at all. Thus requiring a major effort to reinstate the system to operable conditions.
Instead, the present invention provides a method and system for modifying the boot block without having to replace the startup memory 12, while ensuring system integrity by leaving the original boot block 16 in place for a fail-safe recovery of system operation.
In accordance with the present invention, the startup or boot up process of the system 10 is modified as follows: As in
Several methods may be employed to determine the existence and validity of the secondary boot block. In the current embodiment of the invention, however, the original boot block 16 simply checks certain predetermined addresses in the startup memory 12 for data and compares that data with predetermined verification data. If the data matches, the original boot block 16 determines that a secondary boot block 20 has been found. Before passing control to the secondary boot block 20, however, the integrity or validity of the secondary boot block 20 is also checked by performing a checksum on all, or a portion of, the startup memory 12 allocated for the secondary boot block 20. If the checksum is passed, the original boot block 16 passes control to the secondary boot block 20 which resides in the startup memory at the predetermined location. It is contemplated that various methods may be used to verify the existence and integrity of the secondary boot block 20. The key, however, is that so long as one knows what signature the original boot block 16 expects for a secondary boot block 20, the secondary boot block 20 can be constructed with that signature to meet the tests performed by the original boot block 16.
It should also be noted that the theory of a secondary boot block can be extended to multiple, serially-accessed boot blocks. For example, if a secondary boot block needs to be modified or updated, it can typically just be overwritten since it is in alterable memory. In a system where the original boot block contained a significant defect, however, it may be desirable to maintain the secondary boot block for a fail-safe recovery of the system. Accordingly, a third boot block could be implemented so long as the secondary boot block similarly incorporates an initial check for a substitute boot block. In this same manner, any number of substitute boot blocks can be implemented.
If no secondary boot block is found, the system boots normally using the original boot block as shown in block 35. Once the original boot block has completed its startup process, control is passed to the system software, block 38, and the booting process ends at block 39.
If a secondary boot block is found, however, the original boot block transfers control to the secondary boot block as indicated in block 36. The system then continues to boot using the secondary boot block as shown in block 37. Once the secondary boot block has completed its startup process, control is again passed to the system software, block 38, and the booting process ends at block 39.
It should be noted that since the original boot block is maintained, and not overwritten with the secondary boot block, the system is fail-safe. That is, even if the secondary boot block becomes defective, the system can still be started using the original boot block.
The above discussion is meant to be illustrative of the principles and various embodiments of the present invention. While the invention has been particularly shown and described with respect to specific embodiments thereof, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5381549 *||Dec 7, 1993||Jan 10, 1995||Canon Kabushiki Kaisha||Information processing apparatus|
|US6282647 *||Jun 2, 1999||Aug 28, 2001||Adaptec, Inc.||Method for flashing a read only memory (ROM) chip of a host adapter with updated option ROM bios code|
|US6330634 *||Sep 28, 1998||Dec 11, 2001||Sony Corporation||External storage apparatus having redundant boot blocks, and data processing method therefor|
|US6425079 *||Mar 31, 1999||Jul 23, 2002||Adaptec, Inc.||Universal option ROM BIOS including multiple option BIOS images for multichip support and boot sequence for use therewith|
|US6446139 *||Jun 28, 1999||Sep 3, 2002||Adaptec, Inc.||Multiple chip single image BIOS|
|US6513113 *||Jun 16, 1999||Jan 28, 2003||Ricoh Company, Ltd.||Electronic instrument adapted to be selectively booted either from externally-connectable storage unit or from internal nonvolatile rewritable memory|
|US6622246 *||Nov 12, 1999||Sep 16, 2003||Xerox Corporation||Method and apparatus for booting and upgrading firmware|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7716633||May 16, 2005||May 11, 2010||Heath Chester A||Method for extending the life and utility of an existing personal computer by adding instant-on embedded functions|
|US7817157||Oct 19, 2010||Hewlett-Packard Company, L.P.||Method and apparatus for capturing slices of video data|
|US8140836 *||Aug 7, 2008||Mar 20, 2012||Konica Minolta Business Technologies, Inc.||Information processing apparatus and program|
|US8933941||Aug 23, 2005||Jan 13, 2015||Hewlett-Packard Development Company, L.P.||Method and apparatus for redirection of video data|
|US9015516||Feb 29, 2012||Apr 21, 2015||Hewlett-Packard Development Company, L.P.||Storing event data and a time value in memory with an event logging module|
|US20040268116 *||Jun 30, 2003||Dec 30, 2004||Vasisht Virender K||Fault tolerant recovery block with reduced flash footprint|
|US20050071624 *||Sep 29, 2003||Mar 31, 2005||Rothman Michael A.||Providing a self-describing media for a computer system|
|US20060039464 *||Aug 23, 2005||Feb 23, 2006||Emerson Theodore F||Method and apparatus for capturing video data to a virtual screen buffer|
|US20060039465 *||Aug 23, 2005||Feb 23, 2006||Emerson Theodore F||Method and apparatus for redirection of video data|
|US20060039466 *||Aug 23, 2005||Feb 23, 2006||Emerson Theodore F||Method and apparatus for managing changes in a virtual screen buffer|
|US20060039468 *||Aug 23, 2005||Feb 23, 2006||Emerson Theodore F||Method and apparatus for capturing and transmitting screen images|
|US20090063840 *||Aug 7, 2008||Mar 5, 2009||Tomoya Ogawa||Information Processing Apparatus and Program|
|Cooperative Classification||G06F8/66, G06F9/4406|
|European Classification||G06F8/66, G06F9/44A3|
|Apr 16, 2001||AS||Assignment|
Owner name: COMPAQ COMPUTER CORPORATION, TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DYKES, DON A.;ARMSTRONG, RICHMOND L.;REEL/FRAME:011717/0951
Effective date: 20010314
|Jan 15, 2002||AS||Assignment|
Owner name: COMPAQ INFORMATION TECHNOLOGIES GROUP, L.P., TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COMPAQ COMPUTER CORPORATION;REEL/FRAME:012478/0903
Effective date: 20010620
|Dec 2, 2003||AS||Assignment|
Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXAS
Free format text: CHANGE OF NAME;ASSIGNOR:COMPAQ INFORMATION TECHNOLOGIES GROUP L.P.;REEL/FRAME:014177/0428
Effective date: 20021001
Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.,TEXAS
Free format text: CHANGE OF NAME;ASSIGNOR:COMPAQ INFORMATION TECHNOLOGIES GROUP L.P.;REEL/FRAME:014177/0428
Effective date: 20021001
|Aug 22, 2008||FPAY||Fee payment|
Year of fee payment: 4
|Sep 1, 2008||REMI||Maintenance fee reminder mailed|
|Aug 22, 2012||FPAY||Fee payment|
Year of fee payment: 8
|Nov 9, 2015||AS||Assignment|
Owner name: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP, TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.;REEL/FRAME:037079/0001
Effective date: 20151027