CN111949529A - System debugging method and device, computer equipment and storage medium - Google Patents

System debugging method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN111949529A
CN111949529A CN202010785510.XA CN202010785510A CN111949529A CN 111949529 A CN111949529 A CN 111949529A CN 202010785510 A CN202010785510 A CN 202010785510A CN 111949529 A CN111949529 A CN 111949529A
Authority
CN
China
Prior art keywords
file
debugging
identifier
bios
tool
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.)
Granted
Application number
CN202010785510.XA
Other languages
Chinese (zh)
Other versions
CN111949529B (en
Inventor
唐鑫金
邱宏伟
亢曼曼
臧公元
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Dawning Information Industry Beijing Co Ltd
Original Assignee
Dawning Information Industry Beijing Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Dawning Information Industry Beijing Co Ltd filed Critical Dawning Information Industry Beijing Co Ltd
Priority to CN202010785510.XA priority Critical patent/CN111949529B/en
Publication of CN111949529A publication Critical patent/CN111949529A/en
Application granted granted Critical
Publication of CN111949529B publication Critical patent/CN111949529B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)
  • Stored Programmes (AREA)

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 a device to be debugged receives a system debugging instruction comprising a tool identification, a target debugging file identification corresponding to the tool identification is determined according to a first mapping relation between the tool identification and a debugging file identification, a target debugging file corresponding to the target debugging file identification is determined from a BIOS binary file of the device to be debugged according to a second mapping relation between the debugging file identification and the debugging file, and the target debugging file is operated to carry out system debugging on the device to be debugged. In the method, the debugging file is integrated in the BIOS file of the equipment to be debugged, and 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 perform system debugging.

Description

System debugging method and device, computer equipment and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a system debugging method and apparatus, a computer device, and a storage medium.
Background
In the process of project development of a computer system, developers and operation and maintenance personnel are generally required to check or modify information such as a CPU, a memory, a register and the like when an abnormal condition occurs in the system through various debugging tools, so as to find a problem point and repair the problem point.
For a Basic Input Output System (BIOS) based on a Unified Extensible Firmware Interface (UEFI) architecture, a debugging software tool is generally adopted to perform System debugging on a device to be debugged, specifically, the debugging software tool is copied to a third-party device, and the third-party device is connected to the device to be debugged in an external access manner, so as to complete the System debugging of the device to be debugged.
However, the debugging method based on the third-party device 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 commissioning method is provided, the method comprising:
receiving a system debugging instruction; the system debugging instructions comprise tool identification;
determining a target debugging 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 debugging file identifier;
according to the second mapping relation, determining a target debugging file corresponding to the target debugging file identifier from the BIOS binary file of the equipment to be debugged, and operating the target debugging file to perform system debugging on the equipment to be debugged; the second mapping relation comprises a corresponding relation between the debugging file identification and the debugging 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 the BIOS framework.
In this embodiment, 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 framework, when the device to be debugged is subjected to system debugging, the device to be debugged can obtain and run the debug file in the BIOS file according to the first mapping relationship and the second mapping relationship to perform system debugging, because the debug tool is integrated into the BIOS framework of the device to be debugged, the whole debugging process is convenient and fast, the efficiency of system debugging is improved from many aspects such as safety and rapidness, and an external third-party device is not required, thereby avoiding the problem of inconvenience in debugging of the external third-party device.
In one embodiment, the first mapping relationship is that the server adds a debugging file identifier to a startup item file of the BIOS source code file, generates a tool identifier corresponding to the debugging file identifier, and establishes a correspondence between the tool identifier and the debugging file identifier; the second mapping relation is obtained after the server associates the debugging file with the corresponding debugging 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, according to a first mapping relationship established in advance, a target debug file identifier corresponding to the device to be debugged based on the tool identifier in the startup item file, 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.
In one embodiment, the running target debug file performs system debug on the device to be debugged, including:
saving a target debugging file in the BIOS binary file to a preset storage space;
and operating the 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 to perform system test, and starts a process independent from the BIOS file, so that BIOS operating resources are saved, and the operating space and operating speed of the debug file are ensured.
In a second aspect, a system commissioning method is provided, the method comprising:
acquiring a debugging file and a debugging file identifier of the debugging file;
adding the debugging file identification to a starting item file of the BIOS source code file to generate a tool identification corresponding to the debugging file identification;
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 framework to obtain a compiled BIOS binary file, and updating the compiled BIOS binary file into the equipment to be debugged.
In this embodiment, because in the BIOS file that the server complied and generated, debug file identification, debug file, and instrument identification have been integrateed, after in passing through the network update to waiting to debug the equipment with the BIOS file after compiling, can make waiting to debug the equipment and directly acquire and operate the debug file in the BIOS file and carry out system debugging, because the debug tool is integrated in waiting to debug the BIOS framework of equipment, whole debugging process is convenient, swiftly, from many-sided efficiency that has improved system debugging such as safe, swiftly, and need not external third party's equipment, avoided the inconvenient problem of external third party's equipment debugging.
In one embodiment, after the debugging file identifier is added to the boot entry file of the BIOS source code file and the tool identifier corresponding to the debugging file identifier is generated, the method further includes:
establishing a first mapping relation according to a tool identifier corresponding to the debugging file identifier;
associating the debugging file with the corresponding debugging file identifier by utilizing a preset Unified Extensible Firmware Interface (UEFI) driving model so as to establish a second mapping relation; the second mapping relationship comprises a corresponding relationship between the debugging file identification and the debugging file.
In this embodiment, the server may use a random new GUID as the debugging file identifier, and bind the GUID and the debugging file to form a corresponding relationship between the debugging file and the debugging file identifier, so that the device to be debugged may determine the target debugging file through the debugging file identifier by establishing the corresponding relationship between the debugging file identifier and the debugging file, and the method for determining the target debugging file 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:
acquiring a debugging file, and adding the debugging file to an initial BIOS source code file to obtain a first BIOS file;
and generating a debugging file identifier corresponding to the debugging file, and compiling the debugging file and the debugging file identifier in a BIOS compiling environment so as to add the debugging file and the debugging file identifier to 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 coding environment, so that the device to be debugged can determine the corresponding debug file according to the debug file identifier when performing system test based on the BIOS file, and the process is simple and effective.
In one embodiment, the generating of the debug file identifier corresponding to the debug file includes:
and generating a GUID corresponding to the debugging file as a debugging file identifier according to a preset GUID tool specification.
In this embodiment, the server generates the GUID, and uses the GUID as the debugging file identifier corresponding to the debugging file, and because the GUID has uniqueness, the correspondence between the debugging file and the debugging file identifier can be clearly determined.
In one embodiment, the adding the debug file identifier to the boot entry file of the BIOS source code file to generate the tool identifier corresponding to the debug file identifier includes:
adding the debugging file identification to the starting item file of the second BIOS file, and generating a tool identification corresponding to the debugging file identification 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 debugging file identifier and the debugging file in the BIOS compiling environment includes:
and compiling the third BIOS file in a 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 in the BIOS compilation environment to obtain the target BIOS file, and the compiling process is simple and effective.
In a third aspect, a system debugging apparatus is provided, the apparatus including:
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 debugging 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 debugging 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 operating 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 debugging file identification and the debugging 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 the BIOS framework.
In a fourth aspect, a system debugging apparatus is provided, the apparatus comprising:
the acquisition module is used for acquiring the debugging file and the debugging file identifier of the debugging file;
the generating module is used for adding the debugging file identification to a starting item file of the BIOS source code file and generating a tool identification corresponding to the debugging file identification;
and 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 the BIOS framework, 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, which includes 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 and second aspects when executing the computer program.
A sixth aspect provides a computer-readable storage medium, on which a computer program is stored, the computer program, when executed by a processor, implementing the system debugging method of 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 a system debugging instruction comprising a tool identification, a target debugging file identification corresponding to the tool identification is determined according to a first mapping relation between the tool identification and a debugging file identification, a target debugging file corresponding to the target debugging file identification is determined from a BIOS binary file of the equipment to be debugged according to a second mapping relation between the debugging file identification 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 a BIOS compiling environment so as to integrate the debugging file into the BIOS framework, when the equipment to be debugged is subjected to system debugging, the equipment to be debugged can obtain and operate the debugging file in the BIOS file according to the first mapping relation and the second mapping relation so as to carry out system debugging, and the debugging tool is integrated in the BIOS framework of the equipment to be debugged, so that the whole debugging process is convenient and quick, the system debugging efficiency is improved from the aspects of safety, quickness and the like, a third-party device does not need to be externally connected, and the problem of inconvenience in debugging of the externally connected third-party device is avoided.
Drawings
FIG. 1 is a diagram of an application environment of a system debugging method in one embodiment;
FIG. 2 is a flow diagram illustrating a method for debugging a system in one embodiment;
FIG. 3 is a flowchart illustrating a system debugging method according to an embodiment;
FIG. 4 is a flowchart illustrating a system debugging method according to another embodiment;
FIG. 5 is a flowchart illustrating a system debugging method according to an embodiment;
FIG. 6 is a flowchart illustrating a system debugging method according to another embodiment;
FIG. 7 is a block diagram showing the configuration of a system debugging apparatus according to one embodiment;
FIG. 8 is a block diagram showing the construction of a system debugging apparatus according to another embodiment;
FIG. 9 is a block diagram showing the configuration of a system debugging apparatus according to one embodiment;
FIG. 10 is a block diagram showing the configuration of a system debugging apparatus according to one embodiment;
FIG. 11 is a diagram illustrating an internal structure 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 is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The system debugging method provided by the application can be applied to the application environment shown in fig. 1. The server 101 communicates with each device to be debugged 102 through a network. The server 101 may be implemented by an independent server or a server cluster formed by a plurality of servers, the device to be debugged 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers and other computer devices, and it should be noted that a basic input output system BIOS chip is integrated in the device to be debugged.
The following describes in detail the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems by embodiments and with reference to the drawings. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. It should be noted that, in the system debugging method provided in the embodiments of fig. 2 to fig. 3 of the present application, the execution main body is the device 102 to be debugged, and may also be a system debugging apparatus, and the system debugging apparatus may become part or all of the device 102 to be debugged in a software, hardware, or a combination of software and hardware. In the following method embodiments, the execution subject is the device to be debugged 102 as an example.
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 includes the following steps:
s201, receiving a system debugging instruction; the system debug instruction includes a tool identification.
The system debugging instruction can be an instruction triggered by selection based on a starting item list in a display interface of the device to be debugged, and can also be an instruction triggered by a preset function key. Optionally, the startup item list includes a tool identifier, that is, when the tool identifier in the startup item list indicates that it is selected, a system debugging instruction is triggered. Wherein, the Tool identifier refers to a character identifier displayed in the startup item list corresponding to the system debugging Tool, and may be named as "UEFI Tool" for example.
In this embodiment, the device to be debugged receives a system debugging instruction triggered by a user based on a start item list in a display interface, for example, at a power-on self-test stage of the device to be debugged, the user may enter a BIOS Setup menu through a hot key prompted by the system, or enter a BIOS start option list, and select an option of "UEFI Tool" in the menu or the start item list to trigger the system debugging instruction, so that the device to be debugged receives the system debugging instruction carrying a Tool identifier "UEFI Tool" through internal logic, which is not limited in this embodiment.
S202, determining a target debugging file identifier corresponding to the tool identifier according to the first mapping relation; the first mapping relation comprises a corresponding relation between the tool identification and the debugging file identification.
The target debugging file identification refers to a debugging file identification corresponding to a debugging tool file of the device to be debugged. The first mapping relation refers to a corresponding relation between the tool identifier in the configured startup item file and the corresponding debugging file identifier according to a preset configuration environment.
In this embodiment, the device to be debugged determines a triggered tool identifier from the system debugging instruction, and determines a target debugging file identifier corresponding to the tool identifier according to a first mapping relationship established in advance. The device to be debugged can limit a first mapping relation between the tool identifier and the corresponding debugging file identifier based on background interface logic, so that the device to be debugged can determine the debugging file identifier corresponding to the tool identifier directly according to the interface logic; optionally, the device to be debugged may further determine, according to the first mapping relationship stored in the database, a debugging file identifier corresponding to the tool identifier, which is not limited in this embodiment.
S203, according to the second mapping relation, determining a target debugging file corresponding to the target debugging file identifier from the BIOS binary file of the device to be debugged, and operating the target debugging file to perform system debugging on the device to be debugged; the second mapping relation comprises a corresponding relation between the debugging file identification and the debugging 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 the BIOS framework.
The target debugging file refers to a debugging file integrated in the BIOS framework, and the second mapping relation refers to a corresponding relation between the debugging file identification and the functional logic of the debugging file in the BIOS file.
In this embodiment, after determining the target debug file identifier corresponding to the tool identifier according to the first mapping relationship, the device to be debugged determines the target debug file corresponding to the target debug file identifier according to the second mapping relationship that is constructed in advance. For example, the device to be debugged may define the correspondence between the debugging file identifier and the corresponding debugging file based on the background interface logic, thereby directly determining the target debugging file corresponding to the debugging file identifier from the BIOS source code file according to the interface logic, and calling and running the target debugging file to complete system debugging. Optionally, the system debugging includes checking or modifying firmware information of a CPU, a memory, a register, and the like 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 a BIOS compiling environment according to the tool identifier, the debug file, and the debug file identifier. This embodiment is not limited to this.
In the system debugging method, the device to be debugged receives a system debugging instruction comprising a tool identification, a target debugging file identification corresponding to the tool identification is determined according to a first mapping relation between the tool identification and a debugging file identification, a target debugging file corresponding to the target debugging file identification is determined from a BIOS binary file of the device to be debugged according to a second mapping relation between the debugging file identification and the debugging file, and the target debugging file is operated 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 a BIOS compiling environment so as to integrate the debugging file into the BIOS framework, when the equipment to be debugged is subjected to system debugging, the equipment to be debugged can obtain and operate the debugging file in the BIOS file according to the first mapping relation and the second mapping relation so as to carry out system debugging, and the debugging tool is integrated in the BIOS framework of the equipment to be debugged, so that the whole debugging process is convenient and quick, the system debugging efficiency is improved from the aspects of safety, quickness and the like, a third-party device does not need to be externally connected, and the problem of inconvenience in debugging of the externally connected third-party device is avoided.
When the device to be debugged receives a system debugging instruction based on the startup item list, it needs to determine a target debugging file identifier corresponding to a tool identifier in the system debugging instruction according to a corresponding relationship between the tool identifier and a debugging file identifier, where the corresponding relationship is specifically that, in one embodiment, the first mapping relationship is that the server adds the debugging file identifier to a startup item file of a BIOS source code file, generates a tool identifier corresponding to the debugging file identifier, and establishes a corresponding relationship 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 means that there is no source code file of the integrated debugging tool, and the start item file of the BIOS source code file may be a start item list of the device to be debugged; the method can also be a menu list of the POST starting-up stage of the device to be debugged. In this embodiment, the server may register the debug file identifier to the boot device list by modifying a specific code module in the BIOS source code, and define an option of displaying the debug file identifier to the boot item list as a Tool identifier, which may be named "UEFI Tool" optionally.
Optionally, in one embodiment, the attribute of the tool identifier in the launch item file is launch.
In this embodiment, after adding a debug file identifier to the server and associating the debug file identifier with a tool identifier corresponding to the debug file identifier, the server may further determine, according to the UEFI specification, that the registration type of the tool identifier is a LOAD _ OPTION _ ACTIVE attribute, so as to mark the tool identifier in the startup item file as startup, so that the tool identifier may be displayed in a display interface of the device to be debugged when the device to be debugged enters a POST startup phase or enters a system startup item list, which is not limited in this embodiment.
In this embodiment, the device to be debugged may determine the target debug file identifier corresponding to the start item file based on the tool identifier in the start item file according to the first mapping relationship established in advance, so as to perform the subsequent operation.
After the device to be debugged determines the target debugging file identifier corresponding to the tool identifier in the system debugging instruction according to the corresponding relationship between the tool identifier and the debugging file identifier, a target debugging file corresponding to the target debugging file identifier may be determined according to a second mapping relationship, where in one embodiment, the second mapping relationship is obtained after the server associates the debugging file with the corresponding debugging file identifier by using a preset unified extensible firmware interface UEFI driving model.
The debugging file identifier is a GUID defined randomly according to the GUID tool specification. In this embodiment, the server binds the generated GUID with the debug file through the UEFI driver model, and establishes a correspondence between the debug file identifier and the debug file.
In this embodiment, the server generates a GUID as the debugging file identifier, and establishes a correspondence between the debugging file identifier and the debugging file, so that the device to be debugged can determine the target debugging file through the debugging file identifier, and the method for determining the target debugging file by using the mapping relationship is simple and effective.
After the target debugging file is determined, the device to be debugged can directly run the target debugging file to perform system debugging, and can also transfer the target debugging file to another storage space to perform system debugging. In an embodiment, as shown in fig. 3, the executing the target debug file to perform system debug on the device to be debugged includes:
s301, storing the 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 which is finally compiled and integrated with a debugging tool file, and the preset storage space can be a memory space of the device to be debugged or any one designated storage space in the device to be debugged.
In this embodiment, the device to be debugged determines a debugging 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 debugging file corresponding to the tool identifier according to the debugging file identifier, so as to obtain the debugging file from the BIOS binary file, backup the debugging file to a preset storage space, open a new process independent of the BIOS binary file, and execute a system debugging operation; for example, the device to be debugged may store the debug file in a memory of the device to be debugged from the BIOS binary file, and then run the debug file from the memory to perform system debugging.
S302, operating the target debugging file in the storage space, and performing system debugging on the device 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 the system firmware of the device to be debugged, where the system testing may include checking and modifying firmware information such as a CPU, a memory, and a register, which is not limited in this embodiment.
In this embodiment, the device to be debugged stores the debug file in the storage space to perform system test, and starts a process independent from the BIOS file, so that BIOS operating resources are saved, and the operating space and operating speed of the debug file are ensured.
The following describes in detail the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems by embodiments and with reference to the drawings. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. It should be noted that the system debugging method provided in the embodiments of fig. 4 to fig. 5 of the present application has an execution main body of the server 101, and may also be a system debugging apparatus, which may be a part or all of the server 101 through software, hardware, or a combination of software and hardware. In the following method embodiments, the following method embodiments are all described by taking the server 101 as an example of an execution subject.
In an embodiment, as shown in fig. 4, a system debug method is provided, which relates to a process in which a server integrates a debug file into a BIOS framework to obtain a compiled BIOS binary file, and updates the compiled BIOS binary file to a device to be debugged, and includes the following steps:
s401, obtaining a debugging file and a debugging file identifier of the debugging file.
The debugging file is a tool file stored in a BIOS file directory; the debugging file identification is an identification which is generated by the server and corresponds to the debugging 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 a debugging file identifier according to the GUID tool specification, and bind the GUID and the debugging file to form a corresponding relationship between the debugging file and the debugging file identifier, and further, the server may also import the debugging file identifier and the debugging file into the BIOS source code compiling environment for pre-compiling, which is not limited in this embodiment.
S402, adding the debugging file identification to the starting item file of the BIOS source code file, and generating a tool identification corresponding to the debugging file identification.
In this embodiment, optionally, the server may add the debug file identifier to a boot entry file in a specified code module by modifying the current BIOS source code file, for example, the boot entry file may be a boot entry list of the system or a boot menu of the BIOS. Further, the server may define a Tool identifier corresponding to the debugging file identifier, where the Tool identifier is a selection item displayed in the display interface, and optionally, the server may name the Tool identifier as "UEFI Tool", which is not limited in this embodiment.
And S403, 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 framework, obtain a compiled BIOS binary file, and update the compiled BIOS binary file into the device 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 tool identifier, the debug file identifier, and the debug file to obtain a BIOS binary file that integrates the tool identifier, the debug file identifier, and the debug file. Optionally, the server may also update the integrated BIOS binary file to the computer device that needs 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 identifier of the debugging file, so that the debugging file identifier is added to the starting item file of the BIOS source code file, a tool identifier corresponding to the debugging file identifier is generated, the tool identifier, the debugging file identifier and the debugging file are compiled in a BIOS compiling environment, the debugging file is integrated into a BIOS framework, the compiled BIOS binary file is obtained, and the compiled BIOS binary file is updated into the device to be debugged. In the method, because the BIOS file generated by compiling the server is integrated with the debugging file identifier, the debugging file and the tool identifier, the compiled BIOS file is updated into the device to be debugged through the network, the device to be debugged can directly acquire and operate the debugging file in the BIOS file for system debugging, because the debugging tool is integrated into the BIOS framework of the device to be debugged, the whole debugging process is convenient and quick, the efficiency of system debugging is improved from many aspects such as safety and quickness, and the external third-party device is not needed, thereby avoiding the problem of inconvenient debugging of the external third-party device.
When the server performs precompilation of the BIOS file according to the debug file and the debug file identifier, in an embodiment, after the debug file identifier is added to the boot entry file of the BIOS source code file, and a tool identifier corresponding to the debug file identifier is generated, the method further includes:
and establishing a first mapping relation according to the tool identifier corresponding to the debugging file identifier.
In this embodiment, similar to the above embodiment, the server may use a random new GUID as the debugging file identifier, and bind the GUID and the debugging file to form a corresponding relationship between the debugging file and the debugging file identifier.
Optionally, in an embodiment, the system debugging method further includes: associating the debugging file with the corresponding debugging file identifier by utilizing a preset Unified Extensible Firmware Interface (UEFI) driving model so as to establish a second mapping relation; the second mapping relationship comprises a corresponding relationship between the debugging file identification and the debugging file.
In this embodiment, the server associates and binds the debug file identifier GUID and the debug file by using a preset unified extensible firmware interface UEFI driver model, and forms a corresponding relationship between the debug file and the debug file identifier as a 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.
Specifically, in an embodiment, as shown in fig. 5, the obtaining of the file identifiers of the debug file and the debug file includes:
s501, obtaining a debugging file, and adding the debugging file to the initial BIOS source code file to obtain a first BIOS file.
In this embodiment, the server may copy or move the debug file to the target directory by receiving a file moving instruction or a file copying instruction triggered based on the server display interface, where the instruction carries the debug file and the target directory of the BIOS file, so as to obtain the BIOS file including the debug file.
S502, generating a debugging file identifier corresponding to the debugging file, and compiling the debugging file and the debugging file identifier in a BIOS compiling environment so as to add the debugging file and the debugging file identifier to 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 a debugging file identifier according to the GUID tool specification, and bind the GUID and the debugging file to form a corresponding relationship between the debugging file and the debugging file identifier, further, the server imports the debugging file identifier and the debugging file into a BIOS source code compiling environment, and performs pre-compiling to obtain a second BIOS file integrating the debugging file, the debugging file identifier, and the corresponding relationship thereof, 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 coding environment, so that the device to be debugged can determine the corresponding debug file according to the debug file identifier when performing system test based on the BIOS file, and the process is simple and effective.
When the server generates the debug file identifier corresponding to the debug file, the server may obtain the debug file identifier according to any method for randomly generating an identifier, and in one embodiment, the generating the debug file identifier corresponding to the debug file includes:
and generating a GUID corresponding to the debugging file as a debugging 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 and the corresponding debug file through the UEFI driver model, so as to obtain the GUID corresponding to the debug file, and use the GUID as the debug file identifier corresponding to the debug file, which is not limited in this embodiment.
In this embodiment, the server generates the GUID, and uses the GUID as the debugging file identifier corresponding to the debugging file, and because the GUID has uniqueness, the correspondence between the debugging file and the debugging file identifier can be clearly determined.
After the server obtains the correspondence between the debug file and the debug file identifier, the server further needs to establish an identifier corresponding to the debug file identifier in the boot entry file of the BIOS, so that the user triggers a system debug operation based on the boot entry file, in one embodiment, the adding the debug file identifier to the boot entry file of the BIOS source code file generates a tool identifier corresponding to the debug file identifier, including:
adding the debugging file identification to the starting item file of the second BIOS file, and generating a tool identification corresponding to the debugging file identification 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, for example, the server may register a debug file identifier to the boot entry 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, and optionally, the server may display the Tool identifier to the boot entry list, and name the Tool identifier as "UEFI Tool", thereby obtaining a third BIOS file.
Optionally, when a tool identifier corresponding to the debugging file identifier is generated, in an embodiment, the attribute of the tool identifier in the startup item file is startup.
In this embodiment, similar to the above embodiment, after the server adds the debug file identifier and associates the debug file identifier with the tool identifier corresponding to the debug file identifier, the server may further determine, according to the UEFI specification, that the registration type of the tool identifier is a LOAD _ OPTION _ 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 be displayed in its display interface after entering a POST startup phase or entering a 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 by compiling for multiple times, so that the compiling operation on the third BIOS file after execution is performed, and the process is simple and fast.
Optionally, 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 in a 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 to obtain a final code-integrated BIOS file integrated with a debug tool, which is used to send the final code-integrated BIOS file to the device to be debugged to perform system debugging.
In this embodiment, the server compiles the third BIOS file including the tool identifier, the debug file identifier, and the debug file in the BIOS compilation environment to obtain the target BIOS file, and the compiling process is simple and effective.
In the prior art, system debugging of a device to be debugged is implemented by an external third-party device, such as a USB disk, the method is not suitable for an environment where the external third-party device is prohibited, and the external third-party device has a high operation risk and is inconvenient to operate.
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 compiled BIOS binary file is obtained, the server may send the file to the device to be debugged according to the BMC network, so as to replace and update the BIOS file in the device to be debugged. Optionally, the server may also update the compiled BIOS binary file to a device that needs to be debugged according to other network communication methods such as a local area network, which is not limited in this embodiment.
In this embodiment, after obtaining 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 does not need to update the BIOS file of the device to be debugged through an external third-party device, for example, an external USB disk.
To better explain the above method, as shown in fig. 6, the present embodiment provides a system debugging method, which specifically includes:
s101, a server acquires a debugging file, and adds the debugging file to an initial BIOS source code file to obtain a first BIOS file;
s102, the server generates a GUID corresponding to a debugging file as a debugging file identifier according to a preset GUID tool specification;
s103, the server associates the debugging file with the corresponding debugging file identifier by using a preset Unified Extensible Firmware Interface (UEFI) driving model so as to establish a second mapping relation;
s104, compiling the debugging file and the debugging file identification in a BIOS compiling environment by the server so as to add the debugging file and the debugging file identification to the first BIOS file to obtain a second BIOS file;
s105, the server adds the debugging file identification to the starting item file of the second BIOS file, and generates a tool identification corresponding to the debugging file identification to obtain a third BIOS file;
s106, the server establishes a first mapping relation according to the tool identification corresponding to the debugging file identification;
s107, the server compiles the third BIOS file in a BIOS compiling environment;
s108, the server updates the compiled BIOS binary file into the device to be debugged;
s109, receiving a system debugging instruction by the equipment to be debugged;
s110, determining a target debugging file identifier corresponding to the tool identifier by the device to be debugged according to the first mapping relation;
s111, 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 by the equipment to be debugged;
and S112, operating the target debugging file by the equipment to be debugged, and performing system debugging on the equipment to be debugged.
In this embodiment, because the BIOS file generated by server compiling is integrated with the debug file identifier, the debug file, and the tool identifier, 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, the whole debugging process is convenient and fast, the efficiency of system debugging is improved from many aspects such as safety and rapidness, and an external third-party device is not needed, thereby avoiding the problem of inconvenience in debugging of the external third-party device.
The system debugging method provided by the above embodiment has the similar implementation principle and technical effect as those of the above method embodiment, and is not described herein again.
It should be understood that although the various steps in the flow charts of fig. 2-6 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-6 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 7, there is provided a system debugging apparatus including: receiving module 01, determining module 02 and debugging module 03, wherein:
the receiving module 01 is used for receiving a system debugging instruction; the system debugging instruction comprises a tool identifier;
the determining module 02 is 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 debugging 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 debugging file identification and the debugging 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 the BIOS framework.
In an embodiment, the first mapping relationship is a correspondence relationship between a tool identifier and a debugging file identifier, where the tool identifier corresponds to the debugging file identifier, generated by adding the debugging file identifier to a boot entry file of the BIOS source code file by the server.
In one embodiment, the attribute of the tool identification in the launch item file is launch.
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 an embodiment, the debugging module 03 is specifically configured to store a target debugging file in a BIOS binary file into a preset storage space; and operating the 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 apparatus is provided, including: an obtaining module 11, a generating module 12 and a compiling module 13, wherein:
the obtaining module 11 is configured to obtain a debug file and a debug file identifier of the debug file;
the generating module 12 is configured to add the debug file identifier to the startup item file of the BIOS source code file, and generate a tool identifier corresponding to the debug file identifier;
and the compiling module 13 is configured to compile the tool identifier, the debug file identifier, and the debug file in a BIOS compiling environment, so as to integrate the debug file into the BIOS framework, obtain a compiled BIOS binary file, and update the compiled BIOS binary file into the device to be debugged.
In an embodiment, as shown in fig. 9, the system debugging apparatus further includes a first building module 14, configured to establish a first mapping relationship according to a tool identifier corresponding to the debugging file identifier.
In one embodiment, the attribute of the tool identification in the launch item file is launch.
In an embodiment, as shown in fig. 10, the system debugging apparatus further includes a second building module 15, configured to associate a debugging file with a corresponding debugging 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 comprises a corresponding relationship between the debugging file identification and the debugging file.
In an 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; and generating a debugging file identifier corresponding to the debugging file, and compiling the debugging file and the debugging file identifier in a BIOS compiling environment so as to add the debugging file and the debugging file identifier to the first BIOS file to obtain a second BIOS file.
In an embodiment, the obtaining module 11 specifically uses, according to a preset GUID tool specification, a GUID corresponding to a debug file generated as a debug file identifier.
In an embodiment, the generating module 12 is specifically configured to add the debug file identifier to the boot entry 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 in a BIOS compiling environment.
In an embodiment, the compiling module 13 is specifically configured to update the compiled BIOS binary file to the device to be debugged through a BMC network of the baseboard management controller.
For specific limitations of the system debugging apparatus, reference may be made to the above limitations of the system debugging method, which are not described herein again. The modules in the system debugging device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server or a device to be debugged, and its internal structure diagram 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 comprises a nonvolatile 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 an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a system commissioning 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, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain 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 a computer program stored therein, the processor implementing the following steps when executing the computer program:
receiving a system debugging instruction; the system debugging instructions comprise tool identification;
determining a target debugging 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 debugging file identifier;
according to the second mapping relation, determining a target debugging file corresponding to the target debugging file identifier from the BIOS binary file of the equipment to be debugged, and operating the target debugging file to perform system debugging on the equipment to be debugged; the second mapping relation comprises a corresponding relation between the debugging file identification and the debugging 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 the BIOS framework.
The implementation principle and technical effect of the computer device provided by the above embodiment are similar to those of the above method embodiment, and are not described herein again.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
acquiring a debugging file and a debugging file identifier of the debugging file;
adding the debugging file identification to a starting item file of the BIOS source code file to generate a tool identification corresponding to the debugging file identification;
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 framework to obtain a compiled BIOS binary file, and updating the compiled BIOS binary file into the equipment to be debugged.
The implementation principle and technical effect of the computer device provided by the above embodiment are similar to those of the above method embodiment, and are not described herein again.
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 instructions comprise tool identification;
determining a target debugging 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 debugging file identifier;
according to the second mapping relation, determining a target debugging file corresponding to the target debugging file identifier from the BIOS binary file of the equipment to be debugged, and operating the target debugging file to perform system debugging on the equipment to be debugged; the second mapping relation comprises a corresponding relation between the debugging file identification and the debugging 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 the BIOS framework.
The implementation principle and technical effect of the computer-readable storage medium provided by the above embodiments are similar to those of the above method embodiments, and are not described herein again.
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:
acquiring a debugging file and a debugging file identifier of the debugging file;
adding the debugging file identification to a starting item file of the BIOS source code file to generate a tool identification corresponding to the debugging file identification;
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 framework to obtain a compiled BIOS binary file, and updating the compiled BIOS binary file into the equipment to be debugged.
The implementation principle and technical effect of the computer-readable storage medium provided by the above embodiments are similar to those of the above method embodiments, and are not described herein again.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (11)

1. A method of system commissioning, the method comprising:
receiving a system debugging instruction; the system debugging instructions comprise tool identification;
determining a target debugging 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 debugging file identifier;
according to the second mapping relation, determining a target debugging file corresponding to the target debugging file identifier from a Basic Input Output System (BIOS) binary file of the equipment to be debugged, and operating 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 debugging file identification and the debugging file; the BIOS binary file is a file obtained by 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 framework.
2. The method according to claim 1, wherein the first mapping relationship is that a server adds a debugging file identifier to a boot entry file of a BIOS source code file, generates a tool identifier corresponding to the debugging file identifier, and establishes a correspondence relationship between the tool identifier and the debugging file identifier; and the second mapping relation is obtained after the server associates the debugging file with the corresponding debugging file identifier by using a preset Unified Extensible Firmware Interface (UEFI) driving model.
3. The method according to claim 1 or 2, wherein the running the target debug file to perform system debugging on the device to be debugged comprises:
saving a target debugging file in the BIOS binary file to a preset storage space;
and operating the target debugging file in the storage space, and performing system debugging on the equipment to be debugged.
4. A method of system commissioning, the method comprising:
acquiring a debugging file and a debugging file identifier of the debugging file;
adding the debugging file identification to a starting item file of a BIOS source code file to generate a tool identification corresponding to the debugging file identification;
compiling the tool identification, the debugging file identification and the debugging file in a BIOS compiling environment so as to integrate the debugging file into a BIOS framework to obtain a compiled BIOS binary file, and updating the compiled BIOS binary file into equipment to be debugged.
5. The method of claim 4, wherein after the adding the debug file identifier to the boot entry file of the BIOS source code file and generating the tool identifier corresponding to the debug file identifier, the method further comprises:
establishing a first mapping relation according to the tool identification corresponding to the debugging file identification; associating the debugging file with the corresponding debugging 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 debugging file identification and the debugging file.
6. The method according to claim 4 or 5, 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;
and generating a debugging file identifier corresponding to the debugging file, and compiling the debugging file and the debugging file identifier in a BIOS compiling environment so as to add the debugging file and the debugging file identifier to a first BIOS file to obtain a second BIOS file.
7. The method of claim 6, wherein adding the debug file identifier to a boot entry file of a BIOS source code file, and generating a tool identifier corresponding to the debug file identifier comprises:
adding the debugging file identification to the starting item file of the second BIOS file, and generating a tool identification corresponding to the debugging file identification to obtain a third BIOS file; the third BIOS file comprises the debug file, the debug file identifier, and the tool identifier;
the compiling the tool identifier, the debugging file identifier and the debugging file in a BIOS compiling environment includes:
and compiling the third BIOS file in a BIOS compiling environment.
8. A system debugging apparatus, characterized in that the apparatus comprises:
the receiving module is used for receiving a system debugging instruction; the system debugging instructions comprise tool identification;
the determining module is used for determining a target debugging 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 debugging file identifier;
the debugging module is used for determining a target debugging file corresponding to the target debugging file identifier from a BIOS binary file of the equipment to be debugged according to the second mapping relation, and operating 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 debugging file identification and the debugging file; the BIOS binary file is a file obtained by 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 framework.
9. A system debugging apparatus, characterized in that the apparatus comprises:
the device comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a debugging file and a debugging file identifier of the debugging file;
the generating module is used for adding the debugging file identification to a starting item file of a BIOS source code file and generating a tool identification corresponding to the debugging file identification;
and 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 framework, obtain a compiled BIOS binary file and update the compiled BIOS binary file into the equipment to be debugged.
10. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
CN202010785510.XA 2020-08-06 2020-08-06 System debugging method, device, computer equipment and storage medium Active CN111949529B (en)

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 true CN111949529A (en) 2020-11-17
CN111949529B 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)

Cited By (2)

* Cited by examiner, † Cited by third party
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
CN116069668A (en) * 2023-03-07 2023-05-05 中科方德软件有限公司 Debugging method, device, equipment and storage medium for distributed compiling construction task

Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010034880A1 (en) * 2000-03-02 2001-10-25 Jonathan Dzoba Configurable debug system using source and data objects
US20030154429A1 (en) * 2002-02-13 2003-08-14 Chen Song Bor Method of debugging using a USB connecting system
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
US20060059330A1 (en) * 2004-09-10 2006-03-16 Ong Soo K Remotely providing basic input/output system to a client 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
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
US20090292949A1 (en) * 2008-05-21 2009-11-26 Dell Products, Lp System and method of managing bios test routnes
US20110179260A1 (en) * 2010-01-21 2011-07-21 Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd. Method for integrating operating system into bios chip and method for booting operating system from server
US20110296409A1 (en) * 2010-05-28 2011-12-01 Dell Products, Lp System and Method for Pre-Boot Authentication of a Secure Client Hosted Virtualization in an Information Handling System
US20120137181A1 (en) * 2010-11-30 2012-05-31 International Business Machines Corporation Preventing log wrap with debug scripts
CN104142843A (en) * 2014-08-07 2014-11-12 浪潮电子信息产业股份有限公司 System power-on failure diagnosis method
US20160170862A1 (en) * 2014-12-15 2016-06-16 Dell Products L.P. Obfuscating debugging filenames
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
US20190317882A1 (en) * 2018-04-13 2019-10-17 Baidu Usa Llc Method and apparatus for testing a code file
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

Patent Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010034880A1 (en) * 2000-03-02 2001-10-25 Jonathan Dzoba Configurable debug system using source and data objects
US20030154429A1 (en) * 2002-02-13 2003-08-14 Chen Song Bor Method of debugging using a USB connecting system
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
US20060059330A1 (en) * 2004-09-10 2006-03-16 Ong Soo K Remotely providing basic input/output system to a client 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
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
US20090292949A1 (en) * 2008-05-21 2009-11-26 Dell Products, Lp System and method of managing bios test routnes
US20110179260A1 (en) * 2010-01-21 2011-07-21 Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd. Method for integrating operating system into bios chip and method for booting operating system from server
US20110296409A1 (en) * 2010-05-28 2011-12-01 Dell Products, Lp System and Method for Pre-Boot Authentication of a Secure Client Hosted Virtualization in an Information Handling System
US20120137181A1 (en) * 2010-11-30 2012-05-31 International Business Machines Corporation Preventing log wrap with debug scripts
CN104142843A (en) * 2014-08-07 2014-11-12 浪潮电子信息产业股份有限公司 System power-on failure diagnosis method
US20160170862A1 (en) * 2014-12-15 2016-06-16 Dell Products L.P. Obfuscating debugging filenames
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
US20190317882A1 (en) * 2018-04-13 2019-10-17 Baidu Usa Llc Method and apparatus for testing a code file
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)

* Cited by examiner, † Cited by third party
Title
崔莹;王宝涛;沈钢纲;: "UEFI下基于USB的调试信息输出工具的设计与实现", 计算机工程与设计, no. 24 *
庞钰宁;龙翔;高小鹏;: "SIMSOC模拟器远程调试系统的研究与实现", 微计算机信息, no. 29 *
裘文锋;: "UEFI让系统安全从启动开始", 电脑迷, no. 08 *
高云岭;杨国栋;郭元兴;: "UEFI计算机系统快速调试方法的实现", 信息安全与通信保密, no. 07 *

Cited By (2)

* Cited by examiner, † Cited by third party
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
CN116069668A (en) * 2023-03-07 2023-05-05 中科方德软件有限公司 Debugging method, device, equipment and storage medium for distributed compiling construction task

Also Published As

Publication number Publication date
CN111949529B (en) 2024-03-22

Similar Documents

Publication Publication Date Title
CN110851114A (en) Business system development method and device, electronic equipment and storage medium
RU2630171C2 (en) Method of initialization of computer system with plurality of central processors
CN101488173B (en) Method for measuring completeness of credible virtual field start-up files supporting non-delaying machine
JP5678778B2 (en) Systems and migration methods
CN111158741B (en) Method and device for monitoring dependency relationship change of service module on third party class library
CN112162753A (en) Software deployment method and device, computer equipment and storage medium
CN111008132B (en) Application debugging method and device for Android system, computer equipment and storage medium
CN104679500B (en) Method and device for realizing automatic generation of entity class
CN112558946A (en) Method, device and equipment for generating code and computer readable storage medium
CN111949529B (en) System debugging method, device, computer equipment and storage medium
CN111459541A (en) Application program packaging method and device, computer equipment and storage medium
CN113504918A (en) Equipment tree configuration optimization method and device, computer equipment and storage medium
CN112965731B (en) Method, device, equipment and storage medium for Flutter hot update based on Tinker
US11599342B2 (en) Pathname independent probing of binaries
CN111949262A (en) Front-end project construction method and device, computer equipment and storage medium
CN115017436B (en) Data interaction method and device of application program, computer equipment and storage medium
CN112214213B (en) Linux kernel development and management method and device, computer equipment and storage medium
CN112988602B (en) Verification platform generation method and device, computer equipment and storage medium
CN115964721A (en) Program verification method and electronic equipment
CN113010199B (en) Application updating method and device, computer equipment and storage medium
CN113868127A (en) Online debugging method and device, computer equipment and storage medium
CN112230939A (en) Hardware module repairing method and device, computer equipment and storage medium
CN112162743A (en) Driver generation method, device, computer equipment and storage medium
CN113535143A (en) Stack information processing method and device, electronic equipment and storage medium
CN105573891A (en) Android application electricity consumption statistics method and device

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