Satellite integrated electronic subsystem software setting recovery method and system

Abstract

The invention provides a satellite integrated electronic subsystem software setting recovery method and system. The method comprises the following steps: S1, setting a software recovery function module of a satellite integrated electronic subsystem; s2, realizing backup management of system setting parameters based on a backup recovery operation process unit; and S3, based on the backup recovery operation process unit and the backup information data structure unit, setting backup content classification and trigger rules of system setting parameters. According to the invention, the comprehensive electronic subsystem software is set to restore the overall framework for the system setting of the MRAM, and the corresponding synchronization head and check bit are set, so that important system parameters on the satellite can be backed up in time. When a single machine triggers reset operation in satellite on-orbit service, system setting and parameters such as an initial value and a threshold value of comprehensive service can be recovered in time, and the robustness of comprehensive electronic subsystem software and the anti-interference recovery capability of a satellite are greatly improved.

Description

Technical Field

[0001] The present invention relates to the field of spacecraft technology, and in particular to a method and system for restoring software settings of a satellite integrated electronic subsystem based on MRAM. Background Art

[0002] In the current aerospace sector, the need for storage and backup of critical information is increasing. Satellite operations involve a vast amount of critical data and parameters, requiring reliable storage to ensure system stability and mission execution. In this context, various types of random access memory (RAM) are widely used in satellites.

[0003] Common static random access memory (SRAM) can store internal data without the need for a refresh circuit, but it has the disadvantages of low integration and higher power consumption than dynamic random access memory (DRAM). DRAM, as an internal memory that can directly exchange data with the CPU, has fast read and write speeds, but requires periodic charging and regular refresh. In comparison, magnetoresistive random access memory (MRAM) has significant advantages. It has fast read and write speeds, enabling low-latency data access; it has a long erase and write life and can withstand a large number of read and write operations without damage or failure; and as a non-volatile memory, it avoids the trouble of traditional memory requiring data backup and recovery during power outages. Based on these characteristics, the use of MRAM to back up important information in the satellite integrated electronic subsystem software has become the primary choice.

[0004] Satellite payload data is rich and diverse, encompassing conventional telemetry, memory-downloaded telemetry, returner telemetry, image telemetry, and time-lapse telemetry. This data transmission requires extremely high timeliness, making it essential to preprocess the data, set priorities, and properly partition the storage area. This not only allows for rapid retrieval of high-priority payload data, prioritizing the downlink of critical data in emergencies, but also maximizes cache utilization, effectively conserving onboard storage and transmission resources.

[0005] The integrated electronic subsystem software requires a significant amount of critical information to be backed up, including energy security management threshold parameters, thermal control threshold information, integrated service packages, and their associated pre-stored configuration parameters. These system parameters not only play a decisive role in the proper operation of the integrated electronic subsystem but also profoundly impact the operation of the thermal control subsystem and payload services. Therefore, timely backing up this crucial data is crucial. If a single unit in the integrated electronic subsystem triggers a power-off reset, this data can be immediately restored, ensuring the stable operation of the satellite's integrated electronic subsystem and other subsystems, enhancing the robustness of the integrated electronic subsystem software and the satellite's anti-interference resilience.

[0006] A search of patent documents revealed an invention patent with publication number CN116192809B, which discloses a dual-machine cold standby, highly reliable satellite service and attitude control interaction architecture system. This architecture system consists of a comprehensive electronic hardware framework and a satellite service and attitude control interaction interface. The comprehensive electronic hardware framework includes two independent but functionally identical machines, A and B, which form a dual-machine cold standby system. The satellite service and attitude control interaction interface includes substructures and corresponding interface functions that implement specific functions. This invention comprehensively considers hardware redundancy and the requirements of satellite service and attitude control interaction, and implements an integrated hardware and software design for the dual-machine cold standby onboard computer. This design not only defines the onboard computer hardware framework but also specifies the data structures and interface functions for various specific interaction requirements. This system enables highly reliable autonomous recovery of the active machine during an abnormal reset, as well as highly reliable switching recovery of the other machine during a dual-machine cold standby switchover. This ensures continuous and stable system operation in the event of various on-orbit anomalies. This patent focuses on the dual-machine cold standby architecture and the interaction design between satellite services and attitude control. It does not involve the specific processes and rules for data backup and recovery in terms of the systematic nature of software setting recovery, parameter backup management, and classification triggering rules.

[0007] In summary, in response to the above-mentioned problems of the existing technology, researching a method and system for recovering software settings of a satellite integrated electronic subsystem based on MRAM has become a key task that needs to be solved urgently. Summary of the Invention

[0008] In view of the defects in the prior art, the purpose of the present invention is to provide a method and system for recovering software settings of a satellite integrated electronic subsystem based on MRAM.

[0009] According to the present invention, a method for restoring software settings of a satellite integrated electronic subsystem based on MRAM includes the following steps:

[0010] Step S1, setting a software recovery function module of the satellite integrated electronic subsystem, the software recovery function module includes a backup and recovery operation process unit and a backup information data structure unit, the backup and recovery operation process unit is used to back up data in real time when the satellite integrated electronic subsystem is operating normally, and restore data after reset; the backup information data structure unit is used to define the storage format of system setting parameters in MRAM and the classification and trigger conditions of the stored system setting parameters;

[0011] Step S2, based on the backup and recovery operation process unit, realize the backup management of system setting parameters;

[0012] Step S3: Based on the backup and recovery operation process unit and the backup information data structure unit, the backup content classification and triggering rules of the system setting parameters are set.

[0013] Preferably, in step S1 , a dedicated storage area is allocated in the MRAM for storing system setting parameters.

[0014] Preferably, step S2 includes the following sub-steps:

[0015] Step S2.1: In the dedicated storage area, the backup management unit allocates an independent data block for each system setting parameter. The backup management unit performs registration, writing, reading, and destruction operations through the interface provided by the backup and recovery operation unit to manage the storage and access of the system setting parameters.

[0016] Step S2.2, adding a synchronization header and a checksum to the system setting parameters to be stored, generating a data block and storing it in the MRAM;

[0017] Step S2.3, performing a two-out-of-three vote and verification on the data stored in the MRAM. If the verification passes, the system configuration parameters stored in the MRAM are loaded; otherwise, the default initial parameter values ​​are loaded.

[0018] Preferably, in step S2.1, the registration operation allocates an independent data block in the MRAM for the new system setting parameters; the write operation and the read operation are based on virtual address mapping to ensure that the system setting parameters only access their own data blocks; the destruction operation destroys the MRAM high-end area access handle by clearing the MRAM application space.

[0019] Preferably, in step S2.2, the synchronization header is a fixed value EB90, and the checksum is an XOR check value of the system setting parameters to be stored.

[0020] Preferably, step S3 includes the following sub-steps:

[0021] Step S3.1: Through the backup and recovery operation process unit, based on data update characteristics, the system configuration parameters are divided into periodic backup parameters and event-triggered backup parameters. The periodic backup parameters include thermal control parameters, telemetry parameters, and safety threshold parameters. The event-triggered backup parameters include system status parameters and service configuration parameters. The system status parameters include the startup status of the satellite integrated electronic subsystem software. The service configuration parameters include the integrated service package and pre-stored configuration parameter packages. The safety threshold parameters include the energy safety threshold, the load bus current threshold, and the thermal control threshold table.

[0022] Step S3.2, setting trigger conditions for each type of parameter through the backup and recovery operation process unit;

[0023] In step S3.3, various parameters and trigger conditions are stored in the backup information data structure unit for the backup and recovery operation process unit to call and perform the backup or recovery operation.

[0024] Preferably, in step S3.1, the integrated service package includes task timing parameters, and the task timing parameters include task resolution time, task duration and task mode.

[0025] Preferably, step S3.2 includes:

[0026] The trigger condition for writing periodic backup parameters is the arrival of the timing cycle, and the trigger condition for reading is system initialization;

[0027] The writing trigger condition for event-triggered backup parameters is parameter value change or ground instruction; the writing trigger condition for safety threshold parameters is threshold change, and the reading trigger condition for safety threshold parameters is system initialization; the reading trigger condition for the startup status is system initialization, and the reading trigger condition for the comprehensive business package and pre-stored configuration parameter package is business function call.

[0028] Preferably, the backup and recovery operation process unit is also used to: when reading the safety threshold parameter fails, write the preset default parameter value to the backup information data structure unit; when receiving a ground write instruction, overwrite the current storage value in the backup information data structure unit.

[0029] The present invention also provides a satellite integrated electronic subsystem software setting and recovery system based on MRAM, comprising:

[0030] Module M1, setting the software recovery function module of the satellite integrated electronic subsystem, the software recovery function module includes a backup and recovery operation process unit and a backup information data structure unit. The backup and recovery operation process unit is used to back up data in real time when the satellite integrated electronic subsystem is operating normally and restore data after reset; the backup information data structure unit is used to define the storage format of the system setting parameters in the MRAM and the classification and trigger conditions of the stored system setting parameters;

[0031] Module M2, based on the backup and recovery operation process unit, realizes the backup management of system setting parameters;

[0032] Module M3 sets the backup content classification and triggering rules of the system setting parameters based on the backup and recovery operation process unit and the backup information data structure unit.

[0033] Compared with the prior art, the present invention has the following beneficial effects:

[0034] This invention implements a comprehensive electronic subsystem software framework for MRAM system settings and restores the overall framework, along with corresponding synchronization headers and parity bits, enabling timely backup of important satellite system parameters. When a single satellite triggers a reset during on-orbit operations, system settings and integrated service parameters, such as initial values ​​and thresholds, are promptly restored, significantly improving the robustness of the comprehensive electronic subsystem software and the satellite's anti-interference recovery capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Other features, objects and advantages of the present invention will become more apparent upon reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0036] Figure 1 This is a diagram showing the overall framework for restoring the MRAM system settings in an embodiment of the present invention;

[0037] Figure 2 A diagram illustrating a method for implementing system backup settings in an embodiment of the present invention;

[0038] Figure 3 A schematic diagram of system backup settings in an embodiment of the present invention. DETAILED DESCRIPTION

[0039] The present invention will be described in detail below with reference to specific embodiments. The following examples will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those skilled in the art, several changes and improvements can be made without departing from the scope of the present invention. These all fall within the scope of protection of the present invention.

[0040] The present invention discloses a method and system for restoring satellite integrated electronic subsystem software settings based on MRAM. This method, by configuring the integrated electronic subsystem software to restore the overall MRAM system settings framework and setting corresponding synchronization headers and parity bits, enables timely backup of important satellite system parameters. When a single unit triggers a reset operation during on-orbit satellite operations, system settings and integrated service parameters, such as initial values ​​and thresholds, can be promptly restored, significantly improving the robustness of the integrated electronic subsystem software and the satellite's anti-interference recovery capabilities.

[0041] Example 1:

[0042] Figure 1 This is a diagram of the overall framework for restoring the MRAM system settings in an embodiment of the present invention.

[0043] like Figure 1 As shown, this embodiment provides a method for restoring software settings of a satellite integrated electronic subsystem based on MRAM, comprising the following steps:

[0044] Step S1, setting a software recovery function module of the satellite integrated electronic subsystem. Based on the non-volatile storage characteristics of MRAM, the software recovery function module includes a backup and recovery operation process unit and a backup information data structure unit. The backup and recovery operation process unit is used to back up data in real time when the satellite integrated electronic subsystem is operating normally and restore data after reset; the backup information data structure unit is used to define the storage format of system setting parameters in MRAM and the classification and trigger conditions of the stored system setting parameters.

[0045] In this embodiment, MRAM is selected to perform real-time backup of important information because it does not require a backup capacitor and can still store data before power failure after power failure.

[0046] Specifically, a dedicated storage area is allocated in the MRAM for storing system setting parameters.

[0047] Step S2: Based on the backup and recovery operation process unit, backup management of system setting parameters is implemented.

[0048] Figure 2 A diagram illustrating a method for implementing system backup settings in an embodiment of the present invention.

[0049] like Figure 2 As shown, step S2 includes the following sub-steps:

[0050] Step S2.1, in the dedicated storage area, an independent data block is allocated for each system setting parameter through the backup management unit. The backup management unit performs registration, writing, reading and destruction operations through the interface provided by the backup recovery operation unit to manage the storage and access of the system setting parameters.

[0051] In this embodiment, the backup management unit enables independent management of each system setting, ensuring data isolation and scalability. The registration operation allocates a separate data block in MRAM for the new system setting parameter. Write and read operations are based on virtual address mapping, ensuring that the system setting parameter only accesses its own data block. The destruction operation clears the MRAM allocation space and destroys the access handle to the MRAM high-end area.

[0052] In other words, when a new system setting requires backup, a registration process is initiated, and the backup management unit creates a data block for it in the memory space. Read and write processes are initiated using the virtual addresses within each system setting block. The backup management unit maps the virtual addresses to the MRAM space and restricts each system setting from reading or writing outside its own data block.

[0053] Step S2.2: Add a synchronization header and a checksum to the system setting parameters to be stored, generate a data block and store it in the MRAM.

[0054] In this embodiment, in step S2.2, the synchronization header is a fixed value EB90, and the checksum is an XOR check value of the system setting parameters to be stored, so as to ensure the correctness of the information.

[0055] Step S2.3, performing a two-out-of-three vote and verification on the data stored in the MRAM. If the verification passes, the system configuration parameters stored in the MRAM are loaded; otherwise, the default initial parameter values ​​are loaded.

[0056] In other words, the read process consists of two steps: extracting two out of three and verifying. After extracting two out of three from the information stored in the MRAM area, the extracted information is verified. If the verification result is true, the data in the MRAM is used as the system data after the integrated electronic subsystem software is reset. If the verification result is false, the initial default value is used as the system data after the integrated electronic subsystem software is reset.

[0057] Step S3: Based on the backup and recovery operation process unit and the backup information data structure unit, the backup content classification and triggering rules of the system setting parameters are set.

[0058] Figure 3 A schematic diagram of system backup settings in an embodiment of the present invention.

[0059] like Figure 3 As shown, step S3 includes the following sub-steps:

[0060] Step S3.1, through the backup and recovery operation process unit, according to the data update characteristics, the system configuration parameters are divided into periodic backup parameters and event-triggered backup parameters. The periodic backup parameters include thermal control parameters, telemetry parameters and safety threshold parameters. The event-triggered backup parameters include system status parameters and business configuration parameters. The system status parameters include the startup status of the satellite integrated electronic subsystem software. The business configuration parameters include the integrated business package and the pre-stored configuration parameter package. The safety threshold parameters include the energy safety threshold, the load bus current threshold and the thermal control threshold table.

[0061] Furthermore, the integrated service package includes task timing parameters, and the task timing parameters include task resolution time, task duration, and task mode.

[0062] Step S3.2: Setting trigger conditions for each type of parameter through the backup and recovery operation process unit.

[0063] Specifically, step S3.2 includes:

[0064] The trigger condition for writing periodic backup parameters is the arrival of the timing cycle, and the trigger condition for reading is system initialization;

[0065] The writing trigger condition for event-triggered backup parameters is parameter value change or ground instruction; the writing trigger condition for safety threshold parameters is threshold change, and the reading trigger condition for safety threshold parameters is system initialization; the reading trigger condition for the startup status is system initialization, and the reading trigger condition for the comprehensive business package and pre-stored configuration parameter package is business function call.

[0066] Specifically, the startup state of the integrated electronic subsystem software is backed up. This startup state determines the software's initialization behavior. The startup state is written after initialization, when the new software state is determined or when the system is logged on the ground, and read during the initialization process. The integrated electronic subsystem software's comprehensive service package and its associated pre-stored configuration parameter packages are backed up. These system settings do not change during runtime, and the read action is event-driven. Alternatively, the system can be written during login and read during use.

[0067] Furthermore, the backup and recovery operation process unit is also used to: when reading the safety threshold parameter fails, write the preset default parameter value to the backup information data structure unit; when receiving a ground write instruction, overwrite the current storage value in the backup information data structure unit.

[0068] Specifically, the integrated electronic subsystem software's energy safety threshold, load bus current threshold, and thermal control threshold tables are backed up. These system settings do not change autonomously during operation and are frequently used. These tables are written when they change and read during initialization. If the read fails or a write command is sent from the ground, the default values ​​are written.

[0069] In step S3.3, various parameters and trigger conditions are stored in the backup information data structure unit for the backup and recovery operation process unit to call and perform the backup or recovery operation.

[0070] Specifically, if the data changes frequently, the backup data writing process is initiated periodically, otherwise it is initiated only when the data changes; if the data is used frequently, the backup data reading process is initiated at initialization, otherwise it is initiated only when it is used.

[0071] Example 2:

[0072] The present invention also provides a satellite integrated electronic subsystem software setting recovery system based on MRAM. The satellite integrated electronic subsystem software setting recovery system based on MRAM can be implemented by executing the process steps of the satellite integrated electronic subsystem software setting recovery method based on MRAM. That is, those skilled in the art can understand the satellite integrated electronic subsystem software setting recovery method based on MRAM as a preferred implementation of the satellite integrated electronic subsystem software setting recovery system based on MRAM.

[0073] Specifically, the MRAM-based satellite integrated electronic subsystem software setting recovery system includes:

[0074] Module M1, setting the software recovery function module of the satellite integrated electronic subsystem, the software recovery function module includes a backup and recovery operation process unit and a backup information data structure unit. The backup and recovery operation process unit is used to back up data in real time when the satellite integrated electronic subsystem is operating normally and restore data after reset; the backup information data structure unit is used to define the storage format of the system setting parameters in the MRAM and the classification and trigger conditions of the stored system setting parameters;

[0075] Module M2, based on the backup and recovery operation process unit, realizes the backup management of system setting parameters;

[0076] Module M3 sets the backup content classification and triggering rules of the system setting parameters based on the backup and recovery operation process unit and the backup information data structure unit.

[0077] Specifically, module M2 includes the following submodules:

[0078] Module M2.1 allocates an independent data block for each system setting parameter in the dedicated storage area through the backup management unit. The backup management unit performs registration, writing, reading and destruction operations through the interface provided by the backup recovery operation unit to manage the storage and access of system setting parameters.

[0079] In this embodiment, the backup management unit enables independent management of each system setting, ensuring data isolation and scalability. The registration operation allocates a separate data block in MRAM for the new system setting parameter. Write and read operations are based on virtual address mapping, ensuring that the system setting parameter only accesses its own data block. The destruction operation clears the MRAM allocation space and destroys the access handle to the MRAM high-end area.

[0080] In other words, when a new system setting requires backup, a registration process is initiated, and the backup management unit creates a data block for it in the memory space. Read and write processes are initiated using the virtual addresses within each system setting block. The backup management unit maps the virtual addresses to the MRAM space and restricts each system setting from reading or writing outside its own data block.

[0081] Module M2.2 adds a synchronization header and a checksum to the system setting parameters to be stored, generates a data block and stores it in the MRAM.

[0082] In this embodiment, in module M2.2, the synchronization header is a fixed value EB90, and the checksum is an XOR check value of the system setting parameters to be stored to ensure the correctness of the information.

[0083] Module M2.3 performs a two-out-of-three vote and verification on the data stored in the MRAM. If the verification passes, the system configuration parameters stored in the MRAM are loaded; otherwise, the default initial parameter values ​​are loaded.

[0084] In other words, the read process consists of two steps: extracting two out of three and verifying. After extracting two out of three from the information stored in the MRAM area, the extracted information is verified. If the verification result is true, the data in the MRAM is used as the system data after the integrated electronic subsystem software is reset. If the verification result is false, the initial default value is used as the system data after the integrated electronic subsystem software is reset.

[0085] Specifically, module M3 includes the following submodules:

[0086] Module M3.1, through the backup and recovery operation process unit, divides the system configuration parameters into periodic backup parameters and event-triggered backup parameters according to the data update characteristics. The periodic backup parameters include thermal control parameters, telemetry parameters and safety threshold parameters. The event-triggered backup parameters include system status parameters and business configuration parameters. The system status parameters include the startup status of the satellite integrated electronic subsystem software. The business configuration parameters include the integrated business package and the pre-stored configuration parameter package. The safety threshold parameters include the energy safety threshold, the load bus current threshold and the thermal control threshold table.

[0087] Furthermore, the integrated service package includes task timing parameters, and the task timing parameters include task resolution time, task duration, and task mode.

[0088] Module M3.2 sets trigger conditions for each type of parameter through the backup and recovery operation process unit.

[0089] Specifically, module M3.2 includes:

[0090] The trigger condition for writing periodic backup parameters is the arrival of the timing cycle, and the trigger condition for reading is system initialization;

[0091] The writing trigger condition for event-triggered backup parameters is parameter value change or ground instruction; the writing trigger condition for safety threshold parameters is threshold change, and the reading trigger condition for safety threshold parameters is system initialization; the reading trigger condition for the startup status is system initialization, and the reading trigger condition for the comprehensive business package and pre-stored configuration parameter package is business function call.

[0092] Specifically, the startup state of the integrated electronic subsystem software is backed up. This startup state determines the software's initialization behavior. The startup state is written after initialization, when the new software state is determined or when the system is logged on the ground, and read during the initialization process. The integrated electronic subsystem software's comprehensive service package and its associated pre-stored configuration parameter packages are backed up. These system settings do not change during runtime, and the read action is event-driven. Alternatively, the system can be written during login and read during use.

[0093] Furthermore, the backup and recovery operation process unit is also used to: when reading the safety threshold parameter fails, write the preset default parameter value to the backup information data structure unit; when receiving a ground write instruction, overwrite the current storage value in the backup information data structure unit.

[0094] Specifically, the integrated electronic subsystem software's energy safety threshold, load bus current threshold, and thermal control threshold tables are backed up. These system settings do not change autonomously during operation and are frequently used. These tables are written when they change and read during initialization. If the read fails or a write command is sent from the ground, the default values ​​are written.

[0095] Module M3.3 stores various parameters and trigger conditions in the backup information data structure unit for the backup and recovery operation process unit to call and perform backup or recovery operations.

[0096] Specifically, if the data changes frequently, the backup data writing process is initiated periodically, otherwise it is initiated only when the data changes; if the data is used frequently, the backup data reading process is initiated at initialization, otherwise it is initiated only when it is used.

[0097] Those skilled in the art will appreciate that, in addition to implementing the system and its various devices, modules, and units provided by the present invention in purely computer-readable program code, it is entirely possible to implement the same functions of the system and its various devices, modules, and units provided by the present invention in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system and its various devices, modules, and units provided by the present invention can be considered a hardware component, and the devices, modules, and units included therein for implementing various functions can also be considered as structures within the hardware component; the devices, modules, and units for implementing various functions can also be considered as both software modules implementing the method and structures within the hardware component.

[0098] The above describes specific embodiments of the present invention. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art may make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. The embodiments of this application and the features in the embodiments may be combined with each other in any manner unless there is a conflict.

Claims

1. A method for restoring software settings of a satellite integrated electronic subsystem based on MRAM, characterized in that: The steps include: Step S1, setting a software recovery function module of the satellite integrated electronic subsystem, the software recovery function module including a backup and recovery operation process unit and a backup information data structure unit, the backup and recovery operation process unit is used to back up data in real time when the satellite integrated electronic subsystem is operating normally, and to restore data after reset; The backup information data structure unit is used to define the storage format of the system setting parameters in the MRAM and the classification and trigger conditions for storing the system setting parameters; Step S2, based on the backup and recovery operation process unit, realizing the backup management of the system setting parameters; Step S3: Setting the backup content classification and triggering rules of the system setting parameters based on the backup and recovery operation process unit and the backup information data structure unit.

2. The method for restoring software settings of a satellite integrated electronic subsystem based on MRAM according to claim 1, characterized in that: In the step S1 , a dedicated storage area is allocated in the MRAM for storing system setting parameters.

3. The method for restoring software settings of a satellite integrated electronic subsystem based on MRAM according to claim 2, characterized in that: The step S2 includes the following sub-steps: Step S2.1, in the dedicated storage area, allocating an independent data block for each system setting parameter by a backup management unit, and performing registration, writing, reading, and destruction operations by the backup management unit through an interface provided by the backup and recovery operation unit to manage the storage and access of the system setting parameters; Step S2.2, adding a synchronization header and a checksum to the system setting parameters to be stored, generating a data block and storing it in the MRAM; Step S2.3, performing a two-out-of-three vote and verification on the data stored in the MRAM. If the verification passes, the system configuration parameters stored in the MRAM are loaded; otherwise, the default initial parameter values ​​are loaded.

4. The method for restoring software settings of a satellite integrated electronic subsystem based on MRAM according to claim 3, characterized in that: In step S2.1, the registration operation allocates an independent data block in the MRAM for the new system setting parameters; the write operation and the read operation are based on virtual address mapping to ensure that the system setting parameters only access their own data blocks; the destruction operation destroys the MRAM high-end area access handle by clearing the MRAM application space.

5. The method for restoring software settings of a satellite integrated electronic subsystem based on MRAM according to claim 3, characterized in that: In step S2.2, the synchronization header is a fixed value EB90, and the checksum is an XOR check value of the system setting parameters to be stored.

6. The method for restoring software settings of a satellite integrated electronic subsystem based on MRAM according to claim 1, characterized in that: The step S3 includes the following sub-steps: Step S3.1, through the backup and recovery operation process unit, based on data update characteristics, the system configuration parameters are divided into periodic backup parameters and event-triggered backup parameters. The periodic backup parameters include thermal control parameters, telemetry parameters, and safety threshold parameters. The event-triggered backup parameters include system status parameters and service configuration parameters. The system status parameters include the startup status of the satellite integrated electronic subsystem software. The service configuration parameters include an integrated service package and a pre-stored configuration parameter package. The safety threshold parameters include an energy safety threshold, a load bus current threshold, and a thermal control threshold table. Step S3.2, setting trigger conditions for each type of parameter through the backup and recovery operation process unit; Step S3.3: Store various parameters and the trigger conditions in the backup information data structure unit for the backup and restore operation process unit to call and perform the backup or restore operation.

7. The method for restoring software settings of a satellite integrated electronic subsystem based on MRAM according to claim 6, characterized in that: In step S3.1, the integrated service package includes task timing parameters, and the task timing parameters include task resolution time, task duration, and task mode.

8. The method for restoring software settings of a satellite integrated electronic subsystem based on MRAM according to claim 6, characterized in that: The step S3.2 includes: The write trigger condition of the periodic backup parameters is the arrival of the timing cycle, and the read trigger condition is system initialization; The write trigger condition of the event-triggered backup parameter is a parameter value change or a ground instruction; the write trigger condition of the safety threshold parameter is a threshold change, and the read trigger condition of the safety threshold parameter is system initialization; the read trigger condition of the startup status is system initialization, and the read trigger condition of the comprehensive business package and the pre-stored configuration parameter package is a business function call.

9. The method for restoring software settings of a satellite integrated electronic subsystem based on MRAM according to claim 6, characterized in that: The backup and recovery operation process unit is also used to: when reading the safety threshold parameter fails, write the preset default parameter value to the backup information data structure unit; when receiving a ground write instruction, overwrite the current storage value in the backup information data structure unit.

10. A satellite integrated electronic subsystem software setting and recovery system based on MRAM, characterized in that: include: Module M1, setting a software recovery function module of the satellite integrated electronic subsystem, the software recovery function module includes a backup and recovery operation process unit and a backup information data structure unit, the backup and recovery operation process unit is used to back up data in real time when the satellite integrated electronic subsystem is operating normally, and restore data after reset; The backup information data structure unit is used to define the storage format of the system setting parameters in the MRAM and the classification and trigger conditions for storing the system setting parameters; Module M2, based on the backup and recovery operation process unit, realizes the backup management of the system setting parameters; Module M3 sets the backup content classification and triggering rules of the system setting parameters based on the backup and recovery operation process unit and the backup information data structure unit.

Images