CN113805848B - Target machine control software integration method and system - Google Patents
Target machine control software integration method and system Download PDFInfo
- Publication number
- CN113805848B CN113805848B CN202010527363.6A CN202010527363A CN113805848B CN 113805848 B CN113805848 B CN 113805848B CN 202010527363 A CN202010527363 A CN 202010527363A CN 113805848 B CN113805848 B CN 113805848B
- Authority
- CN
- China
- Prior art keywords
- software
- target machine
- application software
- machine control
- data
- 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
- 230000010354 integration Effects 0.000 title claims abstract description 35
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000004088 simulation Methods 0.000 claims abstract description 39
- 230000006870 function Effects 0.000 claims description 52
- 230000003993 interaction Effects 0.000 claims description 26
- 230000002452 interceptive effect Effects 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 10
- 238000012795 verification Methods 0.000 abstract description 19
- 238000010586 diagram Methods 0.000 description 14
- 238000012545 processing Methods 0.000 description 7
- 230000008878 coupling Effects 0.000 description 6
- 238000010168 coupling process Methods 0.000 description 6
- 238000005859 coupling reaction Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000002093 peripheral effect Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 239000008186 active pharmaceutical agent Substances 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 208000037218 exstrophy-epispadias complex Diseases 0.000 description 2
- 238000007667 floating Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000002347 injection Methods 0.000 description 1
- 239000007924 injection Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 239000000243 solution Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a target machine control software integration method and system, and relates to the technical field of simulation. The method comprises the following steps: simulating target machine hardware on a simulation platform; constructing application software and operation software of the target machine, wherein the application software and the operation software interact through a data interface; integrating application software and operation software; the integrated application software and operation software respectively generate corresponding binary files; and loading the binary file into the simulated target machine. The simulation degree of the target machine is improved, so that the simulation platform and the target platform achieve the consistency of the target code level, verification data which can be obtained in the simulated target machine are not required to be verified again on the target platform, the confidence level of the verification data is improved, and the verification cost is reduced.
Description
Technical Field
The disclosed simulation technology field especially relates to a target machine control software integration method and system.
Background
The development of commercial aeroengine control software not only needs to meet the functional and performance requirements of the engine, but also needs to meet the airworthiness requirements. Because of the inherent cost advantage of the digital simulation technology, the digital simulation technology has been widely applied to the development process of civil aviation engines. The development flow of the control software is generally that the integrated test is carried out on the simulation platform, and the integration of the FADEC (Full Authority Digital Engine Control, full-authority digital electronic controller) hardware is carried out on the premise of ensuring the correct functional logic, so that the development efficiency is greatly improved.
However, the simulation platform is different from the real hardware platform, for example, the simulation platform is different from the compiler adopted by the real hardware platform, in the running software of the simulation platform and the real hardware platform, only the source code is consistent, but the target code is inconsistent, and under the traditional architecture adopting software function call, the consistency of the target code level is difficult to achieve, so that the confidence of the verification data obtained by the simulation platform is often not high.
Disclosure of Invention
The technical problem to be solved by the present disclosure is to provide a method and a system for integrating target machine control software, which can achieve the consistency of target code levels of a simulation platform and a target platform, and improve the confidence of verification data.
According to an aspect of the present disclosure, a target machine control software integration method is provided, including: simulating target machine hardware on a simulation platform; constructing application software and operation software of the target machine, wherein the application software and the operation software interact through a data interface; integrating application software and operation software; the integrated application software and operation software respectively generate corresponding binary files; and loading the binary file into the simulated target machine.
In some embodiments, the interaction between the application software and the operating software through the data interface comprises: defining interactive data in operation software, recording identification of the interactive data, and declaring the identification of the interactive data in application software; and defining the entry function in the application software, recording the identification of the entry function, and declaring the identification of the entry function in the operation software.
In some embodiments, the interaction between the application software and the operating software through the data interface further comprises: the application task address is initialized in an entry function of the application.
In some embodiments, the integrated application software and operating software includes: after compiling the application software and the operation software respectively, linking the application software and the operation software through a linker.
In some embodiments, linking by the linker comprises: and linking the compiled application software and the compiled operation software through a linker based on the same linking configuration as the target machine.
In some embodiments, the integrated application software and operating software further comprises: replacing the identification of the interactive data in the application software by using the physical address of the interactive data; and replacing the identity of the entry function in the operating software with the physical address of the entry function.
In some embodiments, the target machine is an engine electronic controller EEC.
According to another aspect of the present disclosure, there is also provided a target machine control software integration system, including: the hardware simulation unit is configured to simulate the target machine hardware on the simulation platform; the system comprises a software construction unit, a data interface and a data processing unit, wherein the software construction unit is configured to construct application software and operation software of the target machine, and the application software and the operation software interact through the data interface; a software integration unit configured to integrate application software and operation software; the file generation unit is configured to generate corresponding binary files respectively by the integrated application software and the operation software; and a file loading unit configured to load the binary file into the simulated target machine.
According to another aspect of the present disclosure, there is also provided a target machine control software integration system, including: a memory; and a processor coupled to the memory, the processor configured to execute the target machine control software integration method as described above based on instructions stored in the memory.
According to another aspect of the present disclosure, there is also provided a computer-readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the above-described target machine control software integration method.
In the embodiment of the disclosure, the simulation degree of the target machine is improved, so that the simulation platform and the target platform realize the consistency of the target code level, therefore, verification data which can be obtained in the simulated target machine does not need to be verified again on the target platform, the confidence of the verification data is improved, and the verification cost is reduced.
Other features of the present disclosure and its advantages will become apparent from the following detailed description of exemplary embodiments of the disclosure, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The disclosure may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings in which:
fig. 1 is a flow diagram of some embodiments of a target machine control software integration method of the present disclosure.
FIG. 2 is a flow chart of other embodiments of the target machine control software integration method of the present disclosure.
Fig. 3 is a schematic diagram of a simulation platform of the present disclosure.
Fig. 4 is a schematic diagram of a software architecture based on a data structure of the present disclosure.
FIG. 5 is a schematic diagram of some embodiments of a target machine control software integration system of the present disclosure.
FIG. 6 is a schematic diagram of other embodiments of a target machine control software integration system of the present disclosure.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless it is specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective parts shown in the drawings are not drawn in actual scale for convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail, but should be considered part of the specification where appropriate.
In all examples shown and discussed herein, any specific values should be construed as merely illustrative, and not a limitation. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further discussion thereof is necessary in subsequent figures.
For the purposes of promoting an understanding of the principles and advantages of the disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same.
Fig. 1 is a flow diagram of some embodiments of a target machine control software integration method of the present disclosure.
At step 110, target machine hardware is simulated at a simulation platform. The target machine is, for example, an EEC (Electronic Engine Control, engine electronic controller).
In some embodiments, a SIMICS platform is employed as the running platform for the simulation software, which provides an environment for running digital EECs, and on the basis of this, processor models as well as peripheral models are developed.
In step 120, application software (AS, application software) and Operating Software (OS) of the target machine are built, wherein the application software and the operating software interact with each other through a data interface.
In some embodiments, data interaction and function call are performed between the AS and the OS through the data interface, so that coupling between the AS and the OS is reduced. For example, the AS is mainly responsible for realizing functional logic, the OS is mainly responsible for realizing software scheduling and input and output, and the two are communicated in a data sharing manner, so that the purpose of loose coupling is achieved.
In step 130, the application software and the operating software are integrated.
In some embodiments, the application software and the operating software are linked by a linker after being compiled separately.
In step 140, the integrated application software and the operation software respectively generate corresponding binary files.
In step 150, the binary file is loaded into the simulated target machine.
In the embodiment, the application software and the operation software of the target machine are constructed through simulating the hardware of the target machine, interaction is carried out between the application software and the operation software through the data interface, the integrated application software and operation software respectively generate the corresponding binary files, the binary files are loaded into the simulated target machine, and the simulation degree of the target machine is improved, so that the simulation platform and the target platform achieve the consistency of the target code level, verification data obtained in the simulated target machine does not need to be verified again on the target platform, the confidence of the verification data is improved, and the verification cost is reduced.
FIG. 2 is a flow chart of other embodiments of the target machine control software integration method of the present disclosure. In this embodiment, the target is presented for EEC purposes.
At step 210, EEC hardware is simulated at a simulation platform.
In some embodiments, a processor model, a peripheral model, and the like are simulated. The processor model mainly models registers, instruction sets, and execution modes of instructions. The aim of running the target instruction on the simulation platform is fulfilled by simulating the instruction set and the register of the EEC hardware central processing unit.
Registers are for example general purpose registers, floating point registers and special purpose registers.
The instruction set includes, for example, integer arithmetic instructions, floating point instructions, access operation instructions, flow control instructions, processor control instructions, synchronization instructions, signal processing instructions, and the like.
The instruction execution model needs to translate the instructions of the PowerPC into the instructions of X86 by either an interpreted execution or dynamic translation method. Both methods have low operation efficiency, so that dynamic translation and a certain cache technology are adopted in actual operation to improve the instruction operation efficiency.
The peripheral model mainly simulates the behavior.
In some embodiments, as shown in FIG. 3, the EEC peripheral environment may also be simulated, e.g., simulating controlled objects and other interactive objects, the EEC peripheral environment simulation being independent of the EEC simulation, both synchronized over the Ethernet. The controlled object is, for example, an engine, and the other interactive objects include, for example, an aircraft outside the engine and equipment on the aircraft, a network, and other electronic equipment such as an engine monitoring device, a sensor, an action mechanism, and the like inside the engine. The simulated engine is mainly integrated with an engine performance model, a sensor model, a fuel model and the like, so that the operation logic of the engine is simulated. The simulated engine transmits signals to the simulated EEC through the interface module. In a digital environment, the engine is also integrated with a fault injection module, which can optionally inject the desired engine fault, thereby fully verifying the control logic. The digital engine may be implemented in various forms, such as direct encoding, or by modeling. In some embodiments, the digital engine is implemented in a modeling+encoded form, wherein the logic portion employs a modeling approach and the interface portion employs an encoded form. To ensure versatility, interfaces may be abstracted.
In some embodiments, the integrated verification software may also be simulated. The integrated verification software is mainly injected by the use case, when the use case is controlled, data of the EEC and the engine are received, and the result is automatically compared, so that the integration work of an integration staff is facilitated, and most of energy is used for the design of the use case by the integration staff.
In step 220, the AS and OS of the EEC are built. To implement a data interface-based AS-OS architecture, the AS and OS have independent program and instruction spaces, respectively, and the coupling between the AS and OS is minimized in terms of data interaction and function call.
At step 230, AS-OS interaction data is defined in the OS and the identity of the interaction data is recorded and declared in the AS. Interactive data, i.e., data shared by the AS and the OS.
In some embodiments, the interaction data is accessed in the form of a structure, and the symbols of the data structure are recorded in the OS. The symbols of the interactive data structure are declared in the AS so that no errors are reported at the time of compilation by the AS.
In step 240, an entry function is defined in the AS and the identity of the entry function is recorded and declared in the OS.
In some embodiments, the entry function is an initialization function, such as a main function. A main function is defined in the AS, the main function symbol is recorded, and the main function symbol is declared in the OS, so that the OS cannot report errors during compiling.
The AS other task functions are transferred to the OS by the entry functions through function pointers, and the task function relationships are transferred through the form of a schedule.
AS shown in fig. 4, the AS may send the OS datamemory to the OS, the OS may send the AS datamemory to the AS, and the AS and the OS do not need to implement data interaction or function call by calling the API.
At step 250, the AS task address is initialized in the AS entry function. For example, an AS task address in the AS-OS shared area is initialized such that the OS invokes a task according to the task address. The AS-OS shared area also stores a schedule. The schedule includes the sequence, period, etc. of task operations to be known for system operation. When the OS performs system scheduling, the corresponding system task time sequence is operated according to the configuration of the scheduling table.
After compiling the AS and OS separately, the AS-OS is linked by a linker using a linking configuration consistent with the EEC.
In some embodiments, after compiling the AS and OS, the AS and OS are submitted to an integrator in the form of a for AS-OS integration.
At step 270, the identity of the interaction data in the AS is replaced with the physical address of the interaction data, and the identity of the entry function in the OS is replaced with the physical address of the entry function.
In step 280, the AS and OS generate respective binary files and load the binary files into the simulated EECs.
Under the traditional software architecture, data transfer and coupling are mainly performed between the AS and the OS through a large number of APIs, but in the embodiment, the coupling between the AS and the OS is only two quantities through a data interface mode, wherein one is a base address of shared data, and the other is an address of an entry function. In the linking process, AS is finally loaded in binary form into the simulated EEC, the finally formed execution file does not contain any sign information. Moreover, when the computer is running, the interactive data symbol cannot be recognized to be coincident with the entry function, and therefore, it is necessary to replace the symbol of the OS used in the AS and the symbol of the AS used in the OS with a physical address. Based on the software architecture of the embodiment, the operation of replacing the symbol with the physical address can be completed through two searches, so that the operation of replacing a large number of addresses in the traditional linking process is eliminated.
In the embodiment, the simulation model of the control software operation hardware is added, and the simulation platform and the target platform can achieve the consistency of the target code through the simulation technology of the digital processor and the model of the time behavior, so that AS can directly operate on the simulation platform or the target platform without modification, verification data obtained on the simulation platform can be directly used AS pilot evidence for verification, and the target platform does not need to be verified again, so that the verification cost is reduced. In addition, under the condition of lacking a target platform, the integrated work can be cooperatively carried out, so that the working efficiency is improved, and the integrated cost is reduced.
FIG. 5 is a schematic diagram of some embodiments of a target machine control software integration system of the present disclosure. The system includes a hardware simulation unit 510, a software construction unit 520, a software integration unit 530, a file generation unit 540, and a file loading unit 550.
The hardware simulation unit 510 is configured to simulate target machine hardware at a simulation platform. The target is, for example, an EEC.
The software construction unit 520 is configured to construct application software and operation software of the target machine, wherein the application software and the operation software interact with each other through a data interface.
In some embodiments, data interaction and function call are performed between the AS and the OS through the data interface, so that coupling between the AS and the OS is reduced. For example, AS-OS interaction data is defined in the OS, and the identity of the interaction data is recorded, and the identity of the interaction data is declared in the AS. Defining an entry function in the AS, recording the identity of the entry function, and declaring the identity of the entry function in the OS. The AS other task functions are transferred to the OS by the entry functions through function pointers, and the task function relationships are transferred through the form of a schedule. The AS task address is initialized in the AS entry function.
The software integrating unit 530 is configured to integrate application software and operation software.
In some embodiments, the AS and OS are linked by a linker after being compiled separately. For example, after the AS and the OS are compiled separately, the AS-OS is linked by a linker using a linking configuration consistent with the EEC.
In some embodiments, the identity of the interaction data in the AS is replaced with a physical address of the interaction data, and the identity of the entry function in the OS is replaced with a physical address of the entry function. In the linking process, AS is finally loaded in binary form into the simulated EEC, the finally formed execution file does not contain any sign information. Moreover, when the computer is running, the interactive data symbol cannot be recognized to be coincident with the entry function, and therefore, it is necessary to replace the symbol of the OS used in the AS and the symbol of the AS used in the OS with a physical address.
The file generating unit 540 is configured to generate corresponding binary files by the integrated application software and operation software, respectively.
The file loading unit 550 is configured to load a binary file into the simulated target machine.
In the embodiment, the application software and the operation software of the target machine are constructed through simulating the hardware of the target machine, interaction is carried out between the application software and the operation software through the data interface, the integrated application software and operation software respectively generate the corresponding binary files, the binary files are loaded into the simulated target machine, and the simulation degree of the target machine is improved, so that the simulation platform and the target platform achieve the consistency of the target code level, verification data obtained in the simulated target machine does not need to be verified again on the target platform, the confidence of the verification data is improved, and the verification cost is reduced.
FIG. 6 is a schematic diagram of other embodiments of a target machine control software integration system of the present disclosure. The system includes a memory 610 and a processor 620. Wherein: the memory 610 may be a magnetic disk, flash memory, or any other non-volatile storage medium. Memory 610 is used to store instructions in the corresponding embodiments of fig. 1-2. Processor 620, coupled to memory 610, may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 620 is configured to execute instructions stored in the memory.
In other embodiments of the present disclosure, processor 620 is coupled to memory 610 through BUS 630. The system 600 may also be coupled to external storage 650 via a storage interface 640 for invoking external data, and may also be coupled to a network or another computer system (not shown) via a network interface 660, not described in detail herein.
In the embodiment, the data instruction is stored by the memory, and then the instruction is processed by the processor, so that the confidence of verification data is improved, and the verification cost is reduced.
In other embodiments, a computer readable storage medium has stored thereon computer program instructions which, when executed by a processor, implement the steps of the method of the corresponding embodiment of fig. 1-2. It will be apparent to those skilled in the art that embodiments of the present disclosure may be provided as a method, apparatus, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Thus far, the present disclosure has been described in detail. In order to avoid obscuring the concepts of the present disclosure, some details known in the art are not described. How to implement the solutions disclosed herein will be fully apparent to those skilled in the art from the above description.
Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It will be appreciated by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the disclosure. The scope of the present disclosure is defined by the appended claims.
Claims (9)
1. A target machine control software integration method comprises the following steps:
simulating target machine hardware on a simulation platform;
constructing application software and operation software of the target machine, wherein the application software and the operation software interact through a data interface, wherein interaction data are defined in the operation software, identifications of the interaction data are recorded, identifications of the interaction data are declared in the application software, entry functions are defined in the application software, identifications of the entry functions are recorded, and identifications of the entry functions are declared in the operation software;
integrating the application software and the operation software;
the integrated application software and the integrated operation software respectively generate corresponding binary files; and
and loading the binary file into the simulated target machine.
2. The target machine control software integration method according to claim 1, wherein the interaction between the application software and the operation software through a data interface further comprises:
initializing an application software task address in an entry function of the application software.
3. The target machine control software integration method according to claim 1, wherein integrating the application software and the operation software includes:
and after the application software and the operation software are compiled respectively, linking is carried out through a linker.
4. The target machine control software integration method according to claim 3, wherein the linking by the linker comprises:
and linking the compiled application software and the compiled operation software through a linker based on the same linking configuration as the target machine.
5. The target machine control software integration method of claim 3, wherein integrating the application software and the operating software further comprises:
replacing the identification of the interactive data in the application software by using the physical address of the interactive data; and
replacing the identity of the entry function in the operating software with the physical address of the entry function.
6. The target machine control software integration method according to any one of claims 1 to 5, wherein,
the target machine is an engine electronic controller EEC.
7. A target machine control software integration system, comprising:
the hardware simulation unit is configured to simulate the target machine hardware on the simulation platform;
a software construction unit configured to construct application software and operation software of the target machine, wherein interaction is performed between the application software and the operation software through a data interface, interaction data is defined in the operation software, identification of the interaction data is recorded, identification of the interaction data is declared in the application software, an entry function is defined in the application software, identification of the entry function is recorded, and identification of the entry function is declared in the operation software;
a software integration unit configured to integrate the application software and the operation software;
the file generation unit is configured to generate corresponding binary files respectively by the integrated application software and the operation software; and
and the file loading unit is configured to load the binary file into the simulated target machine.
8. A target machine control software integration system, comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the target machine control software integration method of any one of claims 1-6 based on instructions stored in the memory.
9. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the target machine control software integration method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010527363.6A CN113805848B (en) | 2020-06-11 | 2020-06-11 | Target machine control software integration method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010527363.6A CN113805848B (en) | 2020-06-11 | 2020-06-11 | Target machine control software integration method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113805848A CN113805848A (en) | 2021-12-17 |
| CN113805848B true CN113805848B (en) | 2024-03-26 |
Family
ID=78943674
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010527363.6A Active CN113805848B (en) | 2020-06-11 | 2020-06-11 | Target machine control software integration method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113805848B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115589407B (en) * | 2022-11-22 | 2023-03-10 | 大方智造(天津)科技有限公司 | File transmission verification method based on PLM-DNC integrated system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102968377A (en) * | 2012-12-13 | 2013-03-13 | 中国航空无线电电子研究所 | Virtual machine technique based airborne software system testing general platform |
| CN106970825A (en) * | 2017-03-10 | 2017-07-21 | 深圳航天科技创新研究院 | A kind of ARM7 simulation objectives machine implementation methods based on GDB configurable frameworks |
| CN107562969A (en) * | 2016-06-30 | 2018-01-09 | 中国航发商用航空发动机有限责任公司 | The integrated approach and device of aeroengine control system software |
| CN107678958A (en) * | 2017-09-25 | 2018-02-09 | 中国航空工业集团公司西安飞机设计研究所 | A kind of method of testing for comprehensive parameters display system software |
| CN111123737A (en) * | 2018-11-30 | 2020-05-08 | 中国航空工业集团公司沈阳飞机设计研究所 | Digital hardware virtual simulation system |
| CN111190820A (en) * | 2019-12-25 | 2020-05-22 | 中国航空工业集团公司西安飞机设计研究所 | Construction method and test method of configuration item test platform of display control software |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2940586B1 (en) * | 2014-04-29 | 2023-03-01 | Hitachi, Ltd. | Method and system for testing control software of a controlled system |
-
2020
- 2020-06-11 CN CN202010527363.6A patent/CN113805848B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102968377A (en) * | 2012-12-13 | 2013-03-13 | 中国航空无线电电子研究所 | Virtual machine technique based airborne software system testing general platform |
| CN107562969A (en) * | 2016-06-30 | 2018-01-09 | 中国航发商用航空发动机有限责任公司 | The integrated approach and device of aeroengine control system software |
| CN106970825A (en) * | 2017-03-10 | 2017-07-21 | 深圳航天科技创新研究院 | A kind of ARM7 simulation objectives machine implementation methods based on GDB configurable frameworks |
| CN107678958A (en) * | 2017-09-25 | 2018-02-09 | 中国航空工业集团公司西安飞机设计研究所 | A kind of method of testing for comprehensive parameters display system software |
| CN111123737A (en) * | 2018-11-30 | 2020-05-08 | 中国航空工业集团公司沈阳飞机设计研究所 | Digital hardware virtual simulation system |
| CN111190820A (en) * | 2019-12-25 | 2020-05-22 | 中国航空工业集团公司西安飞机设计研究所 | Construction method and test method of configuration item test platform of display control software |
Non-Patent Citations (1)
| Title |
|---|
| 某型发动机控制软件全数字仿真研究与实施;顾鸣祺;张炜;高征;;航空计算技术;20170925(05);第123-126页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113805848A (en) | 2021-12-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102760098B (en) | Processor fault injection method oriented to BIT software test and simulator thereof | |
| US10360322B2 (en) | Simulation of virtual processors | |
| CN103136406B (en) | The method of visualization applications simulations function code | |
| CN102480467B (en) | A kind of SOC software and hardware cooperating simulation verification method of communications protocol Network Based | |
| CN104750603A (en) | Multi-core DSP (Digital Signal Processor) software emulator and physical layer software testing method thereof | |
| US8230402B2 (en) | Testing and debugging of dynamic binary translation | |
| CN106650149B (en) | Modelica model-based runtime fault injection system and method | |
| CN113196243A (en) | Improving simulation and tracking performance using compiler-generated simulation-optimized metadata | |
| CN113805848B (en) | Target machine control software integration method and system | |
| CN114417757A (en) | Method for automatically compiling and generating FPGA (field programmable Gate array) engineering with different functions | |
| Pohl et al. | vMAGIC—automatic code generation for VHDL | |
| CN103218250B (en) | A kind of processor analogy method | |
| Kooli et al. | Fault injection tools based on virtual machines | |
| CN108614764B (en) | IMA application software fault injection method | |
| CN102331961A (en) | Method, system and dispatcher for simulating multiple processors in parallel | |
| CN111597115A (en) | Automatic closed-loop test system and test method for embedded operating system | |
| CN105335203A (en) | Binary translation execution method of shared libraries and device | |
| US20120311542A1 (en) | Dynamic interface reduction for software model checking | |
| Engblom | Worst-case execution time analysis for optimized code | |
| US6853968B2 (en) | Simulation of data processing apparatus | |
| US6813751B2 (en) | Creating standard VHDL test environments | |
| CN112988145B (en) | Method for generating aeroengine software architecture and aeroengine control device | |
| CN112231165A (en) | Memory fault simulation method based on link library injection and memory mapping mode | |
| US8914274B1 (en) | Method and system for instruction set simulation with concurrent attachment of multiple debuggers | |
| Yau et al. | An object-oriented approach to software development for autonomous decentralized systems |
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 |