Airborne embedded application software digital simulation system and method
By simulating the hardware and software environment of embedded systems in a general computing environment, the problem that traditional embedded software development depends on actual hardware is solved, an efficient and flexible development process is achieved, and development efficiency and software quality are improved.
Patent Information
- Application Number
- CN202411434242.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-15
- Publication Date
- 2025-02-18
AI Technical Summary
Traditional embedded software development relies on the actual hardware environment, resulting in high development costs, long development cycles, flexibility and inefficiency, especially when hardware resources are limited or unavailable.
Simulate the hardware and software environment of an embedded system in a general computing environment, and provide the same system calls and hardware interfaces as the actual embedded system through virtual target machines and virtual simulation devices to realize software development, debugging and verification.
It improves development efficiency, shortens development cycle, reduces development costs, enhances test coverage, and improves software quality.
Smart Images
Figure CN119473494A_ABST
Abstract
Description
Technical Field
[0001] The invention belongs to the field of avionics, and in particular relates to an airborne embedded application software digital simulation system and method. Background Art
[0002] Embedded application software is a core component of avionics systems, involving multiple key functions such as flight control, navigation, and communication. As the complexity of aviation systems increases, the software development process faces huge challenges, including long development cycles, limited hardware resources, and high costs. Traditional embedded software development relies on the actual hardware environment, which not only increases development costs, but also limits the flexibility and efficiency of the development process.
[0003] For example, the development of airborne embedded application software requires frequent debugging and testing, and these operations usually rely on expensive and scarce hardware devices. For embedded systems that are still in the early stages of development, developers have to wait for the availability of hardware resources because the hardware devices are not yet mature or are limited in number, which prolongs the development cycle. In addition, hardware failures or upgrades may also have a significant impact on development work. Summary of the invention
[0004] Purpose of the invention: To provide an airborne embedded application software digital simulation system and method, which can simulate the hardware and software environment of the embedded system in a general computing environment, so that developers can develop, debug and verify software without relying on actual hardware, thereby improving development efficiency, shortening the development cycle, and reducing development costs.
[0005] Technical Solution
[0006] An airborne embedded application software digital simulation system, the system comprising:
[0007] Virtual target machine arranged on PC: Virtual target machine simulates the hardware environment of airborne embedded system on general-purpose computer, including RTOS adaptation layer, providing the same system call, driver call and C language library call as the actual embedded system; RTOS adaptation layer implements various system interfaces of RTOS by using Windows API, including task scheduling, memory management and interrupt processing interface;
[0008] Virtual simulation device: used to simulate the input and output of airborne equipment and provide interactive signals with embedded software; the virtual simulation device includes a protocol parsing module and a communication module; the protocol parsing module is responsible for parsing the instructions and data packets received from the embedded software and converting them into display signals of the virtual simulation device; the communication module uses the UDP protocol to realize the embedded software and the virtual simulation device.
[0009] Furthermore, the RTOS adaptation layer includes: a task management module, an interrupt management module, a memory management module, a timer management module, an inter-task communication module, a file system module, a network communication module, and an input / output management module.
[0010] Furthermore, the task management module uses Windows thread API to create and manage tasks; the thread priority is set through SetThreadPriority to simulate the priority scheduling mechanism in RTOS; the switching between tasks is automatically performed through the thread scheduler;
[0011] The interrupt management module handles asynchronous events and uses Windows event objects to simulate interrupt management. When an interrupt is triggered, the event object is set to trigger the corresponding ISR thread to handle the interrupt.
[0012] The memory management module is responsible for the allocation and release of dynamic memory. In RTOS, memory management usually includes heap memory management and stack management. Use Windows memory management API to simulate the allocation and release of heap memory. Use _alloca or local variables to simulate the management of stack memory.
[0013] The file system module provides a file operation interface for data storage and reading in embedded systems; uses Windows' file I / O API to simulate the operation of embedded file systems; creates virtual files, reads and writes data through Windows' file system;
[0014] The input / output management module manages the input and output operations of the system, such as device drivers and port management; it uses Windows I / O API to simulate the I / O operations of the device.
[0015] Furthermore, the timer management module is used to manage system timers, support timed tasks and time delay functions, and use Windows' high-precision timers and timer API to simulate timer functions.
[0016] Furthermore, the inter-task communication module supports data exchange and synchronization between tasks; in RTOS, commonly used IPC mechanisms include message queues, semaphores, and mutexes;
[0017] The message queue uses the Windows message queue API to implement message delivery;
[0018] Semaphore uses Windows semaphore API to achieve task synchronization;
[0019] Mutexes use the Windows mutex API to ensure mutually exclusive access to shared resources.
[0020] Furthermore, the communication module supports the implementation of a network protocol stack for the transmission and management of network data; uses Winsock API to implement TCP / IP communication in a Windows environment; and uses socket, bind, connect, send, and recv API functions to simulate the operation of an embedded network protocol stack;
[0021] The power management module is responsible for the control and management of the system power, including switching to low power mode and managing the device power state. In Windows, the power management API is used to simulate the power management function, control the system to enter standby or hibernation state, and simulate the behavior of low power mode.
[0022] Further, the protocol parsing module: This parses the data packets received from the onboard embedded application software and converts them into instructions that the virtual device can understand; the protocol parsing module needs to be designed according to the specific communication protocol to ensure the correct decoding and processing of the data; the parsing process includes the identification of the message header, the parsing of the data field and the verification of the checksum to ensure the integrity and correctness of the data packet during the transmission process;
[0023] The communication module is the bridge for data interaction between virtual simulation devices and embedded application software; the UDP protocol is used for communication, and the construction of the communication module includes the creation and management of UDP sockets, and the sending and receiving of data packets are realized through Windows API; the communication module needs to handle the fragmentation and reassembly of data packets during transmission to ensure data integrity and transmission efficiency under high load conditions.
[0024] The data display module is responsible for processing and displaying the received simulation data; the data is presented to the user in a graphical manner; the data display module uses the Windows graphical interface API to realize the graphical display of data, helping developers to intuitively monitor data changes during the simulation process.
[0025] A digital simulation method for airborne embedded application software, the steps are as follows:
[0026] Analyze embedded software to identify hardware interface types, system calls, memory management, overall operation mode and logic;
[0027] Involving virtual hardware interfaces according to the hardware interface type to simulate the physical hardware environment in the embedded system;
[0028] Build an RTOS adaptation layer to redirect RTOS system calls and hardware driver interfaces to Windows API; the RTOS adaptation layer includes task scheduling, interrupt handling, memory management, timer management, and inter-task communication of the RTOS used;
[0029] Communication protocol adaptation, establish UDP communication channel between onboard embedded application software and virtual simulation device; use Windows "socket" API to create UDP socket, "sendto" API is used to send data, and "recvfrom" API is used to receive data; configure communication protocol: configure communication protocol according to the format read by virtual simulation device for normal reading;
[0030] Run the adapted embedded software on the digital simulation platform and conduct comprehensive testing and optimization: Verify whether the software behaves as expected in the digital simulation environment by running actual communication management tasks, including verifying the correctness of serial port communication, the punctuality of timer-triggered tasks, and the reliability of inter-task communication;
[0031] During the testing process, if performance bottlenecks are found, corresponding optimizations are performed.
[0032] In summary, the beneficial effects of the present invention are as follows:
[0033] Improve development efficiency: By implementing system functions in a virtual environment, developers can continue development work when hardware resources are limited or unavailable, significantly shortening the development cycle.
[0034] Reduce development costs: Reduce dependence on actual hardware devices and reduce the need for expensive equipment during the development process, thereby saving costs.
[0035] Enhanced test coverage: Ability to fully simulate external devices and operation scenarios to improve software test coverage and reliability.
[0036] Improve software quality: By discovering and resolving potential issues at an early stage, the risk of software failure in actual hardware deployment is reduced, ensuring a high-quality final product. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] Figure 1 This is a schematic diagram of the digital simulation platform framework for airborne embedded application software;
[0038] Figure 2 It is a schematic diagram of the virtual target machine composition;
[0039] Figure 3 This is a schematic diagram of the composition of the virtual simulation device. DETAILED DESCRIPTION
[0040] The airborne embedded application software digital simulation platform of the present invention includes the following modules:
[0041] Virtual target machine module: This module simulates the hardware environment of the airborne embedded system on a general-purpose computer, including the RTOS adaptation layer, which can provide the same system calls, driver calls, and C language library calls as the actual embedded system. The RTOS adaptation layer uses Windows API to implement various system interfaces of RTOS, including task scheduling, memory management, interrupt processing and other functions, to ensure that the running behavior of embedded software on real hardware is accurately simulated in the virtual environment.
[0042] Virtual simulation device module: This module is used to simulate the input and output of airborne devices and provide interactive functions with embedded software. The virtual simulation device module includes a protocol parsing module and a communication module. The protocol parsing module is responsible for parsing the instructions and data packets received from the embedded software and converting them into control signals for the virtual device. The communication module uses the UDP protocol to achieve efficient data transmission, ensuring smooth and low-latency communication between the embedded software and the virtual device.
[0043] Communication mechanism: In order to ensure the real-time and reliability of data transmission between embedded application software and virtual simulation devices, the present invention adopts UDP communication protocol for data transmission. The selection of UDP communication protocol is based on its low latency and high transmission efficiency, which enables the simulation system to quickly respond to the input of the software and feedback the output data of the device.
[0044] Specifically, the steps to adapt the airborne embedded software to the digital simulation platform are as follows:
[0045] 1. Embedded software analysis: Conduct a detailed analysis of the target airborne embedded application software to clarify its dependence on hardware interfaces (such as GPIO ports, RS422, I2C, SPI, ARINC429, 1553B, IEEE 1394, etc.), system calls, memory management, as well as its overall operating mode and logic.
[0046] 2. Virtual hardware interface design: Based on the analysis results, design virtual hardware interfaces that will simulate the physical hardware environment in the embedded system. Virtual interfaces include simulating various hardware interfaces so that embedded software can run in a virtual environment without modifying the code.
[0047] 3. RTOS Adaptation Layer Construction: By building the RTOS adaptation layer, the RTOS system calls and hardware driver interfaces are redirected to the Windows API. The RTOS adaptation layer includes the implementation of the RTOS task scheduling, interrupt handling, memory management, timer management, inter-task communication and other modules to ensure that the onboard embedded application software has the same operating behavior in the virtual environment as the actual hardware environment.
[0048] 4. Data communication adaptation: Use UDP protocol to establish a communication channel between embedded software and virtual simulation equipment to ensure the real-time and reliability of data transmission. It is necessary to confirm the number of external interfaces of the onboard embedded software and assign IP and port numbers. The interface control protocol needs to be configured according to the specified format so that the virtual simulation equipment can read it. When parsing the data protocol, pay attention to whether the big and small ends of the onboard embedded platform are consistent with the PC environment. If not, it is necessary to add big and small end conversion in the data communication interface adaptation.
[0049] 5. Functional verification and performance tuning: Through comprehensive functional testing, verify the running effect of the airborne embedded application software on the digital simulation platform. The tuning process includes adjusting thread priority, optimizing memory management strategy, improving communication efficiency, etc., to ensure the running efficiency and stability of the software in the virtual environment.
[0050] Construction method of RTOS adaptation layer
[0051] The RTOS adaptation layer is the core component of the virtual target machine module, responsible for simulating the functions of various real-time operating systems (RTOS) in embedded systems. The following is a detailed description of all key modules in RTOS and their implementation in the Windows environment:
[0052] 1. Task management module
[0053] Task management is one of the core functions of RTOS, which is responsible for managing and scheduling multiple tasks. Each task usually exists in the form of a thread and can be set with different priorities.
[0054] Implementation method: Use Windows thread API (such as CreateThread, SetThreadPriority) to create and manage tasks. Set the thread priority through SetThreadPriority to simulate the priority scheduling mechanism in RTOS. Switching between tasks is automatically performed through the thread scheduler.
[0055] 2. Interrupt management module
[0056] The interrupt management module handles asynchronous events, such as hardware interrupts, timer interrupts, etc. Interrupts usually interrupt the task being executed and execute a specific interrupt service routine (ISR).
[0057] Implementation method: Use Windows event objects (such as CreateEvent, SetEvent, WaitForSingleObject) to simulate interrupt management. When an interrupt is triggered, set the event object to trigger the corresponding ISR thread to handle the interrupt.
[0058] 3. Memory management module
[0059] The memory management module is responsible for the allocation and release of dynamic memory. In RTOS, memory management usually includes heap memory management, stack management, etc.
[0060] Implementation method: Use Windows memory management API (such as VirtualAlloc, VirtualFree) to simulate the allocation and release of heap memory. At the same time, use _alloca or local variables to simulate the management of stack memory.
[0061] 4. Timer management module
[0062] The timer management module is used to manage system timers and support timed tasks and time delay functions. Timers are crucial functions in real-time systems and are used for periodic task scheduling, timeout management, etc.
[0063] Implementation method: Use Windows' high-precision timer (such as QueryPerformanceCounter) and timer API (such as SetTimer) to simulate the timer function. Developers can set the timer interval to trigger specific tasks regularly.
[0064] 5. Inter-task communication (IPC) module
[0065] The inter-task communication (IPC) module supports data exchange and synchronization between tasks. In RTOS, commonly used IPC mechanisms include message queues, semaphores, and mutexes.
[0066] Implementation method:
[0067] Message queue: Use Windows message queue API (such as PostMessage, GetMessage) to implement message delivery.
[0068] Semaphore: Use Windows semaphore API (such as CreateSemaphore, WaitForSingleObject, ReleaseSemaphore) to achieve task synchronization.
[0069] Mutex: Use Windows mutex API (such as CreateMutex, WaitForSingleObject, ReleaseMutex) to ensure mutual exclusion access to shared resources.
[0070] 6. File system module
[0071] The file system module provides a file operation interface for storing and reading data in embedded systems. The file system in RTOS may include lightweight file systems (such as FAT, YAFFS, etc.).
[0072] Implementation method: Use Windows file I / O API (such as CreateFile, ReadFile, WriteFile, CloseHandle) to simulate the operation of the embedded file system. You can create virtual files, read and write data through the Windows file system.
[0073] 7. Network communication module
[0074] The network communication module supports the implementation of the network protocol stack, such as the TCP / IP protocol, for the transmission and management of network data.
[0075] Implementation method: Use Winsock API to implement TCP / IP communication in Windows environment. Use API functions such as socket, bind, connect, send, recv, etc. to simulate the operation of embedded network protocol stack.
[0076] 8. Power management module
[0077] The power management module is responsible for the control and management of the system power, including switching to low power mode and managing the power status of the device.
[0078] Implementation method: In Windows, power management APIs (such as SetThreadExecutionState, GetSystemPowerStatus) are used to simulate power management functions, which can control the system to enter standby or hibernation state and simulate the behavior of low power mode.
[0079] 9. Input / Output (I / O) Management Module
[0080] The I / O management module handles the input and output operations of the system, such as device drivers, port management, etc.
[0081] Implementation method: Use Windows I / O API (such as ReadFile, WriteFile, DeviceIoControl) to simulate the I / O operation of the device. By creating a virtual device file or using a simulated hardware interface, developers can test I / O functions in the Windows environment.
[0082] Through the detailed implementation of the above RTOS module, the RTOS adaptation layer of the present invention can accurately simulate various real-time operating system functions in the embedded system in the Windows environment, providing a complete virtual platform for the development and testing of airborne embedded application software.
[0083] Construction method of virtual simulation device module
[0084] The virtual simulation device module is an important component of the present invention, and is mainly responsible for the interaction with the onboard embedded application software. This module consists of the following submodules:
[0085] Protocol parsing module: The main function of this module is to parse the data packets received from the onboard embedded application software and convert them into instructions that the virtual device can understand. The protocol parsing module needs to be designed according to the specific communication protocol to ensure the correct decoding and processing of the data. The parsing process usually includes the identification of the message header, the parsing of the data field and the verification of the checksum to ensure the integrity and correctness of the data packet during transmission.
[0086] Communication module: The communication module is a bridge for data interaction between virtual simulation devices and embedded application software. The present invention adopts UDP protocol for communication because it has the advantages of low latency and efficient transmission. The construction of the communication module includes the creation and management of UDP sockets, and the sending and receiving of data packets are realized through Windows API (such as socket, bind, sendto, recvfrom). The communication module needs to handle the fragmentation and reorganization of data packets during transmission to ensure data integrity and transmission efficiency under high load conditions.
[0087] Data display module: This module is mainly responsible for processing and displaying the received simulation data. The data can be presented to the user in a graphical way, such as real-time curves, data tables, etc. The data display module uses Windows' graphical interface API (such as GDI+) to realize the graphical display of data, helping developers to intuitively monitor data changes during the simulation process.
[0088] Example
[0089] Assume that we have an embedded application software for airborne communication management system, which runs on RTOS platform and relies on multiple serial port modules and timers for data communication and task scheduling. The goal is to adapt the software to the digital simulation platform of the present invention so that it can be developed and tested in Windows environment.
[0090] 1. Analysis and decomposition
[0091] First, a detailed analysis of the onboard embedded application software is performed:
[0092] Hardware interface analysis: The serial port interface through which the software communicates with external devices was identified. It was found that the software exchanges data with external sensors through two serial ports and relies on timers to trigger periodic tasks.
[0093] System calls and resource management: The software uses RTOS system calls to create tasks, allocate memory, manage timers, and handle interrupts. Task priority scheduling is used to ensure the real-time performance of critical tasks.
[0094] Memory and Buffer Management: Analyzes how memory is managed in the software, including dynamic memory allocation and buffer management, to ensure that these operations are performed correctly in a virtual environment.
[0095] 2. Virtual hardware interface design
[0096] According to the software's dependence on the hardware interface, design the corresponding virtual hardware interface:
[0097] Virtual serial port design: Create a virtual serial port in the Windows environment and use the "CreateFile", "ReadFile", and "WriteFile" APIs to simulate serial port communications in embedded systems. Through these interfaces, onboard embedded application software can read sensor data and send control instructions on the digital simulation platform without modifying the original code.
[0098] Virtual timer setting: Use Windows timer API to simulate the timer function in RTOS. The timer triggers the task periodically to ensure that the task can be executed at the correct time.
[0099] 3. RTOS adaptation layer construction
[0100] Build an RTOS adaptation layer in the virtual target machine to ensure that the system calls of the onboard embedded application software can be executed in the Windows environment:
[0101] Task scheduling: Use Windows thread APIs (such as "CreateThread" and "SetThreadPriority") to implement the task management function of RTOS. Each RTOS task corresponds to a thread in the Windows environment, and the thread priority is set through the "SetThreadPriority" API to ensure that the execution order of tasks is consistent with that in RTOS.
[0102] Interrupt handling: In RTOS, interrupts are used to handle asynchronous events. Hardware interrupts are simulated through the "CreateEvent", "SetEvent" and "WaitForSingleObject" APIs to ensure that the interrupt service routine can respond correctly in the simulation environment.
[0103] Memory management: Use Windows memory management APIs (such as "VirtualAllocation" and "VirtualFree") to implement dynamic memory allocation and release of RTOS, ensuring that the software's memory operations in the virtual environment are consistent with the actual hardware environment.
[0104] 4. Data communication adaptation
[0105] In order to ensure that the data communication between the onboard embedded application software and the virtual simulation device is consistent with the actual environment, UDP communication is used for adaptation:
[0106] Establish a communication channel: Establish a UDP communication channel between the onboard embedded application software and the virtual simulation device. Use the Windows "socket" API to create a UDP socket, the "sendto" API to send data, and the "recvfrom" API to receive data. Through this communication channel, the onboard embedded application software can send and receive data just like in the actual hardware environment.
[0107] Configure the communication protocol: Configure the communication protocol according to the format read by the virtual simulation device so that the virtual simulation device can read it normally.
[0108] Data format and protocol analysis: Ensure that the format of the data packets sent and received is consistent with the protocol in the actual environment, and ensure that the big and small ends of the airborne embedded environment and the PC environment are consistent. The protocol analysis module decodes the received data packets and converts them into data that can be displayed in the virtual simulation device.
[0109] 5. Functional verification and performance tuning
[0110] Run the adapted embedded software on the digital simulation platform and conduct comprehensive testing and optimization:
[0111] Functional verification: By running actual communication management tasks, verify whether the behavior of the software in the digital simulation environment is consistent with expectations. This includes verifying the correctness of serial port communication, the punctuality of timer-triggered tasks, and the reliability of inter-task communication.
[0112] Performance tuning: During the test, if performance bottlenecks are found, corresponding optimizations are performed. For example, thread priorities are adjusted to improve task response time, memory management strategies are optimized to reduce memory fragmentation, and UDP communication parameters are improved to reduce transmission delays.
Claims
1. An airborne embedded application software digital simulation system, characterized in that: The system includes: Virtual target machine arranged on PC: Virtual target machine simulates the hardware environment of airborne embedded system on general-purpose computer, including RTOS adaptation layer, providing the same system call, driver call and C language library call as the actual embedded system; RTOS adaptation layer implements various system interfaces of RTOS by using Windows API, including task scheduling, memory management and interrupt processing interface; Virtual simulation device: used to simulate the input and output of airborne equipment and provide interactive signals with embedded software; the virtual simulation device includes a protocol analysis module and a communication module; The protocol parsing module is responsible for parsing the instructions and data packets received from the embedded software and converting them into display signals of the virtual simulation device; the communication module uses the UDP protocol to realize the embedded software and the virtual simulation device.
2. The system according to claim 1, characterized in that: The RTOS adaptation layer includes: task management module, interrupt management module, memory management module, timer management module, inter-task communication module, file system module, network communication module, and input / output management module.
3. The system according to claim 2, characterized in that: The task management module uses Windows thread API to create and manage tasks; SetThreadPriority is used to set the thread priority to simulate the priority scheduling mechanism in RTOS; switching between tasks is automatically performed through the thread scheduler; The interrupt management module handles asynchronous events and uses Windows event objects to simulate interrupt management. When an interrupt is triggered, the event object is set to trigger the corresponding ISR thread to handle the interrupt. The memory management module is responsible for the allocation and release of dynamic memory. In RTOS, memory management usually includes heap memory management and stack management. Use Windows memory management API to simulate the allocation and release of heap memory. Use _alloca or local variables to simulate the management of stack memory. The file system module provides a file operation interface for data storage and reading in embedded systems; uses Windows' file I / O API to simulate the operation of embedded file systems; creates virtual files, reads and writes data through Windows' file system; The input / output management module manages the input and output operations of the system, such as device drivers and port management; it uses Windows I / O API to simulate the I / O operations of the device.
4. The system according to claim 3, characterized in that: The timer management module is used to manage system timers, support scheduled tasks and time delay functions; and use Windows' high-precision timers and timer API to simulate timer functions.
5. The system according to claim 4, characterized in that: The inter-task communication module supports data exchange and synchronization between tasks; in RTOS, commonly used IPC mechanisms include message queues, semaphores, and mutexes; The message queue uses the Windows message queue API to implement message delivery; Semaphore uses Windows semaphore API to achieve task synchronization; Mutexes use the Windows mutex API to ensure mutually exclusive access to shared resources.
6. The system according to claim 5, characterized in that: The communication module supports the implementation of the network protocol stack for the transmission and management of network data; uses Winsock API to implement TCP / IP communication in Windows environment; uses socket, bind, connect, send, and recv API functions to simulate the operation of the embedded network protocol stack; The power management module is responsible for the control and management of the system power, including switching to low power mode and managing the device power state. In Windows, the power management API is used to simulate the power management function, control the system to enter standby or hibernation state, and simulate the behavior of low power mode.
7. The system according to claim 6, characterized in that: Protocol parsing module: This module parses the data packets received from the onboard embedded application software and converts them into instructions that the virtual device can understand. The protocol parsing module needs to be designed according to the specific communication protocol to ensure the correct decoding and processing of the data. The parsing process includes the identification of the message header, the parsing of the data field and the verification of the checksum to ensure the integrity and correctness of the data packet during transmission. The communication module is the bridge for data interaction between virtual simulation devices and embedded application software; the UDP protocol is used for communication, and the construction of the communication module includes the creation and management of UDP sockets, and the sending and receiving of data packets are realized through Windows API; the communication module needs to handle the fragmentation and reassembly of data packets during transmission to ensure data integrity and transmission efficiency under high load conditions. The data display module is responsible for processing and displaying the received simulation data; the data is presented to the user in a graphical manner; The data display module uses Windows' graphical interface API to achieve graphical display of data, helping developers to intuitively monitor data changes during the simulation process.
8. A digital simulation method for airborne embedded application software, based on the system implementation of any of the above, characterized in that: Here are the steps: Analyze embedded software to identify hardware interface types, system calls, memory management, overall operation mode and logic; Involving virtual hardware interfaces according to the hardware interface type to simulate the physical hardware environment in the embedded system; Build an RTOS adaptation layer to redirect RTOS system calls and hardware driver interfaces to Windows API; the RTOS adaptation layer includes task scheduling, interrupt handling, memory management, timer management, and inter-task communication of the RTOS used; Communication protocol adaptation, establish UDP communication channel between onboard embedded application software and virtual simulation device; use Windows "socket" API to create UDP socket, "sendto" API is used to send data, "recvfrom" API is used to receive data; configure communication protocol: configure communication protocol according to the format read by virtual simulation device for normal reading; Run the adapted embedded software on the digital simulation platform and conduct comprehensive testing and optimization: Verify whether the software behaves as expected in the digital simulation environment by running actual communication management tasks, including verifying the correctness of serial port communication, the punctuality of timer-triggered tasks, and the reliability of inter-task communication; During the testing process, if performance bottlenecks are found, corresponding optimizations are performed.