The FSFW example for the STM32H7 MCU family, using the FSFW RTEMS OSAL
Go to file
Robin Müller 231de8477d
everything is working
2022-05-29 21:09:25 +02:00
.idea/runConfigurations everything is working 2022-05-29 21:09:25 +02:00
bsp_stm32h7_rtems everything is working 2022-05-29 21:09:25 +02:00
cmake apply afmt 2022-05-27 02:17:19 +02:00
example_common@ebb6a6d6a1 apply afmt 2022-05-27 02:17:19 +02:00
fsfw@55313ee0fc everything is working 2022-05-29 21:09:25 +02:00
generators added all submodules 2021-07-15 17:01:49 +02:00
misc/eclipse updated .cproject file 2021-07-16 14:45:41 +02:00
scripts apply afmt 2022-05-27 02:17:19 +02:00
tmtc updating RTEMS example 2022-05-27 01:46:51 +02:00
.gitignore updating RTEMS example 2022-05-27 01:46:51 +02:00
.gitmodules added RTEMS cmake submodules 2021-07-15 17:03:42 +02:00
CMakeLists.txt apply afmt 2022-05-27 02:17:19 +02:00
LICENSE init commit 2021-07-15 16:55:08 +02:00
NOTICE init commit 2021-07-15 16:55:08 +02:00 updating RTEMS example 2022-05-27 01:46:51 +02:00

FSFW Example Application

This repository features a demo application. The example has been run successfully on the following platforms:

  • Linux host machine with the Linux OSAL or the Host OSAL
  • Windows with the Host OSAL
  • STM32H743ZI-Nucleo with the FreeRTOS OSAL
  • Raspberry Pi with the Linux OSAL
  • STM32H743ZI-Nucleo with the RTEMS OSAL

The purpose of this example is to provide a demo of the FSFW capabilities. However, it can also be used as a starting point to set up a repository for new flight software. It also aims to provide developers with practical examples of how the FSFW is inteded to be used and how project using the FSFW should or can be set up and it might serve as a basic test platform for the FSFW as well to ensure all OSALs are compiling and running as expected.

The repository contains a Python TMTC program which can be used to showcase the TMTC capabilities of the FSFW (currently, using the ECSS PUS packet standard).

Configuring the Example

The build system will copy three configuration files into the build directory:

  1. commonConfig.h which contains common configuration parameters
  2. OBSWConfig.h which can contain machine and architecture specific configuration options
  3. FSFWConfig.h which contains the configuration for the flight software framework

These files can be edited manually after CMake build generation.


Getting started with Eclipse for C/C++
Getting started with CMake

Getting started with the Hosted OSAL
Getting started with the FreeRTOS OSAL on a STM32
Getting started with the RTEMS OSAL on a STM32
Getting started with the Raspberry Pi
Getting started with the Beagle Bone Black

FSFW demo with FreeRTOS OSAL on the STM32H743ZI

This demo can be run on a STM32H743ZI-Nucleo board with the RTEMS OSAL.

General information

The board is flashed and debugged with OpenOCD and this README specifies on how to make this work with the Eclipse IDE. Other IDEs or the command line can be used as well as long as OpenOCD integration is given. Debug otuput can be read directly from the USB connection to the board.


See Prerequisites for detailed instructions on how to set them up.

  1. RTEMS BSP arm/stm32h7 installed (arm-rtems6)
  2. RTEMS LwIP support installed for networking. It is recommended to generate a build folder first because this will generate the required lwipopts.h file.
  3. MinGW64 or Ninja Build installed on Windows. Not required on Linux.
  4. Recommended for application code development: Eclipse for C/C++ installed with the Eclipse MCU plugin
  5. OpenOCD installed for Eclipse debugging
  6. STM32 USB drivers installed

Building the software with CMake

On Windows, the following steps should be performed inside the MinGW64 console after installing MSYS2. It is recommended to still use git for Windows for the git related steps.

  1. Clone this repository

    git clone
  2. Set up submodules

    git submodule init
    git submodule update
  3. Navigate into the cloned repository and create a folder for the build. We will create a Debug build folder.

    mkdir build-Debug
    cd build-Debug
  4. Ensure that the RTEMS ARM compiler has been added to the path and can be called from the command line. For example, the following command should work:

    arm-rtems6-gcc --version

    Now we will create the build configuration for cross-compilation of an ARM target. On Linux, run the following command:

    cmake -G "Ninja" -DFSFW_OSAL=rtems -DCMAKE_BUILD_TYPE=Debug ..

    The build configuration can also be performed with the shell scripts located inside cmake/scripts/RTEMS or the Python helper script inside cmake/scripts. You can also use Make by using -G "Unix Makefiles" or -G "MinGW Makefiles" as the build generator.

  5. Build the application

    cmake --build . -j

    The application will be located inside the Debug folder and has been compiled for the flash memory.

  6. You can test the application by first connecting the STM32H743ZI-Nucleo via USB. The device should now show up in the list of connected devices (make sure the USB drivers are installed as well). Drag and drop the binary file into the connected device to flash it. The debug output is also sent via the connected USB port and a blink pattern (1 second interval) can be used to verify the software is running properly.

Setting up the prerequisites

Setting up RTEMS

Building a software for RTEMS generally requires building a cross-compiler toolchain for the target architecture first and then building a board or chip specific BSP. The RTEMS QuickStart Guide specifies the general steps required to build a BSP. The following steps will show how to build the arm/nucleo-h743zi BSP required for the STM32H743ZI-Nucleo board. It is recommended to build the BSP on Linux because the build process in Windows has proven problematic numerous times. On Windows, it is recommended to download a pre-compiled tool suite or build cross-compile the toolchain for Windows on a Linux system. The BSP build process with waf should work on both OSes without issues.

For Linux, it is recommended you clone and follow the steps specified in this respository. In any case, it is recommended to use this fork to build the BSP from the RTEMS sources because it contains important fixes for the relatively new arm/nucleo-h743zi BSP.

You can also download the pre-compiled toolchains from here

Installing LwIP for RTEMS

If you have not installed lwIP for RTEMS yet, you need to do it once. Installing it requires two variables:

  • LWIP_OPTS_PATH: Path to the lwiptops.h. This path will usually be the build folder after CMake build generation, for example build-Debug for a Debug build
  • RTEMS_PREFIX: RTEMS prefix. The lwIP support will be installed there, and the prefix should be the same location used when installing the RTEMS BSP
  • RTEMS_BSP: RTEMS BSP being used

You can install the lwIP support like this

export RTEMS_PREFIX=<pathToRtemsPrefix>
cd build-Debug
export LWIP_OPTS_PATH=$(pwd)
cd ..
cd cmake/rtems-lwip
./waf configure --prefix=$RTEMS_PREFIX --lwip-opts=$LWIP_OPTS_PATH --rtems-bsp=arm/nucleo-h743zi
./waf install

This will install the required headers and liblwip.a at the specified prefix so you can use them when building RTEMS applications.

Installing the USB drivers for the STM32


You can install the STM32 USB drivers


You can install the STM32 USB drivers on Ubuntu with the following command

sudo apt-get install stlink-tools

Setting up Eclipse for comfortable development

The separate Eclipse README specifies how to set up Eclipse. The STM32 configuration uses the xPacks OpenOCD and the xPacks ARM Toolchain, so those should be installed as well. OpenOCD should be configured correctly in the STM32 launch configurations.

It is recommended to use the given project files which include a RTEMS configuration which only requires a few steps to work properly. When using the project files, go to the project properties → C/C++ Build → Build Variables and adapt the build variable RTEMS_PREFIX to point to your RTEMS prefix location, for example $HOME/RTEMS/rtems-tools/rtems/6. After that, Eclipse should be able to autodetermine the BSP specific include paths.


OpenOCD errors

If you get the following error in OpenOCD: "Error: auto_probe failed", this could be related from switching between FreeRTOS and RTEMS. You can try the following steps:

  1. First way: Flash the binary manually by drag & droping the binary into the USB drive manually once

  2. Second way: Add -c "gdb_memory_map disable" to the OpenOCD arguments (in Eclipse) and run once. Debugging might not be possible, so remove it for subsequent runs.

  3. Third way (most reliable): Add the following lines to the stm32h7x.cfg file located inside the OpenOCD folder inside the scripts/target folder:

    $_CHIPNAME.cpu0 configure -event gdb-attach {
    $_CHIPNAME.cpu0 configure -event gdb-attach {
        reset init