Method for maintaining embedded software module of spacecraft

Abstract

The invention provides a method for maintaining an embedded software module of a spacecraft. The method comprises the following steps: (1) designing and realizing flight software of the spacecraft; (2) designing and realizing a modified module or function; (3) completing the maintenance of the embedded software module or function, exactly, establishing a mapping table for storing entry addresses of all modules (or functions) of the flight software, and setting an address table as a default state when the software is solidified; storing executing codes of the modified modules (or functions) into a memory space when the modules (or functions) need to be modified in the future; and simultaneously modifying a address mapping table, and changing the orientation of the modules (or functions) which is not modified to the entrance of the modified modules (or functions), thus the change of the invoke relationship can be realized and the purpose of modifying or maintaining any module (or function) can be achieved.

Description

technical field [0001] The invention discloses an embedded software module maintenance method, relates to the field of space electronics, and in particular relates to the general design of a spacecraft, an embedded computer system of a spacecraft and a method for processing a space information processing system. Background technique [0002] With the development of computer technology and software technology, real-time embedded systems with high autonomy and flexibility have been widely used in domestic spacecraft. These embedded systems often have high requirements for long-running autonomy and reliability. Therefore, there is an urgent requirement for the system's on-orbit maintenance capability, which is mainly reflected in two aspects: (1) During the long-term operation of the software, certain design defects may be exposed, or those that were not found and eliminated during the test Program design errors require timely correction and improvement; (2) In order to adapt ...

AI Technical Summary

Problems solved by technology

[0007] The above three methods all have specific use occasions. From the perspective of maintenance, they all have certain limitations. The first method can only change the parameters, but cannot change the logical structure of the software. When an error is found in the software , the modification cannot be completed; methods (2) and (3) maintain a relatively coarse granularity, and if an error occurs in a certain module (or function), a more complicated process needs to be implemented, especially the method (3) ) method requires a large amount of data to be transmitted uplink and takes a long time

Images