CN116339207A - Method, device, equipment and medium for operating tool software - Google Patents

Method, device, equipment and medium for operating tool software Download PDF

Info

Publication number
CN116339207A
CN116339207A CN202310319406.5A CN202310319406A CN116339207A CN 116339207 A CN116339207 A CN 116339207A CN 202310319406 A CN202310319406 A CN 202310319406A CN 116339207 A CN116339207 A CN 116339207A
Authority
CN
China
Prior art keywords
task
scheduling
function
tool software
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.)
Pending
Application number
CN202310319406.5A
Other languages
Chinese (zh)
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.)
Shenzhen Comen Medical Instruments Co Ltd
Original Assignee
Shenzhen Comen Medical Instruments 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 Shenzhen Comen Medical Instruments Co Ltd filed Critical Shenzhen Comen Medical Instruments Co Ltd
Priority to CN202310319406.5A priority Critical patent/CN116339207A/en
Publication of CN116339207A publication Critical patent/CN116339207A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0423—Input/output
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25257—Microcontroller
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention provides an operation method, a device, equipment and a medium of tool software, wherein whether scheduling conditions of task functions are met or not is judged according to a first operation interval and a first execution period by detecting whether abnormal conditions occur in front and back task scheduling of the tool software, if the abnormal conditions occur in front and back task scheduling, the state information of a system task is read, and if the scheduling conditions of the task functions are met, the task functions are called. When the technical scheme is implemented, when abnormal conditions occur in foreground and background task scheduling, the task function is called, so that the condition that a certain task is always executed is avoided, and the running stability of software is ensured. Meanwhile, the process of calling the task function belongs to a time slice polling mode, the execution time of the CPU can be divided into one block again, and the execution state time is short enough, so that the effect of multitasking can be realized, the occupied time of single operation of the CPU is reduced, and the software operation efficiency is greatly improved.

Description

Method, device, equipment and medium for operating tool software
Technical Field
The invention relates to the technical field of communication, in particular to a method, a device, equipment and a medium for operating tool software.
Background
At present, the tooling software generally does not use OS (Operating System) because of the limitation of the internal resources of the MCU and the requirement of complex algorithm and data structure for the program, so as not to occupy most of the resources. So most common tool software framework designs are front-to-back systems.
Because the coupling (association degree) between the main program and the interrupt in the foreground and background system is large, the main program and the interrupt are easy to wind together, the main program and the interrupt must be carefully processed to prevent the main program and the interrupt from being undetected, and therefore, sentences of a plurality of irrelevant services can be generated to influence the logic of the program, the readability of the program is reduced, the working efficiency is influenced when the tooling program is maintained and transplanted, and if the detail processing aspect is not completely cared, the running stability cannot be ensured.
Accordingly, the prior art is in need of improvement.
Disclosure of Invention
The invention mainly aims to provide a method, a device, equipment and a medium for operating tool software, which at least solve the technical problem of poor stability of the tool software in the related art during operation.
The first aspect of the invention provides a method for operating tool software, which comprises the following steps:
detecting whether abnormal conditions occur in foreground and background task scheduling of the tool software;
if abnormal conditions occur in the foreground task scheduling and the background task scheduling, reading state information of a system task; the state information of the system task comprises a first running interval and a first execution period;
judging whether the scheduling condition of the task function is met or not according to the first running interval and the first execution period;
and if the scheduling condition of the task function is met, calling the task function.
In a second aspect of the present invention, there is provided an operating device for tool software, including:
the detection module is used for detecting whether abnormal conditions occur in foreground and background task scheduling of the tool software;
the reading module is used for reading the state information of the system task if the foreground task scheduling and the background task scheduling are abnormal; the state information of the system task comprises a first running interval and a first execution period;
the judging module is used for judging whether the scheduling condition of the task function is met or not according to the first running interval and the first execution period;
and the calling module is used for calling the task function if the scheduling condition of the task function is met.
In a third aspect of the invention, an electronic device is provided, comprising a memory, a processor, and a bus;
the bus is used for realizing connection communication between the memory and the processor;
the processor is used for executing the computer program stored on the memory;
and when the processor executes the computer program, the steps in the running method of the tool software provided in the first aspect are realized.
In a fourth aspect of the present invention, there is provided a computer readable storage medium having stored thereon a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the method for operating a tooling software provided in the first aspect.
According to the running method, the running device, the running equipment and the running medium of the tool software, whether the scheduling conditions of the task functions are met or not is judged according to the first running interval and the first execution period by detecting whether the scheduling of the foreground and the background tasks of the tool software is abnormal or not, if the scheduling of the foreground and the background tasks is abnormal, the state information of the system tasks is read, and if the scheduling conditions of the task functions are met, the task functions are called. When the technical scheme is implemented, when abnormal conditions occur in foreground and background task scheduling, the task function is called, so that the condition that a certain task is always executed is avoided, and the running stability of software is ensured. Meanwhile, the process of calling the task function belongs to a time slice polling mode, the execution time of the CPU can be divided into one block again, each block has a corresponding state to be completed, and the execution state time is short enough, so that the effect of multitasking can be realized, the occupied time of single operation of the CPU is reduced, and the software operation efficiency is greatly improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a basic flow diagram of an operation method of tool software according to an embodiment of the present application;
fig. 2 is a schematic diagram of task execution conditions of a foreground system and a background system according to an embodiment of the present application;
fig. 3 is a detailed flowchart of an operation method of the tool software according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a program module of a static code scanner according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
It is noted that related terms such as "first," "second," and the like may be used to describe various components, but these terms are not limiting of the components. These terms are only used to distinguish one element from another element. For example, a first component could be termed a second component, and, similarly, a second component could be termed a first component, without departing from the scope of the present invention. The term "and/or" refers to any one or more combinations of related items and descriptive items.
Referring to fig. 1 and 2, an operation method of tool software provided by an embodiment of the invention includes the following steps:
step S101, detecting whether abnormal conditions occur in foreground and background task scheduling of tool software.
It should be noted that, the design scheme of the tool software framework is often a combination of a foreground system and a background system, and an application program usually executed by the background system is an infinite loop, and corresponding functions are called in the loop to complete corresponding operations. While foreground systems typically execute interrupt service routines and handle asynchronous events.
Specifically, the foreground task scheduling of the tool software refers to the related situation of the foreground system executing task and the background system executing task, and when the detection is performed, whether an abnormal situation occurs or not can be determined through the foreground task executing state and the background task executing state, for example, whether the winding (mutual interference) situation occurs or not can be determined through analyzing the task executing states of the foreground task executing state and the background task executing state. Generally, because the coupling (association degree) between the main program and the interrupt is large, the main program (executed by the background system) and the interrupt (executed by the foreground system) are entangled together, that is, abnormal conditions occur in the foreground and background task scheduling, and the execution stability of the tool software is affected if the abnormal conditions are not processed. For example, for a part of peripheral equipment, after the MCU (single chip microcomputer) executes the statement, the execution delay is performed to wait for the peripheral equipment to be ready to be completed, and the MCU does not perform any effective operation in the period of time, so that system resources are wasted, and the operation time of an operator is wasted in the actual use process of the tool. Therefore, it is necessary to determine whether the foreground and background task scheduling of the tool software is abnormal, so as to execute subsequent processing steps.
It should be further noted that the critical operation with strong time dependence must be guaranteed by interrupting the service. Because the information provided by the interrupt service is not processed until the background program goes to the step of processing the information, the system is worse than can be actually done in the timeliness of processing the information. This results in a task level response time, which in the worst case depends on the execution time of the entire loop. Because the execution time of the loop is not constant, the accurate time of the program passing through a specific part cannot be determined, and finally, the foreground and background task scheduling is abnormal.
Step S102, if abnormal conditions occur in the foreground and background task scheduling, the state information of the system task is read.
Specifically, when an abnormal situation occurs in the current background task scheduling, the state information of the system task is read, for example, the first running interval and the first execution period of the system task are read. The running interval and the execution period differ in that, for the running interval, it refers to the time interval between the start of the last execution and the next execution, and the execution period refers to the time point determined from (specified time + delay) or (current time + delay).
It should be understood that the running interval and execution period look as if there were any difference, in fact, the difference is that for a. For the Timer, the time at which the TimerTask is executed is not very accurately determined, it is related to the time at which its previous task is executed, e.g., it has executed a dead cycle, which is permanently without execution opportunity; b. the time at which the task execution interval type task is expected to be executed is uncertain, and the specific execution time thereof cannot be determined at all; c. the time at which the task execution cycle type task is expected to be executed is determined, and the specific execution time thereof cannot be determined at all; d. the time-periodic task is executed periodically, while other tasks are executed only once e.TimerTask can be canceled as long as its own state attribute is set.
Step S103, judging whether the scheduling condition of the task function is met or not according to the first operation interval and the first execution period.
Specifically, after the first running interval and the first execution period of the system task are obtained, whether the scheduling condition of the task function is satisfied is detected through the first running interval and the first execution period. The scheduling condition of the task function may be preset such that the first operation interval is greater than the first execution period, and whether the scheduling condition is satisfied may be determined according to a magnitude relation between the first operation interval and the first execution period.
Step S104, if the scheduling condition of the task function is satisfied, the task function is called.
Specifically, when the scheduling condition of the task function is satisfied according to the first operation interval and the first execution period, it indicates that the time required by the system task cannot be completed in a time slice, a phenomenon that a certain task is always executed and a bare metal large loop (foreground and background system) appears occurs at this time. In this case, the task function is called, for example, a unpacking function, a key scanning function, an LED control function, a detection task scheduling function, etc., so that the situation that a certain task is always executed is avoided, and thus the stability of software operation is ensured.
In addition, the above steps S101 to S104 belong to a system-level task scheduling flow (time slice polling) for scheduling a unpacking function, a key scan function, an LED control function, a detection task scheduling function, and the like. In the above mechanism, for the software writing of a long task, the task needs to be divided into a plurality of states, each time scheduling only completes one state (the execution time cannot be prolonged to be longer than the time slice in a similar delay mode, and only a short delay less than the time slice can be executed), then the execution time of the CPU can be divided into a block, each block has a corresponding state to complete, and the execution state time is short enough, so that the effect of multitasking can be realized, the occupation time of single operation of the CPU is reduced, and the software operation efficiency is greatly improved.
In an alternative implementation of this embodiment, step S101: before the step of detecting whether the abnormal situation occurs in the foreground and background task scheduling of the tool software, the method further comprises the following steps: and carrying out data initialization processing on the tooling software, carrying out emptying processing on an interface corresponding to the singlechip controlled by the tooling software, creating a system task through the tooling software, and setting an entry function and a first execution period of the system task. Specifically, the data initialization processing of the tool software refers to clearing historical use data of the tool software, the clearing processing of the interface of the singlechip refers to adjusting the use state of the interface to an initial state, creating a system task through the tool software after the initial processing of the software and the hardware is completed, setting an entry function and a first execution period of the system task, and thus completing the preparation stage work.
In an alternative implementation of this embodiment, step S103: judging whether the scheduling condition of the task function is met or not according to the first running interval and the first execution period, wherein the step specifically comprises the following steps: and calculating a difference value between the first running interval and the first execution period, comparing the difference value with 0 to obtain a comparison result, and judging whether the scheduling condition of the task function is met or not according to the comparison result. When the preset scheduling condition of the task function is that the first operation interval is larger than the first execution period, the comparison result between the difference value of the first operation interval and the first execution period and 0 can reflect the magnitude relation between the first operation interval and the first execution period, so that whether the scheduling condition of the task function is met or not can be accurately determined according to the comparison result. For example, if the comparison result is that the difference is greater than 0, the task function is called.
In an optional implementation manner of this embodiment, in step S104, the step of calling the task function specifically includes: and reading state information of the tool detection task, detecting whether a second operation interval is larger than a second execution period, judging whether the precondition of the tool detection task function is met if the second operation interval is larger than the second execution period, reading the tool detection task function and executing a corresponding statement if the precondition of the tool detection task function is met, and adding 1 to the counting bit of the tool detection task.
Specifically, the task function comprises a tool detection task function, in the process of calling the task function, the state information of the detection task is firstly read, so as to obtain the state information of the detection task, namely a second operation interval and a second execution period, then whether the preset size relation is met or not is judged according to the second operation interval and the second execution period, when the second operation interval is larger than the second execution period, whether the pre-condition of the task function is met is further judged, if the pre-condition of the task function is met, the task function is finally read, corresponding sentences are executed, and the counting bit of the task function is increased by 1. That is, the above procedure of calling the task function belongs to a task scheduling process (time slice polling) for scheduling tool detection tasks, for example: and detecting the internal function block execution (state machine management) of the detection task, such as power supply voltage detection, power supply short circuit detection and the like.
In this way, the technical scheme forms a two-layer scheduling flow, namely a system-level task scheduling flow (time slice polling) used for scheduling a unpacking function, a key scanning function, an LED control function, a detection task scheduling function and the like; secondly, a task detection scheduling process (time slice polling) is used for scheduling tool detection tasks, for example: and detecting the internal function block execution (state machine management) of the detection task, such as power supply voltage detection, power supply short circuit detection and the like. I.e. pseudo-multithreading is implemented using a time slice poll + state machine, multithreading can be implemented when the execution time is sufficiently short.
In an alternative implementation manner of this embodiment, after the step of determining whether the scheduling condition of the task function is satisfied according to the first operation interval and the first execution period, the method further includes: if the scheduling condition of the task function is not met, adding 1 to the counting bit of the task function, and returning to the step of reading the state information of the system task. When the scheduling condition of the task function is not met, the task function does not need to be called to avoid the winding condition of a foreground system and a background system, and the step of reading the state information of the system task is returned.
Referring to fig. 3, the method in fig. 3 is an operation method of the thinned tool software provided in the embodiment of the present application, where the operation method of the tool software includes:
step S301, carrying out data initialization processing on the tooling software, carrying out emptying processing on an interface corresponding to a singlechip controlled by the tooling software, creating a system task, and setting an entry function and a first execution period;
step S302, acquiring a foreground task execution state and a background task execution state of tool software, and detecting whether an abnormal condition occurs according to the foreground task execution state and the background task execution state;
step S303, if abnormal conditions occur in the front-background task scheduling, reading state information of the system task; the state information of the system task comprises a first running interval and a first execution period;
step S304, calculating a difference value between the first operation interval and the first execution period, comparing the difference value with 0 to obtain a comparison result, and judging whether the scheduling condition of the task function is met or not according to the comparison result;
step S305, if the scheduling condition of the task function is satisfied, reading the state information of the tool detection task, and detecting whether the second operation interval is larger than the second execution period;
step S306, if the second running interval is larger than the second executing period, judging whether the precondition of the tool detection task function is met, if so, reading the tool detection task function and executing the corresponding sentence, and adding 1 to the counting bit of the tool detection task.
Through implementation of the technical scheme, when abnormal conditions occur in foreground and background task scheduling, the situation that a certain task is executed all the time is avoided by calling the task function, so that the running stability of software is ensured. Meanwhile, the process of calling the task function belongs to a time slice polling mode, the execution time of the CPU can be divided into one block again, each block has a corresponding state to be completed, and the execution state time is short enough, so that the effect of multitasking can be realized, the occupied time of single operation of the CPU is reduced, and the software operation efficiency is greatly improved.
Fig. 4 shows an operation device of tool software provided in an embodiment of the present application, including:
the detection module 401 is used for detecting whether abnormal conditions occur in foreground and background task scheduling of the tool software;
the reading module 402 is configured to read status information of a system task if an abnormal situation occurs in foreground and background task scheduling; the state information of the system task comprises a first running interval and a first execution period;
a judging module 403, configured to judge whether a scheduling condition of the task function is satisfied according to the first running interval and the first execution period;
and a calling module 404, configured to call the task function if the scheduling condition of the task function is satisfied.
According to the implementation of the running device of the tool software, the time slice polling and the state machine are used for realizing pseudo-multithreading, the execution time of the MCU is divided into one block, then the time of the one block is allocated according to the own requirement, and when the execution time of a task (the task realized in the time slice polling method) is short enough, the multithreading can be realized, the occupied time of single running of the CPU is reduced, and the running efficiency of the software is greatly improved.
Fig. 5 shows an electronic device provided in an embodiment of the present invention, where the electronic device may be used to implement the method for running the tool software in any of the foregoing embodiments. The electronic device includes:
memory 501, processor 502, bus 503, and a computer program stored in memory 501 and executable on processor 502, memory 501 and processor 502 being connected by bus 503. When the processor 502 executes the computer program, the method for operating the tool software in the foregoing embodiment is implemented. Wherein the number of processors may be one or more.
The memory 501 may be a high-speed random access memory (RAM, random Access Memory) memory or a non-volatile memory (non-volatile memory), such as a disk memory. The memory 501 is used for storing executable program codes, and the processor 502 is coupled to the memory 501.
Further, the embodiments of the present application also provide a computer readable storage medium, which may be provided in the electronic device in the above embodiments, and the computer readable storage medium may be a memory.
The computer readable storage medium stores a computer program which, when executed by a processor, implements the method of operating the tool software of the foregoing embodiment. Further, the computer-readable medium may be any medium capable of storing a program code, such as a usb (universal serial bus), a removable hard disk, a Read-Only Memory (ROM), a RAM, a magnetic disk, or an optical disk.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules is merely a logical function division, and there may be additional divisions of actual implementation, e.g., multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.
The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in software functional modules.
The integrated modules, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a readable storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned readable storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
It should be noted that, for the sake of simplicity of description, the foregoing method embodiments are all expressed as a series of combinations of actions, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily all necessary for the present application.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims (10)

1. The method for operating the tool software is characterized by comprising the following steps:
detecting whether abnormal conditions occur in foreground and background task scheduling of the tool software;
if abnormal conditions occur in the foreground task scheduling and the background task scheduling, reading state information of a system task; the state information of the system task comprises a first running interval and a first execution period;
judging whether the scheduling condition of the task function is met or not according to the first running interval and the first execution period;
and if the scheduling condition of the task function is met, calling the task function.
2. The method for running the tool software according to claim 1, further comprising, before the step of detecting whether an abnormality occurs in the foreground and background task scheduling of the tool software:
carrying out data initialization processing on the tool software;
carrying out emptying treatment on interfaces corresponding to the singlechip controlled by the tool software;
and creating a system task through the tool software, and setting an entry function and a first execution period of the system task.
3. The method for operating the tool software according to claim 1, wherein the step of determining whether the scheduling condition of the task function is satisfied according to the first operation interval and the first execution period specifically includes:
calculating a difference between the first running interval and the first execution period;
comparing the difference value with 0 to obtain a comparison result;
and judging whether the scheduling condition of the task function is met or not according to the comparison result.
4. A method of operating the tool software according to claim 3, wherein the task function is scheduled under the condition that the operation interval is greater than the execution period;
and if the scheduling condition of the task function is met, calling the task function, wherein the method specifically comprises the following steps:
and if the comparison result is that the difference value is greater than 0, calling the task function.
5. The method of operating tool software according to claim 1, wherein the task functions include tool detection task functions;
the step of calling the task function specifically comprises the following steps:
reading state information of a tool detection task, wherein the state information of the tool detection task comprises a second running interval and a second execution period;
detecting whether the second running interval is greater than the second execution period;
if the second running interval is larger than the second execution period, judging whether the precondition of the tool detection task function is met or not;
and if the pre-condition of the tool detection task function is met, reading the tool detection task function and executing a corresponding statement, and adding 1 to the counting bit of the tool detection task.
6. The method for operating the tool software according to claim 1, wherein the step of detecting whether an abnormal situation occurs in the foreground and background task scheduling of the tool software specifically includes:
acquiring a foreground task execution state and a background task execution state of tool software;
and detecting whether abnormal conditions occur according to the execution state of the foreground task and the execution state of the background task.
7. The method for operating the tool software according to claim 1, further comprising, after the step of determining whether the scheduling condition of the task function is satisfied according to the first operation interval and the first execution period:
and if the scheduling condition of the task function is not met, adding 1 to the counting bit of the task function, and returning to the step of reading the state information of the system task.
8. An operating device of tool software is characterized in that,
the detection module is used for detecting whether abnormal conditions occur in foreground and background task scheduling of the tool software;
the reading module is used for reading the state information of the system task if the foreground task scheduling and the background task scheduling are abnormal; the state information of the system task comprises a first running interval and a first execution period;
the judging module is used for judging whether the scheduling condition of the task function is met or not according to the first running interval and the first execution period;
and the calling module is used for calling the task function if the scheduling condition of the task function is met.
9. An electronic device, comprising a memory, a processor, and a bus;
the bus is used for realizing connection communication between the memory and the processor;
the processor is used for executing the computer program stored on the memory;
the processor, when executing the computer program, implements the steps of the method of operating the tool software of any one of claims 1 to 7.
10. A computer readable storage medium having stored thereon a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the method of operating the tool software of any of claims 1 to 7.
CN202310319406.5A 2023-03-22 2023-03-22 Method, device, equipment and medium for operating tool software Pending CN116339207A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310319406.5A CN116339207A (en) 2023-03-22 2023-03-22 Method, device, equipment and medium for operating tool software

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310319406.5A CN116339207A (en) 2023-03-22 2023-03-22 Method, device, equipment and medium for operating tool software

Publications (1)

Publication Number Publication Date
CN116339207A true CN116339207A (en) 2023-06-27

Family

ID=86892634

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310319406.5A Pending CN116339207A (en) 2023-03-22 2023-03-22 Method, device, equipment and medium for operating tool software

Country Status (1)

Country Link
CN (1) CN116339207A (en)

Similar Documents

Publication Publication Date Title
CN108319495B (en) Task processing method and device
US20110138397A1 (en) Processing time estimation method and apparatus
US20120137295A1 (en) Method for displaying cpu utilization in a multi-processing system
CN107783829B (en) Task processing method and device, storage medium and computer equipment
CN109885565B (en) Data table cleaning method and device
US11182318B2 (en) Processor and interrupt controller
US8612991B2 (en) Dynamic critical-path recalculation facility
CN115269196A (en) Thread pool dynamic creation method, device, equipment and storage medium
US20230305880A1 (en) Cluster distributed resource scheduling method, apparatus and device, and storage medium
RU2134446C1 (en) Method for controlling primitive program overflow by messages in multiprocessor control system (versions)
CN116339207A (en) Method, device, equipment and medium for operating tool software
US11307973B2 (en) Method and device for testing robustness and stability of SMM, and storage medium
CN116880986A (en) Task scheduling method and device, vehicle-mounted controller, electronic equipment and storage medium
CN107423206B (en) Method and device for measuring system management interruption time
CN113505017A (en) Problem troubleshooting method, device, storage medium and equipment
CN112673354B (en) System state detection method, system state device and terminal equipment
CN112181853A (en) Program debugging method, device and system
CN117290113B (en) Task processing method, device, system and storage medium
CN112579299B (en) Resource scheduling method, electronic device and storage medium
CN112131009B (en) Memory scheduling method and device and computer readable storage medium
CN111726418B (en) Cloud resource allocation method and device, terminal equipment and storage medium
CN114356517B (en) Method, system, electronic equipment and storage medium for managing serial bus resources
CN116185940B (en) Atomic counter operation method, device, equipment and storage medium
CN116561226A (en) Data synchronization method, device and medium
CN117687899A (en) Automatic test method, device, terminal equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination