CN109213680B - Automatic testing method based on embedded software simulator - Google Patents
Automatic testing method based on embedded software simulator Download PDFInfo
- Publication number
- CN109213680B CN109213680B CN201810984482.7A CN201810984482A CN109213680B CN 109213680 B CN109213680 B CN 109213680B CN 201810984482 A CN201810984482 A CN 201810984482A CN 109213680 B CN109213680 B CN 109213680B
- Authority
- CN
- China
- Prior art keywords
- module
- simulator
- program
- register
- automatic test
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
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
- G06F11/3644—Software debugging by instrumenting at runtime
Abstract
The automatic test method based on the embedded software simulator comprises the following steps: step S0, creating an automatic test script module to prepare for the test requirement; step S1, compiling a test logic conforming to the tested software in the automatic test script module according to the functions provided by the simulator API module, wherein the simulator API module comprises address bus read-write, register read-write, memory read-write, program breakpoint, condition breakpoint, symbol table acquisition, simulator control, simulation time acquisition, simulation timer and/or trigger interrupt; step S2, loading the automatic test script module into the simulator software; step S3, starting simulator software and executing an automatic test script module; step S4, verifying the correctness of the code logic of the automatic test script module and making adjustment and modification; step S5, if the step S4 is passed, the automatic test of the embedded software is executed and operated through the automatic test script module; and step S6, finishing the test. The program debugging is controllable and changeable, and the program logic error can be quickly positioned.
Description
Technical Field
The invention relates to an automatic test method of computer software, in particular to an automatic test method based on an embedded software simulator.
Background
Currently, an embedded software simulator on the market can only manually control simulator software in the process of testing target software, such as starting and stopping of a manual execution program; during the program operation, if the numerical value of a register of some peripheral equipment is changed or faults are injected into some memory addresses to test and observe the system execution behavior, the method can be realized only by manually modifying by a tester; however, if the software is tested in a fault injection manner at a certain specific moment, the manual operation often fails to accurately control the time, which causes the deviation of the injection time and affects the test result.
Aiming at the problems of low efficiency and complex operation of debugging target software of an embedded software simulator in the prior art, an effective solution is not provided in the prior art.
Disclosure of Invention
The invention aims to provide an automatic testing method based on an embedded software simulator, so that the embedded software can be tested more flexibly, conveniently and quickly, the testing work of testing personnel can be effectively reduced, and the testing efficiency is improved.
In order to achieve the above object, the present invention provides an automated testing method based on an embedded software simulator, comprising the following steps: step S0, creating an automatic test script module to prepare for the test requirement; step S1, compiling a test logic conforming to the tested software in the automatic test script module according to the function provided by the simulator API module, wherein the simulator Application Programming Interface module comprises address bus read-write, register read-write, memory read-write, program breakpoint, condition breakpoint, symbol table acquisition, simulator control, simulation time acquisition, simulation timer and/or trigger interrupt; step S2, loading the automatic test script module into the simulator software; step S3, starting simulator software and executing an automatic test script module; step S4, verifying the correctness of the code logic of the automatic test script module and making adjustment and modification; step S5, if the step S4 is passed, the embedded software automation test can be executed and operated through the automation test script module; and step S6, obtaining a result after the test is finished.
Preferably, steps S0 through S4 are executed to register a monitor callback module for a specified memory address, global variable and/or device register through the emulator API module; step S5 includes: when the embedded program accesses the monitored memory address, the monitored global variable and/or the monitored equipment register during execution, the embedded program enters a monitoring callback module; judging what type of operation is, and according to different operation modes, processing different things in the monitoring callback module; when the operation is a read operation, monitoring a callback function to return a specified numerical value to the memory address, the global variable and/or the equipment register; when the operation is write operation, monitoring the callback function to process the write operation according to the test requirement; and the tested embedded program changes the original execution logic or execution code branch because the read memory address, the global variable and/or the device register are/is changed by the monitoring callback module to change the original normal numerical value.
Preferably, the steps S0 to S4 are executed to acquire the simulation runtime in real time through the simulator API module, and the unit of the simulation runtime may be set to be seconds, milliseconds, microseconds or nanoseconds; step S5 includes: when the time of the simulator is executed to a specified value, entering a setting processing callback module; the processing callback module reads or writes a specified numerical value to a specified memory address, a global variable and/or a device register; and when the next unit time arrives, the original execution logic or execution code branch is changed because the values of the key memory address, the global variable and/or the device register are dynamically changed.
Preferably, steps S0 through S4 are performed to set a program breakpoint or a conditional breakpoint through the emulator API module, and to set its breakpoint watch callback module; step S5 includes: when the embedded program is executed to the position of the program breakpoint or meets the condition breakpoint, the embedded program enters the breakpoint monitoring callback module and performs some related operations according to the test requirements.
The present invention also provides a computer readable storage medium having stored therein a plurality of instructions adapted to be loaded by a processor and to perform the aforementioned method.
The present invention also provides an electronic device comprising: a processor; and a memory having stored therein computer program instructions which, when executed by the processor, cause the processor to perform the aforementioned method.
Compared with the prior art, the automatic test method can control simulator software through automatic test script configuration, dynamically inject faults and monitor the occurrence of the faults, and then operate the simulator to inject test data according to test requirements. The fault injection comprises monitoring the change of a memory value or a variable value, acquiring a millisecond value of simulation time, a condition fault of the simulation time, inserting or deleting a condition breakpoint and inserting or deleting a program breakpoint. Therefore, the invention can change the traditional way to debug the embedded software, so that the program debugging becomes controllable and changeable, and the program logic error can be quickly positioned. The invention can debug the target software more efficiently.
Drawings
Fig. 1 is a schematic structural diagram of an automated testing method based on an embedded software simulator according to the present invention.
FIG. 2 is a flowchart of example 1 of an embedded software simulator based automated testing method of the present invention.
FIG. 3 is a flowchart of example 2 of the embedded software simulator based automated testing method of the present invention.
FIG. 4 is a flowchart of example 3 of the embedded software simulator automation test method of the present invention.
Detailed Description
Hereinafter, embodiments of an embedded software simulator-based automated testing method of the present invention will be described with reference to the accompanying drawings.
The embodiments described herein are specific embodiments of the present invention, are intended to be illustrative and exemplary in nature, and are not to be construed as limiting the scope of the invention. In addition to the embodiments described herein, those skilled in the art will be able to employ other technical solutions which are obvious based on the disclosure of the claims and the specification of the present application, and these technical solutions include technical solutions which employ any obvious replacement or modification of the embodiments described herein.
The drawings accompanying this specification are diagrammatic and serve to assist in explaining the concepts of the present invention.
Fig. 1 is a schematic structural diagram of an automated testing method based on an embedded software simulator according to the present invention.
The simulator API module comprises address bus reading and writing, register reading and writing, memory reading and writing, program breakpoints, condition breakpoints, symbol table acquisition, simulator control, simulation time acquisition, simulation timers, triggering interruption and the like.
Through the simulator API module, the following functions can be provided: when the appointed memory address, the global variable and the register are read immediately, a corresponding service program can be accessed, and the values of the appointed memory address, the global variable and the register are modified; when the appointed memory address, the global variable and the register are written, the corresponding service program can be accessed, and the values of the appointed memory address, the global variable and the register are read; the specified memory address, the global variable and the register can be read and written in real time; providing an interface for acquiring a global variable address; providing and acquiring a simulation runtime interface; providing a text file interface which can be read and written in user definition; when the breakpoint is in the function, the local variable address can be obtained; providing an interface capable of realizing a system resetting function; the timer may be implemented in an external device; when the values of the specified variables and the addresses meet specified conditions, generating a callback processing function; controlling the execution, the stop and the injection of program breakpoints of the software simulator; and triggering interruption to the CPU or injecting data to the simulation peripheral at regular time.
Further, the automated testing method further comprises the following steps: the tester can write an automatic test script module to meet the test requirement, and the automatic test script module can call the functions provided by the API module of the simulator to realize the automatic test of the embedded software.
Referring to fig. 1 again, the automated testing method based on the embedded software simulator of the present invention may be operated in different environments, such as Windows, Linux, Mac OS, etc.
In the structural diagram, the data layer is in a conceptual sense and generally refers to data which can be used in a design automation test script and data which needs to be saved. Most of the data is some logic data in the test logic or some input/output data on the bus device.
The automatic test module redesigns and packages more universal interfaces according to the interfaces provided by the existing simulator API module, the interfaces are directly related to the automatic test, and the interfaces are provided for calling the automatic test script; on the other hand, the automatic test module can be provided with program logic, so that the test logic can be flexibly written and the simulator API module can be executed, thereby realizing the complete control of the automatic test script on the simulator.
In the automatic test module, when the specified memory address, the global variable and the register are read or written at the previous moment, a corresponding service program can be entered, and the values of the specified memory address, the global variable and the register are modified; the values can be read and written in real time for the specified memory address, the global variable and the register; acquiring simulation time, and performing corresponding operation at a special moment as required; controlling the execution, stopping and injecting program breakpoints \ condition breakpoints of the simulator; setting timing to trigger interruption to a CPU or inject data into a simulation peripheral; and when the values of the specified variable and the specified address meet specified conditions, generating a callback processing function.
The simulator API module comprises API interfaces shown in the figure, the API interfaces are the basis for ensuring the realization of automatic testing, and the API interfaces are an intermediate layer for ensuring the control of the simulator and the control of the external module.
The emulator software comprises a processor core, an address bus module and an equipment module. The processor module (i.e., processor core) is the core of the emulator software for simulating the execution logic of a real CPU processor; the address bus module is a special structure for communicating the computer memory component and peripheral equipment by the CPU. In an embedded simulation environment, a processor module accesses various equipment modules through an address bus module.
The automatic testing method based on the embedded software simulator comprises the following steps:
step S0, creating an automatic test script module to prepare for the test requirement;
step S1, compiling test logic conforming to the tested software in the automatic test script module according to the functions provided by the simulator API module, wherein the test logic can comprise address bus reading and writing, register reading and writing, memory reading and writing, program breakpoints, condition breakpoints, symbol table acquisition, simulator control, simulation time acquisition, simulation timer, triggering interruption and the like;
step S2, loading the automatic test script module into the simulator software;
step S3, starting simulator software and executing an automatic test script module;
step S4, verifying the correctness of the code logic of the automatic test script module and making adjustment and modification;
step S5, if the step S4 is passed, the embedded software automation test can be executed and operated through the automation test script module;
and step S6, obtaining a result after the test is finished.
FIG. 2 is a flow chart of example 1 of the embedded software simulator automated testing method of the present invention. In this example, a monitor callback module is registered in the automated testing module for the specified memory address, global variable, and/or device register, and is used to monitor the access of the embedded program to the specified memory address, global variable, and/or device register, so as to change the original correct value, and implement the branch test of the embedded program.
As shown in fig. 2, the method comprises the steps of:
step a: executing the steps S0 to S4 to register a monitor callback module for the specified memory address, global variable and/or device register through the emulator API module; (corresponding to the above-mentioned steps S0-S4)
Step b: when the embedded program accesses the monitored memory address, the monitored global variable and/or the monitored equipment register during execution, the embedded program enters a monitoring callback module; (execution of step S5)
Step c: judging what type of operation is, and according to different operation modes, processing different things in the monitoring callback module; (execution of step S5)
Step d: when the operation is a read operation, monitoring a callback function to return a specified numerical value to the memory address, the global variable and/or the equipment register; (execution of step S5)
Step e: when the operation is write operation, the monitoring callback function processes the write operation according to the test requirement (the general write operation has no test requirement); (execution of step S5)
Step f: the read memory address, the global variable and/or the equipment register of the tested embedded program are monitored and called back by the callback module to change the original normal numerical value, so that the original execution logic or the execution code branch is changed; (execution of step S5)
Step g: and (6) completing the test. (step S6)
FIG. 3 is a flow chart of example 2 of the embedded software simulator automated testing method of the present invention. In this example, the test is accomplished by dynamically monitoring the emulator time to change the values of critical memory addresses, global variables, and/or device registers for the embedded program at specified times.
Specifically, the flow of the method provided by this example is as follows:
step a: executing the above steps S0 to S4 to obtain the simulation runtime in real time through the simulator API module, where the unit may be set to be second, millisecond, microsecond or nanosecond; (corresponding to the above-mentioned steps S0-S4)
Step b: when the time of the simulator is executed to a specified value, entering a set monitoring callback module; (execution of step S5)
Step c: the monitoring callback module reads or writes a specified numerical value into a specified memory address, a global variable and/or a device register; (execution of step S5)
Step d: the embedded program continues to execute, and the next unit time arrives, because the values of the critical memory address, global variables and/or device registers are dynamically changed, the original execution logic or execution code branches are changed. (execution of step S5)
FIG. 4 is a flowchart of example 3 of the embedded software simulator automation test method of the present invention.
Specifically, the flow of the method provided by this example is as follows:
step a: executing steps S0 to S4 to set program breakpoints or conditional breakpoints through the emulator API module, and set a breakpoint monitor callback module thereof; (corresponding to the above-mentioned steps S0-S4)
Step b: when the embedded program is executed to the position of the program breakpoint or meets the condition breakpoint, the embedded program enters the breakpoint monitoring callback module and performs related operation according to the test requirement. (execution of step S5)
By utilizing the automatic testing method, the simulator software can be controlled through automatic testing script configuration, faults are dynamically injected and monitored, and then the simulator is operated to inject testing data according to testing requirements. The fault injection comprises monitoring the change of a memory value or a variable value, acquiring a millisecond value of simulation time, a condition fault of the simulation time, inserting or deleting a condition breakpoint and inserting or deleting a program breakpoint. The invention can change the traditional debugging of embedded software, so that the program debugging becomes controllable and changeable, and the program logic error can be quickly positioned. By the method and the device, the target software can be debugged more efficiently.
The above description is directed to an embodiment of an automated testing method based on an embedded software simulator, which is provided to explain the spirit of the present invention. Note that those skilled in the art can modify and combine the features of the above-described embodiments without departing from the spirit of the present invention, and therefore, the present invention is not limited to the above-described embodiments.
Claims (6)
1. An automatic testing method based on an embedded software simulator comprises the following steps:
step S0, creating an automatic test script module to prepare for the test requirement;
step S1, compiling a test logic conforming to the tested software in the automatic test script module according to the functions provided by the simulator API module, wherein the simulator API module comprises address bus reading and writing, register reading and writing, memory reading and writing, program breakpoints, condition breakpoints, symbol table acquisition, simulator control, simulation time acquisition, a simulation timer and/or trigger interruption; wherein the functions provided by the emulator API module include:
when the appointed memory address, the global variable and the register are read immediately, entering a corresponding service program, and modifying the appointed memory address, the global variable and the value of the register; when the appointed memory address, the global variable and the register are written, the corresponding service program is entered, and the appointed memory address, the global variable and the value of the register are read; reading and writing specified memory addresses, global variables and registers in real time; providing an interface for acquiring a global variable address; providing and acquiring a simulation runtime interface; providing an interface for reading and writing user-defined text files; when the breakpoint is in the function, obtaining a local variable address; providing an interface for realizing a system resetting function; implementing a timer in the external device; when the values of the specified variables and the addresses meet specified conditions, generating a callback processing function; controlling the execution, the stop and the injection of program breakpoints of the software simulator; triggering interruption to a CPU or injecting data to a simulation peripheral at fixed time;
step S2, loading the automatic test script module into the simulator software;
step S3, starting simulator software and executing an automatic test script module;
step S4, verifying the correctness of the code logic of the automatic test script module and making adjustment and modification;
step S5, if the step S4 is passed, the embedded software automation test is executed and operated through the automation test script module;
and step S6, obtaining a result after the test is finished.
2. The automated testing method of claim 1, wherein steps S0 through S4 are performed to register a monitor callback module for a specified memory address, global variable and/or device register through the emulator API module; and is
Step S5 includes:
when the embedded program accesses the monitored memory address, the monitored global variable and/or the monitored equipment register during execution, the embedded program enters a monitoring callback module;
judging what type of operation is, and according to different operation modes, processing different things in the monitoring callback module;
when the operation is a read operation, monitoring a callback function to return a specified numerical value to the memory address, the global variable and/or the equipment register;
when the operation is write operation, monitoring the callback function to process the write operation according to the test requirement; and
the embedded program to be tested changes the original execution logic or execution code branch because the read memory address, the global variable and/or the device register are/is changed by the monitoring callback module to change the original normal value.
3. The automated testing method of claim 1, wherein the steps S0 to S4 are performed to obtain the simulation runtime in real time through the simulator API module, and the unit of the simulation runtime can be set to be seconds, milliseconds, microseconds, or nanoseconds; and is
When the time of the simulator is executed to a specified value, entering a set monitoring callback module;
the monitoring callback module reads or writes a specified value to a specified memory address, a global variable and/or a device register; and
the embedded program continues to execute, and the next unit time arrives, because the values of the critical memory address, global variables and/or device registers are dynamically changed, the original execution logic or execution code branches are changed.
4. The automated testing method of claim 1, wherein steps S0 through S4 are performed to set program breakpoints or conditional breakpoints through an emulator API module, and to set a breakpoint watch callback module thereof; and is
When the embedded program is executed to the position of the program breakpoint or meets the condition breakpoint, the embedded program enters the breakpoint monitoring callback module and performs related operation according to the test requirement.
5. A computer readable storage medium having stored therein a plurality of instructions adapted to be loaded by a processor and to carry out the steps of the method according to any one of claims 1 to 4.
6. An electronic device, comprising:
a processor; and
memory in which computer program instructions are stored, which, when executed by the processor, cause the processor to carry out the steps of the method according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810984482.7A CN109213680B (en) | 2018-08-28 | 2018-08-28 | Automatic testing method based on embedded software simulator |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810984482.7A CN109213680B (en) | 2018-08-28 | 2018-08-28 | Automatic testing method based on embedded software simulator |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109213680A CN109213680A (en) | 2019-01-15 |
| CN109213680B true CN109213680B (en) | 2022-01-25 |
Family
ID=64985943
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810984482.7A Active CN109213680B (en) | 2018-08-28 | 2018-08-28 | Automatic testing method based on embedded software simulator |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109213680B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110719199B (en) * | 2019-09-30 | 2023-01-24 | 深圳市元征科技股份有限公司 | Network automatic testing and fault positioning method and device |
| CN111044925A (en) * | 2019-12-20 | 2020-04-21 | 深圳市新威尔电子有限公司 | Simulator for battery detection system |
| CN111025166A (en) * | 2019-12-27 | 2020-04-17 | 深圳市新威尔电子有限公司 | Debugger for battery detection system |
| CN112084113B (en) * | 2020-09-16 | 2024-02-23 | 上海创景信息科技有限公司 | Configurable automatic test method and system based on embedded simulation verification software |
| CN112464594B (en) * | 2020-12-11 | 2022-10-28 | 苏州浪潮智能科技有限公司 | Circuit function simulation test method, device, equipment and readable storage medium |
| CN112632883B (en) * | 2020-12-21 | 2022-04-29 | 南京华大九天科技有限公司 | Method, device, equipment and medium for testing simulation result of device model |
| CN113933627A (en) * | 2021-10-08 | 2022-01-14 | 网易有道信息技术（北京）有限公司 | Method for automatically testing and verifying electronic product and related product |
| CN115168129B (en) * | 2022-08-09 | 2023-02-10 | 北京得瑞领新科技有限公司 | Automatic test system of implant simulator and SSD (solid State disk) test method |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6536008B1 (en) * | 1998-10-27 | 2003-03-18 | Logic Vision, Inc. | Fault insertion method, boundary scan cells, and integrated circuit for use therewith |
| CN102354298A (en) * | 2011-07-27 | 2012-02-15 | 哈尔滨工业大学 | Software testing automation framework (STAF)-based fault injection automation testing platform and method for high-end fault-tolerant computer |
| CN102760098A (en) * | 2012-06-13 | 2012-10-31 | 北京航空航天大学 | Processor fault injection method oriented to BIT software test and simulator thereof |
| CN104536303A (en) * | 2014-12-11 | 2015-04-22 | 中国航空工业集团公司第六三一研究所 | Fault injection method |
| CN104657247A (en) * | 2015-02-10 | 2015-05-27 | 上海创景计算机系统有限公司 | System and method for realizing universal type fault injection based on JTAG (Joint Test Action Group) debug mode |
| CN106326107A (en) * | 2016-07-27 | 2017-01-11 | 北京计算机技术及应用研究所 | Non-intrusion type embedded software abnormity processing verification method based on simulation environment |
| CN107729231A (en) * | 2017-09-19 | 2018-02-23 | 北京东土科技股份有限公司 | A kind of fault filling method and device based on operating system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100511149C (en) * | 2003-05-07 | 2009-07-08 | 华为技术有限公司 | Logic emulation testing system and method |
| CN102156760B (en) * | 2010-08-23 | 2013-05-01 | 北京航空航天大学 | Saber-based circuit failure simulation analyzing method |
| CN105068858A (en) * | 2015-07-29 | 2015-11-18 | 北京世冠金洋科技发展有限公司 | Multi-source heterogeneous system emulation method and apparatus |
-
2018
- 2018-08-28 CN CN201810984482.7A patent/CN109213680B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6536008B1 (en) * | 1998-10-27 | 2003-03-18 | Logic Vision, Inc. | Fault insertion method, boundary scan cells, and integrated circuit for use therewith |
| CN102354298A (en) * | 2011-07-27 | 2012-02-15 | 哈尔滨工业大学 | Software testing automation framework (STAF)-based fault injection automation testing platform and method for high-end fault-tolerant computer |
| CN102760098A (en) * | 2012-06-13 | 2012-10-31 | 北京航空航天大学 | Processor fault injection method oriented to BIT software test and simulator thereof |
| CN104536303A (en) * | 2014-12-11 | 2015-04-22 | 中国航空工业集团公司第六三一研究所 | Fault injection method |
| CN104657247A (en) * | 2015-02-10 | 2015-05-27 | 上海创景计算机系统有限公司 | System and method for realizing universal type fault injection based on JTAG (Joint Test Action Group) debug mode |
| CN106326107A (en) * | 2016-07-27 | 2017-01-11 | 北京计算机技术及应用研究所 | Non-intrusion type embedded software abnormity processing verification method based on simulation environment |
| CN107729231A (en) * | 2017-09-19 | 2018-02-23 | 北京东土科技股份有限公司 | A kind of fault filling method and device based on operating system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109213680A (en) | 2019-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109213680B (en) | Automatic testing method based on embedded software simulator | |
| US8136096B1 (en) | Backward post-execution software debugger | |
| CN112084113B (en) | Configurable automatic test method and system based on embedded simulation verification software | |
| US10095611B1 (en) | Methodology for unit test and regression framework | |
| EP2204738A2 (en) | Method and system for performing software verification | |
| US8271955B1 (en) | Forward post-execution software debugger | |
| US20050268195A1 (en) | Apparatus and method for improving emulation speed of high-level languages in on-chip emulation systems | |
| US9262299B1 (en) | Simulation observability and control of all hardware and software components of a virtual platform model of an electronics system | |
| CN110580226B (en) | Object code coverage rate testing method, system and medium for operating system level program | |
| US8402442B1 (en) | Common debugger method and system | |
| US9483374B2 (en) | PSMI using at-speed scan capture | |
| US9262305B1 (en) | Simulation observability and control of all hardware and software components of a virtual platform model of an electronics system | |
| US7007268B2 (en) | Method and apparatus for debugging in a massively parallel processing environment | |
| CN104657247A (en) | System and method for realizing universal type fault injection based on JTAG (Joint Test Action Group) debug mode | |
| CN105528284A (en) | Kernel fault injection method and electronic device | |
| US8132159B1 (en) | Post-execution software debugger with event display | |
| US20060150007A1 (en) | Parallel processing platform with synchronous system halt/resume | |
| US7827540B2 (en) | Method for program debugging | |
| CN111400997B (en) | Processor verification method, system and medium based on synchronous execution | |
| CN110704315A (en) | Fault injection device for embedded software test | |
| Fidalgo et al. | Using NEXUS compliant debuggers for real time fault injection on microprocessors | |
| CN114780421A (en) | Abnormity testing method, system and storage medium based on virtual instruction set platform | |
| JP2019204388A (en) | Semiconductor device and debug method | |
| Cantoro et al. | On the optimization of SBST test program compaction | |
| US8914274B1 (en) | Method and system for instruction set simulation with concurrent attachment of multiple debuggers |
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 |