Method for quick firmware update and booting to enter operating system

Abstract

The invention provides a method for quick firmware update and booting to enter an operating system, and relates to the field of large-scale computer testing. The method comprises the following steps of: 1) determining that a first startup item of a machine is boot from build-in shell; 2) putting a firmware file and a tool into a U disk or a hard disk; 3) entering a file system storing the firmware file and the tool after entering UEFI shell by the machine, and automatically running a firmware update command; 4) after the firmware update is completed, if firmware does not need to be restarted and activated, automatically calling an operating system boot file by a program, and starting the operating system to perform diagnostic testing; and 5) if the firmware needs to be restarted and activated after being updated, restarting the machine to automatically enter uefi shell, directly calling the operating system boot file by the program, and booting the operating system to be started for performing diagnostic testing. According to the method, the operating system does not need to be loaded, so that the update time is shortened; and the requirements of the firmware update tool on the operating system do not need to be considered, so that the update process is simplified.

Description

technical field [0001] The invention relates to the field of large-scale testing of computers, in particular to a method for quickly updating firmware and guiding it into an operating system. Background technique [0002] In the current large-scale computer testing process, most diagnostic tests need to update the firmware of BIOS, BMC and various PCIe cards. [0003] In the current test process, most of the diagnostic tests perform firmware updates in DOS, Linux, and Windows operating systems, and most of them require online firmware updates for BIOS, BMC and other chips and various PCIe cards. Some factories update under DOS, and some factories update under Linux, Windows and other operating systems. In the current mode, there are the following problems: [0004] (1) The DOS environment cannot directly start Linux, you need to use tools or modify the startup file, and UEFI BIOS gradually does not support DOS. [0005] (2) If you need to start the system to update the fi...

AI Technical Summary

Problems solved by technology

[0004] (1) The DOS environment cannot directly start Linux, you need to use tools or modify the startup file, and UEFI BIOS gradually does not support DOS

[0005] (2) If you need to start the system to update the firmware on the Linux / Windows system side, it will take a long time to load the system regardless of the PXE boot mode or the hard disk boot mode

[0006] (3) Updating the firmware on the Linux / Windows system side depends on the system, and needs to adjust the operating system, such as installing drivers and corresponding tools, which is not conducive to large-scale testing in the factory

[0007] (4) Many firmware updates need to be restarted. When there are many components that need to update the firmware, it often happens that after a long time of testing, the machine is still loading the system and restarting, which seriously causes waste of manpower and time, and low test efficiency.

Images