CN111949529B - System debugging method, device, computer equipment and storage medium - Google Patents
System debugging method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111949529B CN111949529B CN202010785510.XA CN202010785510A CN111949529B CN 111949529 B CN111949529 B CN 111949529B CN 202010785510 A CN202010785510 A CN 202010785510A CN 111949529 B CN111949529 B CN 111949529B
- Authority
- CN
- China
- Prior art keywords
- file
- debug
- identifier
- debugging
- bios
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 81
- 238000013507 mapping Methods 0.000 claims abstract description 90
- 238000004590 computer program Methods 0.000 claims description 17
- 238000010276 construction Methods 0.000 claims 2
- 230000008569 process Effects 0.000 abstract description 15
- 238000010586 diagram Methods 0.000 description 10
- 230000001960 triggered effect Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 238000012360 testing method Methods 0.000 description 5
- 230000008676 import Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
Abstract
The application relates to a system debugging method, a system debugging device, computer equipment and a storage medium. The method comprises the following steps: the method comprises the steps that equipment to be debugged receives a system debugging instruction comprising a tool identifier, a target debugging file identifier corresponding to the tool identifier is determined according to a first mapping relation between the tool identifier and the debugging file identifier, a target debugging file corresponding to the target debugging file identifier is determined from a BIOS binary file of the equipment to be debugged according to a second mapping relation between the debugging file identifier and the debugging file, and the target debugging file is operated to carry out system debugging on the equipment to be debugged. In the method, since the debugging files are integrated in the BIOS files of the equipment to be debugged, the equipment to be debugged can acquire and operate the debugging files in the BIOS files according to the first mapping relation and the second mapping relation to carry out system debugging, the whole debugging process is convenient and quick, the system debugging efficiency is improved, no external third party equipment is needed, and the problem of inconvenient debugging of the external third party equipment is avoided.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a system debugging method, a device, a computer device, and a storage medium.
Background
In the process of developing a project of a computer system, developers and operation and maintenance personnel are usually required to check or modify information such as a CPU, a memory, a register and the like when the system is abnormal through various debugging tools, so that a problem point is found and repaired.
Aiming at a basic input output system (Basic Input Output System, BIOS) based on a unified extensible firmware interface (Unified Extensible Firmware Interface, UEFI) architecture, a debugging software tool is generally adopted to carry out system debugging on equipment to be debugged, specifically, the debugging software tool is copied into third party equipment, and the third party equipment is connected to the equipment to be debugged in an external access mode, so that the system debugging on the equipment to be debugged is completed.
However, the third party equipment-based debugging method has the problems of inconvenient debugging and low debugging efficiency.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a system debugging method, apparatus, computer device, and storage medium.
In a first aspect, a system debugging method is provided, the method comprising:
receiving a system debugging instruction; the system debugging instruction comprises a tool identifier;
Determining a target debug file identifier corresponding to the tool identifier according to the first mapping relation; the first mapping relation comprises a corresponding relation between a tool identifier and a debug file identifier;
determining a target debugging file corresponding to the target debugging file identification from the BIOS binary file of the equipment to be debugged according to the second mapping relation, and running the target debugging file to perform system debugging on the equipment to be debugged; the second mapping relation comprises a corresponding relation between the debug file identification and the debug file; the BIOS binary file is a file obtained by compiling the tool identifier, the debug file identifier and the debug file in a BIOS compiling environment to integrate the debug file into a BIOS architecture.
In this embodiment, since the BIOS binary file is a file obtained by compiling the tool identifier, the debug file identifier and the debug file in the BIOS compiling environment so as to integrate the debug file into the BIOS architecture, when the device to be debugged performs system debugging, the device to be debugged may acquire and operate the debug file in the BIOS file according to the first mapping relationship and the second mapping relationship to perform system debugging.
In one embodiment, the first mapping relationship is that the server adds the debug file identifier to the startup file of the BIOS source code file, generates a tool identifier corresponding to the debug file identifier, and establishes a correspondence between the tool identifier and the debug file identifier; the second mapping relation is obtained after the server associates the debug file with the corresponding debug file identifier by using a preset Unified Extensible Firmware Interface (UEFI) driving model; wherein the attribute of the tool identifier in the startup item file is startup.
In this embodiment, the device to be debugged may determine, based on the tool identifier in the startup file, the target debug file identifier corresponding to the device to be debugged according to the first mapping relationship constructed in advance, and by generating a GUID as the debug file identifier and establishing a correspondence between the debug file identifier and the debug file, the device to be debugged may determine the target debug file through the debug file identifier, and the method for determining the target debug file by using the two mapping relationships is simple and effective, and does not need to connect with a third party device.
In one embodiment, the running target debug file performs system debug on a device to be debugged, including:
Storing a target debugging file in the BIOS binary file into a preset storage space;
and running a target debugging file in the storage space, and performing system debugging on the equipment to be debugged.
In this embodiment, the device to be debugged stores the debug file in the storage space for system test, and starts the process of independent and BIOS files, so as to save BIOS operation resources and ensure the operation space and operation speed of the debug file.
In a second aspect, a system debugging method is provided, the method comprising:
obtaining a debugging file and a debugging file identification of the debugging file;
adding the debug file identifier into a startup item file of the BIOS source code file to generate a tool identifier corresponding to the debug file identifier;
compiling the tool identifier, the debugging file identifier and the debugging file in a BIOS compiling environment to integrate the debugging file into a BIOS architecture, obtaining a compiled BIOS binary file, and updating the compiled BIOS binary file into the equipment to be debugged.
In this embodiment, since the debug file identifier, the debug file, and the tool identifier are integrated in the BIOS file generated by compiling the server, after updating the compiled BIOS file to the device to be debugged through the network, the device to be debugged can directly acquire and run the debug file in the BIOS file to perform system debugging.
In one embodiment, after the adding the debug file identifier to the boot item file of the BIOS source code file and generating the tool identifier corresponding to the debug file identifier, the method further includes:
establishing a first mapping relation according to a tool identifier corresponding to the debug file identifier;
associating the debug file with a corresponding debug file identifier by using a preset Unified Extensible Firmware Interface (UEFI) driving model so as to establish a second mapping relation; the second mapping relationship includes a correspondence between the debug file identification and the debug file.
In this embodiment, the server may use a random new GUID as the debug file identifier, bind the GUID with the debug file to form a corresponding relationship between the debug file identifier and the debug file identifier, and by establishing the corresponding relationship between the debug file identifier and the debug file, the device to be debugged may determine the target debug file through the debug file identifier, and the method for determining the target debug file by using the two mapping relationships is simple and effective.
In one embodiment, the obtaining the debug file and the file identifier of the debug file includes:
obtaining a debugging file, and adding the debugging file into an initial BIOS source code file to obtain a first BIOS file;
Generating a debug file identifier corresponding to the debug file, compiling the debug file and the debug file identifier under a BIOS compiling environment, and adding the debug file and the debug file identifier into the first BIOS file to obtain a second BIOS file.
In this embodiment, the server generates the second BIOS file including the debug file and the debug file identifier by importing the debug file and the debug file identifier into the BIOS encoding environment, so that the device to be debugged may determine the corresponding debug file according to the debug file identifier when performing a system test based on the BIOS file.
In one embodiment, the generating the debug file identifier corresponding to the debug file includes:
and generating a GUID corresponding to the debug file as a debug file identifier according to a preset GUID tool specification.
In this embodiment, the server generates the GUID, and uses the GUID as the debug file identifier corresponding to the debug file, and because the GUID has uniqueness, the corresponding relationship between the debug file and the debug file identifier can be clearly determined.
In one embodiment, the adding the debug file identifier to the boot item file of the BIOS source code file to generate the tool identifier corresponding to the debug file identifier includes:
Adding the debug file identifier into a startup item file of the second BIOS file, and generating a tool identifier corresponding to the debug file identifier to obtain a third BIOS file; the third BIOS file comprises a debugging file, a debugging file identifier and a tool identifier;
the compiling the tool identifier, the debug file identifier and the debug file in the BIOS compiling environment includes:
and compiling the third BIOS file under the BIOS compiling environment.
In this embodiment, the server compiles the third BIOS file including the tool identifier, the debug file identifier, and the debug file under the BIOS compiling environment to obtain the target BIOS file, so that the compiling process is simple and effective.
In a third aspect, there is provided a system debugging device, the device comprising:
the receiving module is used for receiving a system debugging instruction; the system debugging instruction comprises a tool identifier;
the determining module is used for determining a target debug file identifier corresponding to the tool identifier according to the first mapping relation; the first mapping relation comprises a corresponding relation between a tool identifier and a debug file identifier;
the debugging module is used for determining a target debugging file corresponding to the target debugging file identifier from the BIOS binary file of the equipment to be debugged according to the second mapping relation, and running the target debugging file to carry out system debugging on the equipment to be debugged; the second mapping relation comprises a corresponding relation between the debug file identification and the debug file; the BIOS binary file is a file obtained by compiling the tool identifier, the debug file identifier and the debug file in a BIOS compiling environment to integrate the debug file into a BIOS architecture.
In a fourth aspect, there is provided a system debugging device, the device comprising:
the acquisition module is used for acquiring the debug file and the debug file identification of the debug file;
the generating module is used for adding the debug file identifier into the startup item file of the BIOS source code file to generate a tool identifier corresponding to the debug file identifier;
the compiling module is used for compiling the tool identifier, the debugging file identifier and the debugging file in a BIOS compiling environment so as to integrate the debugging file into a BIOS architecture, obtain a compiled BIOS binary file, and update the compiled BIOS binary file into the equipment to be debugged.
In a fifth aspect, a computer device is provided, including a memory and a processor, where the memory stores a computer program, and the processor implements the system debugging method according to any one of the first aspect and the second aspect when the processor executes the computer program.
In a sixth aspect, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the system debugging method according to any one of the first and second aspects.
According to the system debugging method, the device, the computer equipment and the storage medium, the equipment to be debugged receives the system debugging instruction comprising the tool identifier, the target debugging file identifier corresponding to the tool identifier is determined according to the first mapping relation between the tool identifier and the debugging file identifier, the target debugging file corresponding to the target debugging file identifier is determined from the BIOS binary file of the equipment to be debugged according to the second mapping relation between the debugging file identifier and the debugging file, and the target debugging file is operated to carry out system debugging on the equipment to be debugged. In the method, the BIOS binary file is a file obtained by compiling the tool identifier, the debugging file identifier and the debugging file in the BIOS compiling environment so as to integrate the debugging file into the BIOS architecture, when the equipment to be debugged is subjected to system debugging, the equipment to be debugged can acquire and operate the debugging file in the BIOS file according to the first mapping relation and the second mapping relation to carry out system debugging, and the whole debugging process is convenient and quick because the debugging tool is integrated into the BIOS architecture of the equipment to be debugged, so that the efficiency of system debugging is improved from multiple aspects such as safety, rapidness and the like, no external third-party equipment is needed, and the problem of inconvenient debugging of the external third-party equipment is avoided.
Drawings
FIG. 1 is an application environment diagram of a system debug method in one embodiment;
FIG. 2 is a flow diagram of a system debug method in one embodiment;
FIG. 3 is a flow diagram of a system debug method in one embodiment;
FIG. 4 is a flow chart of a system debugging method in another embodiment;
FIG. 5 is a flow diagram of a system debug method in one embodiment;
FIG. 6 is a flow chart of a system debugging method in another embodiment;
FIG. 7 is a block diagram of a system debug apparatus in one embodiment;
FIG. 8 is a block diagram of a system debugging device in another embodiment;
FIG. 9 is a block diagram of a system debugging device in one embodiment;
FIG. 10 is a block diagram of a system debugging device in one embodiment;
FIG. 11 is an internal block diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
The system debugging method provided by the application can be applied to an application environment shown in figure 1. Wherein the server 101 communicates with each device to be commissioned 102 through a network. The server 101 may be implemented by an independent server or a server cluster formed by a plurality of servers, and the device to be debugged 102 may be, but is not limited to, various computer devices such as a personal computer, a notebook computer, a smart phone, a tablet computer, etc., and it should be noted that a BIOS chip of a basic input/output system is integrated in the device to be debugged.
The following will specifically describe the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems by means of examples and with reference to the accompanying drawings. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. It should be noted that, in the system debugging method provided in the embodiments of fig. 2 to 3 of the present application, the execution body is the device to be debugged 102, and may also be a system debugging device, where the system debugging device may be a part or all of the device to be debugged 102 in a mode of software, hardware or a combination of software and hardware. In the following method embodiments, the execution subject is the device to be debugged 102 is taken as an example to describe.
In one embodiment, as shown in fig. 2, a system debugging method is provided, which relates to a process of performing system debugging on a device to be debugged based on a debugging tool integrated into a BIOS architecture after receiving a system debugging instruction, and the method comprises the following steps:
s201, receiving a system debugging instruction; the system debug instruction includes a tool identification.
The system debugging instruction may be an instruction triggered by selecting a starting item list in a display interface of the device to be debugged, or may be an instruction triggered by a preset function key. Optionally, the startup list includes a tool identifier, that is, when the tool identifier in the startup list is selected, a system debug instruction is triggered. Wherein the Tool identifier refers to a character identifier displayed in the startup item list corresponding to the system debugging Tool, which may be named "UEFI Tool", for example.
In this embodiment, the device to be debugged receives a system debug instruction triggered by a user based on a startup item list in a display interface, for example, in a startup self-checking stage of the device to be debugged, the user may enter a BIOS Setup menu through a hot key of a system prompt, or enter a BIOS startup item list, and select an option of "UEFI Tool" in the menu or startup item list to trigger the system debug instruction, so that the device to be debugged receives, through internal logic, the system debug instruction carrying a Tool identifier "UEFI Tool", which is not limited in this embodiment.
S202, determining a target debug file identifier corresponding to the tool identifier according to a first mapping relation; the first mapping relationship includes a correspondence between tool identifiers and debug file identifiers.
The target debug file identifier refers to a debug file identifier corresponding to a debug tool file of the device to be debugged. The first mapping relation refers to a corresponding relation between tool identifiers in the configured startup files and debug file identifiers corresponding to the tool identifiers according to a preset configuration environment.
In this embodiment, the device to be debugged determines a triggered tool identifier from the system debug instruction, and determines, according to a first mapping relationship constructed in advance, a target debug file identifier corresponding to the tool identifier. The first mapping relation between the tool identifier and the corresponding debug file identifier can be defined on the basis of the background interface logic, so that the device to be debugged can directly determine the debug file identifier corresponding to the tool identifier according to the interface logic; optionally, the device to be debugged may further determine a debug file identifier corresponding to the tool identifier according to the first mapping relationship stored in the database, which is not limited in this embodiment.
S203, determining a target debugging file corresponding to the target debugging file identifier from the BIOS binary file of the equipment to be debugged according to the second mapping relation, and running the target debugging file to perform system debugging on the equipment to be debugged; the second mapping relation comprises a corresponding relation between the debug file identification and the debug file; the BIOS binary file is a file obtained by compiling the tool identifier, the debug file identifier and the debug file in a BIOS compiling environment to integrate the debug file into a BIOS architecture.
The target debug file refers to a debug file integrated in the BIOS architecture, and the second mapping relationship refers to a correspondence between a debug file identifier and debug file function logic in the BIOS file.
In this embodiment, after determining, according to the first mapping relationship, a target debug file identifier corresponding to the tool identifier, the device to be debugged determines, according to a second mapping relationship constructed in advance, a target debug file corresponding to the target debug file identifier. For example, the corresponding relation between the debug file identifier and the corresponding debug file can be limited based on the background interface logic, so that the target debug file corresponding to the debug file identifier is determined from the BIOS source code file directly according to the interface logic, and the target debug file is called and operated to complete system debugging. Optionally, system debugging includes checking or modifying firmware information such as a CPU, a memory, a register, etc. of the system, so as to find a problem point and repair the problem point, where the BIOS binary file is compiled by the server in the BIOS compiling environment according to the tool identifier, the debug file, and the debug file identifier. This embodiment is not limited thereto.
In the system debugging method, the device to be debugged receives the system debugging instruction comprising the tool identifier, determines the target debugging file identifier corresponding to the tool identifier according to the first mapping relation between the tool identifier and the debugging file identifier, determines the target debugging file corresponding to the target debugging file identifier from the BIOS binary file of the device to be debugged according to the second mapping relation between the debugging file identifier and the debugging file, and operates the target debugging file to carry out system debugging on the device to be debugged. In the method, the BIOS binary file is a file obtained by compiling the tool identifier, the debugging file identifier and the debugging file in the BIOS compiling environment so as to integrate the debugging file into the BIOS architecture, when the equipment to be debugged is subjected to system debugging, the equipment to be debugged can acquire and operate the debugging file in the BIOS file according to the first mapping relation and the second mapping relation to carry out system debugging, and the whole debugging process is convenient and quick because the debugging tool is integrated into the BIOS architecture of the equipment to be debugged, so that the efficiency of system debugging is improved from multiple aspects such as safety, rapidness and the like, no external third-party equipment is needed, and the problem of inconvenient debugging of the external third-party equipment is avoided.
When the device to be debugged receives a system debugging instruction based on a startup list, a target debugging file identifier corresponding to the tool identifier in the system debugging instruction is required to be determined according to the corresponding relation between the tool identifier and the debugging file identifier, wherein the corresponding relation is specifically that in one embodiment, the first mapping relation is that a server adds the debugging file identifier to a startup file of a BIOS source code file, generates a tool identifier corresponding to the debugging file identifier, and establishes a corresponding relation between the tool identifier and the debugging file identifier.
Optionally, the BIOS source code file is an initial source code file of the BIOS, which refers to a source code file without an integrated debugging tool, and a startup item file of the BIOS source code file may be a startup item list of the device to be debugged; and the menu list of the POST startup stage of the equipment to be debugged can also be provided. In this embodiment, the server may add the debug file identification registration to the boot device list by modifying a specified code module in the BIOS source code, while defining its options displayed to the boot item list as a Tool identification, which may optionally be named "UEFI Tool".
Optionally, in one embodiment, the attribute of the tool identifier in the launch item file is launch.
In this embodiment, after adding the debug file identifier and associating the debug file identifier with the corresponding tool identifier, the server may further determine, according to the UEFI specification, the registration type of the tool identifier as a load_operation_active attribute, so as to mark the tool identifier in the startup item file as startup, so that the device to be debugged may display the tool identifier in the display interface after entering the POST startup stage or entering the system startup item list, which is not limited in this embodiment.
In this embodiment, the device to be debugged may determine, based on the tool identifier in the startup file, the target debug file identifier corresponding to the device to be debugged according to the first mapping relationship constructed in advance, so as to execute the subsequent operation.
After determining the target debug file identifier corresponding to the tool identifier in the system debug instruction according to the corresponding relation between the tool identifier and the debug file identifier, the device to be debugged may determine the target debug file corresponding to the target debug file identifier according to a second mapping relation, where in an embodiment, the second mapping relation is obtained after the server uses a preset unified extensible firmware interface UEFI driving model to associate the debug file with the corresponding debug file identifier.
Wherein the debug file is identified as defining a random GUID according to the GUID tool specification. In this embodiment, the server binds the generated GUID and the debug file through the UEFI driving model, and establishes a correspondence between the debug file identifier and the debug file.
In this embodiment, the server generates a GUID as the debug file identifier, and establishes a correspondence between the debug file identifier and the debug file, so that the device to be debugged can determine the target debug file through the debug file identifier, and the method for determining the target debug file by using the mapping relationship is simple and effective.
After determining the target debugging file, the device to be debugged can directly operate the target debugging file to perform system debugging, or can transfer the target debugging file to another storage space to perform system debugging. In one embodiment, as shown in fig. 3, the running target debug file performs system debug on a device to be debugged, including:
s301, storing a target debugging file in the BIOS binary file into a preset storage space.
The BIOS binary file is different from a BIOS source code file, the BIOS binary file is a file integrated with a debugging tool file obtained through final compiling, and the preset storage space can be a memory space of equipment to be debugged or a storage space appointed by any one of the equipment to be debugged.
In this embodiment, the device to be debugged determines a debug file identifier corresponding to the tool identifier according to the first mapping relationship and the second mapping relationship in the BIOS file, and determines a debug file corresponding to the debug file identifier according to the debug file identifier, so as to obtain the debug file from the BIOS binary file, and back up the debug file into a preset storage space, so as to start a new process of the BIOS binary file independently, and execute a system debugging operation; for example, the device to be debugged may store the debug file from the BIOS binary file into the memory of the device to be debugged, and further run the debug file from the memory to perform system debug, which is not limited in this embodiment.
S302, running a target debugging file in the storage space, and performing system debugging on equipment to be debugged.
In this embodiment, the device to be debugged directly runs the target debug file in the storage space, and performs system debugging on its own system firmware, where the system test may include checking and modifying firmware information such as CPU, memory, and registers, which is not limited in this embodiment.
In this embodiment, the device to be debugged stores the debug file in the storage space for system test, and starts the process of independent and BIOS files, so as to save BIOS operation resources and ensure the operation space and operation speed of the debug file.
The following will specifically describe the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems by means of examples and with reference to the accompanying drawings. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. It should be noted that, in the system debugging method provided in the embodiments of fig. 4 to 5 of the present application, the execution body is the server 101, and may also be a system debugging device, where the system debugging device may be a part or all of the server 101 in a manner of software, hardware, or a combination of software and hardware. In the following method embodiments, the execution subject is the server 101 as an example.
In one embodiment, as shown in fig. 4, a system debugging method is provided, which relates to a process that a server integrates a debugging file into a BIOS architecture to obtain a compiled BIOS binary file, and updates the compiled BIOS binary file into a device to be debugged, and includes the following steps:
s401, obtaining a debugging file and a debugging file identification of the debugging file.
The debugging file is a tool file stored under the BIOS file directory; the debug file identifier is an identifier generated by the server and corresponding to the debug file.
In this embodiment, the server may copy the debug tool source file or debug file to the BIOS source code directory by receiving a move file instruction, or a copy file instruction. Optionally, the server may generate and define a random new GUID as the debug file identifier according to the GUID tool specification, bind the GUID with the debug file to form a corresponding relationship between the debug file and the debug file identifier, and further, the server may further import the debug file identifier and the debug file into the BIOS source code compiling environment for precompiled.
S402, adding the debug file identifier into a startup item file of the BIOS source code file, and generating a tool identifier corresponding to the debug file identifier.
In this embodiment, optionally, the server may add the debug file identifier registration to the startup item file in the specified code module by modifying the current BIOS source code file, and the startup item file may be a startup item list of the system or a startup menu of the BIOS, for example. Further, the server may define a Tool identifier corresponding to the debug file identifier, where the Tool identifier is a selection item displayed in the display interface, alternatively, the server may designate the Tool identifier as "UEFI Tool", which is not limited in this embodiment.
S403, compiling the tool identifier, the debugging file identifier and the debugging file in a BIOS compiling environment to integrate the debugging file into a BIOS architecture, obtaining a compiled BIOS binary file, and updating the compiled BIOS binary file into the equipment to be debugged.
In this embodiment, the server imports the tool identifier, the debug file identifier, and the debug file into the BIOS compiling environment, and compiles the BIOS binary file after integrating the tool identifier, the debug file identifier, and the debug file. Optionally, the server may update the integrated BIOS binary file to the computer device to be debugged through a BMC network or other networks, which is not limited in this embodiment.
In the system debugging method, the server acquires the debugging file and the debugging file identification of the debugging file, so that the debugging file identification is added into the startup item file of the BIOS source code file, the tool identification corresponding to the debugging file identification is generated, the tool identification, the debugging file identification and the debugging file are compiled in the BIOS compiling environment, the debugging file is integrated into the BIOS architecture, the compiled BIOS binary file is obtained, and the compiled BIOS binary file is updated into the equipment to be debugged. In the method, because the debugging file identification, the debugging file and the tool identification are integrated in the BIOS file generated by compiling the server, after the compiled BIOS file is updated to the equipment to be debugged through the network, the equipment to be debugged can directly acquire and operate the debugging file in the BIOS file to carry out system debugging, and because the debugging tool is integrated into the BIOS framework of the equipment to be debugged, the whole debugging process is convenient and quick, the efficiency of system debugging is improved from multiple aspects such as safety and rapidness, and the problem of inconvenient debugging of the external third party equipment is avoided without the external third party equipment.
When the server precompiles the BIOS file according to the debug file and the debug file identifier, in one embodiment, after adding the debug file identifier to the startup item file of the BIOS source code file to generate the tool identifier corresponding to the debug file identifier, the method further includes:
and establishing a first mapping relation according to the tool identifier corresponding to the debug file identifier.
In this embodiment, similar to the above embodiment, the server may use a random new GUID as the debug file identifier, and bind the GUID with the debug file to form a correspondence between the debug file and the debug file identifier.
Optionally, in one embodiment, the system debugging method further includes: associating the debug file with a corresponding debug file identifier by using a preset Unified Extensible Firmware Interface (UEFI) driving model so as to establish a second mapping relation; the second mapping relationship includes a correspondence between the debug file identification and the debug file.
In this embodiment, the server uses a preset unified extensible firmware interface UEFI driving model to associate and bind the debug file identifier GUID with the debug file, so as to form a corresponding relationship between the debug file and the debug file identifier, and use the corresponding relationship as the second mapping relationship.
In this embodiment, the server establishes a correspondence between the debug file identifier and the debug file, so that the device to be debugged can determine the target debug file through the debug file identifier, and the method for determining the target debug file by using the mapping relationship is simple and effective.
In the step of obtaining the debug file and the debug file identifier, the server needs to integrate the debug file and the debug file identifier into the BIOS architecture, specifically, in one embodiment, as shown in fig. 5, the obtaining the debug file and the debug file identifier includes:
s501, obtaining a debugging file, and adding the debugging file into an initial BIOS source code file to obtain a first BIOS file.
In this embodiment, the server may receive a mobile file instruction or a copy file instruction triggered based on a display interface of the server, where the instruction carries a target directory of the debug file and the BIOS file, so that the server copies or moves the debug file to the target directory, and obtains the BIOS file including the debug file.
S502, generating a debug file identifier corresponding to the debug file, compiling the debug file and the debug file identifier under a BIOS compiling environment, and adding the debug file and the debug file identifier into the first BIOS file to obtain a second BIOS file.
In this embodiment, optionally, the server may generate and define a random new GUID as the debug file identifier according to the GUID tool specification, bind the GUID with the debug file to form a corresponding relationship between the debug file and the debug file identifier, further, import the debug file identifier and the debug file into the BIOS source code compiling environment, and precompiled the debug file identifier and the second BIOS file of the corresponding relationship, which is not limited in this embodiment.
In this embodiment, the server generates the second BIOS file including the debug file and the debug file identifier by importing the debug file and the debug file identifier into the BIOS encoding environment, so that the device to be debugged may determine the corresponding debug file according to the debug file identifier when performing a system test based on the BIOS file.
When generating the debug file identifier corresponding to the debug file, the server may obtain the debug file identifier according to any random identifier generation method, and in one embodiment, the generating the debug file identifier corresponding to the debug file includes:
And generating a GUID corresponding to the debug file as a debug file identifier according to a preset GUID tool specification.
The preset GUID tool specification can be any method for randomly generating GUIDs, and the generated GUIDs have uniqueness. In this embodiment, optionally, the server may generate a new GUID according to the GUID tool specification, and then bind the GUID with the corresponding debug file through the UEFI driving model, so as to obtain a GUID corresponding to the debug file, and use the GUID as a debug file identifier corresponding to the debug file.
In this embodiment, the server generates the GUID, and uses the GUID as the debug file identifier corresponding to the debug file, and because the GUID has uniqueness, the corresponding relationship between the debug file and the debug file identifier can be clearly determined.
After the server obtains the correspondence between the debug file and the debug file identifier, the server also needs to establish an identifier corresponding to the debug file identifier in the startup file of the BIOS, so that the user triggers a system debug operation based on the startup file, and in one embodiment, the adding the debug file identifier to the startup file of the BIOS source code file generates a tool identifier corresponding to the debug file identifier, which includes:
Adding the debug file identifier into a startup item file of the second BIOS file, and generating a tool identifier corresponding to the debug file identifier to obtain a third BIOS file; the third BIOS file includes a debug file, a debug file identification, and a tool identification.
In this embodiment, the server may add the debug file identifier registration to the startup file by modifying a specified code module in the BIOS source code, and generate a Tool identifier corresponding to the debug file identifier at the same time, or alternatively, the server may display the Tool identifier to the startup list, and name the Tool identifier as "UEFI Tool", so as to obtain a third BIOS file.
Optionally, when generating the tool identifier corresponding to the debug file identifier, in one embodiment, the attribute of the tool identifier in the startup item file is startup.
In this embodiment, similar to the above embodiment, after adding the debug file identifier and associating the debug file identifier with the corresponding tool identifier, the server may further determine, according to the UEFI specification, the registration type of the tool identifier as a load_operation_active attribute, and mark the tool identifier in the startup item file as being capable of being started, so that the device to be debugged may display the tool identifier in its display interface after entering the POST startup stage, or entering the system startup item list, which is not limited in this embodiment.
In this embodiment, the device to be debugged obtains the third BIOS file including the debug file, the debug file identifier, and the tool identifier through multiple compilations, so that the compiling operation on the third BIOS file after execution is simple and fast.
Optionally, compiling the tool identifier, the debug file identifier and the debug file in the BIOS compiling environment includes:
and compiling the third BIOS file under the BIOS compiling environment.
In this embodiment, the service device compiles a third BIOS file including a tool identifier, a debug file identifier, and a debug file in a BIOS compiling environment, so as to obtain a final BIOS file integrated with a debug tool after code integration, and sends the BIOS file to a device to be debugged for system debugging.
In this embodiment, the server compiles the third BIOS file including the tool identifier, the debug file identifier, and the debug file under the BIOS compiling environment to obtain the target BIOS file, so that the compiling process is simple and effective.
In the prior art, system debugging of equipment to be debugged is realized through an external third party device, such as a USB disk, the method is not suitable for an environment in which the external third party device is forbidden, and the external third party device has large operation risk and inconvenient operation.
And updating the compiled BIOS binary file into the equipment to be debugged through a Baseboard Management Controller (BMC) network.
In this embodiment, after the server obtains the compiled BIOS binary file, the server may send the file to the device to be debugged according to the BMC network, so as to replace the BIOS file in the device to be debugged. Optionally, the server may update the compiled BIOS binary file to the device to be debugged according to other network communication modes such as a local area network, which is not limited in this embodiment.
In this embodiment, after the server obtains the BIOS binary file of the integrated debugging file, the server only needs to send the file to the device to be debugged through the network to replace and update the BIOS file of the device to be debugged, and the BIOS file of the device to be debugged does not need to be updated through an external third party device, for example, an external USB disk.
In order to better illustrate the above method, as shown in fig. 6, this embodiment provides a system debugging method, which specifically includes:
s101, a server acquires a debugging file, and adds the debugging file into an initial BIOS source code file to obtain a first BIOS file;
s102, the server generates a GUID corresponding to the debug file as a debug file identifier according to a preset GUID tool specification;
s103, the server utilizes a preset Unified Extensible Firmware Interface (UEFI) driving model to associate the debug file with the corresponding debug file identifier so as to establish a second mapping relation;
s104, compiling the debugging file and the debugging file identifier under a BIOS compiling environment by the server so as to add the debugging file and the debugging file identifier into the first BIOS file to obtain a second BIOS file;
s105, the server adds the debug file identifier into a startup item file of the second BIOS file, and generates a tool identifier corresponding to the debug file identifier to obtain a third BIOS file;
s106, the server establishes a first mapping relation according to the tool identifier corresponding to the debug file identifier;
s107, the server compiles the third BIOS file in a BIOS compiling environment;
s108, the server updates the compiled BIOS binary file into the equipment to be debugged;
S109, the equipment to be debugged receives a system debugging instruction;
s110, the equipment to be debugged determines a target debug file identifier corresponding to the tool identifier according to the first mapping relation;
s111, the equipment to be debugged determines a target debugging file corresponding to the target debugging file identification from the BIOS binary file of the equipment to be debugged according to the second mapping relation;
s112, the equipment to be debugged runs the target debugging file and performs system debugging on the equipment to be debugged.
In this embodiment, since the debug file identifier, the debug file, and the tool identifier are integrated in the BIOS file compiled and generated by the server, after the compiled BIOS file is updated to the device to be debugged through the network, the device to be debugged can acquire and operate the debug file in the BIOS file according to the first mapping relationship and the second mapping relationship to perform system debugging, so that the whole debugging process is convenient and fast, the efficiency of system debugging is improved from multiple aspects such as safety and rapidness, and the problem of inconvenient debugging of the external third party device is avoided without the external third party device.
The system debugging method provided in the above embodiment has similar implementation principle and technical effects to those of the above method embodiment, and will not be described herein.
It should be understood that, although the steps in the flowcharts of fig. 2-6 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 2-6 may include multiple steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the steps or stages are performed necessarily performed in sequence, but may be performed alternately or alternately with at least a portion of the steps or stages in other steps or other steps.
In one embodiment, as shown in fig. 7, there is provided a system debugging apparatus, comprising: a receiving module 01, a determining module 02 and a debugging module 03, wherein:
a receiving module 01, configured to receive a system debug instruction; the system debugging instruction comprises a tool identifier;
a determining module 02, configured to determine, according to the first mapping relationship, a target debug file identifier corresponding to the tool identifier; the first mapping relation comprises a corresponding relation between a tool identifier and a debug file identifier;
The debugging module 03 is configured to determine, according to the second mapping relationship, a target debugging file corresponding to the target debugging file identifier from the BIOS binary file of the device to be debugged, and run the target debugging file to perform system debugging on the device to be debugged; the second mapping relation comprises a corresponding relation between the debug file identification and the debug file; the BIOS binary file is a file obtained by compiling the tool identifier, the debug file identifier and the debug file in a BIOS compiling environment to integrate the debug file into a BIOS architecture.
In one embodiment, the first mapping relationship is that the server adds the debug file identifier to the boot item file of the BIOS source code file, generates a tool identifier corresponding to the debug file identifier, and establishes a correspondence relationship between the tool identifier and the debug file identifier.
In one embodiment, the attribute of the tool identifier in the startup item file is startup.
In one embodiment, the second mapping relationship is obtained after the server associates the debug file with the corresponding debug file identifier by using a preset unified extensible firmware interface UEFI driving model.
In one embodiment, the debug module 03 is specifically configured to save a target debug file in a BIOS binary file to a preset storage space; and running a target debugging file in the storage space, and performing system debugging on the equipment to be debugged.
In one embodiment, as shown in fig. 8, another system debugging device is provided, comprising: an acquisition module 11, a generation module 12 and a compiling module 13, wherein:
an obtaining module 11, configured to obtain a debug file and a debug file identifier of the debug file;
the generating module 12 is configured to add a debug file identifier to a startup item file of the BIOS source code file, and generate a tool identifier corresponding to the debug file identifier;
the compiling module 13 is configured to compile the tool identifier, the debug file identifier, and the debug file in a BIOS compiling environment, integrate the debug file into a BIOS architecture, obtain a compiled BIOS binary file, and update the compiled BIOS binary file into the device to be debugged.
In one embodiment, as shown in fig. 9, the system debug apparatus further includes a first building module 14, configured to build a first mapping relationship according to a tool identifier corresponding to the debug file identifier.
In one embodiment, the attribute of the tool identifier in the startup item file is startup.
In one embodiment, as shown in fig. 10, the system debugging device further includes a second building module 15, configured to associate a debug file with a corresponding debug file identifier by using a preset unified extensible firmware interface UEFI driving model, so as to establish a second mapping relationship; the second mapping relationship includes a correspondence between the debug file identification and the debug file.
In one embodiment, the obtaining module 11 is specifically configured to obtain a debug file, and add the debug file to an initial BIOS source code file to obtain a first BIOS file; generating a debug file identifier corresponding to the debug file, compiling the debug file and the debug file identifier under a BIOS compiling environment, and adding the debug file and the debug file identifier into the first BIOS file to obtain a second BIOS file.
In one embodiment, the obtaining module 11 specifically generates, as the debug file identifier, a GUID corresponding to the debug file according to a preset GUID tool specification.
In one embodiment, the generating module 12 is specifically configured to add a debug file identifier to a boot item file of the second BIOS file, and generate a tool identifier corresponding to the debug file identifier, so as to obtain a third BIOS file; the third BIOS file comprises a debugging file, a debugging file identifier and a tool identifier; the compiling module 13 is specifically configured to compile the third BIOS file under a BIOS compiling environment.
In one embodiment, the compiling module 13 is specifically configured to update the compiled BIOS binary file to the device to be debugged through the baseboard management controller BMC network.
The specific limitation of the system debugging device can be referred to the limitation of the system debugging method hereinabove, and the description thereof is omitted here. The respective modules in the system debugging device described above may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a server or a device to be debugged, and its internal structure may be as shown in fig. 11. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program, when executed by a processor, implements a system debugging method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 11 is merely a block diagram of a portion of the structure associated with the present application and is not limiting of the computer device to which the present application applies, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:
receiving a system debugging instruction; the system debugging instruction comprises a tool identifier;
determining a target debug file identifier corresponding to the tool identifier according to the first mapping relation; the first mapping relation comprises a corresponding relation between a tool identifier and a debug file identifier;
determining a target debugging file corresponding to the target debugging file identification from the BIOS binary file of the equipment to be debugged according to the second mapping relation, and running the target debugging file to perform system debugging on the equipment to be debugged; the second mapping relation comprises a corresponding relation between the debug file identification and the debug file; the BIOS binary file is a file obtained by compiling the tool identifier, the debug file identifier and the debug file in a BIOS compiling environment to integrate the debug file into a BIOS architecture.
The computer device provided in the foregoing embodiments has similar implementation principles and technical effects to those of the foregoing method embodiments, and will not be described herein in detail.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:
obtaining a debugging file and a debugging file identification of the debugging file;
adding the debug file identifier into a startup item file of the BIOS source code file to generate a tool identifier corresponding to the debug file identifier;
compiling the tool identifier, the debugging file identifier and the debugging file in a BIOS compiling environment to integrate the debugging file into a BIOS architecture, obtaining a compiled BIOS binary file, and updating the compiled BIOS binary file into the equipment to be debugged.
The computer device provided in the foregoing embodiments has similar implementation principles and technical effects to those of the foregoing method embodiments, and will not be described herein in detail.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
receiving a system debugging instruction; the system debugging instruction comprises a tool identifier;
Determining a target debug file identifier corresponding to the tool identifier according to the first mapping relation; the first mapping relation comprises a corresponding relation between a tool identifier and a debug file identifier;
determining a target debugging file corresponding to the target debugging file identification from the BIOS binary file of the equipment to be debugged according to the second mapping relation, and running the target debugging file to perform system debugging on the equipment to be debugged; the second mapping relation comprises a corresponding relation between the debug file identification and the debug file; the BIOS binary file is a file obtained by compiling the tool identifier, the debug file identifier and the debug file in a BIOS compiling environment to integrate the debug file into a BIOS architecture.
The computer readable storage medium provided in the above embodiment has similar principle and technical effects to those of the above method embodiment, and will not be described herein.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
obtaining a debugging file and a debugging file identification of the debugging file;
adding the debug file identifier into a startup item file of the BIOS source code file to generate a tool identifier corresponding to the debug file identifier;
Compiling the tool identifier, the debugging file identifier and the debugging file in a BIOS compiling environment to integrate the debugging file into a BIOS architecture, obtaining a compiled BIOS binary file, and updating the compiled BIOS binary file into the equipment to be debugged.
The computer readable storage medium provided in the above embodiment has similar principle and technical effects to those of the above method embodiment, and will not be described herein.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (10)
1. A system debugging method, the method comprising:
receiving a system debugging instruction based on a starting item list; the system debugging instruction comprises a tool identifier;
determining a target debug file identifier corresponding to the tool identifier according to a first mapping relation; the first mapping relation is that a server adds a debugging file identifier to a starting item file of a Basic Input Output System (BIOS) source code file of equipment to be debugged, a tool identifier corresponding to the debugging file identifier is generated, and a corresponding relation between the tool identifier and the debugging file identifier is established;
Determining a target debugging file corresponding to the target debugging file identifier from a BIOS binary file according to a second mapping relation, and running the target debugging file to perform system debugging on the equipment to be debugged; the second mapping relation is a corresponding relation between the debug file identification and the debug file which is established by the server associating the debug file with the corresponding debug file identification by using a preset unified extensible firmware interface UEFI driving model; the BIOS binary file is obtained by compiling the tool identifier, the debug file identifier and the debug file under a BIOS compiling environment, and updating the tool identifier, the debug file identifier and the debug file into the equipment to be debugged through a network so as to integrate the debug file into a BIOS architecture.
2. The method of claim 1, wherein the running the target debug file system-debugs the device to be debugged, comprising:
storing a target debugging file in the BIOS binary file into a preset storage space;
and running the target debugging file in the storage space, and performing system debugging on the equipment to be debugged.
3. A system debugging method, the method comprising:
Acquiring a debugging file and a debugging file identification of the debugging file;
adding the debug file identifier to a startup item file of a BIOS source code file, and generating a tool identifier corresponding to the debug file identifier;
establishing a first mapping relation according to the tool identifier corresponding to the debug file identifier;
associating the debug file with a corresponding debug file identifier by using a preset Unified Extensible Firmware Interface (UEFI) driving model so as to establish a second mapping relation; the second mapping relation comprises a corresponding relation between the debug file identification and the debug file;
compiling the tool identifier, the debugging file identifier and the debugging file under a BIOS compiling environment to integrate the debugging file into a BIOS architecture, obtaining a compiled BIOS binary file, and updating the compiled BIOS binary file into equipment to be debugged through a network.
4. The method of claim 3, wherein the obtaining the debug file and the file identification of the debug file comprises:
acquiring the debugging file, and adding the debugging file into an initial BIOS source code file to obtain a first BIOS file;
Generating a debug file identifier corresponding to the debug file, compiling the debug file and the debug file identifier under a BIOS compiling environment, and adding the debug file and the debug file identifier into a first BIOS file to obtain a second BIOS file.
5. The method of claim 4, wherein the adding the debug file identifier to a boot item file of a BIOS source code file, generating a tool identifier corresponding to the debug file identifier, comprises:
adding the debug file identifier to a startup item file of the second BIOS file, and generating a tool identifier corresponding to the debug file identifier to obtain a third BIOS file; the third BIOS file comprises the debug file, the debug file identification, and the tool identification;
the compiling the tool identifier, the debug file identifier and the debug file in the BIOS compiling environment includes:
and compiling the third BIOS file under a BIOS compiling environment.
6. A system commissioning device, the device comprising:
the receiving module is used for receiving a system debugging instruction based on the startup list; the system debugging instruction comprises a tool identifier;
The determining module is used for determining a target debug file identifier corresponding to the tool identifier according to the first mapping relation; the first mapping relation is that a server adds a debugging file identifier to a starting item file of a Basic Input Output System (BIOS) source code file of equipment to be debugged, a tool identifier corresponding to the debugging file identifier is generated, and a corresponding relation between the tool identifier and the debugging file identifier is established;
the debugging module is used for determining a target debugging file corresponding to the target debugging file identifier from BIOS binary files of equipment to be debugged according to the second mapping relation, and running the target debugging file to carry out system debugging on the equipment to be debugged; the second mapping relation is a corresponding relation between the debug file identification and the debug file which is established by the server associating the debug file with the corresponding debug file identification by using a preset unified extensible firmware interface UEFI driving model; the BIOS binary file is obtained by compiling the tool identifier, the debug file identifier and the debug file under a BIOS compiling environment, and updating the tool identifier, the debug file identifier and the debug file into the equipment to be debugged through a network so as to integrate the debug file into a BIOS architecture.
7. The apparatus of claim 6, wherein the debug module is further to:
storing a target debugging file in the BIOS binary file into a preset storage space; and running the target debugging file in the storage space, and performing system debugging on the equipment to be debugged.
8. A system commissioning device, the device comprising:
the acquisition module is used for acquiring the debug file and the debug file identification of the debug file;
the generating module is used for adding the debug file identifier to a startup item file of the BIOS source code file to generate a tool identifier corresponding to the debug file identifier;
the first construction module is used for establishing a first mapping relation according to the tool identifier corresponding to the debug file identifier;
the second construction module is used for associating the debug file with the corresponding debug file identifier by utilizing a preset Unified Extensible Firmware Interface (UEFI) driving model so as to establish a second mapping relation; the second mapping relation comprises a corresponding relation between the debug file identification and the debug file;
the compiling module is used for compiling the tool identifier, the debugging file identifier and the debugging file under a BIOS compiling environment so as to integrate the debugging file into a BIOS architecture, obtain a compiled BIOS binary file, and update the compiled BIOS binary file into equipment to be debugged through a network.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any one of claims 1 to 5 when the computer program is executed.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010785510.XA CN111949529B (en) | 2020-08-06 | 2020-08-06 | System debugging method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010785510.XA CN111949529B (en) | 2020-08-06 | 2020-08-06 | System debugging method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111949529A CN111949529A (en) | 2020-11-17 |
| CN111949529B true CN111949529B (en) | 2024-03-22 |
Family
ID=73331789
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010785510.XA Active CN111949529B (en) | 2020-08-06 | 2020-08-06 | System debugging method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111949529B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113849239A (en) * | 2021-09-29 | 2021-12-28 | 超越科技股份有限公司 | Method and medium for remotely modifying BIOS starting item by server |
| CN116069668B (en) * | 2023-03-07 | 2023-06-09 | 中科方德软件有限公司 | Debugging method, device, equipment and storage medium for distributed compiling construction task |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE10320303A1 (en) * | 2002-11-15 | 2004-06-09 | Kaltenstadler, Luitpold, Dipl.-Inform. (FH) | Synchronous real-time storage comparison of two parallel-running programs, involves adapting data supplied from compared programs to achieve correspondence |
| CN1670700A (en) * | 2004-03-19 | 2005-09-21 | 英业达股份有限公司 | Computer program data automatic compiling method and system |
| TW200532555A (en) * | 2004-03-16 | 2005-10-01 | Inventec Corp | Method and system for automatically compiling computer program data |
| CN1848093A (en) * | 2005-04-17 | 2006-10-18 | 深圳市顶星数码网络技术有限公司 | Method for debugging high configuration and power supply interface module in basic inputting and outputting system |
| CN104142843A (en) * | 2014-08-07 | 2014-11-12 | 浪潮电子信息产业股份有限公司 | System power-on failure diagnosis method |
| CN106201790A (en) * | 2015-05-08 | 2016-12-07 | 深圳市祈飞科技有限公司 | A kind of adjustment method based on DSDT table and debugging system |
| CN106909362A (en) * | 2015-12-23 | 2017-06-30 | 研祥智能科技股份有限公司 | The method and apparatus that the method and apparatus of BMC firmwares generation, BMC systems start |
| CN109992517A (en) * | 2019-04-03 | 2019-07-09 | 中电科技（北京）有限公司 | Firmware module adjustment method and system based on UEFI |
| CN110018965A (en) * | 2019-04-12 | 2019-07-16 | 广东虹勤通讯技术有限公司 | A kind of BIOS single-step debug control method, apparatus and system |
| CN110413467A (en) * | 2019-07-31 | 2019-11-05 | 浪潮商用机器有限公司 | A kind of adjustment method, device, equipment and the medium of server B IOS |
| CN110990253A (en) * | 2019-10-24 | 2020-04-10 | 苏州浪潮智能科技有限公司 | Method and device for realizing application debugging, computer storage medium and terminal |
| CN111367745A (en) * | 2020-03-13 | 2020-07-03 | 苏州浪潮智能科技有限公司 | Memory pressure testing method and system without support of operating system and related components |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7055136B2 (en) * | 2000-03-02 | 2006-05-30 | Texas Instruments Incorporated | Configurable debug system with dynamic menus |
| US6941491B2 (en) * | 2002-02-13 | 2005-09-06 | Inventec Corporation | Method of debugging using a USB connecting system |
| US7353377B2 (en) * | 2004-09-10 | 2008-04-01 | Intel Corporation | Remotely providing basic input/output system to a client system |
| US20070168978A1 (en) * | 2005-12-19 | 2007-07-19 | Inventec Corporation | Computer program code debugging method and system |
| US20080141073A1 (en) * | 2006-12-07 | 2008-06-12 | Inventec Corporation | BIOS debugging system and method |
| US7895472B2 (en) * | 2008-05-21 | 2011-02-22 | Dell Products, Lp | System and method of managing BIOS test routnes |
| CN102135893A (en) * | 2010-01-21 | 2011-07-27 | 鸿富锦精密工业（深圳）有限公司 | Method for integrating operating system on BIOS (Basic Input Output System) chip and starting operating system on server |
| US8589702B2 (en) * | 2010-05-28 | 2013-11-19 | Dell Products, Lp | System and method for pre-boot authentication of a secure client hosted virtualization in an information handling system |
| US8694834B2 (en) * | 2010-11-30 | 2014-04-08 | International Business Machines Corporation | Preventing log wrap with debug scripts |
| US9483381B2 (en) * | 2014-12-15 | 2016-11-01 | Dell Products L.P. | Obfuscating debugging filenames |
| US11151018B2 (en) * | 2018-04-13 | 2021-10-19 | Baidu Usa Llc | Method and apparatus for testing a code file |
-
2020
- 2020-08-06 CN CN202010785510.XA patent/CN111949529B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE10320303A1 (en) * | 2002-11-15 | 2004-06-09 | Kaltenstadler, Luitpold, Dipl.-Inform. (FH) | Synchronous real-time storage comparison of two parallel-running programs, involves adapting data supplied from compared programs to achieve correspondence |
| TW200532555A (en) * | 2004-03-16 | 2005-10-01 | Inventec Corp | Method and system for automatically compiling computer program data |
| CN1670700A (en) * | 2004-03-19 | 2005-09-21 | 英业达股份有限公司 | Computer program data automatic compiling method and system |
| CN1848093A (en) * | 2005-04-17 | 2006-10-18 | 深圳市顶星数码网络技术有限公司 | Method for debugging high configuration and power supply interface module in basic inputting and outputting system |
| CN104142843A (en) * | 2014-08-07 | 2014-11-12 | 浪潮电子信息产业股份有限公司 | System power-on failure diagnosis method |
| CN106201790A (en) * | 2015-05-08 | 2016-12-07 | 深圳市祈飞科技有限公司 | A kind of adjustment method based on DSDT table and debugging system |
| CN106909362A (en) * | 2015-12-23 | 2017-06-30 | 研祥智能科技股份有限公司 | The method and apparatus that the method and apparatus of BMC firmwares generation, BMC systems start |
| CN109992517A (en) * | 2019-04-03 | 2019-07-09 | 中电科技（北京）有限公司 | Firmware module adjustment method and system based on UEFI |
| CN110018965A (en) * | 2019-04-12 | 2019-07-16 | 广东虹勤通讯技术有限公司 | A kind of BIOS single-step debug control method, apparatus and system |
| CN110413467A (en) * | 2019-07-31 | 2019-11-05 | 浪潮商用机器有限公司 | A kind of adjustment method, device, equipment and the medium of server B IOS |
| CN110990253A (en) * | 2019-10-24 | 2020-04-10 | 苏州浪潮智能科技有限公司 | Method and device for realizing application debugging, computer storage medium and terminal |
| CN111367745A (en) * | 2020-03-13 | 2020-07-03 | 苏州浪潮智能科技有限公司 | Memory pressure testing method and system without support of operating system and related components |
Non-Patent Citations (4)
| Title |
|---|
| SIMSOC模拟器远程调试系统的研究与实现;庞钰宁;龙翔;高小鹏;;微计算机信息(第29期);全文 * |
| UEFI下基于USB的调试信息输出工具的设计与实现;崔莹;王宝涛;沈钢纲;;计算机工程与设计(第24期);全文 * |
| UEFI计算机系统快速调试方法的实现;高云岭;杨国栋;郭元兴;;信息安全与通信保密(第07期);全文 * |
| UEFI让系统安全从启动开始;裘文锋;;电脑迷(第08期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111949529A (en) | 2020-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110851114A (en) | Business system development method and device, electronic equipment and storage medium | |
| CN111949529B (en) | System debugging method, device, computer equipment and storage medium | |
| CN107632827B (en) | Method and device for generating installation package of application | |
| CN111158741B (en) | Method and device for monitoring dependency relationship change of service module on third party class library | |
| CN104679500B (en) | Method and device for realizing automatic generation of entity class | |
| CN112256321A (en) | Static library packaging method and device, computer equipment and storage medium | |
| CN112558946A (en) | Method, device and equipment for generating code and computer readable storage medium | |
| CN109255107A (en) | Configuration software processing method, device, computer equipment and storage medium | |
| CN110990048A (en) | Method and system for monitoring resource loss of Unity project | |
| CN103257852A (en) | Method and device for building development environment of distributed application system | |
| CN111949262A (en) | Front-end project construction method and device, computer equipment and storage medium | |
| CN110928548A (en) | Data processing method and equipment | |
| CN111124872A (en) | Branch detection method and device based on difference code analysis and storage medium | |
| CN112561690A (en) | Method, system, equipment and storage medium for testing credit card staging service interface | |
| US20150355997A1 (en) | Server-Platform Simulation Service | |
| CN110908644A (en) | Configuration method and device of state node, computer equipment and storage medium | |
| CN113791809B (en) | Application exception handling method and device and computer readable storage medium | |
| CN104021007A (en) | Parameter renewing method and electronic devices | |
| CN110597552A (en) | Configuration method, device and equipment of project continuous integration pipeline and storage medium | |
| CN113535182B (en) | Project engineering construction method and device, computer equipment and storage medium | |
| CN114090785A (en) | Service processing method, device, computer equipment and storage medium | |
| CN112214213A (en) | Linux kernel development and management method and device, computer equipment and storage medium | |
| CN112612474A (en) | Product transplanting method and device, storage medium and electronic equipment | |
| CN105573891A (en) | Android application electricity consumption statistics method and device | |
| CN113010199B (en) | Application updating method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |