KOSMOS status lists IMA and TSP compatibility and software partitions
- Verified KOSMOS status entries record compatibility with IMA and TSP.
- The entries describe software partitions for command-control, memory, anomalies, and shared input/output peripherals.
- KOSMOS is listed at niveau B ECSS with boot software qualified on a Zynq target.
- Other entries cover PUS communication, telecommand authentication and encryption, and onboard procedures.
- The status data includes development items such as LVROOT, APPDK, APPDKPUS, and CCDK.
What happened
Verified status entries describe KOSMOS objectives, compatibility with IMA and TSP, and software partitions. The entries also record niveau B ECSS and boot software qualified on a Zynq target.
What we know
KOSMOS is listed with always active objectives, compatibility with IMA and TSP, niveau B ECSS, and qualified boot software on a Zynq target.
IMA has been implemented on Airbus and Boeing aircraft since the A380 and B777, and TSP is listed as Time & Space Partitionning.
Status entries describe software partitions for shared input/output peripherals, memory, anomalies, and command-control.
Other entries cover a generic PUS communication protocol library, authentication and encryption of telecommands, and implementation of onboard procedures.
Example and development items include LVROOT, APPDK, APPDKPUS with the PUS library, and CCDK for the command-control partition.
Why it matters
The verified entries describe a partitioned software stack covering command-control, memory, anomalies, shared input/output peripherals, authentication, telecommand encryption, onboard procedures, and PUS communication.
For readers tracking the lunar industry, the facts provide concrete technical markers: KOSMOS compatibility with IMA and TSP, niveau B ECSS, qualified boot software on a Zynq target, and IMA's aircraft implementation record.
Sources
Written by AI systems from the sources above and checked automatically; no personal byline. How this site works