The framework code.
Go to file
2021-03-04 16:48:21 +01:00
action success flag not explicitely expected for actions 2021-03-03 15:13:03 +01:00
container applied to cmakelists file 2021-01-28 11:58:18 +01:00
contrib/sgp4 renormalized files 2020-09-18 13:15:14 +02:00
controller fixed order 2021-03-03 23:49:27 +01:00
coordinates msvc tests 2020-12-20 15:32:03 +01:00
datalinklayer correct preprocessor define now used 2021-01-03 14:16:52 +01:00
datapool renamed guard class 2021-03-04 16:38:35 +01:00
datapoollocal small form stuff 2021-03-04 16:36:34 +01:00
defaultcfg Squashed commit of the following: 2021-01-13 11:53:34 +01:00
devicehandlers success flag not explicitely expected for actions 2021-03-03 15:13:03 +01:00
doc doxyfile update 2021-01-25 11:37:19 +01:00
events less confusing code 2021-01-19 14:37:52 +01:00
fdir type and name change for HasParametersIF 2021-01-29 22:45:53 +01:00
globalfunctions set deser test complete 2021-02-28 16:34:11 +01:00
health correct preprocessor define now used 2021-01-03 14:16:52 +01:00
housekeeping better documentation 2021-02-27 13:06:55 +01:00
internalError improved internal interface 2021-01-14 11:50:33 +01:00
ipc Merge branch 'mueller/followup-pullrequest' of https://egit.irs.uni-stuttgart.de/KSat/fsfw into mueller/followup-pullrequest 2021-03-02 14:59:03 +01:00
logo Added the new logos, colors are WIP at the moment 2020-11-30 18:30:58 +01:00
memory reordered returnvalues 2021-03-02 12:36:13 +01:00
modes Merge branch 'development' into mueller/cmake-init 2020-12-09 10:07:22 +01:00
monitoring type and name change for HasParametersIF 2021-01-29 22:45:53 +01:00
objectmanager added srv20 written by J. Gerhards 2021-01-30 20:29:23 +01:00
osal updated clock module 2021-03-03 17:13:37 +01:00
parameters srv20 improvements and bugfixes 2021-01-31 20:53:25 +01:00
power type and name change for HasParametersIF 2021-01-29 22:45:53 +01:00
pus small tweak 2021-02-03 22:18:00 +01:00
returnvalues updated HasFileSystemIF 2021-03-02 01:04:51 +01:00
rmap clened up a bit 2020-12-13 22:12:57 +01:00
serialize missing include added 2021-01-03 16:48:18 +01:00
serviceinterface cyan instead of magenta for debug now 2021-01-16 14:24:59 +01:00
storagemanager more renaming 2021-01-19 15:06:21 +01:00
subsystem correct preprocessor define now used 2021-01-03 14:16:52 +01:00
tasks added new static function to print missed deadline 2021-02-22 18:43:09 +01:00
tcdistribution correct preprocessor define now used 2021-01-03 14:16:52 +01:00
thermal type and name change for HasParametersIF 2021-01-29 22:45:53 +01:00
timemanager whitespaces instead of tabs 2021-03-04 16:44:17 +01:00
tmstorage updated tm storage 2020-12-22 15:58:52 +01:00
tmtcpacket correct preprocessor define now used 2021-01-03 14:16:52 +01:00
tmtcservices Merge remote-tracking branch 'origin/development' into mueller/fsfw-update-2 2021-02-09 14:44:19 +01:00
unittest renamed guard class 2021-03-04 16:38:35 +01:00
.gitignore Added .gitignore for eclipse project files 2018-07-12 17:13:04 +02:00
.gitmodules unittest now contained directly 2020-10-20 17:11:23 +02:00
CHANGELOG removing whitespaces 2021-03-04 16:48:21 +01:00
CMakeLists.txt cmake lists update 2021-01-24 21:40:44 +01:00
fsfw.mk Squashed commit of the following: 2021-01-13 11:53:34 +01:00
FSFWVersion.h Version number 2020-11-13 15:09:00 +01:00
LICENSE updating code from Flying Laptop 2018-07-12 16:29:32 +02:00
NOTICE Added the new logos, colors are WIP at the moment 2020-11-30 18:30:58 +01:00
README.md doc update 2021-01-13 11:39:19 +01:00

FSFW Logo

Flight Software Framework (FSFW)

The Flight Software Framework is a C++ Object Oriented Framework for unmanned, automated systems like Satellites.

The initial version of the Flight Software Framework was developed during the Flying Laptop Project by the University of Stuttgart in cooperation with Airbus Defence and Space GmbH.

Quick facts

The framework is designed for systems, which communicate with external devices, perform control loops, receive telecommands and send telemetry, and need to maintain a high level of availability. Therefore, a mode and health system provides control over the states of the software and the controlled devices. In addition, a simple mechanism of event based fault detection, isolation and recovery is implemented as well.

The FSFW provides abstraction layers for operating systems to provide a uniform operating system abstraction layer (OSAL). Some components of this OSAL are required internally by the FSFW but is also very useful for developers to implement the same application logic on different operating systems with a uniform interface.

Currently, the FSFW provides the following OSALs:

  • Linux
  • Host
  • FreeRTOS
  • RTEMS

The recommended hardware is a microprocessor with more than 1 MB of RAM and 1 MB of non-volatile Memory. For reference, current applications use a Cobham Gaisler UT699 (LEON3FT), a ISISPACE IOBC or a Zynq-7020 SoC. The fsfw was also successfully run on the STM32H743ZI-Nucleo board and on a Raspberry Pi and is currently running on the active satellite mission Flying Laptop.

Getting started

The FSFW example provides a good starting point and a demo to see the FSFW capabilities and build it with the Make or the CMake build system. It is recommended to evaluate the FSFW by building and playing around with the demo application.

Generally, the FSFW is included in a project by compiling the FSFW sources and providing a configuration folder and adding it to the include path. There are some functions like printChar which are different depending on the target architecture and need to be implemented by the mission developer.

A template configuration folder was provided and can be copied into the project root to have a starting point. The configuration section provides more specific information about the possible options.

Index

1. High-level overview
2. Core components
3. OSAL overview
4. PUS services
5. Device Handler overview
6. Controller overview
7. Local Data Pools