Real-time FADEC operating system transplanting method

Abstract

The invention discloses a real-time FADEC operating system transplantation method which comprises the following steps: determining a selected hardware processor model and a specific operating system kernel according to FADEC control software performance requirements; the method comprises the following steps: dividing interfaces of an application software layer and an operating system layer in FADEC control software, and modifying an initial starting part code of operating system software according to a selected processor model and an operating system kernel, including adjusting operating system kernel codes of different processor chips and software and hardware configuration in an initialization process; based on the defined interface, packaging the driving equipment before transplantation; the initialization code and the packaging interface function are combined, transplanted operating system software is obtained, an application layer interface is not changed, and the development process of the FADEC control software is completed; debugging and verifying power-on initialization, signal input and output, communication receiving and sending, task allowance and an abnormal response mechanism, and judging whether requirements are met or not according to verification results; the demand tracing error rate is reduced, and the research and development efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of computer operating system software design, and particularly relates to a method for transplanting a real-time FADEC operating system. Background Art

[0002] The FADEC (Full Authority Digital Electronic Controller) operating system software is an important platform software for the real-time control of aeroengines, which is determined by the FADEC controller hardware and the operating system kernel architecture. However, due to different performance requirements of control software for different aircraft engines, and considering cost and performance, different FADEC controllers may adopt different hardware. At the same time, the FADEC controllers used for the same type of aeroengine may also be upgraded. In this case, for application layer software developers, changing the application software code may introduce more problems, and the amount of code to be changed is huge. Re-testing, reviewing, and various processes are also more complex. And the operating system software is strongly related to the hardware, and it is necessary to be able to achieve software compatibility under different hardware platforms or different operating system kernels through design, ensure the consistency of the operating system layer / application layer interface and the certainty of the application layer call method, so as to minimize the workload of software re-development and the defect rate introduced, and achieve the goal of improving quality and efficiency. Therefore, it is necessary to propose a reasonable and effective operating system transplantation method, which can be compatible with different hardware characteristics and operating system kernel architectures, design an operating system software that meets the performance requirements of engine control software, and minimize the modification of the application layer code as much as possible to reduce the software R & D cost. This is one of the hot issues in the field of control software design. Summary of the Invention

[0003] Object of the Invention: The object of the present invention is to provide a method for transplanting a real-time FADEC operating system. According to the hardware characteristics of different FADEC controllers and the operating system kernel architecture, and based on the interface between the operating system and the application software, each driver function is hooked on the same call interface, the startup functions of different kernels are optimized and adjusted, the underlying driver is accessed in the form of pointer passing, the hardware acquisition value of the FADEC controller is obtained in real time, a value is injected into the hardware in real time, and the control state is changed.

[0004] Technical Solution: A method for transplanting a real-time FADEC operating system according to the present invention includes the following steps: (1) Determine the selected hardware processor model and the specific operating system kernel according to the performance requirements of the FADEC control software; (2)Divide the interfaces between the application software layer and the operating system layer in the FADEC control software into device loading interfaces, input interfaces, output interfaces, control interfaces, and other driver interfaces; (3)Modify the initial startup part of the operating system software according to the selected processor model and operating system kernel, including adjusting the operating system kernel code of different processor chips and the software and hardware configurations in the initialization process; (4)Based on the defined interfaces, encapsulate the pre-migration driver devices, including analog input, analog output, digital input, digital output, frequency input, BIT signal input, enable control, status acquisition, communication reception, communication transmission, etc. drivers; (5)Merge the initialization code and the encapsulated interface functions to obtain the migrated operating system software, with the application layer interfaces remaining unchanged, and complete the development process of the FADEC control software; (6)Debug and verify the power-on initialization, signal input and output, communication reception and transmission, task margin, and exception response mechanism, and judge whether it meets the requirements according to the verification results.

[0005] Furthermore, the hardware processor models include MPC5554, MPC5674, and P2020.

[0006] Furthermore, when the operating system based on the MPC5554 and MPC5674 processor chips is changed to a multi-core operating system based on the P2020 processor chip, modify the operating system kernel code and modify the software and hardware configurations of the P2020 chip in the initialization process, including LAW, LBC, MMU, and startup timing, and add the configurations of some peripherals, including the PCIE bus and the initial configuration of the dual-core; when the multi-core operating system based on the P2020 processor chip is changed to an operating system based on the MPC5554 and MPC5674 processor chips, modify the operating system kernel code and modify the software and hardware configurations of the MPC5554 and MPC5674 chips in the initialization process, including TLB, MMU, and startup timing.

[0007] Furthermore, the encapsulated Read interface includes drivers such as analog input, digital input, frequency input, BIT signal input, and communication reception; the encapsulated Write interface includes drivers such as analog output, digital output, and communication transmission; the encapsulated Ioctl interface includes drivers such as enable control and status acquisition.

[0008] Further, the specific evaluation criteria for debugging and verification include: power-on initialization time: the control software runs normally without the risk of crashing; signal input and output: the collected values of analog input, digital input, frequency input, etc. match the expected input values, and the controller output results such as analog output and digital output match the expected outputs; communication reception and transmission: for RS232, RS422, RS485, ARINC429, ARINC664, CCDL, ARINC659, I2C, CAN, Ethernet, etc., the data on the receiving link meets the requirements of the receiving protocol, and the data on the sending link meets the requirements of the sending protocol; task margin: the maximum time-consuming of the real-time tasks of the FADEC control software is within the safety margin without timeout; exception response mechanism: the transplanted operating system can correctly trigger the exception response mechanism after an exception occurs and accurately record the exception information.

[0009] Further, it also includes sorting out the driver functions under the general transplantation interface to form a general transplantation driver library, and solidifying the initialization code into the minimum system, which is convenient for reuse in subsequent other projects and improves the production and R & D efficiency.

[0010] Further, judging whether the requirements are met according to the verification results is specifically as follows: if there is a non-passing situation, the software of the non-passing part is modified. When modifying the code at the operating system layer, it is necessary to repeat the steps of encapsulating the interface, merging the code and continuing the verification. When only the application layer code needs to be modified, the above-mentioned steps do not need to be repeated until all tests are completed, and the R & D of the FADEC control software based on the operating system transplantation method is completed.

[0011] A real-time FADEC operating system transplantation system according to the present invention includes: A hardware processor model determination module, configured to determine the selected hardware processor model and the specific operating system kernel according to the performance requirements of the FADEC control software; An interface division module, configured to divide the interfaces between the application software layer and the operating system layer in the FADEC control software; A startup code modification module, configured to modify the initial startup part of the operating system software according to the selected processor model and operating system kernel; A driver encapsulation module, configured to encapsulate the pre-transplantation driver devices based on the defined interfaces; A code merging module, configured to merge the initialization code and the encapsulated interface functions to obtain the transplanted operating system software; A debugging and verification module, configured to debug and verify the power-on initialization, signal input and output, communication reception and transmission, task margin, and exception response mechanism; A software modification module, configured to modify the software of the non-passing part according to the debugging and verification results.

[0012] An electronic device according to the present invention includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the computer program is loaded into the processor, it implements any one of the real-time FADEC operating system transplantation methods.

[0013] A storage medium according to the present invention stores a computer program. When the computer program is executed by a processor, it implements any one of the real-time FADEC operating system transplantation methods.

[0014] Beneficial effects: Compared with the prior art, the present invention has the following remarkable advantages: When the FADEC controller hardware is upgraded and the host performance indicators change, the software R & D and testing costs can be effectively reduced; In software R & D, a change model is adopted. For those with unchanged hardware peripherals, the underlying hardware drivers can be reused in large quantities, and only need to be encapsulated by transplanting general interfaces; The usage methods of the application layer and the operating system interface remain consistent, reducing the writing of tens of thousands of lines of code, reducing the error rate of requirement traceability, and accelerating the R & D efficiency; Testers only need to review the changed parts and execute test cases. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a flowchart of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0016] The technical solution of the present invention will be further described below with reference to the drawings.

[0017] As Figure 1 shown, an embodiment of the present invention provides a real-time FADEC operating system transplantation method, including the following steps: S1: According to the performance requirements of the FADEC control software, first determine the selected hardware processor model and the specific operating system kernel. S2: Clearly divide the interfaces between the application software layer and the operating system layer in the FADEC control software, mainly into 5 types of general transplantation interfaces: device loading interface (Open), input interface (Read), output interface (Write), control interface (Ioctl), and other driver interfaces. S3: Based on the processor model and operating system kernel in S1, modify the initial startup part of the operating system software code. S31: When changing the operating system based on the MPC5554 and MPC5674 processor chips to a multi-core operating system based on the P2020 processor chip, it is necessary to modify the operating system kernel code, modify the software and hardware configurations of the P2020 chip in the initialization process (such as LAW, LBC, MMU, and startup timing, etc.), and add the configurations of some peripherals (PCIE bus, initial configuration of dual cores, etc.) to meet the chip usage requirements. S32: When changing the multi-core operating system based on the P2020 processor chip to an operating system based on the MPC5554 and MPC5674 processor chips, it is necessary to modify the operating system kernel code and modify the software and hardware configurations (such as TLB, MMU, and startup timing, etc.) of the MPC5554 and MPC5674 chips during the initialization process to meet the chip usage requirements.

[0018] S4: Based on the interfaces defined in S2, encapsulate the pre-migration driver devices, which mainly include 10 types of drivers: analog input, analog output, digital input, digital output, frequency input, BIT signal input, enable control, status acquisition, communication reception, and communication transmission. Among them, the encapsulated Read interface includes the aforementioned 5 types of drivers (analog input, digital input, frequency input, BIT signal input, communication reception), the encapsulated Write interface includes the aforementioned 3 types of drivers (analog output, digital output, communication transmission), and the encapsulated Ioctl interface includes the aforementioned 2 types of drivers (enable control, status acquisition). Other driver interfaces (such as Flash read / write, time measurement, etc.) can directly reuse the pre-migration drivers and provide them for use by the application software function interfaces.

[0019] S5: Combine the initialization code and the encapsulated interface functions to obtain the post-migration operating system software. The application layer interfaces remain unchanged (the usage method is the same as that of the interfaces in the pre-migration operating system layer), and complete the development process of the FADEC control software.

[0020] S6: Debug and verify the power-on initialization, signal input / output, communication reception / transmission, task margin, and exception response mechanisms respectively. The specific judgment process for the verification results of the migration software is as Figure 1 shown, and the normal criteria for each result judgment are as follows: S61: Power-on initialization time: The control software runs normally without the risk of crashing.

[0021] S62: Signal input / output: The collected values of analog input, digital input, frequency input, etc. are consistent with the expected input values, and the controller output results of analog output, digital output, etc. are consistent with the expected outputs.

[0022] S63: Communication reception / transmission: For RS232, RS422, RS485, ARINC429, ARINC664, CCDL, ARINC659, I2C, CAN, Ethernet, etc., whether the data on the receiving link all meet the requirements of the receiving protocol, and whether the data on the sending link meet the requirements of the sending protocol.

[0023] S64: Task margin: The maximum time consumption of the real-time tasks of the FADEC control software is within the safety margin, without timeout phenomena S65: Exception response mechanism: After an exception occurs in the transplanted operating system, the exception response mechanism can be correctly triggered to accurately record the exception information.

[0024] S7: If there are any non-conforming situations, modify the software of the non-conforming parts. When modifying the code at the operating system layer, repeat S4 and S5 for the modified parts and continue to execute S6; when only the application layer code needs to be modified, the foregoing steps do not need to be executed. Finally, complete all tests. The R & D of the FADEC control software based on the operating system transplantation method is completed and enters the delivery process.

Claims

1. A method for porting a real-time FADEC operating system, characterized in that, It includes the following steps: (1) Determine the selected hardware processor model and the specific operating system kernel according to the performance requirements of the FADEC control software; (2) Divide the interfaces between the application software layer and the operating system layer in the FADEC control software into device loading interfaces, input interfaces, output interfaces, control interfaces, and other driver interfaces; (3) Modify the initial startup part of the operating system software according to the selected processor model and operating system kernel, including adjusting the operating system kernel code and the software and hardware configurations of the initialization process for different processor chips; (4) Package the pre-migration driver devices based on the defined interfaces, including analog input, analog output, digital input, digital output, frequency input, BIT signal input, enable control, status acquisition, communication reception, communication transmission, etc. drivers; (5) Merge the initialization code and the packaged interface functions to obtain the migrated operating system software, with the application layer interface remaining unchanged, and complete the development process of the FADEC control software; (6) Debug and verify the power-on initialization, signal input and output, communication reception and transmission, task margin, and exception response mechanism, and judge whether it meets the requirements according to the verification results.

2. A method for transplanting a real-time FADEC operating system according to claim 1, characterized in that The hardware processor models include MPC5554, MPC5674, and P2020.

3. A method for transplanting a real-time FADEC operating system according to claim 1, characterized in that, When the operating system based on the MPC5554 and MPC5674 processor chips is changed to a multi-core operating system based on the P2020 processor chip, modify the operating system kernel code and modify the software and hardware configurations of the P2020 chip during the initialization process, including LAW, LBC, MMU, and startup timing, and add the configurations of some peripherals, including the PCIE bus and the initial configuration of the dual-core; When the multi-core operating system based on the P2020 processor chip is changed to an operating system based on the MPC5554 and MPC5674 processor chips, modify the operating system kernel code and modify the software and hardware configurations of the MPC5554 and MPC5674 chips during the initialization process, including TLB, MMU, and startup timing.

4. A method for porting a real-time FADEC operating system according to claim 1, characterized in that, The packaged Read interface includes drivers such as analog input, digital input, frequency input, BIT signal input, and communication reception; the packaged Write interface includes drivers such as analog output, digital output, and communication transmission; the packaged Ioctl interface includes drivers such as enable control and status acquisition.

5. A method for transplanting a real-time FADEC operating system according to claim 1, characterized in that, Specific evaluation criteria for debugging and verification include: Power-on initialization time: The control software runs normally without the risk of crashing; Signal input and output: The acquisition values of analog input, digital input, frequency input, etc. are consistent with the expected input values, and the controller output results such as analog output and digital output are consistent with the expected outputs; Communication reception and transmission: For RS232, RS422, RS485, ARINC429, ARINC664, CCDL, ARINC659, I2C, CAN, Ethernet, etc., the data on the receiving link meets the requirements of the receiving protocol, and the data on the sending link meets the requirements of the sending protocol; Task margin: The maximum time consumption of the real-time tasks of the FADEC control software is within the safety margin without timeout; Exception response mechanism: The transplanted operating system can correctly trigger the exception response mechanism after an exception occurs and accurately record the exception information.

6. A method for porting a real-time FADEC operating system according to claim 1, characterized in that It also includes sorting out the driver functions under the general transplantation interface to form a general transplantation driver library, and solidifying the initialization code into the minimum system, which is convenient for reuse in subsequent other projects and improves the production and R & D efficiency.

7. A method for transplanting a real-time FADEC operating system according to claim 1, characterized in that, Judging whether the requirements are met according to the verification results is specifically as follows: If there is a non-compliant situation, modify the software of the non-compliant part. When modifying the code at the operating system layer, it is necessary to repeat the steps of encapsulating the interface, merging the code and continuing the verification. When only the application layer code needs to be modified, the above steps do not need to be repeated until all tests are completed, and the R & D of the FADEC control software based on the operating system transplantation method is completed.

8. A real-time FADEC operating system transplantation system, characterized in that, Including: A hardware processor model determination module, which is used to determine the selected hardware processor model and the specific operating system kernel according to the performance requirements of the FADEC control software; An interface division module, which is used to divide the interface between the application software layer and the operating system layer in the FADEC control software; A startup code modification module, which is used to modify the initial startup part of the operating system software according to the selected processor model and operating system kernel; A driver encapsulation module, which is used to encapsulate the pre-transplantation driver devices based on the defined interface; A code merging module, which is used to merge the initialization code and the encapsulated interface functions to obtain the transplanted operating system software; A debugging and verification module, which is used to debug and verify the power-on initialization, signal input and output, communication reception and transmission, task margin, and exception response mechanism; A software modification module, which is used to modify the non-compliant part of the software according to the debugging and verification results.

9. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the computer program is loaded into the processor, it implements a real-time FADEC operating system transplantation method according to any one of claims 1-7.

10. A storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements a real-time FADEC operating system transplantation method according to any one of claims 1-7.

Images