CN115185734A - Firmware abnormity diagnosis method and device based on interruption, computer equipment and storage medium - Google Patents

Abstract

The invention relates to a firmware abnormity diagnosis method based on interrupt, a device, a computer device and a storage medium, wherein the method comprises the following steps: running the firmware; judging whether the running firmware enters a loop death state or not; if the running firmware enters the endless loop state, triggering external interruption to enable the CPU to enter an interruption mode; dumping a user call stack according to the interrupt mode; and analyzing the call path according to the call stack to obtain an analysis result. The invention stores the user call stack in the interrupt mode by triggering the interrupt, thereby analyzing and obtaining the call path and the transmitted parameters of the firmware and finding out the design defects of the firmware.

Description

Interrupt-based firmware abnormality diagnosis method, device, computer equipment and storage medium

technical field

The present invention relates to the technical field of firmware abnormality diagnosis, in particular to an interrupt-based firmware abnormality diagnosis method, device, computer equipment and storage medium.

Background technique

Without a debugger, logic exceptions in firmware are often difficult to analyze and locate. For example, due to a flaw in the firmware design, triggered by a certain command sequence, the firmware enters an infinite loop state. At this time, the CPU cannot respond to external requests and cannot obtain further diagnostic information.

SUMMARY OF THE INVENTION

The purpose of the present invention is to overcome the deficiencies of the prior art, and to provide an interrupt-based firmware abnormality diagnosis method, device, computer equipment and storage medium.

In order to solve the above-mentioned technical problems, the present invention adopts the following technical solutions:

In a first aspect, this embodiment provides an interrupt-based firmware abnormality diagnosis method, including the following steps:

run firmware;

Determine whether the running firmware has entered an infinite loop state;

If the running firmware enters an infinite loop state, an external interrupt is triggered to make the CPU enter the interrupt mode;

Dump the user call stack according to the interrupt mode;

According to the call stack, analyze the call path to obtain the analysis result.

A further technical solution thereof is: after the step of judging whether the running firmware enters an infinite loop state, the step further includes: if the running firmware does not enter the infinite loop state, jumping to execute the running firmware.

Its further technical solution is: the external interrupt is triggered, so that the CPU enters the interrupt mode step, and the external interrupt is triggered by pulling down or pulling up the GPIO, or sending IPC information through other CPUs.

A further technical solution thereof is: after the step of analyzing the calling path according to the calling stack to obtain the analysis result, the method further includes: analyzing the reason why the firmware enters an infinite loop according to the analysis result.

In a second aspect, this embodiment provides an interrupt-based firmware abnormality diagnosis device, including: a running unit, a judging unit, a trigger entry unit, a calling unit, and an analyzing unit;

the running unit for running firmware;

The judging unit is used to judge whether the running firmware enters an infinite loop state;

The trigger entry unit is used to trigger an external interrupt if the running firmware enters an infinite loop state, so that the CPU enters the interrupt mode;

The calling unit is used to dump the user call stack according to the interrupt mode;

The analysis unit is configured to analyze the call path according to the call stack to obtain the analysis result.

Its further technical solution is as follows: it further includes: a jumping unit for jumping to execute the running firmware if the running firmware does not enter an infinite loop state.

Its further technical solution is: the trigger enters the unit, and the external interrupt is triggered by pulling down or pulling up the GPIO, or sending IPC information through other CPUs.

The further technical solution is as follows: further comprising: an analysis unit for analyzing the reason why the firmware enters an infinite loop according to the analysis result.

In a third aspect, this embodiment provides a computer device, the computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned based on the computer program when the processor executes the computer program. Interrupted firmware exception diagnostic method.

In a fourth aspect, this embodiment provides a storage medium, where the storage medium stores a computer program, the computer program includes program instructions, and the program instructions, when executed by a processor, can implement the above-mentioned interrupt-based firmware exception diagnosis method.

Compared with the prior art, the present invention has the beneficial effects that: by triggering an interrupt, the user call stack is dumped in the interrupt mode, thereby analyzing the calling path of the firmware and the transferred parameters, and finding out the firmware design defect.

The present invention will be further described below with reference to the accompanying drawings and specific embodiments.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only for the present invention. In some embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

1 is a schematic flowchart of an interrupt-based firmware abnormality diagnosis method provided by an embodiment of the present invention;

2 is a schematic block diagram of an interrupt-based firmware abnormality diagnosis apparatus provided by an embodiment of the present invention;

FIG. 3 is a schematic block diagram of a computer device according to an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

It is to be understood that, when used in this specification and the appended claims, the terms "comprising" and "comprising" indicate the presence of the described features, integers, steps, operations, elements and/or components, but do not exclude one or The presence or addition of a number of other features, integers, steps, operations, elements, components, and/or sets thereof.

It is also to be understood that the terminology used in this specification of the present invention is for the purpose of describing particular embodiments only and is not intended to limit the present invention. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural unless the context clearly dictates otherwise.

It should further be understood that, as used in this specification and the appended claims, the term "and/or" refers to and including any and all possible combinations of one or more of the associated listed items .

Referring to the specific embodiment shown in FIG. 1 , the present invention discloses a method for diagnosing abnormality of firmware based on interrupt, comprising the following steps:

S1, run the firmware;

Specifically, the firmware is SSD firmware. Run the firmware to enable the CPU's GPIO interrupts and IPC interrupts.

S2, determine whether the running firmware enters an infinite loop state;

Specifically, whether the running firmware enters an infinite loop state is distinguished by judging whether the firmware responds to an external request.

Specifically, after step S2, the method further includes: if the running firmware does not enter an infinite loop state, jumping to execute step S1.

Specifically, the infinite loop state is no longer responding to external requests.

S3, if the running firmware enters an infinite loop state, an external interrupt is triggered to make the CPU enter the interrupt mode;

Specifically, in step S3, the external interrupt is triggered by pulling low or high GPIO (General Purpose Input/OutputPort, general input and output port) or sending IPC (inter-processor communication module) information through other CPUs.

S4, according to the interrupt mode, dump the user call stack;

Specifically, after entering the interrupt mode, obtain the user mode (user mode) stack pointer and stack content, and print and save them through the serial port.

S5, analyze the call path according to the call stack to obtain the analysis result.

Specifically, according to the stack pointer and stack content of the user mode, the firmware calling path and the passed parameters are analyzed and obtained, which provides help for firmware abnormal diagnosis and finds firmware design defects.

Specifically, after step S5, the method further includes: analyzing the reason why the firmware enters an infinite loop according to the analysis result. For example, due to a flaw in the firmware design, the firmware enters an infinite loop state triggered by a certain command sequence.

The invention dumps the user call stack in the interrupt mode by triggering the interrupt, thereby analyzing the calling path of the firmware and the transmitted parameters, and finding out the design defect of the firmware.

Referring to FIG. 2 , the present invention also discloses an interrupt-based firmware abnormality diagnosis device, comprising: a running unit 10 , a judging unit 20 , a trigger entry unit 30 , a calling unit 40 and an analyzing unit 50 ;

the running unit 10, for running firmware;

The judging unit 20 is used for judging whether the running firmware enters an infinite loop state;

The trigger entry unit 30 is used to trigger an external interrupt if the running firmware enters an infinite loop state, so that the CPU enters the interrupt mode;

The calling unit 40 is used to dump the user call stack according to the interrupt mode;

The analysis unit 50 is configured to analyze the call path according to the call stack to obtain the analysis result.

Wherein, the device further includes: a jumping unit, configured to jump to execute the running firmware if the running firmware does not enter an infinite loop state.

Wherein, the trigger enters the unit 30, and the external interrupt is triggered by pulling down or pulling up the GPIO, or sending IPC information through other CPUs.

Wherein, the device further includes: an analysis unit, configured to analyze the reason why the firmware enters an infinite loop according to the analysis result.

It should be noted that those skilled in the art can clearly understand that, for the specific implementation process of the above-mentioned interrupt-based firmware abnormality diagnosis device and each unit, reference may be made to the corresponding descriptions in the foregoing method embodiments. For the convenience and brevity of the description, It is not repeated here.

The above-mentioned interrupt-based firmware abnormality diagnosis apparatus can be implemented in the form of a computer program, and the computer program can be executed on a computer device as shown in FIG. 3 .

Please refer to FIG. 3, which is a schematic block diagram of a computer device provided by an embodiment of the present application; the computer device 500 may be a terminal or a server, wherein the terminal may be a smart phone, a tablet computer, a notebook computer, a Electronic devices with communication capabilities, such as desktop computers, personal digital assistants, and wearables. The server can be an independent server or a server cluster composed of multiple servers.

Referring to FIG. 3 , the computer device 500 includes a processor 502 , a memory and a network interface 505 connected by a system bus 501 , wherein the memory may include a non-volatile storage medium 503 and an internal memory 504 .

The nonvolatile storage medium 503 can store an operating system 5031 and a computer program 5032 . The computer program 5032 includes program instructions that, when executed, cause the processor 502 to perform an interrupt-based firmware exception diagnosis method.

The processor 502 is used to provide computing and control capabilities to support the operation of the entire computer device 500 .

The internal memory 504 provides an environment for running the computer program 5032 in the non-volatile storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can execute an interrupt-based firmware abnormality diagnosis method.

The network interface 505 is used for network communication with other devices. Those skilled in the art can understand that the structure shown in FIG. 3 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device 500 to which the solution of the present application is applied. The specific computer device 500 may include more or fewer components than shown, or combine certain components, or have a different arrangement of components.

Wherein, the processor 502 is used to run the computer program 5032 stored in the memory to realize the following steps:

Step S1, run the firmware;

Step S2, judging whether the running firmware enters an infinite loop state;

In step S3, if the running firmware enters an infinite loop state, an external interrupt is triggered, so that the CPU enters the interrupt mode;

Step S4, according to the interrupt mode, dump the user call stack;

Step S5, analyze the call path according to the call stack to obtain the analysis result.

It should be understood that, in this embodiment of the present application, the processor 502 may be a central processing unit (Central Processing Unit, CPU), and the processor 502 may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), dedicated integrated Circuit (Application Specific Integrated Circuit, ASIC), off-the-shelf Programmable Gate Array (Fiel-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. Wherein, the general-purpose processor can be a microprocessor or the processor can also be any conventional processor or the like.

It can be understood by those skilled in the art that all or part of the processes in the methods for implementing the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program includes program instructions, and the computer program can be stored in a storage medium, and the storage medium is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the flow steps of the above-described method embodiments.

Therefore, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium. The storage medium stores a computer program, wherein the computer program includes program instructions, the program instructions can implement the above interrupt-based firmware abnormality diagnosis method when executed by the processor. The storage medium stores a computer program, and the computer program includes program instructions that, when executed by a processor, can implement the above-mentioned method. The program instructions include the following steps:

Step S1, run the firmware;

Step S2, judging whether the running firmware enters an infinite loop state;

In step S3, if the running firmware enters an infinite loop state, an external interrupt is triggered, so that the CPU enters the interrupt mode;

Step S4, according to the interrupt mode, dump the user call stack;

Step S5, analyze the call path according to the call stack to obtain the analysis result.

The storage medium may be various computer-readable storage media that can store program codes, such as a U disk, a removable hard disk, a read-only memory (Read-Only Memory, ROM), a magnetic disk, or an optical disk.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. Interchangeability, the above description has generally described the components and steps of each example in terms of function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.

In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is only a logical function division, and other division methods may be used in actual implementation. For example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.

The steps in the method of the embodiment of the present invention may be adjusted, combined and deleted in sequence according to actual needs. Units in the apparatus of the embodiment of the present invention may be combined, divided, and deleted according to actual needs. In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention is essentially or a part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

The above-mentioned embodiment is a preferred implementation scheme of the present invention. In addition, the present invention can also be implemented in other ways, and any obvious replacements are within the protection scope of the present invention without departing from the concept of the technical solution.

Claims (10)

1. The firmware abnormity diagnosis method based on the interrupt is characterized by comprising the following steps:

running the firmware;

judging whether the running firmware enters a loop death state or not;

if the running firmware enters the endless loop state, triggering external interruption to enable the CPU to enter an interruption mode;

dumping a user call stack according to the interrupt mode;

and analyzing the call path according to the call stack to obtain an analysis result.

2. The interrupt-based firmware exception diagnosis method according to claim 1, wherein after the step of determining whether the running firmware enters the loop-death state, the method further comprises: and if the running firmware does not enter the endless loop state, skipping to execute the running firmware.

3. The interrupt-based firmware exception diagnosis method as claimed in claim 1, wherein the step of triggering external interrupt to make CPU enter interrupt mode triggers external interrupt by pulling GPIO low or high, or by other CPUs sending IPC information.

4. The interrupt-based firmware exception diagnosis method according to claim 1, wherein after the step of analyzing the call path according to the call stack to obtain the analysis result, the method further comprises: and analyzing the reason of the firmware entering the endless loop according to the analysis result.

5. An interrupt-based firmware abnormality diagnosis apparatus, comprising: the operation unit, the judgment unit, the triggering entry unit, the calling unit and the analysis unit;

the running unit is used for running the firmware;

the judging unit is used for judging whether the running firmware enters a closed loop state;

the trigger entering unit is used for triggering external interruption if the running firmware enters a dead cycle state so as to enable the CPU to enter an interruption mode;

the call unit is used for dumping a user call stack according to the interrupt mode;

and the analysis unit is used for analyzing the call path according to the call stack to obtain an analysis result.

6. The interrupt-based firmware abnormality diagnostic apparatus according to claim 5, characterized by further comprising: and the skipping unit is used for skipping to execute the running firmware if the running firmware does not enter a dead loop state.

7. The interrupt-based firmware abnormality diagnosis device according to claim 5, characterized in that the trigger entering unit triggers external interrupt by pulling GPIO low or high, or by other CPU sending IPC information.

8. The interrupt-based firmware abnormality diagnostic apparatus according to claim 5, characterized by further comprising: and the analysis unit is used for analyzing the reason of the firmware entering the endless loop according to the analysis result.

9. A computer device comprising a memory having a computer program stored thereon and a processor that, when executing the computer program, implements the interrupt-based firmware exception diagnostic method of any one of claims 1-4.

10. A storage medium storing a computer program comprising program instructions which, when executed by a processor, implement the interrupt-based firmware exception diagnostic method of any one of claims 1-4.

Images