WO2012155439A1

WO2012155439A1 - System and method for bios booting

Info

Publication number: WO2012155439A1
Application number: PCT/CN2011/080541
Authority: WO
Inventors: 程旭; 李皓; 郑衍松; 佟冬; 管雪涛
Original assignee: 北京北大众志微系统科技有限责任公司; 济南众志信息技术有限公司
Priority date: 2011-05-16
Filing date: 2011-10-08
Publication date: 2012-11-22
Also published as: CN102169446A; CN102169446B

Abstract

A method and a system for BIOS booting relate to the field of computer application. The method comprises that the interrupt service routine of the operating system interface module of BIOS is implemented in the form of OptionROM module; when the operating system of computer powers on, the on-board core module of BIOS initializes on-board devices and outputs the system information, a MAPPER module converts the system information into a system information sheet recognizable by the operating system interface module, the on-board core module initializes the interrupt service routine in sequence based on the information in the system information sheet. The solution provided by the invention can be applied to the computer system with the open-source BIOS based BIOS system, to boot the open-source operating system and the large-scale business non-open-source operating system.

Description

BIOS startup system and method

Technical field

The present invention relates to the field of computer applications, and in particular, to a basic input/output system (BIOS) booting system and method.

Background technique

Since IBM developed the basic input/output system (BIOS) for the world's first personal computer (PC) in 1981, in order to maintain backward compatibility, although various computer hardware and software emerged one after another, the traditional PC BIOS The hardware and software interface, its architecture has not changed much. The general-purpose PC BIOS consists of two parts: First, the board-level module, which is specific to each system platform, is used to initialize all the devices in the system platform to a stable state that can work, including the central processing unit (CPU), south bridge, north bridge. And the hardware modules connected to the north and south bridges; one is the interface module, which is generally applicable to all platforms, and serves as a general-purpose interface, and communicates with the board-level device by abstracting the board-level device to the unified interface of the operating system. Its functions mainly include: 1) Power On Self Test (POST), after the computer system is powered on, control is given to the BIOS, and the BIOS performs system detection, including initialization of the CPU and various conventional devices. Programming interval timer, programmable interrupt controller, direct memory access controller, etc.; 2) Initialize the registers of the cache memory, motherboard chipset, graphics card and related peripherals; 3) Save system settings, store in non-volatile In the memory; 4) Save the interrupt service routine in memory, and provide the call to the operating system startup process and running process. Typical interrupt service routines include INT10H's graphics service routines, INT13H's disk service routines, INT16H's keyboard service routines, and more.

However, with the development of computers, PC BIOS is not open due to hardware and software interfaces, industry industry specifications are extensive, PC BIOS running under x86 system is mostly implemented in assembly language, and assembly language provides less language-level abstraction. Complex, and the constant addition of new functional modules in the PC BIOS makes the size and capacity of the traditional PC BIOS huge and redundant, obscure, outdated, slow to start and bugs (BUG). Therefore, before the introduction of the Extensible Firmware Interface (UEFI) specification, open source BIOS emerged, such as the coreboot system (formerly known as LinuxBIOS) created by Los Alamos National Laboratory, and now by Germany's DENX Software Engineering Center Wolfgang Denk. Protected U-Boot systems, which generally have the advantages of modular architecture design, high scalability, high-level language development, portability, and rich system platform support. The main functions of the open source BIOS include: 1) Power-on self-test (POST). When the computer system is powered up, the system control is given to the open source BIOS, and the open source BIOS performs system detection, including CPU registers, programmable interval timers, and Program interrupt controller and direct memory access controller; 2) Initialize the registers of the cache, motherboard chipset, graphics card and related peripherals; 3) Save the system settings and store them in non-volatile memory.

However, these open source BIOSes cannot support large commercial non-open source operating systems such as the Windows family because they do not provide interrupt service routines that commercial non-open source operating systems rely on. Therefore, it is an urgent problem to develop a system and method based on an open source BIOS to boot an operating system that supports both traditional and modern operating systems. Summary of the invention

The problem to be solved by the present invention is to provide a BIOS-based booting system and a booting method that can support both an open source operating system and a non-open source commercial operating system.

In order to solve the above technical problem, the present invention provides a BIOS startup method, which includes: an interrupt service routine of an operating system interface (INTERFACE) module of a basic input/output system (BIOS), using optional read-only memory (Option) ROM) module (Module) mode implementation;

When the computer system is powered on, the BIOS-level board-level core module (CORE) initializes the board-level device and outputs system information, and the BIOS's board-level core module abstraction layer (MAPPER) module converts the system information according to the system information. a system information table identified by the operating system interface module, wherein the board level core module sequentially initializes the interrupt service routine included in the operating system interface module according to information in the system information table, where the system information includes The hardware list of the computer system, the corresponding port address, and the information of the memory size.

Optionally, the operating system interface module implements the interrupt service routine by using an Option ROM Module. The operating system interface module includes multiple Option ROMs, and each Option ROM corresponds to a service routine. The ROM includes the service routine, an initialization routine of the service routine, and an optional read-only memory header (Option ROM Header), The initialization routine of the service routine includes entry address information of the service routine, and the Option ROM Header includes information of a size of the Option ROM and an initialization routine address of the service routine.

Optionally, the board level core module is an extensible open source BIOS; and the MAPPER module is related to the open source BIOS.

Optionally, the board-level core module further saves an address range of the operating system interface module, and the step of sequentially performing the initialization of the Option ROM includes:

After the MAPPER module is initialized, the board core module scans the operating system interface module within the address range of the operating system interface module according to the size of the data unit specified by the Option ROM, and scans to the first Option. a ROM, calling a function entry of a service routine initialization routine of the Option ROM specified in an Option ROM Header of the Option ROM, and initializing a monthly service routine corresponding to the Option ROM;

After the Option ROM is initialized, the board core module scans the next Option ROM of the Option ROM in the operating system interface module, and invokes the Option specified in the Option ROM Header of the Option ROM that is currently scanned. The function routine of the ROM service routine initialization routine initializes the service routine corresponding to the current Option ROM until the service routine corresponding to the last Option ROM of the operating system interface module is initialized.

Optionally, the Option ROM header further includes signature information, and the step of the board core module determining to scan the Option ROM includes: the board level core module is configured according to a size of the data unit specified by the Option ROM. The operating system interface module is scanned within the address range of the operating system interface module. If the first two bytes are detected as the signature information, one of the Option ROMs is scanned.

Optionally, the board-level core module scans the Option ROM, and after scanning the signature, performs parity check on the entire Option ROM according to the information about the size of the corresponding service routine saved in the Option ROM Header. If the parity check is correct, the service routine corresponding to the Option ROM is initialized.

Optionally, the method further includes: after the parity check is correct, the board core module initializes a service routine corresponding to the Option ROM, and further, according to the Option ROM Header The saved information of the service routine size updates the base address of the Option ROM scanning algorithm; if the parity check is incorrect, the board level core module is updated in units of data unit sizes provided in the Option ROM Header The base address of the Option ROM scanning algorithm;

After updating the base address of the scanning algorithm, the board-level core module further determines whether the base address exceeds an address range of the operating system interface module, and if so, loads the file into a floppy disk, a hard disk, or a CD ROM according to user settings. The operating system, if no, scans the next Option ROM.

Optionally, the step of the Option ROM corresponding to the service routine being initialized according to the system information table includes:

The operating system interface module obtains the system information table maintained by the MAPPER module by querying the system information table maintained by the MAPPER module when the service routine needs to determine whether the related hardware of the service routine operation exists or when the port address or the available memory size is queried. The required information, the system information table is stored in a BIOS data area or a non-volatile memory (Non-Volatile RAM).

Optionally, when the service routine corresponding to the Option ROM is initialized, the service routine initialization routine in the Option ROM further registers an entry address of the service routine into an Interrupt Vector Table (Interrupt Vector Table). The interrupt service vector table is maintained by the MAPPER module.

Optionally, the interrupt service routine of the operating system interface module is a service routine required for starting the computer operating system, including a graphics service routine INT10H, a memory size service routine INT12H, a disk service routine INT13H, and a miscellaneous service. The routine INT15H, the keyboard service routine INT16H and the external device interconnection bus device basic input/output system (PCI BIOS) service routine INT1AH and the like.

In order to solve the above technical problem, the present invention also provides a BIOS booting system, which includes a board level core module, a board level core module abstraction layer (MAPPER) module, and an operating system interface module, wherein:

The board level core module is configured to: after the computer system is powered on, initialize the board level device and output system information, where the system information includes a hardware list of the computer system, a corresponding port, and a memory size information; The MAPPER module is configured to: convert, according to the system information, a system information table that is identifiable by the operating system interface module;

The operating system interface module is configured to: implement an interrupt service routine by using an optional ROM (Option ROM) module, and sequentially initialize the interrupt service routine according to the system information table.

Optionally, the operating system interface module includes a plurality of Option ROMs, each Option ROM corresponding to a service routine, where the Option ROM includes a service routine itself, an initialization routine of the service routine, and a selective Read the memory head (Option ROM Header), where

The initialization routine of the service routine is configured to: save entry address information of the service routine, configure hardware, and register entry address information of the service routine into an interrupt vector table;

The Option ROM Header is set to: store information of a size of the service routine and an initialization routine address of the service routine.

Optionally, the board level core module is further configured to: after initializing the board level device, jumping to the MAPPER module, where the board level core module is an expandable open source BIOS;

The MAPPER module is further configured to: perform an initialization function of the internal initialization function, read and parse the system information output by the board core module, and create and maintain the system information table according to the system information, and jump To the board level core module, the MAPPER module is related to the open source BIOS.

Optionally, the board level core module is further configured to: save an address range of the operating system interface module, initialize an INTERFACE module, scan the INTERFACE module according to the address range, scan to the first Option ROM, and save the location a base address of the Option ROM, calling a function entry of a service routine initialization routine of the Option ROM specified in an Option ROM Header of the Option ROM, jumping back from the Option ROM, and scanning the operating system interface module Updating the base address of the scanning algorithm according to the size of the Option ROM specified in the Option ROM Header of the Option ROM that is currently scanned, and determining whether the base address is exceeded. The address range of the operating system interface module, if yes, loading the operating system into the floppy disk, the hard disk, or the CD ROM according to the user setting, and if not, scanning the next Option ROM of the current Option ROM; The MAPPER module is further configured to: maintain a BIOS data area and an interrupt service vector table; the operating system interface module is further configured to: a function entry of a service routine initialization routine of the Option ROM is invoked, and the Option ROM is executed An initialization routine of the corresponding service routine initializes the service routine, and the initialization completes jumping back to the board-level core module;

The service routine initialization routine of the Option ROM of the operating system interface module is further configured to: register an entry address of the service routine to the interrupt service vector table.

Optionally, the Option ROM header further includes signature information, where

The board-level core module is further configured to: scan the INTERFACE module according to the address range of the INTERFACE module, and if the first two bytes are detected as the signature information, scan the Option ROM, according to the Option ROM. The information about the size of the corresponding service routine saved in the header is parity-checked to the entire Option ROM. If the parity is correct, the Option ROM specified in the Option ROM header of the Option ROM is called. a function entry of the service routine initialization routine, updating the base address of the scan algorithm according to the information of the size of the service routine saved by the Option ROM Header; if the parity check is incorrect, updating in units of 512 bytes a base address of the scan algorithm, after updating the base address of the scan, determining whether the base address exceeds an address range of the operating system interface module, and if so, loading operations to a floppy disk, a hard disk, or a CD ROM according to user settings The system, if no, scans the next Option ROM.

Optionally, the operating system interface module is further configured to: query, when the service routine needs to determine whether the related hardware of the service routine exists or query a port address or an available memory size, query the MAPPER module. The maintained system information form gets the information you need.

According to one or more embodiments provided by the present invention, the board level core module (CORE) selects an open source basic input/output system (BIOS) to initialize a board level device, and outputs system information, and the system information includes a memory size and a device type, etc. The Interrupt Service Routine in the system interface module is implemented by using an Option ROM module, and the interrupt service routine converts the system information table that can be recognized by the operating system interface (INTERFACE) module according to the system information conversion. Initialize in sequence, and register the interrupt service routine into the interrupt vector table. Introducing the board-level core module abstraction layer (MAPPER) module as a board-level core module and operating system by extending the architecture of the open source BIOS The interface between the interface modules, and the operating system interface module uses the Option ROM module to implement the service routines required for the startup of the computer operating system, and develops a BIOS system combining the operating system interface module and the open source BIOS, which can not only support open source. The operating system can also support non-open source commercial operating systems, such as the Windows operating system, with good compatibility.

BRIEF abstract

1 is a schematic diagram showing the structure of a computer system based on a BIOS system and method according to an embodiment of the present invention;

2(a) is a schematic structural diagram of a BIOS system based on an open source BIOS in a computer flash memory (FLASH) according to an embodiment of the present invention;

2(b) is a schematic structural diagram of a BIOS system based on an open source BIOS in a computer memory according to an embodiment of the present invention;

3 is a schematic structural diagram of a BIOS system based on an open source BIOS according to Embodiment 1 of the present invention; FIG. 4 is a flowchart of a method for a BIOS system in a computer startup process according to an embodiment of the present invention; FIG. 5 is a flowchart of a method according to an embodiment of the present invention; During the startup process, the board-level core module CORE initializes the flow chart of an Option ROM of the operating system interface module INTERFACE.

Preferred embodiment of the invention

Embodiments of the present invention will be further described in detail below with reference to the drawings and specific embodiments. It should be noted that the features in the embodiments and the embodiments of the present application may be arbitrarily combined with each other without conflict.

1 is a schematic structural diagram of a computer system based on a BIOS system and method according to the present invention, including an interconnected south bridge and a north bridge, a central processing unit (CPU) connected to the north bridge, a graphics card and a memory, and a large connection with the south bridge. Capacity storage and system basic input/output system (System BIOS), less pin interface (LPC) bus, peripheral component interconnect standard (PCI) bus, and PCI device connected to the PCI bus.

The structure of the System BIOS of the present application in the flash memory (FLASH) is as shown in FIG. 2(a), including Board Level Core Module (CORE), Board Level Core Module Abstraction Layer (MAPPER) module and Operating System Interface Module (INTERFACE). The BIOS system of the present application is obtained by extending the open source BIOS. The operating system interface module implements an interrupt service routine by using an optional read-only memory (Option ROM) module, which is a compressed binary code formed by compressing the compiled binary code. .

After the BIOS of the application is powered on by the computer hardware system, in order to obtain a faster execution speed, the board-level core module and the MAPPER module are copied into the memory for execution, and the operating system interface module is decompressed and copied into the memory for execution. The service routine in the operating system interface module is decompressed into binary code. The structure of the BIOS in memory is as shown in Figure 2(b), including the System BIOS (ie, the board-level core module, the MAPPER module, and the operating system interface module), the VGA BIOS and the data area, in descending order of address, Traditional DOS application workspace, BIOS data area, and interrupt vector table.

The board-level core module is configured to: after the computer hardware system is powered on, initialize the board-level device and output system information, and jump to the MAPPER module, the system information includes a hardware list of the computer system, a corresponding port address, and a memory size. Information, also used to save the address range of the operating system interface module.

The board-level core module is open source BIOS-related, and its function and structure depend on the function and structure of the open source BIOS.

The board level core module abstraction layer (MAPPER) module is configured to: execute an internal initialization function to complete its own initialization, read and parse system information output by the board level core module, and create and maintain according to the system information. The system information table identified by the operating system interface (INTERFACE) module jumps to the board level core module, and the MAPPER module is related to the open source BIOS. The format of the system information table is determined according to the open source BIOS and stored in the BIOS data area or Non-Volatile RAM. The MAPPER module is also used to maintain an interrupt service vector table.

The operating system interface module is configured to: implement an interrupt service routine required for starting the computer operating system by using an optional read-only memory (Option ROM) module, and the interrupt service routine is maintained according to the MAPPER module. The system information table is initialized in sequence.

The operating system interface module includes multiple Option ROMs, and each Option ROM corresponds to one service. The Option ROM includes a service routine, an initialization routine of the service routine, and an optional ROM head (Option ROM Header), wherein

The initialization routine of the service routine is set to: configure the hardware and save the entry address information of the service routine;

The Option ROM Header is set to: save the signature information, the size of the Option ROM, and the address of the initialization routine address of the service routine. The size of the service routine is an integer multiple of the data unit size specified by the Option ROM. In this embodiment, the data unit of the Option ROM is exemplified by 512 bytes.

In the computer flash memory (FLASH), the service routine is a compressed binary code formed by compression of the compiled binary code. After the computer hardware system is started, in order to improve the execution speed, the board-level core module and the MAPPER module of the BIOS system are directly copied into the memory for execution, and the service routine in the operating system interface module is decompressed into binary code and copied into the memory. .

After the MAPPER module is initialized, the board core module scans the first Option ROM in the operating system interface module, saves the base address of the Option ROM, and scans the signature in the Option ROM Header according to the Option ROM. The information about the size of the corresponding service routine saved in the header is parity-checked to the entire Option ROM. If the parity is correct, the service routine initialization example of the Option ROM specified in the Option ROM Header of the Option ROM is called. The function entry of the program, and the base address of the update scan algorithm is the sum of the base address of the current Option ROM scan algorithm and the size of the current Option ROM, and the base address of the scan algorithm is still an integer multiple of 512 bytes. If the parity check is incorrect, the board core module updates the scanned base address in a set size address segment, such as 512 bytes. After updating the scanned base address, it is determined whether the base address is exceeded. The address range of the operating system interface module, if yes, indicates that all Option ROMs are initialized, and the operating system can be loaded into the floppy disk, the hard disk, or the CD ROM according to the user settings. If not, the next Option ROM is scanned.

The operating system interface module is further configured to: the function entry of the service routine initialization routine of the Option ROM is invoked, execute an initialization routine of the service routine corresponding to the Option ROM, and initialize the service routine, the Option ROM The service routine initialization routine registers the entry address of the service routine to the interrupt service vector table maintained by the MAPPER module, and the initialization completes the jump back to the board level core module. After the current Option ROM is initialized, the board core module scans the next Option ROM of the current Option ROM in the operating system interface module, and scans the signature of the Option ROM according to the corresponding service example saved in the Option ROM Header. The size of the information is parity checked on the entire Option ROM. If the parity is correct, the function entry of the service routine initialization routine of the Option ROM specified in the Option ROM Header of the Option ROM is invoked. The information of the service routine size saved by the Option ROM Header updates the base address of the scan algorithm, and calls the function entry of the service routine initialization routine of the Option ROM specified in the Option ROM Header of the Option ROM currently scanned, as described above. The parity check is incorrect, and the board level core module updates the scanned base address in units of 512 bytes. The board-level core module determines whether the base address exceeds an address range of the operating system interface module. If yes, it indicates that all Option ROMs are initialized, and the operating system can be loaded into a floppy disk, a hard disk, or a CD ROM according to user settings. If no, the next Option ROM of the current Option ROM is scanned to initialize the service routine corresponding to the next Option ROM in the same manner.

The interrupt service routine stored by the operating system interface module includes the service routines necessary for the computer system to start, including the graphics service routine INT10H, the memory size service routine INT12H, the disk service routine INT13H, the miscellaneous service routine INT15H, the keyboard The service routine INT16H and the external device interconnection bus device basic input/output system (PCI BIOS) service routine INT1AH and the like.

The operating system interface module is further configured to: need to determine whether the relevant hardware of the service routine operation exists during the initialization of the service routine, or query the system information table maintained by the MAPPER module when querying the port address or the available memory size Information. If the disk service routine INT13H needs to determine whether there is a floppy disk, a hard disk or a CD, the operating system interface module queries the hardware list in the system information table maintained by the MAPPER module to obtain the required information. If the corresponding hardware exists, the Option The initialization routine of the service routine corresponding to the ROM registers the function entry address of the service routine INT13H into the interrupt service vector table maintained by the MAPPER. For INT12H, which is used to report the memory size to the operating system, during the INT12H initialization process, the operating system interface module does not need to detect the size of the memory, and directly queries the system information table maintained by the MAPPER module.

BIOS startup method based on open source basic input/output system (BIOS) of embodiment of the present invention The BIOS operating system interface module is implemented by an optional read-only memory (Option ROM) module. The BIOS initializes the board level device and outputs system information when the computer hardware system is powered on, the system information includes a hardware list of the computer system, a corresponding port address, and a memory size, and the operating system interface module is configured according to the operating system interface module. The system information table recognized by the operating system interface (INTERFACE) module obtained by the system information conversion sequentially initializes the Option ROM therein. The details will be described below in conjunction with specific embodiments.

Embodiment 1

The schematic diagram of the structure of the open source BIOS based BIOS system of this embodiment is shown in FIG. 3, and the open source BIOS is an expandable BIOS. The BIOS system shown in Figure 3 is 4Mb in size, and its physical addresses OxDOOOO to OxFFFFF include a board-level core module (CORE), a board-level core module abstraction layer (MAPPER) module, and an operating system interface module (INTERFACE). The physical addresses OxFOOOO to OxFFFFF include the board-level core module and the board-level core module abstraction layer module. The board-level core module is located at a high-order address starting from OxFFFFF, and the MAPPER module is located at a low level of the board-level core module, and the specific location is compiled. When determined.

1) Board Level Core Module (CORE): Set to control the computer system after power up, initialize board level equipment, including central processing unit, cache memory, memory controller, north bridge and north bridge related equipment and south bridge And the south bridge related device, etc., output system information, and jump to the MAPPER module, the system information includes a hardware list of the computer system, a corresponding port address, and a memory size information, and is further configured to: save the The address range of the operating system interface module, jumps back from the MAPPER module, and scans the Option ROM of the operating system interface module.

2) The MAPPER module is set to: execute an internal initialization function to complete its own initialization, read and parse the system information output by the board-level core module, and create and maintain according to the system information by the operating system interface (INTERFACE) The system information table identified by the module jumps to the board level core module and maintains the interrupt service vector table.

3) Operating system interface module (INTERFACE): From the physical address OxDOOOO to OxEFFFF, set to: use the optional read-only memory (Option ROM) module mode to implement the interrupt service routine, the Option ROM is based on the MAPPER module. The maintained system information table is initialized in sequence.

The operating system interface module of this embodiment includes three Option ROMs, each Option ROM. The size is an integer multiple of 512 bytes. The physical address OxDOOOO to OxDFFFF contains two Option ROMs, so there are two Option ROM Headers. These two Option ROMs provide the INT 16H keyboard service routine (Keyboard Service) and the INT 15H miscellaneous service routine (System). Service) „ For the Windows operating system, the Disk ROM of the INT 13H is provided by the Option ROM whose physical address ranges from OxEOOOO to OxEFFFF. The invention does not limit the size of the Option ROM, and the in-memory service routine Option ROM The location within the operating system interface module.

In order to ensure independence, and to provide compatibility support for the operating system interface module to provide advanced operating systems such as Windows operating system and Linux operating system boot, the operating system interface module also conforms to the ROM in the Plug and Play BIOS Specification. The standard format.

The board-level core module scans the Option ROM in the operating system interface module, scans the Option ROM Header in the operating system interface module, and queries the signature saved in the Option ROM Header according to the corresponding saved in the Option ROM Header. The information of the service routine size is parity-checked to the entire Option ROM. If the parity check is correct, the search or the search is performed according to the information about the size of the service routine corresponding to the Option ROM provided in the Option ROM Header. Update the base address of the scan algorithm, call the entry function of the service routine initialization routine of the Option ROM, and jump to the operating system interface module to initialize the corresponding function. If the parity check is incorrect, the board-level core module updates the base address of the scan algorithm in units of 512 bytes. After updating the scan base address, the board level core module further determines whether the base address exceeds the address range of the operating system interface module. If yes, it indicates that all Option ROMs have been initialized, and can continue to be based on user settings to the floppy disk and the hard disk. Or load the operating system in the CD ROM. If no, scan the next Option ROM.

The operating system interface module obtains control, that is, after the function entry of the service routine initialization routine of the Option ROM is invoked, the initialization routine of the service routine corresponding to the Option ROM is executed, and the service routine is initialized. The service routine initialization routine of the Option ROM registers the entry address of the service routine to the interrupt service vector table maintained by the MAPPER module, and the initialization completes the jump back to the board-level core module. The board-level core module scans the next Option ROM and initializes the service routine corresponding to the Option ROM.

The operating system interface module is further configured to: determine the service during the initialization of the service routine If the relevant hardware of the routine operation exists, or when querying the port address or the available memory size, query the system information table maintained by the MAPPER module to obtain the required information. If the disk service routine INT13H needs to determine whether there is a floppy disk, a hard disk or a CD, the operating system interface module queries the hardware list in the system information table maintained by the MAPPER module to obtain the required information. If the corresponding hardware exists, the Option The initialization routine of the service routine corresponding to the ROM registers the function entry address of the service routine INT13H into the interrupt service vector table maintained by the MAPPER. For the INT12H information for reporting the memory size to the operating system, during the INT12H initialization process, the operating system interface module does not need to detect the size of the memory, and directly queries the information from the system information table maintained by the MAPPER module.

The board-level core module, MAPPER module, and operating system interface module are all stored in non-volatile read-only memory.

The BIOS system of the present invention is extensible, and the one or more Option ROMs and their corresponding service examples can be set as needed, because the BIOS system uses the Option ROM module to implement services required during startup or operation of the operating system. Cheng. Because the open source BIOS system provides the same functionality as the industrial PC BIOS, it is compatible with industrial PC BIOS and provides a hardware and software interface compatible with industrial PC BIOS.

The open source BIOS system also includes a system detection module, a BIOS Extensible Firmware Interface (UEFI) module, and a system debug tool module.

The computer system supported by the firmware BIOS based on the open source BIOS system includes an X86 compatible processor, a computer supporting the PCI bus standard, and an advanced operating system such as a Windows operating system and a Linux operating system, including but not limited to DOS, Windows 98, and Windows. 2000, Windows XP, Windows Vista, Window 7, and Linux major distributions.

Embodiment 2

In this embodiment, the X86 processor is taken as an example, and the BIOS startup method processing process based on the open source BIOS is as shown in FIG. 4, and includes the following steps:

Step 301: The computer system is powered on, and the central processor fetches instructions from the physical address 0xF000: OxFFFO of the BIOS, invokes the board-level core module, and gives control to the board-level core module, copying The board level core module and the MAPPER module are in memory, the board level core module decompresses and copies the operating system interface module into the memory, initializes the board level device in the computer system, and outputs system information;

The system information includes a list of hardware of the computer system, corresponding port addresses, and information about the size of the memory.

After the board level device is initialized, the board level core module invokes an entry function of the MAPPER module, and the MAPPER module performs an initialization function saved internally by the module to complete its own initialization, and reads and parses system information output by the board level core module. And creating and maintaining the system information table according to the system information. The table includes a list of hardware for the computer system, corresponding port addresses, and memory size information. The MAPPER module also initializes data in the BIOS data area (BDA) and extended BIOS data area (EBDA), maintains the table prepared for booting the operating system including the Programmable Interrupt Request (PIRQ) table and the Advanced Configuration and Power Interface (ACPI) ) forms, etc. The board-level core module and the MAPPER module are both open source BIOS-related, that is, their function and structure depend on the function and structure of the open source BIOS.

Step 302: The board core module is set to scan the Option ROM algorithm to scan the base address as

OxDOOOO, and save the scan base address;

The operating system interface module includes a plurality of Option ROMs, each Option ROM corresponding to a service routine, the Option ROM including a service routine, an initialization routine of the service routine, and an optional read-only memory head (Option ROM Header) ).

The initialization routine of the service routine includes entry address information of the service routine;

The ROM Header includes information on the signature, size, and initialization routine address of the service routine. The size information of the service routine is information about the size of the memory space when the service routine is uncompressed. The format of the Option ROM is compatible with the industry "Plug and Play BIOS Specification".

Step 303: The board-level core module scans the Option ROM in the operating system interface module according to the saved scan algorithm base address, and performs parity check.

The board-level core module scans the Option ROM Header at the address OxDOOOO to check whether it contains the signature "55AA". If yes, it determines that there is an Option ROM at the address. Otherwise, the board-level core module updates the scan in units of 512 bytes. Base address. The board level core module is definitely An Option ROM exists in the address, and the information about the size of the service routine stored in the Option ROM Header is also queried, and the entire Option ROM is parity-checked according to the size of the Option ROM.

Step 304: The board level core module determines whether the parity check is correct, correct, step 305 is performed, otherwise, step 306 is performed;

The parity of the Option ROM as a whole is to ensure data integrity, and other verification algorithms for ensuring data integrity, such as the CRC algorithm, are also applicable to the method of the present invention.

Step 305: The board-level core module initializes the Option ROM, and performs step 307;

The board-level core module updates the start address of the scan Option ROM algorithm according to the information indicating the size of the Option ROM in the Option ROM Header, and invokes the initialization routine of the service routine corresponding to the Option ROM specified in the Option ROM Header. Function entry, initialize the service routine. The initialization routine of the service routine corresponding to the Option ROM registers the entry address of the service routine into the interrupt service vector table (IVT) maintained by the MAPPER module.

When the service routine needs to determine whether the relevant hardware of the operation of the service routine exists, or when the port address or the available memory size is queried, the operating system interface module queries the system information table maintained by the MAPPER module to obtain the required information. If the disk service routine INT13H needs to determine whether there is a floppy disk, a hard disk or a CD, the operating system interface module queries the hardware list in the system information table maintained by the MAPPER module to obtain the required information. If there is corresponding hardware, the Option The initialization routine of the service routine corresponding to the ROM registers the function entry address of the service routine INT13H into the interrupt service vector table maintained by the MAPPER module. For INT12H, which is used to report the memory size to the operating system, during the INT12H initialization process, the operating system interface module does not need to detect the size of the memory, and directly queries the system information table maintained by the MAPPER module.

Step 306: The board-level core module is incremented by 1 unit in units of 512 bytes, and the base address of the scan Option ROM algorithm is incremented by one unit, and step 307 is performed;

Step 307: Determine whether the scan algorithm base address is greater than OxEFFFF, if yes, go to step 308, otherwise, go to step 303;

Since the physical address of the board-level core module starts from 0xF0000, therefore, the operating system interface The scan of the Option ROM in the module cannot exceed the address. If the base address of the scan algorithm is greater than OxEFFFF, all Option ROMs have been scanned.

Step 308: After the operating system interface module is initialized, the board core module loads the operating system from the specified address according to the user's setting, and the specified address is a floppy disk, a hard disk, or a CD ROM;

Step 309: Boot and run the operating system.

After the operating system interface module initializes each service module, the control right is given to the MAPPER module, and the MAPPER module executes an INT19H interrupt processing routine through a function call, and the routine outputs display information, prompting the user to input information to select to start, and operate. The guidance of the system.

The processing of the Option ROM in the operating system interface module of the board-level core module is as shown in FIG. 5, and the service routine corresponding to the Option ROM uses the disk service routine INT13H as an example. Specifically, the following steps are included:

Step 401: The board-level core module scans an Option ROM in the operating system interface module, and scans the signature of the Option ROM "55AA";

Step 402: Calculate a parity checksum of the entire Option ROM according to the information indicating the size of the service routine corresponding to the Option ROM in the Option ROM Header.

The data unit of the Option ROM is in units of 512 bytes, and the size of the service routine corresponding to the Option ROM is an integer multiple of 512 bytes.

Step 403: Determine whether the parity check is correct, if yes, go to step 405, otherwise go to step 404;

Step 404: In increments of 512 bytes, the starting address of the scanning Option ROM algorithm is incremented by one unit, and step 409 is performed;

Step 405: Update the base address of the scan Option ROM algorithm according to the Option ROM size information in the Option ROM Header, call the Option ROM specified in the Option ROM Header, that is, the function entry of the INT13H, and call and execute the INT13H service routine. Initialization routine, initializes the interrupt service routine INT13H and registers the entry address of the INT13H service routine into the interrupt service vector table maintained by the MAPPER module; Steps 406-408 are all related to the Option ROM in the operating system interface module. Step 406: The control is given to the Option ROM in the operating system interface module, INT13H;

INT13H is critical for large commercial non-open source operating systems, such as the Windows operating system, which is responsible for booting the entire operating system.

Step 407: The Option ROM detects and initializes INT13H related hardware, including a floppy disk, a hard disk, and a CD ROM, and initializes a corresponding controller;

The Option ROM checks whether the hardware is damaged by reading the hardware register information, detects and initializes, and modifies the corresponding vector INT13H*4 in the interrupt vector table, and writes the entry address of the service routine of the Option ROM into the interrupt service vector table. The entry address can be written to the interrupt service vector table in the form of segment values and offsets, and the detected hardware information is stored in a non-volatile memory, such as a complementary metal oxide semiconductor (CMOS), for operation. System use.

Step 408: The current Option ROM gives up the control right, and returns the control right to the board core module;

Step 409: The board core module regains control and scans the next Option ROM to perform detection of the next Option ROM.

Both the board-level core module and the operating system interface module of the embodiment of the present invention support the Option ROM Header format, and communicate using the information in the Option ROM Header. Since the Option ROM in the operating system interface module is independent of the board level core module, the present invention can conveniently provide the necessary support for the open source BIOS to support non-open source operating systems, such as the Windows operating system. Moreover, the development environment of the board-level core module and the operating system interface module of the present invention may be the same or different, and the development environment includes: a programming language, a compilation environment, and a cross-compilation requirement.

Since most open source BIOS supports board-level devices better, the above method only needs to make a small modification to the existing open source BIOS to extend the functionality of the board-level core module.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct the associated hardware, such as a read only memory, a magnetic disk, or an optical disk. Optionally, all or part of the steps of the above embodiments may also be used. One or more integrated circuits are implemented. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

In the above embodiment, the board level core module (CORE) selects an open source basic input/output system (BIOS) to initialize a board level device, and outputs system information, and the system information includes a memory size and a device type, and an interrupt service example in the operating system interface module. The Interrupt Service Routine is implemented by using an Option ROM module, and the interrupt service routine is sequentially initialized according to the system information table recognized by the operating system interface (INTERFACE) module by the system information conversion, and the interrupt service is registered. The routine is in the interrupt vector table. By extending the architecture of the open source BIOS, the board level core module abstraction layer (MAPPER) module is introduced as the interface between the board level core module and the operating system interface module, and the operating system interface module uses the Option ROM module mode to implement the computer operating system boot. The required service routines, the development of a combination of operating system interface module and open source BIOS BIOS system, not only can support open source operating systems, but also support non-open source commercial operating systems, such as Windows operating systems, etc., with good compatibility .

Claims

Claim

1. A basic input/output system (BIOS) booting method, comprising:

The interrupt service routine of the BIOS operating system interface (INTERFACE) module is implemented by an optional read-only memory (Modt 1 e) module (Modu 1 e);

2. The method according to claim 1, wherein the operating system interface module implements the interrupt service routine by using an Op ti on ROM Module method, wherein the operating system interface module comprises a plurality of Opt ion ROMs, each The Opt ion ROM corresponds to a one-month service routine, the Opt ion ROM includes the service routine, an initialization routine of the service routine, and an optional read-only memory head (Opt ion ROM Header). The initialization routine of the service routine includes entry address information of the service routine, and the Option ROM Header includes information of a size of the Opt ion ROM and an initialization routine address of the service routine.

3. The method according to claim 1, wherein the board level core module is an extensible open source BIOS; and the MAPPER module is related to the open source BIOS.

The method according to claim 1 or 2 or 3, wherein the board level core module further saves an address range of the operating system interface module, and the step of initializing the Opt ion ROM in sequence comprises:

After the MAPPER module is initialized, the board core module scans the operating system interface module within the address range of the operating system interface module according to the size of the data unit specified by the Opt ion ROM, and scans to the first Opting the ROM, calling a function entry of the service routine initialization routine of the Opt ion ROM specified in the Opt ion ROM Header of the Opt ion ROM, and initializing a service routine corresponding to the Opt ion ROM;

After the initialization of the Opt ion ROM is completed, the board level core module scans the operating system to connect The next Opt ion ROM of the Opt ion ROM in the port module, calling the function entry of the service routine initialization routine of the Opt ion ROM specified in the Opt ion ROM Header of the Opt ion ROM currently scanned, initializing the current The service routine corresponding to the Opt ion ROM is initialized until the service routine corresponding to the last Opt ion ROM of the operating system interface module is initialized.

The method according to claim 4, wherein the Opt ion ROM header further includes signature information, and the step of the board core module determining to scan the Opt ion ROM comprises: the board level core module according to The size of the data unit specified by the Opt ion ROM scans the operating system interface module within an address range of the operating system interface module. If the first two bytes are detected as the signature information, one of the Opt is scanned. Ion R0M.

6. The method of claim 5 wherein said board level core module scans said Opt ion

After scanning the signature, the ROM further performs parity check on the entire Opt ion ROM according to the information about the size of the corresponding service routine stored in the Opt ion ROM header, and if the parity check is correct, Initializing the service routine corresponding to the Opt ion ROM.

7. The method according to claim 6, the method further comprising: after the parity check is correct, the board level core module initializes a service routine corresponding to the Opt ion ROM, and further according to the Opt The information of the size of the service routine saved by the ion ROM Header updates the base address of the Opt ion ROM scanning algorithm;

If the parity check is incorrect, the board core module updates the base address of the Opt ion ROM scanning algorithm in units of data unit sizes provided in the Opt ion ROM Header;

After updating the base address of the scanning algorithm, the board-level core module further determines whether the base address exceeds an address range of the operating system interface module, and if so, loads the file into a floppy disk, a hard disk, or a CD ROM according to user settings. The operating system, if no, scans the next Opt ion R0M.

The method according to claim 1 or 2 or 3, wherein the step of initializing the Opt ion ROM corresponding to the service routine according to the system information table comprises:

The operating system interface module obtains the system information table maintained by the MAPPER module by querying the system information table maintained by the MAPPER module when the service routine needs to determine whether the related hardware of the service routine operation exists or when the port address or the available memory size is queried. Required information, the system information table is stored Stored in the BIOS data area or non-volatile memory (Non-Volat i le RAM).

9. The method according to claim 4, wherein the service routine corresponding to the Opt ion ROM is initialized, further comprising a service routine initialization routine in the Opt ion ROM registering an entry address of the service routine In the Interrupt Vector Table, the interrupt service vector table is maintained by the MAPPER module.

10. The method according to claim 1, wherein the interrupt service routine of the operating system interface module is a service routine necessary for starting a computer operating system, including a graphics service routine.

INT10H, get memory size service routine INT12H, disk service routine INT13H, miscellaneous service routine INT15H, keyboard service routine INT16H and external device interconnect bus device basic input/output system (PCI BIOS) service routine INT1AH, etc.

11. A basic input/output system (BIOS) booting system, comprising a board level core module, a board level core module abstraction layer (MAPPER) module, and an operating system interface module, wherein:

The board level core module is configured to: after the computer system is powered on, initialize the board level device and output system information, where the system information includes a hardware list of the computer system, a corresponding port, and a memory size information;

The MAPPER module is configured to: convert, according to the system information, a system information table that is identifiable by the operating system interface module;

The operating system interface module is configured to: implement an interrupt service routine by using an optional Opto-Ion module (Module) module, and sequentially initialize the interrupt service routine according to the system information table. .

12. The system according to claim 11, wherein the operating system interface module comprises a plurality of Opt ion ROMs, each Opt ion ROM corresponding to a one-month service routine, the Opt ion ROM comprising a service routine itself, An initialization routine of the service routine and an optional read-only memory header (Opt ion ROM Header), wherein

The Opt ion ROM Header is set to: save the size of the service routine and the service The initialization routine address information for the routine.

13. The system according to claim 11, wherein

The board level core module is further configured to: after initializing the board level device, jump to the MAPPER module, where the board level core module is an expandable open source BIOS;

The MAPPER module is further configured to: perform an initialization function of the internal initialization function, read and parse the system information output by the board level core module, create and maintain the system information table according to the system information, and jump to The board level core module, the MAPPER module is related to the open source BIOS.

14. The system according to claim 11 or 12 or 13, wherein

The board level core module is further configured to: save an address range of the operating system interface module, initialize an INTERFACE module, scan the INTERFACE module according to the address range, scan to a first Opt ion ROM, save the a base address of the Opt ion ROM, calling a function entry of a service routine initialization routine of the Opt ion ROM specified in an Opt ion ROM Header of the Opt ion ROM, jumping back from the Opt ion ROM, scanning the The next Opt ion ROM of the Opt ion ROM in the operating system interface module updates the scanning algorithm according to the size of the Opt ion ROM specified in the Opt ion ROM Header of the Opt ion ROM currently scanned. Base address, and determining whether the base address exceeds an address range of the operating system interface module, and if so, loading an operating system into a floppy disk, a hard disk, or a CD ROM according to user settings, and if not, scanning the current Opt ion ROM Next Opt ion ROM;

The MAPPER module is further configured to: maintain a BIOS data area and an interrupt service vector table; the operating system interface module is further configured to: when the function entry of the service routine initialization routine of the Opt ion ROM is invoked, perform the An initialization routine of the service routine corresponding to the Opt ion ROM, initializing the service routine, and completing the initialization to jump back to the board level core module;

The service routine initialization routine of the Option ROM of the operating system interface module is further configured to register an entry address of the service routine to the interrupt service vector table.

The system according to claim 10 or 11 or 12, wherein the Opt ion ROM Header further includes signature information. The board level core module is further configured to: scan the INTERFACE module according to the INTERFACE module address range, and if the first two bytes are detected as the signature information, scan the Opt ion ROM according to the Opt The information of the corresponding service routine size saved in the ion ROM header is parity-checked to the entire Opt ion ROM. If the parity is correct, the Opt ion ROM header specified in the Opt ion ROM is called. a function entry of the service routine initialization routine of the Opt ion ROM, updating a base address of the scan algorithm according to the information of the size of the service routine saved by the Opt ion ROM Header; if the parity check is incorrect, Updating the base address of the scanning algorithm in units of 512 bytes, and after updating the base address of the scan, determining whether the base address exceeds an address range of the operating system interface module, and if so, according to user settings, to a floppy disk, Load the operating system on the hard disk or CD ROM. If no, scan the next Opt ion R0M.

16. The system according to claim 10 or 11 or 12, wherein

The operating system interface module is further configured to: query the system information maintained by the MAPPER module when it is necessary to determine whether the related hardware of the service routine operation exists or query the port address or the available memory size during the initialization of the service routine The form gets the information you need.