A high-reliability on-orbit file system deployment method

Abstract

The application discloses a high-reliability on-orbit file system deployment method, compared with the error-prone characteristics of the past on-board file system adopting a double-redundancy structure, the application innovatively divides a NorFlash memory into a NorFlash physical area and a NorFlash file system two parts. The three identical operating system images and basic software are stored in the NorFlash physical area. The NorFlash file system is further divided into a main partition and a redundant partition. The two partitions each store a backup of the basic software in the physical area and various extended function software. In this way, the error is minimized, and the basic operation of the on-board file system is ensured.

Description

Technical Field

[0001] This invention relates to the field of spaceborne computer software technology, and in particular to a method for deploying a highly reliable on-orbit file system. Background Technology

[0002] In recent years, my country's space technology has developed rapidly, and the demand for satellite applications has expanded accordingly. The types and amounts of payload data stored have gradually increased, making data storage and management increasingly difficult. This also places higher demands on file-based management and control, as well as reliable transmission. Therefore, addressing the shortcomings of previous on-orbit file systems, this invention provides an improved deployment method for an on-orbit file system, enhancing its reliability. Summary of the Invention

[0003] To overcome the shortcomings of existing technologies, this invention provides a highly reliable on-orbit file system deployment method, which makes significant improvements to address the common anomalies in previous on-orbit file systems and enhances the reliability of the file system.

[0004] To achieve the aforementioned objectives of the invention, the technical solution adopted to solve its technical problems is as follows:

[0005] A method for deploying a highly reliable on-orbit file system includes the following steps:

[0006] Step S1: The NorFlash memory is divided into two main parts: the NorFlash physical area and the NorFlash file system;

[0007] Step S2: The NorFlash physical area stores the operating system image and other basic software that can ensure the basic operation of the satellite. The contents stored in the NorFlash physical area constitute the minimum system to ensure the operation of the satellite.

[0008] Step S3: The operating system image and other basic software are each stored in three copies in the NorFlash physical area;

[0009] Step S4: When storing all data in the NorFlash physical area, the CRC value and length information written during the hardening process are stored in the data header, which occupies a total of 8 bytes;

[0010] Step S5: The NorFlash file system is divided into two partitions: a primary partition and a redundant partition. The redundant partition is a backup of the primary partition. The two partitions contain the same content. In addition, the basic software stored in the NorFlash physical area is also stored in the primary partition and the redundant partition, which serves as a backup. Furthermore, various extended function software also need to be stored in the primary partition and the redundant partition to help the satellite work better.

[0011] Step S6: The program stored in the NorFlash file system is compiled dynamically, and each application needs to generate an MD5 checksum after loading to verify the integrity of the file.

[0012] Furthermore, the NorFlah memory is managed in sectors, with each sector being 64KB in size.

[0013] Furthermore, the applications stored in the NorFlah physical region are generated using a static compilation method and do not depend on the corresponding dynamic libraries at runtime.

[0014] Furthermore, when the NorFlash physical area is loaded at startup, the data is read according to the length information stored in its data header.

[0015] Furthermore, during the verification of data in the NorFlash physical area, the correctness of the stored data is determined by comparing the real-time calculated CRC value with the CRC value stored in the data header.

[0016] Furthermore, the operating system image is stored only in the NorFlash physical area, with three copies stored. During the hardening process, the three copies are hardened with the same data.

[0017] Furthermore, the NorFlash file system uses dynamic compilation to generate target code, and its runtime depends on the corresponding dynamic library.

[0018] By employing the above technical solutions, this invention has the following advantages and positive effects compared with the prior art:

[0019] This invention discloses a highly reliable on-orbit file system deployment method. Compared to the error-prone dual-redundancy structure of past on-board file systems, this invention innovatively divides the NorFlash memory into two main parts: a NorFlash physical area and a NorFlash file system. The NorFlash physical area stores three identical copies of the operating system image and basic software. The NorFlash file system is further divided into a primary partition and a redundant partition. Each partition stores a backup of the basic software from the physical area, along with various other extended functional software. This minimizes errors and ensures the basic operation of the on-board file system. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0021] Figure 1 This is a block diagram illustrating the principle of the present invention;

[0022] Figure 2 This is a schematic diagram illustrating the implementation steps of the present invention;

[0023] Figure 3 This is a schematic diagram of each area of ​​the NorFlash memory in the embodiment;

[0024] Figure 4 This is a schematic diagram of the implementation steps in the example. Detailed Implementation

[0025] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0026] Traditional on-orbit file systems typically employ a dual-redundancy design during deployment, storing two identical versions of the program: a factory version and a version used in actual operation. When the actual operation version encounters an error, a cold boot is performed by swapping the filenames of the factory version and the currently used version to revert to the fixed factory version. This file system modifies the content stored on the NorFlash physical area during use, thus resulting in relatively low reliability.

[0027] To address the aforementioned shortcomings, this invention makes certain changes to the partitioning and storage content of the NorFlash memory. For example... Figure 1 and 2 As shown, this embodiment discloses a method for deploying a highly reliable on-orbit file system, including the following steps:

[0028] Step S1: The NorFlash memory is divided into two main parts: the NorFlash physical area and the NorFlash file system;

[0029] Step S2: The NorFlash physical area stores the operating system image and other basic software that can ensure the basic operation of the satellite. The contents stored in the NorFlash physical area constitute the minimum system to ensure the operation of the satellite.

[0030] Step S3: The operating system image and other basic software are each stored in three copies in the NorFlash physical area;

[0031] Step S4: When storing all data in the NorFlash physical area, the CRC value and length information written during the hardening process are stored in the data header, which occupies a total of 8 bytes;

[0032] Step S5: The NorFlash file system is divided into two partitions: a primary partition and a redundant partition. The redundant partition is a backup of the primary partition. The two partitions contain the same content. In addition, the basic software stored in the NorFlash physical area is also stored in the primary partition and the redundant partition, which serves as a backup. Furthermore, various extended function software also need to be stored in the primary partition and the redundant partition to help the satellite work better.

[0033] Step S6: The program stored in the NorFlash file system is compiled dynamically, and each application needs to generate an MD5 checksum after loading to verify the integrity of the file.

[0034] Furthermore, the NorFlah memory is managed in sectors, with each sector being 64KB in size.

[0035] Furthermore, the applications stored in the NorFlah physical region are generated using a static compilation method and do not depend on the corresponding dynamic libraries at runtime.

[0036] Furthermore, when the NorFlash physical area is loaded at startup, the data is read according to the length information stored in its data header.

[0037] Furthermore, during the verification of data in the NorFlash physical area, the correctness of the stored data is determined by comparing the real-time calculated CRC value with the CRC value stored in the data header.

[0038] Furthermore, the operating system image is stored only in the NorFlash physical area, with three copies stored. During the hardening process, the three copies are hardened with the same data.

[0039] Furthermore, the NorFlash file system uses dynamic compilation to generate target code, and its runtime depends on the corresponding dynamic library.

[0040] Example:

[0041] Please refer to the attached document. Figure 3 and 4This invention provides a method for deploying a highly reliable on-orbit file system, offering a complete space partitioning method based on NorFlash memory, including the following steps:

[0042] Step B1: The NorFlash memory is divided into two main parts: the NorFlash physical area and the NorFlash file system;

[0043] Step B2: The NorFlash physical area stores the operating system image, integrated electronic software, management software, and attitude and orbit control software, respectively. The system composed of these software components is called the minimum system, and its purpose is to ensure the satellite's operational status.

[0044] Step B3: The operating system image is stored only in the NorFlash physical area, with three copies stored. During the hardening process, all three copies are hardened with the same data. In this embodiment, the operating system image size is approximately 1024KB, while each sector of the NorFlash memory is 64KB. Therefore, each operating system image occupies 16 blocks. In this embodiment, the offset addresses of the three operating system images are set as follows: 0x0, 0x6D0000, and 0xDA0000.

[0045] Step B4: The management software, attitude and orbit control software, and integrated electronic software are generated using static compilation and do not depend on corresponding dynamic libraries at runtime. When solidified into the NorFlash physical area, they are also solidified as three identical copies. In this embodiment, the management software is approximately 256KB in size, thus occupying 4 blocks. Its offset addresses are set to: 0x100000, 0x7D0000, and 0xEA0000. The integrated electronic software is approximately 512KB in size, occupying 8 blocks. Its offset addresses are set to: 0x140000, 0x810000, and 0xEE0000. The attitude and orbit control software is approximately 448KB in size, occupying 7 blocks. Its offset addresses are set to: 0x1C0000, 0x890000, and 0xF60000.

[0046] Step B5: When storing all data in the NorFlash physical area, the header of the data contains the CRC value and length information written during the hardening process, totaling 8 bytes. The purpose is to: read the data based on the written length during startup loading; and during later verification, compare the real-time calculated CRC with the stored CRC value to determine the correctness of the stored data.

[0047] Step B6: The NorFlash file system is divided into two partitions: a primary partition and a redundant partition. The redundant partition is a backup of the primary partition, and the two partitions store identical content. In this embodiment, the NorFlash file system stores management software, integrated electronic software, attitude and orbit control software, mission planning software, and various library files. The management software, integrated electronic software, and attitude and orbit control software are backups of the physical partition files described in this embodiment. The mission planning software, used to provide onboard mission planning functions, is subject to updates and is therefore stored in the NorFlash file system. Various library files provide support for the operation of the onboard software.

[0048] Step B7: The NorFlash file system dynamically compiles and generates all application and library files. One copy is stored in both the primary and redundant partitions. After each application and dynamic library is loaded, an MD5 checksum needs to be generated to verify file integrity.

[0049] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for deploying a highly reliable on-orbit file system, characterized in that, Includes the following steps: Step S1: The NorFlash memory is divided into two main parts: the NorFlash physical area and the NorFlash file system; Step S2: The NorFlash physical area stores the operating system image and other basic software that can ensure the basic operation of the satellite. The contents stored in the NorFlash physical area constitute the minimum system to ensure the operation of the satellite. Step S3: The operating system image and other basic software are each stored in three copies in the NorFlash physical area; Step S4: When storing all data in the NorFlash physical area, the CRC value and length information written during the hardening process are stored in the data header, which occupies a total of 8 bytes; Step S5: The NorFlash file system is divided into two partitions: a primary partition and a redundant partition. The redundant partition is a backup of the primary partition. The two partitions contain the same content. In addition, the basic software stored in the NorFlash physical area is also stored in the primary partition and the redundant partition, which serves as a backup. Furthermore, various extended function software also need to be stored in the primary partition and the redundant partition to help the satellite work better. Step S6: The program stored in the NorFlash file system is compiled dynamically, and each application needs to generate an MD5 checksum after loading to verify the integrity of the file.

2. The deployment method of a highly reliable on-orbit file system according to claim 1, characterized in that, The NorFlah memory is managed in sectors, with each sector being 64KB in size.

3. The deployment method of a highly reliable on-orbit file system according to claim 1, characterized in that, The applications stored in the NorFlah physical region are generated using static compilation and do not depend on corresponding dynamic libraries at runtime.

4. The deployment method of a highly reliable on-orbit file system according to claim 1, characterized in that, When the NorFlash physical area is loaded at startup, the data is read according to the length information stored in its data header.

5. The deployment method of a highly reliable on-orbit file system according to claim 1, characterized in that, During the verification process, the data in the NorFlash physical area is compared with the CRC value stored in the data header based on the real-time calculated CRC value to determine the correctness of the stored data.

6. The deployment method of a highly reliable on-orbit file system according to claim 1, characterized in that, The operating system image is stored only in the NorFlash physical area, with three copies stored. During the hardening process, all three copies are hardened with the same data.

7. The deployment method of a highly reliable on-orbit file system according to claim 1, characterized in that, The NorFlash file system uses dynamic compilation to generate target code, and it depends on the corresponding dynamic library at runtime.

Images