Computer system with alterable bootstrapping software and method therefor

Abstract: A computer which carries its BIOS in a Flash EPROM. A UV-EPROM carries a redundant BIOS, which can be overlaid onto the BIOS address space by selection with a physical switch. The BIOS contains a small core software program, at the BIOS entry point, which checks BIOS integrity, and provides for reloading the Flash EPROMS's BIOS if needed (from a floppy disk, or by copying the entire contents of the UV-EPROM).

Description: The present invention relates to a computer system. Any computer system must have some way to begin program execution after a cold start. The hardware architecture of a CPU (processor) will normally provide for a "reset" operation, which places all of the hardware circuits in a known electrical state; but it is still necessary to start the CPU on execution of a desired program. For example, in the very early days of computing, some computer systems would be manually configured to read in a "bootstrap loader" program at startup. This bootstrap program was a simple program which loaded in, and started execution of, another sequence of instructions, which were the beginning of the desired program. Bootstrap programs are often referred to simply as "boot" software. To give a more recent example, the Intel 80x86 microprocessors, after a hardware reset will always attempt to begin program execution from a specific memory address. That is, the microprocessor will read the contents of that memory location, and will attempt to execute the bits it finds there as a microprocessor instruction. Thus, if a branch (or conditional branch) instruction is found at this address, the microprocessor will continue its program execution from whatever address is specified. The specific memory location used by the 80x86 family is xxxFFFFOh, i.e. 16 bits below the top of the memory space. Other microprocessors may use a different starting address, but similar principles apply. Thus, this initial target address is the entry point for every session of use. This address is normally used to enter execution of programs which must be run every time the computer is used. Whatever hardware is used will have its own procedures to return to a known state when a reset occurs. However, at some point these procedures end, and the CPU is ready to begin execution of instructions. At this point the system performs various overhead tasks under software control. These may include surveying the system configuration, sanity checks etc. In modern personal computers, the initial target address is normally used as the entry point to a "basic input/output system" (BIOS) program. The BIOS program contains frequently-used routines for interfacing to key peripherals, for interrupt handling, and so forth. Thus, the BIOS software provides some degree of machine-independence. However, in PC-class computers, this independence is not fully exploited by the available commercial software. Many programs bypass the BIOS software, and directly access the underlying hardware addresses or devices. See Glass, "The IBM PC BIOS", Byte, April 1989, pp. 303ff. In addition to these basic input/output routines, the "BIOS" software also includes some key pieces of overhead software, such as configuration update and the power-on-self-test (POST) routines. The POST routines provide an extensive check for hardware integrity. The BIOS software will also launch the machine into the operating system software. Depending on how the system has been set up, the BIOS software may direct program execution into DOS, Unix, PS/2, a DOS variant, or another operating system. However, the choice of operating system is not particularly relevant to the invention described in the present application. (Thus, the term "BIOS" has become somewhat broader nowadays, and normally refers to this whole collection of basic system routines.) If the BIOS software were to become corrupted, the computer could become unusable. Thus, the BIOS software has conventionally been stored in read-only memory (ROM). When the microprocessor attempts to access the initial target address, it reads out software from the BIOS ROM. In 1980 there was only one source for IBM-compatible BIOS software, and that was from IBM. However, during the 1980s, as IBM-compatible personal computers became more popular, modified versions of IBM-compatible BIOS ROMs were developed, and IBM compatible BIOS ROMs were offered by multiple vendors. As of 1991, BIOS software is often modified to implement system-dependent features, especially in low-power systems. Improvements in BIOS software mean that sometimes it will be desirable to implement a BIOS upgrade. Dedicated users have successfully pried out and replaced ROM chips, but most users would not want this degree of hands-on contact. Some attempts have been made in the past to provide capability for updating the basic system software. See e.g., Bingham, D.B., "Achieving flexible firmware," 1978 MIDCON Technical Papers at 20/3/1-4(1978). It is believed that some vendors may have offererd upgradable-BIOS systems. However, insofar as is known, no system has offered protection against corruption while updating BIOS. Without boot software, a computer could not run any program at all. Thus, corruption of the boot software can make a computer totally unusable. Thus, for security against such corruption, personal computers have commonly been manufactured with their BIOS software in nonvolatile memory chips. However, for rapid system development and upgrading, it is desirable to be able to rapidly provide new BIOS chips, or even to upgrade existing BIOS chips. Over years, a variety of developments in semiconductor device technology have been used to reconcile these needs. One of the simplest nonvolatile memories is the mask ROM. By custom-patterning one level of a chip, a complex pattern of data can be permanently encoded. For example, an array with polysilicon row lines accessed by row decoders, and metal column lines accessed by column decoders, can have contact holes selectively etched, so that one bit of data is encoded at each row/column intersection. Alternatively, polysilicon row lines can be selectively linked to diffused column lines by metal shorting straps. With this technology, a new mask must be prepared whenever any bit of data is changed. In high volume, mask ROMs are reasonably cheap, but they are not suited for rapid upgrading. A "programmable read-only-memory," or PROM, can be electrically written. PROMs are typically built using solid-state fuses (or antifuses), which will become open (or shorted) whenever a high current is driven through them. Thus, the programming of a conventional PROM requires the application of a high voltage (e.g. 10 or 15 V) to achieve the high currents needed. However, once the data has been written it is permanent. An "electrically programmable read-only memory," or EPROM, can be electrically written, and can be erased by ultraviolet light. EPROMs are typically built using a floating-gate avalanche MOS device. This is a MOS transistor with an additional isolated thin film (the floating gate) interposed between the MOS control gate and the channel. By pumping charge into the floating gate, the effective threshold voltage of the MOS transistor can be changed, and this threshold voltage change is detected by a sense amplifier. To write a cell, the channel is typically driven hard, with a high voltage on the control gate. Secondary carrier multiplication in the channel creates hot electrons, which are attracted into the floating gate. Thus the programming of a conventional EPROM requires the application of a high voltage (e.g. 10 or 15 V) to achieve the high currents needed. Moreover, programming is typically quite slow, e.g. several milliseconds per bit. To erase a cell, it is exposed to ultraviolet light. The energetic photons excite energetic carriers, which can pass through the dielectric layer to neutralize the charge on the floating gate. Thus EPROMs normally need a package with a quartz window. EPROMs are very commonly used, since they are cheap and their timing standards are familiar. EPROMs are also referred to as UVPROMs. An "electrically erasable programmable read-only-memory," or EEPROM or E 2 PROM, can be electrically written and electrically erased. EEPROMs, like EPROMS, are typically floating-gate devices. However, in an EEPROM the write and erase operations typically use tunnelling. Thus, the programming of a conventional EEPROM requires the application of a high voltage (e.g. 15 or 20 V). Programming and erasure are typically quite slow, e.g. several milliseconds per bit. EEPROMS are less commonly used than EPROMs, since they tend to be more expensive and to require even higher voltages. A more recent modification of the EPROM is the Flash-EPROM which is electrically erasable in blocks and does not have the bit-by-bit programmability of the EEPROM. Other rewritable non-volatile memory technologies include core" memory technology used in the computers of the 1 950s and early 1960s. U. S. Patent No. 4430704 discloses a programmable bootstrap loader apparatus, for a computer system, including an alterable non-volatile storage memory for storing a set of instructions forming a bootstrap loader program, selected elements of the bootstrap loader program being alterable under the control of firmware means included in the alterable non-volatile storage memory. PATENT ABSTRACTS OF JAPAN (vol. 12, no. 456, P-793, 3303, November 30, 1988) discloses a start-up system, for a computer, which includes means for detecting damage in the main boot area of a memory which is divided into a main boot area and a sub-boot area, the system effecting start-up from the sub-boot area of the memory when damage to the main boot area is detected and, subsequently, copying the contents of the sub-boot area to the main boot area. U. S. Patent No. 4663707 discloses a data processing apparatus including a first non-volatile memory connected directly to a computer means for providing a first level of bootstrap data and a second non-volatile memory cotmected to the computer means through a bootstrap controller for providing a second level of bootstrap data, the data in the second non-volatile memory being alterable and the computer means including hardware means for effecting the transmission of data from the first and second memories to the computer means. The present invention provides a computer system as defined in claim 1 and a method as defined in claim 4. Preferably, the computer system includes a multi-element diagnostic display for indicating the result of an operation to overwrite instructions held in the electrically rewritable first non-volatile memory and, preferably, the second non-volatile memory is an ultraviolet-erasable programmable read-only-memory (UVPROM). Flash-EPROMs or other rewritable non-volatile memories may be used for the rewritable first non-volatile memory. Preferably, the method includes the steps of reading start-up instructions from the electrically rewritable first non-volatile memory, subjecting the read-out start-up instructions to validity checks and, when a validity check is failed, overwriting the start-up instructions held in the electrically rewritable first non-volatile memory by the start-up instructions held in the second non-volatile memory. Since either memory may need to be the target, both memories are mappable to the same address. Note that this causes some difficulty in writing to the electrically rewritable first memory since, if it is not in the memory map it cannot be written to. In this instance, this difficulty is avoided by mapping the core software out to RAM, and then commanding an address configuration change to access the other boot memory. If one boot memory is being copied onto the other, then the contents of the source memory must also be copied out. As noted above, the default mapping of the boot memory address, at initial power-up, is controlled by a physical switch. However, thereafter, a peripheral memory controller chip controls the mapping of the boot memory address. Thus, by issuing a command to this peripheral chip, the core software can change this mapping. Thus, to write to the boot memory, the core software copies itself out to a RAM location, and commands the microprocessor to branch into the RAM address. The bit to select the boot memory is then toggled, so that writes to the boot memory addresses are now directed to the other boot memory (i.e. to the boot memory which was not the source of the code being executed). The desired data can then be written into the target boot memory. Note that, if the source of the data is in the active boot memory, that code must be written out into RAM before the boot memory address toggle is switched. The starting address in the boot software is occupied by a small (and strongly protected) software core, which performs sanity checks, and also provides the needed supervisory functions for boot software upgrading and replacement. Thus, the disclosed computer system solves the problem of performing BIOS restoration/upgrades in-situ (i.e. without removing the FLASH boot memory ROM from the system). The end-user (or a service technician) can program BIOS code into the FLASH without any specialized external hardware or software ROM-programming tools. After any hard reset of the system, the core software detects whether the boot software is corrupted, and whether the user has entered a request for upgrade. If these conditions have occurred, the core software performs the FLASH programming from the appropriate data source. In the presently preferred embodiment, the core software provides for the following three classes of cases. These cases together provide coverage for all conceivable field conditions: First case: While executing reset code from the FLASH, the system BIOS and/or video BIOS are found to have a bad checksum. In this case, power-on-self-test and booting is impossible, therefore, the boot code prompts the user to insert a diskette containing system and video BIOS code and reprograms the FLASH. In the presently preferred embodiment, this is done with the assistance of a small 4-character diagnostic display which is mounted directly on the system chassis. This display is referred to as SmartVu TM . When the system and video BIOS programming is successfully completed, the user is prompted (via SmartVu) to reset the system. Normal POST and boot should follow. Second case: While executing reset code from the FLASH, the boot code detects a "CMOS" flag setting indicating a user requested upgrade. (Personal. computers normally contain a battery-backed CMOS memory which stores configuration parameters; in system discussions, this memory is often referred to merely as the "CMOS" although non-CMOS memories can be used). The boot code then prompts the user (via SmartVu) to insert a diskette containing the upgrade system and video BIOS code. When the system and video BIOS programming is successfully completed, the user is prompted (via SmartVu) to reset the system. Normal POST and boot should follow. Third case; While executing reset code from the UVPROM, the boot code detects that a FLASH is present and that its protected 8k boot sector is jumpered for programming. Since the UVPROM is intended as a secondary ROM device, this condition is understood as a request for FLASH programming and the entire contents of the UVPROM, including the boot code in the upper 8k sector is copied into the FLASH. When the entire FLASH is successfully programmed, the user is prompted to reset the system. If the FLASH is selected as the primary ROM device, normal POST and boot should occur from the FLASH. Note that the foregoing steps may require the CPU to ascertain, while it is running boot code, which memory is the source of the code. This is accomplished, in the presently preferred embodiment, by letting the CPU read a register in a peripheral chip. The preferred rewritable boot memory is a sector-protected Flash-EPROM. The sector which contains the software core is actually protected by a jumper, which must be physically moved before the software core can be overwritten. This provides additional robustness. Because the core software may have to read from floppy disk, it includes the necessary overhead routines to perform this. These routines are generally similar to the BIOS functions under INT13h. The first non-voltaile memory may be a mask ROM, PROM or UVPROM which holds the basic system operating instructions including the bootstrap and BIOS instructions required for system activation. Those instructions may be substantially unalterable, and the system can be activated or reactivated by placing it under the control of the first non-volatile memory Preferably, the bootstrapping instructions held in the second non-volatile memory are such as to effect the over-writing of instructions held in the rewritable non-volatile memory by the bootstrapping instructions held in the second non-volatile memory, following a hard reset of the system. The rewritable non-volatile memory may be a FLASH EPROM or an electrically programmable and erasable ROM to which can be written instructions, including instructions which effect the writing of instructions from an external source to the rewritable non-volatile memory. Thus, instructions can be written to the rewritable non-volatile memory and the rewritable non-volatile memory can then be used as the source of activating instructions for the computer system, with the flexibility that the computer system can itself rewrite at least some of the instructions held in the rewritable non-volatile memory. The computer system can be returned to the operating configuration provided by the instructions held in the first non-volatile memory at any time by means of a user-operated switch, say. Preferably, the computer system includes manually operable means which has a first setting for preventing the over-writing of instructions held in the rewritable non-volatile memory and a second setting permitting the over-writing of instructions held in the rewritable nonvolatile memory. The provision of a means which is only operable manually to inhibit the over-writing of selected instructions held in the rewritable non-volatile memory makes it possible to protect those selected instructions from accidental alteration. Preferably, the instructions are such as to make the computer system capable of writing the instructions from the second non-volatile memory to the rewritable non-volatile memory so that the instructions held in the second non-volatile memory can be readily written to the rewritable non-volatile memory. Preferably, the computer system includes a user settable switch for selecting the second non-volatile memory as its source of bootstrapping instructions and is capable of reversing the switch setting to select the rewritable non-volatile memory as its source of activating instructions thereafter. That is, the computer system is capable of activation in accordance with the instructions held in the second non-volatile memory, following which it can write those instructions to the rewritable non-volatile memory, after which it switches control to the rewritable non-volatile memory. Preferably, the computer system includes multi-element diagnostic display means capable of indicating the result of an operation to over-write instructions held in the rewritable non-volatile memory. The diagnostic display means may be a multi-character display, for example, a 4-character display linked to a sub-system for checking on whether the writing of system and video BIOS has been successful and providing an apparopriate indication. Preferably, the method of operating the computer system includes the steps of reading bootstrapping instructions from the rewritable non-volatile memory, subjecting the bootstrapping instructions to validity checks as they are read and, when a validity check is failed, overwriting the bootstrapping instructions held in the rewritable non-volatile memory with the bootstrapping instructions held in the second non-volatile memory. The method for operating the computer system may comprise the steps, whenever the system has undergone a hard reset, of immediately performing the following operations in a programmable central processing unit (CPU): if the said CPU is executing software from a rewritable nonvolatile boot memory, performing a checksum operation on the basic system software in the said rewritable nonvolatile boot memory, and, if a checksum error is found, prompting the user to provide a data source for the basic system software, and thereafter, reprogramming the said rewritable non-volatile boot memory from the data source provided by the user. A modified method of operating the computer system comprises: reading at least one bit from a predetermined data location, and if the said bit is in a first state, prompting the user to provide a data source for the basic system software, and thereafter, reprogramming the said rewritabole non-volatile boot memory from the data source provided by the user. If the said CPU is executing software from a second nonvolatile boot memory which is not the same as the said rewritable nonvolatile boot memory and if the said rewritable nonvolatile memory is not currently write-protected, THEN the contents of the said rewritable non-volatile memory are overwritten with the contents of the second non-volatile boot memory. The method of operating the computer system may comprise the steps, whenever the system undergoes a power-up transition, of immediately performing the following operations in the system microprocessor: ascertaining whether the said microprocessor is currently executing boot software from a rewritable nonvolatile boot memory or from a second nonvolatile boot memory which is not the same as the said rewritable boot memory but which is mappable onto the same address as the said rewritable boot memory, if the said microprocessor is executing software from said rewritable boot memory, performing a checksum operation on the basic system software in the said rewritable boot memory, and if a checksum error is found, prompting the user to provide a data source for the basic system software, and thereafter, reprogramming the said rewritable boot memory from the data source provided by the user, followed by prompting the user to reboot the system. The method of operation at a power-up transition may include reading at least one bit from a predetermined data location and if the said bit is in a first state, prompting the user to provide a data source for the basic system software, and thereafter, reprogramming the said rewritable boot memory from the data source provided by the user followed by prompting the user to reboot the system. If the said bit is not in the first state, the system executes a power-on-self-test routine from the said rewritable boot memory. If the said microprocessor is executing software from said second boot memory and if said rewritable nonvolatile memory is not currently write-protected the system copies the entire contents of the said second boot memory and overwrites the contents of the said rewritable nonvolatile boot memory, thereafter prompting the user to reboot the system. If any other condition exists, the system executes a power-on-self-test routine from the said second boot memory. The method for operating the computer system may comprise, during normal operation, the steps of: executing a sequence of instructions in at least one CPU which can fetch instructions in a programmable sequence from a memory; initiating a system reset operation which includes a step of resetting the said CPU when a power restoration or software reset command occurs, executing in the said CPU, substantially immediately after the said step of resetting the said CPU, a core software program, stored in a rewritable nonvolatile boot memory, which tests the integrity of data in the said rewritable boot memory, and prompts the user to supply replacement data for said rewritable boot memory is corrupt. If the said CPU executes the said core software program successfully, then a power-on-self-test program is executed subsequently in the said CPU. If the said CPU executes the said power-on-self-test software program successfully, then the said CPU is launched on the execution of operating system software. Preferably, the said rewritable nonvolatile boot memory consists essentially of a Flash EPROM or an electrically programmable and erasible read-only-memory. Preferably, the said second nonvolatile boot memory consists essentially of a programmable-read-only-memory which is not electrically erasable. The present invention will be described with reference to the accompanying drawings, which show embodiments of the invention wherein: Figure 1 is a flow chart which shows key of the invention. Fig. 2 shows a hardware configuration which permits switching between alternative boot memories in an embodiment of the invention. The preferred embodiment is an 80486-based EISA-bus PC system. General features of the EISA bus are described by Glass, "Inside EISA," Byte magazine November 1989, pp/ 417ff, and in the EISA specification. General features of the Intel 80486 are described by Sartore, "The 80486: A Hardware Perspective," Byte Magazine IBM Special Edition, Fall 1989, pp. 67ff. Further detailed background on the 80486 may be found in the "80486 Programmer's Reference" and the "80486 Hardware Reference Manual," both available from Intel. Many of the architectural features of this system are conventional in modern PC systems. However, several unusual features are used. One of these is the provision for dual boot memories, with hardware and software switching betwen them. Another notable feature is the use of the "SLOB" controller chip described below. In the presently preferred embodiment, the system motherboard includes a custom chip, referred to herein as the "SLOB" chip, which performs a variety of special functions. These include reset control, X-bus transceiver control, and control of the boot memories and CMOS nonvoltaile memory. The "X-bus," or "extension bus," is an extension of the system bus, but is not directly connected to it. Instead, data is selectably transferred from the S-bus to the system bus, or vice versa, by bidirectional transceivers. The X-bus is commonly used, in PC architectures, to provide easier loading requirements for a variety of devices on the motherboard. The software core, in the presently preferred embodiment, resides in the protected 8k boot sector of a FLASH ROM or in the upper 8k of a 128k UVPROM. Selection of the primary ROM device is accomplished via a physical switch. Figure 2 shows more detail of how this is implemented. The SLOB chip supplies chip enable (CE) signals separately to the FLASH EPROM 220 and to the UVEPROM 230 (and also to the NVRAM 240). An output enable line OE is connected to both boot ROMs, and address lines are also provided to both. A hardware switch provides a line ROMIN to the SLOB chip, to define which boot memory is the initial default target. In the presently preferred embodiment, the FLASH EPROM has sector-by-sector protection. (This feature is found in the 28F001B type chip available from Intel). In the presently preferred embodiment, one sector 220A, of only 8K bytes, is dedicated to the core software. This sector is protected by a hardware jumper, so corruption of the core software is unlikely. To achieve automatic programming of the Flash memory from a plug-in ROM, the hardware must provide a switching mechanism that allows software to boot from one source and then toggle between sources. This switchability is also required to access EISA configuration from Flash if running BIOS out of a plug-in ROM. A user settable hardware switch determines which boot memory supplies the boot code at power-up or cold boot. This switch sets the polarity of a bit called ROMIN which is decoded by the hardware control logic to enable the selected boot source. This bit is readable from an I/O port, so that software can determine the source of the boot code, i.e. ROM(bit=0) or Flash (bit=1). The software then has the ability to toggle subsequently between accessing ROM or Flash by setting a bit that assumes the opposite state of ROMIN after a cold boot. This bit is called ROMEN and enables Flash when 0 and ROM when 1. This bit is readable as well as writable via an I/O port. This mechanism allows hardware to boot from ROM then gives software the ability to determine the presence of Flash memory and program Flash automatically by transferring the contents of the BIOS in ROM to the Flash. The chip referred to herein as the TRANE chip is a custom memory controller. Besides performing normal DRAM management functions, this chip also provides selection, by memory domains, of which memory areas will be cached or not. The actual implementation of the core software will now be described in detail by way of example only. It must be understood that this specific implementation is merely illustrative. Figure 1 is a flow chart which schematically shows key portions of the methods used in the computer system of the presently preferred embodiment. When the 80486 first comes out of reset, it comes up in real mode (but the high address bits are held high, so that the processor can go to the top of the 4-Gigabyte (32-bit) memory space. The processor accesses adddress FFFFFFFOh. See Glass, "Protected Mode", Byte Magazine December 1989, pp. 377ff. Preferred Assembly Language Implementation The actual implementation of key portions of the core software, in the presently preferred embodiment, will now be given. The following listings in documented assembly language also contain a large number of informal comments. These comments do not necessarily define the scope of the invention, but will help to explain the motivation, structure, and workings of the presently preferred embodiment. Some of the procedures actually used, in the presently preferred embodiment, will now be described in detail. Procedure 8KBOOT STRT Procedure 8kboot_strtis the power-on-reset entry point into the 8k boot sector code for a 128k FLASH EPROM. This code along with a reset vector is located in the upper 8k boot sector of a 128k FLASH EPROM. The reset vector will be located at 1fff0h (physical ROM address), and the start of this routine will be located at 1e000h (start.of the 8k boot sector). The reset vector will contain a NEAR jmp to this code, so execution will start in processor real mode, ROM native mode, at logical address 0ffffe000h. This procedure implements most of the steps in the flow chart of Figure 1. Specifically, this procedure: Saves the state of EAX and DX for later use by POST. Initializes a base address for the DRAM controller (the TRANE chip, in the presently preferred embodiment). Disable interrupts (NMI and INTR). If warm boot, jmp into POST SHUTDOWN routine. Else, if power-on check to see if we're running out of a UVPROM or the FLASH. If FLASH, jump to the "bootFLASH" procedure which programs the flash if the BIOS is corrupted or if the user has requested an upgrade. If UVPROM, jump to the "bootUVPROM" code which copies the UVPROM to the FLASH if a FLASH exists. If either "bootFLASH" or "bootUVPROM" does not program the flash, control returns to "do_reboot" which displays a SmartVu message and halts. NOTE: Because of the redundancy between this code and early parts of POST, (RESET, SHUTDOWN) the BIOS is NOT dependent on this code. This means that a working BIOS can be built for a 64k non-FLASH ROM architecture by simply removing this module from the build process. The original 64k BIOS reset/initialization logic has been left untouched. Procedure BOOTUVPROM Procedure bootUVPROMcontains the 8k power-on logic executed when a UVPROM is installed. When cold-booting from a UVPROM, this code is executed to look for a FLASH ROM and if present, attempts to copy the entire UVPROM contents into the FLASH. If FLASH programming is unsuccessful for any number of reasons, e.g., FLASH is not present, 8k boot sector is not jumpered for erase/programming, etc., then this routine just bails back into POST. Procedure BOOTFLASH Procedure bootFlash contains the 8K power-on logic executed when the system boots from the Flash. The steps are as follow: Checksum the system and video BIOS (96K). If checksum is good, go to I. If checksum is bad, go to II. I. - Does the user request a BIOS upgrade? If upgrade is selected, go to II. If upgrade is not selected, we are done with this routine and shall go to do regular POST. II. - Reset the upgrade option to prevent an endless loop. Initialize a lot of stuff. Initialize 106 so that we have SmartVu. Slob initialization. Trane initialization and get at least 2 meg of DRAM. Initialize the refresh counter. Set refresh page to 0 through the DMA controller. Copy code to RAM and execute from RAM. Set up stack. Test and initialize timers. Calibrate count before first call to DLY100. Set up the DMA controllers. Set up the interrupt descriptor table. Set up the interrupt controllers. Initialize the floppy subsystem. Copy the BIOS from floppy. If unsuccessful, display error message and halt. Make sure we indeed have a valid BIOS in RAM. Set the Flash up for programming. Copy the BIOS from RAM to Flash. If unsuccessful, display error message and halt. Inputs: Native-mode, protected-mode, Trane has grabbed its I/O address. Outputs: Either halts or go to do regular POST. If the BIOS checksum is good and no upgrade is requested, this routine will jump to do regular POST. If the BIOS checksum is bad or an upgrad is requested, then this routine will halt at the end. Other Procedures The actual assembly language realization used contains numerous other procedures, which will now be detailed. Most of these procedures are completely conventional. However, any of these procedures which have any particular relevance to the claimed inventions are actually listed below. INITSTUFF This procedure initializes the "SLOB" and "TRANE" chips. RAM_init Procedure RAM_initperforms RAM initialization for the 8k boot code, initializes TRANE, identifies memory, initializes it, turns on refresh and points RCR0 to a block from 0 - 2Mb. Inputs: HSM_xx ... Host state machine initialization tables. FS ... Must point to a 4Gb data selector based @ 0. bp contains the return address. NOTE: It doesn't matter what type of SIMM we have identified. The presence test assumes that it's a 256kbit chip and initializes the RCR accordingly. If it's actually a 1Mbit or a 4Mbit SIMM it should still behave ok if it's programmed as a 256kbit. Since all we need is 128kb of RAM for copying the UVPROM, who cares what size the SIMM really is? Outputs: SUCCESS ... If successful, returns the following: All SIMMs identified as present or not and tabulated in CMSMTPL below. CMSMTPL... CMOS byte containing the SIMM map. RCROM points to 2 Mb of DRAM. SIMMs for this RAS programmed as 256kbit devices. Refresh enabled. FAILURE ... If no RAM can be found, issues 'fRAM' to SmartVu and waits forever. $INIT _ VL106 Procedure $init_vl106 initializes the vL106. The VL106 is a chip which, among other functions, replaces the 8742 keyboard handler.) PMODE This procedure is a Protected mode entry routine. Inputs: DS ... points to the segment containing "gdt_ptr" and NULL_IDT. RMODE This routine is created for the floppy code to run in real mode. Inputs: none. Outputs: real mode. PMODE2 This routine is created for the floppy code. This will switch the execution back to protected after the floppy code is executed. [Uses different IDT and GDT tables ub low RAM.] Inputs: none. Outputs: protected mode. CMOSSUM This routine checksums the CMOS range 10h thru 2Dh. Inputs: DI ... contains NEAR return offset. Outputs: none. FLASH_MSG Procedure flash_msg displays the SMARTVU message in EAX, waits CX seconds and returns to the NEAR address in DI. Inputs: SS ... Writable segment pointing to code. Dl ... Contains the NEAR return address. CX ... The number of seconds to delay after displaying the SMARTVU message. EAX ... Contains the SmartVu message. DELAY Procedure delay waits for CX seconds. This procedure uses the RTC to implement a delay specified by the count in seconds in CX. If the RTC battery is bad, we just execute a fixed delay loop of DUMMY_DELAY iterations. Inputs: cx ... Countains the number of seconds to delay. GET_SEC This routine reads the seconds count from the RTC (real-time clock), and waits if a time update is in progress. Inputs: SI ... Contains the NEAR return address. Outputs: AL ... Contains the RTC seconds count. BEEP This routine beeps! Inputs: cx = frequency. di = near return address. Outputs: none. INIT_TIMER This routine tests and initializes the timers. SETUPDMA Procedure setupDMA will set up the DMA controllers just like the regular POST. The code are identical so as not to introduce any problem with the INT13H routine. Inputs: Native mode, protected mode. Outputs: If error, let regular POST reports the error. If no error, DMA controllers are now ready for the INT13H routine. SETUPPIC Procedure setupPIC will set up the PICs just like the regular POST. The code is identical to that used in the POST, so as not to introduce any problem with the INT13H routine. Inputs: Native mode, protected mode. Outputs: The PICs are now ready for the INT13H routine. COPY Procedure copy copies the new BIOS from the floppy to RAM. The steps are as follow: Find out if file exists. The file has to be on a 1.2M floppy in the root directory with a filename of "DELLBIOS.BIN". Inputs: none. Outputs: Carry flag set if error. FILEEXIST Procedure fileExist reads in the root directory, and searches to see whether file "DELLBIOS.BIN" is in the directory. Inputs: none. Outputs: Carry clear if file exists. ax has the first disk cluster if file exists. bx:dx has file size. SETTYPE Procedure setTypedetermines the type of floppy drive and sets the drive parameters accordingly. Inputs: none. Outputs: Parameters are initialized. COPYFILE Procedure copyFile copies the desired file from drive 0 to RAM. The steps are as follow: Make sure the file size is what we expected. Read the FAT table. Copy the file to DRAM. Inputs: ax has the first disk cluster of the file. bx:dx has file size. es=GDTD_BUFFER. Outputs: Carry flag set if error. SANITYCHECK Procedure sanityCheck will try to verify that the BIOS copied is a legitimate Dell BIOS. Inputs: BIOS (112K) spans from 5000:0000 thru 6000:C000. Outputs: Carry set if we do not have a legl BIOS. NEXT Procedure next gets the next link from a 12-bit FAT. Input: ax = current entry number. Output: ax = next element in the chain. REL2ABS Procedure rel2abs converts the relative sector number to the absolute sector location. Input: ax = relative sector number. Output: ch = track number. cl = sector number. dh = head number. dl = 0 = drive number. GETFAT Procedure getFat reads in the FAT table. Inputs: es = GDTD_BUFFER. Outputs: Carry set if error. If successful, FAT resides from 4000:0000 thru 4000:0E00. PROGRAM Procedure program writes data into the flash ROM. Inputs: none. Outputs: Carry set if error. ERASE_SECTOR Procedure erase_sectorperforms the following steps: Clear the status register. Set the FLASH to read status mode. Set the FLASH for erase. Do the erase. Verify the erase is successful by reading the status register. Set the carry flag if erase unsuccessful. Clear the status register. Set the FLASH to read array mode. Inputs: es:edi = address of sector to be erased. FLASH program/erase better be enabled before calling this routine. Outputs: If successful, carry flag cleared. ; ; WARNING!!! - the FLASH program jumper must be set for program/erase. ; PROGRAM_SECTOR Procedure program_sectorwrites a sector of the flash ROM. Inputs: ecx = number of bytes to program. ds:esi points to beginning of data. es:edi points to beginning of sector. The steps are as follow: Clear the status register. Set the FLASH to read status mode. Go and program the sector. Abort if error with the carry flag set. Clear the status register. Set the FLASH to read array mode. Outputs: If successful, carry flag cleared. ; : WARNING!!! -- The FLASH program jumper must be set for program/erase. ; ENABLE_fPROGRAM Procedure enable_fProgramenables program/erase operations on the FLASH ROM. Inputs: none. Outputs: FLASH is ready to be programmed or erased. DISABLE_fPROGRAM Procedure disable_fProgramdisables FLASH program/erase. Inputs: none. Outputs: FLASH cannot be programmed or erased. USECWAIT Procedure usecWait creates cx microseconds of delay. Inputs: cx = number of usec. Outputs: cx destroyed. CLR_FLASH_STATUS Procedure clr_Flash_status clears the FLASH status register. This routine was created because the new spec requires the address to be at 00000h of the Flash. Inputs: none. Outputs: Flash status register cleared. READ_FLASH_STATUS Procedure read_Flash_statusreads the FLASH status register at 00000h of the Flash. Inputs: none. Outputs: Flash status register read in al. NMI_ISR Procedure NMI_ISR is a dummy interrupt handler, which swallows any NMMI interrupt. DMATST This routine tests the DMA address and word count registers. Input: CX = # of ports to test DX = first port to test SI = increment between ports Output: flags ? AL = ? AH = ? CX = 0 CALB_SPD Procedure CALB_SPD ("calibrate speed") sets DLLY_CNT with count for 100 us FDISR Procedure fdISR is the floppy drive controller interrupt handler. The steps are as follow: Send EOI to master PIC. Set interrupt bit in DRVSTAT to indicate an interrupt has occurred. INT13H Procedure int13h determines and executes the desired intl3h procedure functions. RESETFLOP Procedure resetFlopresets the floppy system. This is part of the INT13H procedure. Inputs: ah = 0 dl = drive number (0-3), bit7 = 0 for floppy. Outputs: Carry flag set if error. ah = status/error code. ds:ERRSTAT(FDATA) = ah. READSECTOR Procedure readSectorreads al sectors from the floppy. Inputs: ah = 02h. al = number of sectors. ch = track number. cl = sector number. dh = head number. dl = drive number. es:bx = address of buffer. Outputs: Carry flag set if error. al = number of sectors transferred, ah = status = ERRSTAT. SETCARRY Procedure setCarrysets the carry flag on the stack. This is part of the INT13H procedure. CLRCARRY Procedure clrCarryclears the carry flag on the stack. This is part of the INT13H procedure. Inputs: none. Outputs: Carry flag in the flag register on the stack is cleared. Interrupt flag also set. DSKRESET Procedure dskResetresets the floppy system. This is part of the INT13H procedure. The steps are as follow: Disable interrupts. Clear DRVSTAT and ERRSTAT. Get floppy motor status. Issue reset command. Turn off reset command. Enable interrupts and wait for reset result interrupt. Check result. Inputs: dl = drive number (0-3), bit7 = 0 for floppy. Outputs: Carry flag set if error. ds:ERRSTAT(FDATA) = ah = error code if error, else 0. WAITINT Procedure waitInt waits for a FDC interrupt. This is part of the INT13H procedure. This routine uses a regular wait instead of int15h. Inputs: none. Outputs: Carry flag set if timeout error, else not. ERRSTAT bit7 = 1 if timeout. FDCRDY Procedure fdcRdy waits for the floppy controller to be ready. This is part of the INT13H procedure. Inputs: none. Outputs: Carry flag set if timeout. SISSTAT Procedure sisStat senses the interrupt status. This is part of the INT13H procedure. Inputs: none. Outputs: Carry flag set if error, ERRSTAT set, ah = FDC status, else Carry flag clear and al = present cylinder. WRTCMD/WRTCMDA Procedures wrtCmd and wrtCmdA write commands to the FDC, and are part of the INT13H procedure. Inputs: al = command. ds points to FDATA. Outputs: Carry flag and ERRSTAT set if error. ah, dx destroyed. RSLTRD7/RSLTRD Procedure rsltRd7 reads 7 result bytes from the FDC. Procedure rsltRd reads cx result bytes from the FDC. These are part of the INT13H procedure. Inputs: cx = number of result bytes to read. ds points to FDATA. Outputs: al = FDC status. ah = FDC ST0, only valid if no carry. ERRSTAT bit 7 = 1, carry set on timeout. ERRSTAT bit 5 = 1, carry set if FDC results cannot be flushed. Carry set if less results available than expected. DSKST = FDC ST0, only valid if no carry. dx non-zero. I82077EXIST Procedure i82077exist determines if a i82077 FDC is installed. This is part of the INT13H procedure. Inputs: none. Outputs: Carry flag set if i82077 installed and the FIFO enabled. stk_tmp bit0=1 if i82077 installed and bit1 = 1 if FIFO enabled. MLTCMD2/MLTCMD Procedure mltCmd2 writes 2 commands to the FDC. Procedure mltCmd writes cx commands to the FDC. These are part of the INT13H procedure. Inputs: cx = number of bytes to write (mltCmd). bx = starting table offset. Outputs: es:si = disk parameter block. ERRSTAT bit7 = 1 on timeout, bit5 = 1 on controller error. Carry flag set on timeout or controller error, else not set. DPBADR Procedure dpbAdr puts the address of the disk parameter block into es:di. This is part of the INT13H procedure. Inputs: none. Outputs: es:si points to disk parameter block. CONFIGURE Procedure configure issues the configure command to enable the FIFO in the i82077 FDC. This is part of the INT13H procedure. Inputs: ah = byte 2 of configure command. Outputs: Carry flag set if FDC error, else cleared. DSKMOT Procedure dskMot turns the floppy drive motor on. This is part of the INT13H procedure. Inputs: dl = drive number. Outputs: none. CHKCHG Procedure chkChg checks the change line on the floppy drive. This is part of the INT13H procedure. Inputs: none. Outputs: Carry flag set if error. GETDRVINFO Procedure getDrvInfogets drive information from HDCFLG. This is part of the INT13H procedure. Inputs: none. Outputs: Low 3 bits of al = drive information. CLRCHG Procedure clrChg tests and clear the change line. This is part of the INT13H procedure. Inputs: dl = drive number. Outputs: Carry flag set if timeout. ERRSTAT = timeout or change line error. DOSEEK/DOSEEK2 Procedures doSeek and doSeek2 will seek to track specified by ch. This is part of the INT13H procedure. Inputs: ch = track to seek. Outputs: Carry flag and ERRSTAT set if error. DRIHEDSEL Procedure driHedSelloads the head (HDS) and the drive (DS1, DS0) parameters to the FDC. This is part of the INT13H procedure. Inputs: none. Outputs: none. INITDMA Procedure initDMA will initialize the DMA controller for floppy operations. This is part of the INT13H procedure. Inputs: none. Outputs: Carry flag and ERRSTAT set if error. HEADSETTLE Procedure headSettle conditionally waits for the head to settle. This is part of the INT13H procedure. Inputs: dx non-zero if head settle wait needed. Outputs: es:si points to DPB. SPINUP Procedure spinup conditionally waits for the floppy to spinup. This is part of the INT13H procedure. CHKTYP Procedure chkTypchecks the media type. This routine is called prior to read/write operation to verify and update, if necessary, FDMED. Returns with the carry flag set if no remaining valid FDMEDs to try. This is part of the INT13H procedure. Inputs: FDMED, ERRSTAT (if non-zero, it is a retry). bx = drive. Outputs: FDMED updated: ERRSTAT = carry flag = 0 if any more valid rate/step combos. FDMED restored: FDOPER = 0. ERRSTAT and carry flag set if no more valid rate/step combos.; FDTYPIF Procedure fdTypIfgets floppy disk type from CMOS if CMOS is valid. This is part of the INT13H procedure. Inputs: none. Outputs: Carry flag set if CMOS invalid, else al = drive type, zero flag set if no drive or type unknown, top of ah non-zero if another drive. FDTYPE Procedure fdTypegets floppy disk type from CMOS. This is part of the FDTYPIF routine, and part of the INT13H procedure. Inputs: none. Outputs: al = drive type, zero flag set if no drive or type unknown, top of ah non-zero if another drive. SETRATE Procedure setRate sets the transfer rate. This is part of the INT13H procedure. Inputs: bx = drive number. Outputs: Rate control port updated. CHKRES Procedure chkRes reads and checks the results from the FDC. This is part of the INT13H procedure. Inputs: none. Outputs: Carry flag set if error. al = number of sectors transferred. AFTERTRY Procedure afterTrysets the zero flag if there is still more retry after an unsuccessful operation. This is part of the INT13H procedure. Inputs: none. Outputs: Zero flag set if there is still more retry. RESTYP Procedure resTyp forces FDMED[bx] media known and restores compatible low bits. This is part of the INT13H procedure. Inputs: ah = top three bits of FDMED[bx]. Outputs: FDMED[bx] bit4 = 1. STODRVINFO Procedure stoDrvInfo puts the drive information in al into HDCFLG. This is part of the INT13H procedure. Inputs: al = drive information. bx = drive number. Outputs: Drive information in [bx] half of HDCFLG. INITFD Procedure initFD will initialize the floppy subsystem and all the variables used by the INT13H routine. This is part of the INT13H routine. Inputs: none. Outputs: DRVSTAT, FMOTS, FDTIMO, ERRSTAT, DSKST, HDCFLG, FDMED, FDOPER, WTACTF, FDRATE, are all initialized. DSKTEST Procedure dskTest will test and determine drive type. Inputs: ss:bp points to stack frame for disk driver. stk_dl[bp] = drive number. Outputs: FDMED[drive #], HDCFLG initialized. Carry flag set if no drive. SDRVST Procedure sDrvSt senses the drive status. Inputs: none. Outputs: Carry flag set, ERRSTAT set if error. Carry flag clear, ah=FDC's ST0 if no error. Zero flag set if track 0 reached. CKFDCFG Procedure ckFdCfg checks the floppy configuration data against the actual installed hardware. Inputs: byte ptr stk_dl[bp] = drive number. si points to the media type for that drive number. Outputs: Carry set if different configuration. CMREAD Procedure CMREADis a Subroutine to Read a CMOS register. Input: AL = CMOS register address to read Output: AL = CMOS register value Interrupt Flag cleared Carry Flag cleared Zero Flag cleared. CMWRT This is a Subroutine to Write a CMOS register. Input: AH = CMOS register address to write, Bit 7 = 0 enables NMI AL = Value to write to CMOS register Output: Interrupt Flag cleared Carry Flag cleared Zero Flag cleared. DLY100 This procedure will delay for 100 us. The loop count for the delay function is taken from DLY_CNT. DLY_CNT is set during ATPOST, and whenever turbo speed is changed by the routine CALB_SPD. It takes no inputs and gives no outputs. Further Modifications and Variations It will be recognized by those skilled in the art that the innovative concepts disclosed in the present application can be applied in a wide variety of contexts. In particular, the disclosed innovations are not by any means limited to DOS systems, nor to systems using 80x86 microprocessors, nor to systems using a single microprocessor as the CPU. The disclosed innovations provide generally applicable architectural techniques, which can be applied to a wide variety of computer systems, including high-performance systems and multiprocessing systems. It should also be noted that the source for the user-supplied BIOS code does not have to be a floppy drive. For example, a tape cartridge or a dial-in telephone interface could be used instead. In addition, although the Flash EPROM is the preferred device technology for the second nonvolatile boot memory, it should be recognized that other nonvolatile storage technologies can be used if they become practical. Thus, many of the innovative features of the presently preferred embodiment can be directly adapted to a system using EEPROMs, battery-backed SRAM chips, ferroelectric RAMs, or future technologies. It should also be noted that BOTH of the boot memories can be rewriteable nonvolatile memories if desired. Even though this arrangement provides slightly less robustness than the preferred embodiment, it still provides a large added margin of safety over the use of a single rewriteable nonvolatile boot memory.

Claims: A computer system including: an electrically rewritable first non-volatile memory (220, 220A) for holding bootstrapping instructions required by the computer system after a hard reset of the system, a second non-volatile memory (230) which holds bootstrapping instructions required by the computer system after a hard reset of the system and a controller (210) through which the electrically rewritable first non-volatile memory is connectable to the computer system, characterised in that the electrically rewritable first non-volatile memory includes a first sector (220A), which can be protected against overwriting, for holding core bootstrapping instructions and a second sector (220) for holding further instructions, the second non-volatile memory is connectable through the controller (210) to the computer system and the computer system further includes: setting means capable of being set either to prevent or to permit the overwriting of the first sector (220A) of the electrically rewritable first non-volatile memory and user-operable selection means connected to the controller (210) for selecting either the electrically rewritable first non-volatile memory or the second non-volatile memory as the source of bootstrapping instructions for the computer system following a hard reset of the computer system, the bootstrapping instructions held in the second non-volatile memory being effective to copy bootstrapping instructions from the second non-volatile memory to the first and second sectors (220A,220) of the electrically rewritable first non-volatile memory when the user-operable selection means is set to select the second non-volatile memory as the source of bootstrapping instructions and the setting means is set to permit the overwriting of the first sector (220A) of the electrically rewritable first non-volatile memory and the core bootstrapping instructions supplied to the first sector (220A) of the electrically rewritable first non-volatile memory being effective, in response to a user-entry requesting upgrade in the computer system, to perform the overwriting of instructions held in the second sector (220) of the electrically rewritable first non-volatile memory from an external source. A computer system as claimed in claim 1, including a multi-element diagnostic display for indicating the result of an operation to overwrite instructions held in the electrically rewritable first non-volatile memory. A computer system as claimed in claim 1 or claim 2, wherein the second non-volatile memory is an ultraviolet-erasable programmable read-only-memory (UVPROM). A method of operating a computer system including an electrically rewritable first non-volatile memory (220, 220A) for holding bootstrapping instructions required by the computer system after a hard reset of the system, a second non-volatile memory (230) which holds bootstrapping instructions required by the computer system after a hard reset of the system and a controller (210) through which the electrically rewritable first non-volatile memory is connectable to the computer system, characterised by the steps of: providing in the computer system setting means capable of being set either to prevent or to permit the over writing of the first sector (220A) of the electrically rewritable first non-volatile memory and user-operable selection means connected to the controller (210) for selecting either the electrically rewritable first non-volatile memory or the second non-volatile memory as the source of bootstrapping instructions for the computer system following a hard reset of the computer system, wherein the second non-volatile memory is connectable through the controller (210) to the computer system, selecting the second non-volatile memory as the source of bootstrapping instructions when the user-operable selection means is set to select the second non-volatile memory as the source of bootstrapping instructions, copying core bootstrapping instructions from the second non-volatile memory into a first sector (220A) of the electrically rewritable first non-volatile memory and copying other start-up instructions from the second non-volatile memory into a second sector (220) of the electrically rewritable first non-volatile memory when the setting means is set to permit the overwriting of the first sector (220A) of the electrically rewritable first non-volatile memory, providing protection against the overwriting of the core bootstrapping instructions copied into the first sector (220A) of the electrically rewritable first non-volatile memory, selecting the electrically rewritable first non-volatile memory as the source of bootstrapping instructions for the computer system and using the core bootstrapping instructions to effect the overwriting of the bootstrapping instructions copied into the second sector (220) of the electrically rewritable first non-volatile memory by externally supplied bootstrapping instructions in response to a user entry requesting upgrade in the computer system. A method as claimed in claim 4, including the steps of reading bootstrapping instructions from the electrically rewritable first non-volatile memory, subjecting the read-out bootstrapping instructions to validity checks and, when a validity check is failed, overwriting the bootstrapping instructions held in the electrically rewritable first non-volatile memory by the bootstrapping instructions held in the second non-volatile memory.

Inventors: ABBOTT GARY W, CHAN WAI-MING RICHARD, SCHIEVE ERIC W, ZELLER CHARLES P, ABBOTT, GARY W., CHAN, WAI-MING RICHARD, SCHIEVE, ERIC W., ZELLER, CHARLES P.
Applicants: DELL USA LP, DELL USA L.P.
Application year: 1992
Main classification: G06F9
IPC codes: G06F9, G06F11, G06F15