A method for configuring and implementing a logbook based on the ARINC653 standard

Abstract

This application provides a method for configuring and implementing a logbook based on the ARINC653 standard. The method includes: configuring a shared I / O space, wherein the shared I / O space is used for space mapping of the logbook, and the shared I / O space includes virtual addresses; configuring at least one logbook, wherein the logbook exists in the configured shared I / O space, and the logbook includes a name; generating configuration data; initializing the logbook; creating the logbook according to the logbook name, maximum number of messages, maximum message length, and the configuration data, wherein the output parameters of the logbook include a logbook ID; and performing read and write operations on the logbook according to the logbook ID.

Description

Technical Field

[0001] This invention belongs to the technical field of computer system software, and specifically proposes a method for configuring and implementing a logbook based on the ARINC653 standard. Background Technology

[0002] With the development of integrated and modular systems, operating systems with multi-partition structures conforming to the ARINC653 standard are becoming increasingly widely used, and the partition applications running on them are becoming more and more complex. In some user applications, it is necessary to record important information that can still be retrieved after a module power failure or partition restart. Since the data is recorded in RAM, the message logging and sending functions provided by ARINC653 Part 1 result in message loss after a partition restart or module power failure. Storing data using a file system is also very complex.

[0003] Based on the above requirements, there is an urgent need for a logger configuration and implementation method based on the ARINC653 standard. Summary of the Invention

[0004] This invention proposes a logger configuration and implementation method based on the ARINC653 standard, enabling system integrators or developers to read error information recorded in the partition before a partition restarts or a module loses power.

[0005] The advantages and effects of this invention are as follows: This application provides a logbook configuration and implementation method based on the ARINC653 standard. It adds logbook configuration to the shared I / O configuration provided by the ARINC653 standard partitioned operating system; it adds a logbook process and a common buffer design based on the ARINC653 standard definition to enable recording information to multiple logbooks within a partition; and it uses a shared I / O design to shield the differences between different hardware, allowing applications to record data to different non-volatile memories through a unified APEX interface. This provides a data recording method for partitioned operating system applications, allowing users to record data on non-volatile storage devices according to actual needs. This data remains readable and unlost after module power failure or partition restart. Attached Figure Description

[0006] Figure 1 This application provides a schematic diagram of a log recording configuration.

[0007] Figure 2 A schematic diagram of a shared I / O configuration provided in an embodiment of this application;

[0008] Figure 3 This application provides a logbook initialization process for embodiments of the present application;

[0009] Figure 4 This application provides a log recording implementation process. Detailed Implementation

[0010] This invention proposes a logger configuration and implementation method based on the ARINC 653 standard. Through shared I / O technology, it achieves the logger functionality required by the ARINC 653 standard, ensuring that data stored by applications on a partition using the APEX interface is not lost after a partition restart or module power failure. The technical solution includes:

[0011] 1. Log recording of this process and public buffer design

[0012] This invention, based on the ARINC 653 standard, adds a logbook process and a common buffer design. The logbook process and common buffer are created during the initialization of the logbook function; each partition has one logbook process and one common buffer. The logbook process receives messages from the common buffer and determines which log table's corresponding buffer to receive the message from.

[0013] 2. Design based on shared I / O

[0014] This invention maps different physical devices through shared I / O, and the application records data in non-volatile memory instead of RAM through a unified APEX interface, thereby ensuring that data is not lost after the module loses power or the partition restarts.

[0015] It should be noted that the logbook defined by the ARINC 653 standard consists of a non-volatile memory and a buffer in RAM. Considering the potential read / write / erase latency of non-volatile memory, the buffer in RAM allows the application to write messages continuously.

[0016] Example 1

[0017] like Figure 4 As shown, this application provides a method for configuring and implementing a logbook based on the ARINC653 standard. The method includes:

[0018] Step 10: Configure the shared I / O space, which is used for space mapping of the logbook;

[0019] In practical applications, a shared I / O space can be configured using the configuration tools provided by the ARINC653 standard partitioned operating system.

[0020] like Figure 2 As shown, the shared I / O space includes virtual addresses;

[0021] Step 20: Configure at least one logbook, which resides in the configured shared I / O space; the logbook includes a name.

[0022] It should be noted that the configuration tools provided by the ARINC653 standard partitioned operating system can configure multiple logbooks, each belonging to the configured shared I / O space.

[0023] like Figure 1 As shown,

[0024] Step 30: Generate configuration data;

[0025] Step 30 specifically includes:

[0026] Step 31: The operating system configuration tool will check whether each parameter is valid according to the parameter range of each configuration item, and whether the shared IO space meets the space requirements of all logbooks;

[0027] Step 32: The operating system configuration tool will divide the logbook storage area on the shared I / O space according to the number of logbook messages and the maximum message length configured by the user in the configuration record, and record the starting address of each logbook in the generated configuration data.

[0028] Step 40: Initialize the logbook;

[0029] Step 50: Create a logbook based on the logbook name, maximum number of messages, maximum message length, and configuration data. The output parameters of the logbook include the logbook ID.

[0030] Specifically, the application calls the APEX interface to create a logbook.

[0031] Step 60: Perform read and write operations on the logbook according to the logbook ID.

[0032] Example 2

[0033] This application provides a method for configuring and implementing a logger based on the ARINC653 standard, the method including:

[0034] 1) Configure shared I / O, which is used for the logbook;

[0035] Configure a shared I / O space named LogBookSharedIO using the configuration tool provided by the ARINC653 standard partitioned operating system.

[0036] 2) Configure multiple logbooks in the configuration tool provided by the ARINC653 standard partition operating system. Taking three as an example, their names are LogBookA, LogBookB and LogBookC. LogBookB belongs to partition 2, and LogBookA and LogBookC belong to partition 1. All three logbooks belong to the shared I / O space XX.

[0037] 3) The operating system configuration tool will check the validity of each parameter and whether the shared I / O space meets the space requirements of all logbooks based on the parameter range of each configuration item;

[0038] 4) The operating system configuration tool will divide the storage area of ​​the logbook on the shared I / O space according to the number of logbook messages and the maximum message length configured by the user in the configuration record, and record the starting address of each logbook in the generated configuration data;

[0039] 5) During the initialization of the logbook, an announcement buffer is created, and the logbook process is created and started;

[0040] 6) The application calls the APEX interface to create a logbook. The name, maximum number of messages, and maximum message length of the created logbook must be consistent with those configured in the configuration record.

[0041] 7) Taking LogBookA as an example, this illustrates the process of an application writing data to the logbook. Partition 1 can obtain configuration data from LogBookA and LogBookC. If partition 1 tries to send a message to LogBookB, it will fail.

[0042] 8) Combine the message status with the data to be written into a specific structure and send it to the buffer corresponding to LogBookA. Then send a message to the public buffer. The message content is the log record ID of the message to be written.

[0043] 9) The log recording process receives messages from the common buffer, obtains the buffer ID of LogBookA in RAM from the received messages, and uses this ID to receive information from the corresponding buffer and writes the information to message number 0 of the log recorder.

[0044] In summary, this invention belongs to the technical field of computer system software. This method implements a logbook function compliant with the ARINC 653 standard. This method provides a low-level data transmission mechanism for the logbook function compliant with the ARINC 653 standard, adding a logbook process and a shared buffer design to achieve data transfer from RAM to the storage medium. This method adds a logbook configuration to the shared I / O configuration, mapping non-volatile memory through shared I / O to enable partitioned applications to record data on non-volatile memory. This invention implements a logbook function for storing and recording messages, which can still be read after module power failure or partition restart, facilitating user operation.

Claims

1. A method for configuring and implementing a logbook based on the ARINC653 standard, characterized in that, The method includes: Configure a shared I / O space, which is used for space mapping of the logbook. The shared I / O space includes virtual addresses. Configure at least one logbook, which resides in the configured shared I / O space, and the logbook includes a name. Generate configuration data; Logbook initialization; A logbook is created based on the logbook's name, maximum number of messages, maximum message length, and configuration data. The output parameters of the logbook include the logbook ID. Based on the logbook ID, perform read and write operations on the logbook; The configuration of the shared I / O space specifically includes: configuring a shared I / O space in the configuration tool provided by the ARINC653 standard partitioned operating system; The configuration data generation process includes: the operating system configuration tool checking the validity of each parameter based on the parameter range of each configuration item, and whether the shared I / O space meets the space requirements of all logbooks; the operating system configuration tool dividing the logbook storage area on the shared I / O space according to the number of logbook messages and the maximum message length configured by the user in the configuration record, and recording the starting address of each logbook in the generated configuration data.

2. The log recording configuration and implementation method according to claim 1, characterized in that, Creating a logbook specifically includes: The application calls the APEX interface to create a logbook.

Images