TWI273482B - Driver loading method for extensible firmware interface - Google Patents

Abstract

A driver loading method for an extensible firmware interface is disclosed, wherein a host computer loads a driver of the extensible firmware interface into a random access memory of a test computer via a transmission line. The driver loading method of the extensible firmware interface firstly turns on the test computer, executes a communication program of the extensible firmware interface; then determines whether the host computer executes a terminal receiving program; transmits the driver of the extensible firmware interface to the random access memory of the test computer if the host computer executes the terminal receiving program; next, executes the driver within the random access memory; and, activates an operating system.

Description

1273482 IX. Description of the invention: [Technical field to which the sun and the moon belong] The present invention relates to a method of loading a program, and more particularly to a method for loading a driver of an extendable firmware interface. [Prior Art] In a computer system, there is a firmware, which is generally known as a BIOS (Basic Input/Output System), which is accompanied by a host computer and is stored in a read-only memory ( ROM, Read Only ® Memory) is a program that contains a number of basic sub-programs for computer input and output. After the computer power is turned on, the basic input and output system is executed to perform initial value setting and power-on self test (POST, Power-on Self Test), and read and write complementary metal oxide semiconductor (CMOS, Complementary Metal- Data in Oxide Semiconductor (memory size, whether there is a floppy disk drive and hard drive, system time, etc.). Due to the rapid advancement of computer technology, the basic output system (L e g a c y B I 0 S ) with the development of computer systems has also reached its limit. Therefore, in order to overcome the bottleneck in the development of the traditional basic input and output system, Intel Corporation has developed a specification of the EFI (Extensible Firmware Interface), which eliminates the basic input and output system. Innate limitations. Moreover, this extensible firmware interface allows the use of standard programming language tools to add new components' with better scalability, and is written in C language, the program is easy to maintain, read and so on. After the computer is powered on, the CPU (Central Processing Unit' 5 326\patent specification (supplement)\94-〇4\TF944510 1273482 central processing unit) is stored in read-only memory (such as FL AS HP ART). The extendable firmware interface reads the required drivers for self-testing and import-input interface search and setup. Therefore, the extended firmware interface needs to confirm the developed extendable firmware during the development phase. The interface can operate normally.

The current method of developing an extendable firmware interface relies on the help of a ROM simulator (R 0 Μ E mu 1 at 〇r ), which confirms whether the developed extensible interface is working properly, as shown in Figure 1. The block diagram of the technology is shown. In Fig. 1, the plug 1 2 of the R 0 Μ simulator 10 is inserted into the slot 16 of a computer (1) in which a flash memory (not shown) is placed, and one of the external host computers 15 will be The developing extendable firmware interface is transferred to the R 0 Μ simulator 10, and after the computer 14 under test is powered on, the CPU 1 8 of the computer under test 14 is read and stored in the R 0 Μ simulator. The extendable firmware interface in 10 is used for self-test and input/output interface (not shown) for searching and setting. However, the above limitation in using the R 0 Μ simulator 10 is as follows: (1) The ROM simulator is only convenient to use the development of the motherboard (the motherboard manufactured by the motherboard manufacturer according to the specified specifications), if it is used in The bare board of the foundry manufacturer (similar to the public board, but not the motherboard manufactured according to the specified specifications), often caused by the operating voltage of the bare board and the working voltage of the ROM simulator, causing malfunction or even failure to use. The ROM simulator is used to perform the simulation work. (2) When the OEM product is at a certain stage, it must be installed and tested, and the bare board is no longer provided to the engineer who tests the extendable firmware interface. Unless the machine is disassembled, the computer under test cannot. Use the ROM emulator. 6 326\ patent specification (supplement)\94-04\TF944510

1273482 (3) If you encounter a non-slot type of flash memory for bare board installation (such as direct soldering in the main phase slot does not support the plug slot provided by the ROM emulator, this is time consuming and soldered The line is vulnerable to (4) the current flash memory capacity is large or even larger, but the ROM emulator is usually only 7 in order to increase the capacity of the ROM emulator, then the option driver (Option DRIVER) must be temporarily The program can't use the ROM emulator to confirm, and the body does the work of confirming. (5) The current R 0 Μ simulator is about a few thousand dollars, and for a research and development Β I 0S a ROM emulator, will

(6) In the way of burning read-only memory, it is necessary to burn the program code to the burner, which also causes the company to have fewer burners, so if many people are waiting in line to use the burner. Situation; failure, resulting in a situation that is not easy to burn, is inefficient for the company. SUMMARY OF THE INVENTION As described above, the object of the present invention is to provide a method for loading a driver of a surface, which does not need to be simulated, and reduces the hardware cost during testing, and can be adapted to 326\patent specification (supplement)\94- 04\TF944510 (such as FLASHPART) is to make the I board), or the head used there, must be specially welded to damage. 1 Μ Μ Μ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ Γ For a company with a poor focus, if the company is not small, it is often inconvenient to remove the flash memory. Usually, a job for burning, the maker, the slot of the burner is easy or personal. An extendable firmware-based ROM emulator is used for any package type and 1271482 size flash memory, and the extendable firmware interface can be implemented on the public board, bare board or even after installation. The simulation allows the development of an extendable firmware interface to be easily tested at any stage.

The invention provides a loading method of a driver of an extendable firmware interface, wherein a host computer loads a driver of the extendable firmware interface into one of the tested computers by a transmission line. In the memory, the loading method of the driver of the extendable firmware interface comprises the following steps: first, booting a computer under test and executing a constructing program of the extendable firmware interface; and then determining the Whether the host computer executes a terminal receiving program, and when the host computer executes the terminal receiving program, transmitting the driver of the extendable firmware interface to the random access memory of the tested computer; Executing the driver in the random access memory; and starting the operating system. The present invention provides a computer readable recording medium for a computer system having an extendable firmware interface, wherein a host computer loads a driver of the extendable firmware interface by a transmission line. In one of the tested computers, the readable medium of the computer can cause the computer to perform the following steps: first, booting a computer under test and performing one of the extendable firmware interfaces. And determining whether the host computer executes a terminal receiving program, and when the host computer executes the terminal receiving program, transmitting the driver of the extendable firmware interface to the random memory of the tested computer Taking the memory; secondly, executing the driver in the random access memory; and starting the operating system. Other objects and advantages of the present invention will be apparent from the following detailed description and accompanying 8 326\patent specification (supplement)\94-(M\TF944510)

The scope of patent application of 1273482 can be more clearly understood. [Embodiment] In the stage of developing the extendable firmware interface, when the computer is powered on, the computer under test performs self-test and input and search, setting, and the like. If the implementation of the extendable firmware interface fails to enable the computer under test, or the extension of the extendable tough surface of the computer under test, the external computer can be used to provide the extended firmware interface. The program is given to the computer under test to test the work of the extendable tough surface in the computer under test. The structure is shown in Figure 2 of the block diagram of the present invention. In FIG. 2, after the computer 2 2 is powered on, the CPU 24 4 is programmed into each driver of the extensible interface in the read-only memory (such as FLAS Η PART) 26 and will only The respective drivers of the scalable firmware interface in the read memory 26 are moved to the RAM 28 as needed. When the brain 2 2 needs to transmit the required driver from the external host computer 32, the CPU 34 of the host computer 32 transmits the interface 36 and the transmission line to the LL3 40 (you can also use a COMPORT, a LAN, a USB or a 1394) The interface 30 stores the drivers stored in the RAM 38 in the RAM. When the current extendable firmware interface moves the drivers to 28, they will call the extended firmware interface. A subroutine for finding a shift, this subroutine will use this feature from a specified address (this address usually refers to the memory 2 to find the required driver and move it to RA Μ 2 8). Before adding a small section of the main computer 326\patent specification (supplement)\94-04\TF944510 9 the interface is wrong and the interface is in the middle of the body t-type toughness type test, then the line, pass 28 RAM and the driver between the 32 1273482 and the computer under test 2 (hereinafter referred to as the build program), to construct the host computer 3 2 whether to send a driver to the computer 2 2 under test, Burn this configuration program into the read-only memory 26, and in the main Brain 32 receives the terminal end of a program execution. In order to illustrate the foregoing method, one of the VGA drivers in the extendable firmware interface is used as an example to illustrate the flow, and the remaining drivers in the extendable firmware interface have the same processing flow. Figure 3 is a flow chart of the present invention.

In FIG. 3 (and referring to FIG. 2), when the computer 2 under test is powered on (ie, the power is turned on) (step S50), the system needs the extension firmware interface call to find a moving program. When entering this program, the configuration program will be executed first, so that the computer under test 2 2 starts to communicate with the host computer 32 in two directions. Next, it is determined whether the host computer 3 2 executes a terminal receiving program (step S 5 2 ). When the host computer 32 has executed the terminal receiving program, the CPU 24 transmits the interface 30, the LL3 line 40, and the transmission interface. 36 sends a request to the CPU 34 to transmit a VGA driver. At this time, the CPU 34 checks the data of the VGA driver in the extendable firmware interface to determine whether the modified VGA driver can be transmitted to the computer under test 2 2. When the host computer 32 can transmit the modified VGA driver, the host computer 3 2 transmits the VGA driver to the computer under test through the transmission interface 36, the LL 3 line 40 and the transmission interface 30. 2 2 of RA Μ 2 8 (step S 5 4 ), and the host computer 3 2 waits for the computer under test 2 2 to execute the configuration program next time, the transmitted computer 2 2 sends a modified copy to the computer 3 2 Another driver request. At this time, C P U 2 4 executes the modified V G Α driver stored in R A Μ 2 8 (step S 5 6 ) until all the drivers of the extendable firmware interface are executed. Thereafter, the 10 326\patent specification (supplement)\94-04\TF944510 1273482

The final driver of the extendable firmware interface is executed to enter an operating system startup phase (0 S Β ο 〇 t P h a s e ), causing the computer under test 2 2 to start the operating system (step S 60 ). When the computer 32 does not execute the terminal receiving program, or when the host computer 32 cannot transmit the VGA driver, the host computer 3 2 waits for the computer to be tested 2 2 to execute the configuration program next time, and the computer to be tested 2 2 pairs The computer 3 2 sends a request to transfer another modified driver after the failure. At this time, the CPU 24 executes the search and transfer program, and finds and moves the original and unmodified VGA driver programmed in the extensible firmware interface of the read-only memory 26 to the RAM 28, and then the CPU 24 The VGA driver stored in the RAM 28 is executed (step S 5 8). Similarly, the last driver of the extendable firmware interface is executed to enter the operating system boot phase, causing the computer under test 2 2 to boot the operating system (step S 60). As described above, the user can easily verify the difference between before and after the modified extendable firmware interface, because the external host computer 3 2 does not transmit the modified driver to the computer under test 2 2, the computer under test 2 2 The driver that is not modified in the read-only memory 26 will be used; if the external host computer 3 2 transmits the modified driver to the computer 2 under test, the computer 2 to be tested will access the computer 3 2 The modified driver provided so that the user can immediately observe or compare the results of the change. If the modified driver is transferred to the computer 2 to be tested by the external host computer 32, and the modified driver is tested, the tested computer can be turned on and working normally, and the modified code can be modified. The latter driver re-codes the code and burns it into the read-only memory 26, thus completing the development and testing of the extendable firmware interface of the system. 11 326\patent specification (supplement)\94-04\TF944510 1273482 The above method and circuit structure and composition of an extendable toughness loader (EFI Framework-LOADER), in addition to the function of transmission, additionally provided The transfer string, the decimal/value and the program execution message, etc., wherein the transfer program execution can help the user to use the Debug, so that the development interface can quickly find out the need for correction. At the office. Even within ASLC0DE, force. The ASLC0DE carried in the extendable firmware interface architecture can be transmitted without the SMI method; it is simple to verify whether the ASL CODE is normal. Coupled with some of the tested drivers, load the test driver directly where you feel the problem with the extendable code. You don't need to boot to DOS or EFIShell to increase efficiency. The advantage of the present invention is that it does not require the use of a ROM die-LL 3 transmission line or other transmission lines and the bare board FLASHPART on the hardware, which greatly reduces the hardware required for testing. The firmware interface can be tested on bare boards or installed, and the FLASHPART package type is not limited by the operating voltage of the bare board. MASKR0M memory can be used. Moreover, because it is a pure software relationship, it does not occupy the limitation of the capacity of the physical read-only memory. As long as the RAM is normally available to transmit any code, even if it is installed, another advantage of the present invention is that the firmware engineer can Convenient to check the difference between the front and back of the driver of the extended firmware interface, due to the work extension of the message of the hexadecimal number of the 326\patent specification (supplement)\94-04\TF944510 Firmware to, in the ACPI in the transmission of the information required by the f, if necessary, the firmware interface program and test, so the only transcript. Extensible, no need to move, EEPR0M and other spaces, no, can be tested at any time. If the host computer does not implement the 1273482 line of extendable firmware interface architecture loader, it will use the code before the original FLASHPART is changed. When the host computer executes the extendable firmware interface architecture loader, It will be replaced by the new code provided by the original host computer. The user can immediately observe or compare the changes of the extendable firmware interface before and after the modification.

Another advantage of the present invention is that the extendable firmware interface loader can transmit any code, so that the program for burning the read-only memory and the code to be burned can be transmitted to update the FLASHPART. The code does not need to be updated frequently by FLASHPART. The invention may be embodied in various specific forms without departing from the spirit and scope of the invention. The scope of the present invention is defined by the scope of the appended claims, and is not limited by the description, and all changes equivalent to the meaning of the claims are intended to be included in the invention. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram of a system for loading a driver in the prior art; FIG. 2 is a block diagram of a system for loading a driver according to the present invention; and FIG. 3 is a diagram for loading a driver according to the present invention. Flow chart of the program. [Main component symbol description] 1 0 : R Ο Μ simulator 1 2 : Plug 1 4, 2 2 : Computer under test 1 5, 3 2 : Main computer 1 6 : Slot

18' 24 , 34 : CPU 13 326\Patent Specification (Replenishment)\94-04\TF944510 1273482 26 : Read only 28 : RAM 30 > 36 : 40 : LL3 Memory Transfer Interface Line

326\ patent specification (supplement)\94-04\TF944510 14

Claims (1)

1273482 X. Patent application scope: 1. A loading method of a driver of an extendable firmware interface, the host computer drives one of the extendable firmware interfaces into one of the tested computers by a transmission line. In the access memory, the loading method of the extendable interface driver includes the following steps: booting a computer under test and executing a program of the extendable firmware interface; determining whether the host computer has an execution function The terminal receiving program; when the host computer executes the terminal receiving program, transmitting the driver of the flexible firmware interface to the random access body of the tested computer; executing the random access memory The driver; and boot the operating system. 2. The loading method of the extendable firmware interface program according to claim 1, wherein when the main computer does not execute the final program, the memory is read only from one of the tested computers. Transmitting the driver of the flexible firmware interface to the random access memory and the driver. 3. The loading method of the extendable firmware interface program according to claim 1, wherein the transmission line is an LL3 line, a PORT, a LAN, a USB and a 1 3 9 4 Choose one. 4. The loading method of the extendable firmware interface program according to claim 1, wherein the extendable firmware interface to be modified may be modified when the extendable tough surface needs to be modified. Burned in the 326\patent specification (supplement)\94-04\TF944510 15 by a program firmware extension memory drive termination extension implementation of the drive of the drive body of the dielectric test 1273482 brain read only read Memory. 5. The loading method of the executable program of the extendable firmware interface according to claim 1, wherein the constructing program is burned in the read-only memory of the computer under test. 6. A computer readable recording medium for a computer system having an extendable firmware interface, wherein a host computer loads the driver of the extendable firmware interface by a transmission line In a random access memory of the computer under test, the computer readable recording medium can cause the computer to perform the following steps: booting a computer under test and executing one of the extendable firmware interfaces; Whether the host computer executes a terminal receiving program; when the host computer executes the terminal receiving program, transmitting the driver of the extendable firmware interface to the random access memory of the tested computer; Executing the driver in the random access memory; and booting the operating system. 7. The computer readable recording medium according to claim 6, wherein when the host computer does not execute the terminal receiving program, the one of the tested computers transmits the extendable memory. The driver of the firmware interface is in the random access memory and executes the driver. 8. The computer readable recording medium of claim 6, wherein the extendable firmware interface is composed of a plurality of the drivers. 9. The computer readable recording medium 16 326\patent specification (supplement)\94-04\TF944510 1273482 according to claim 6, wherein the transmission line is an LL 3 line, a C Ο Μ P 0 R Τ, one USB and one 1 3 9 4 choose one. 10. The computer readable record according to claim 6, wherein the extendable firmware interface can be edited when the extendable firmware interface needs to be modified. The only part of the computer under test. 1 1. The computer readable record of claim 7, wherein the composition program is burned in the only one of the computer to be tested. LAN, recording media F need to repair I memory recording media i memory 17 326\Patent specification (supplement)\94-04\TF944510