F´ (F Prime) is a component-driven framework that enables rapid development and deployment of spaceflight and other embedded software applications. Originally developed at the Jet Propulsion Laboratory, F´ has been successfully deployed on several space applications. It is tailored but not limited to small-scale spaceflight systems such as CubeSats, SmallSats, and instruments.
F´ comprises several elements:
- An architecture that decomposes flight software into discrete components with well-defined interfaces
- A C++ framework that provides core capabilities such as message queues and threads
- Modeling tools for specifying components and connections and automatically generating code
- A growing collection of ready-to-use components
- Testing tools for testing flight software at the unit and integration levels.
The following utilities are prerequisites to installing F´:
- cmake
- git
- Python 3.5+ with pip
Once these utilities are installed, you can install F´ Python dependencies. Installing dependencies in a Python virtual environment prevents issues at the system level, but installing in a virtual environment is not required.
To install F´ quickly, enter:
git clone https://github.com/nasa/fprime.git
cd fprime
pip install --upgrade wheel setuptools pip
pip install Fw/Python Gds/
For full installation instructions, including virtual environment creation and installation verification, see INSTALL.md.
F´ comes with two example deployments. The deployments represent working F´ applications to help you understand F´. You can use these examples for reference, or clone them to start a new project.
The next section links to more step-by-step tutorials, but it's a good idea to build and run at least the first example deployment to ensure that F´ is installed correctly.
Example one: Ref
The standard reference application demonstrates how most of the system components should be wired together. The reference application can build on Linux or Mac OSX, allowing you to get started immediately without the need for embedded hardware.
Example two: RPI
This Raspberry PI application shows how to run F´ in an embedded context by running on the Raspberry PI (a $35 embedded Linux computer). This application shows you how to get started on embedded projects with cross-compiling, dirvers, and more. The Raspberry Pi was chosen because it is comercially available for a low price and runs Linux.
F´ provides several tutorials in order to help understand and develop within the framework. These tutorials cover basic component creation, system and topology design, tooling, and more. These tutorials are available at docs/Tutorials/README.md.
As F´ becomes a community centered product line, there are more items available from the community at large.
You can join the mailing list at https://groups.google.com/d/forum/fprime-community.
The F´ community GitHub Organization contains third party contributions, more documentation of flight software development, and more! https://github.com/fprime-community.
You can open issues with this repository at: https://github.com/nasa/fprime/issues
F´ has the following key features that enable robust embedded system design.
F´'s component-based architecture enables a high degree of modularity and software reuse.
F´ provides a complete development ecosystem, including modeling tools, testing tools, and a ground data system. Developers use the modeling tools to write high-level specifications, automatically generate implementations in C++, and fill in the implementations with domain-specific code. The framework and the code generators provide all the boilerplate code required in an F´ deployment, including code for thread management, code for communication between components, and code for handling commands, telemetry, and parameters. The testing tools and the ground data system simplify software testing, both on workstations and on flight hardware in the lab.
F´ runs on a wide range of processors, from microcontrollers to multicore computers, and on several operating systems. Porting F´ to new operating systems is straightforward.
F´ utilizes a point-to-point architecture. The architecture minimizes the use of computational resources and is well suited for smaller processors.
F´ is tailored to the level of complexity required for small missions. This makes F´ accessible and easy to use while still supporting a wide variety of missions.
The typed port connections provide strong compile-time guarantees of correctness.
- This is the initial release of the software to open source. See the license file for terms of use.
- Updated contributor list. No code changes.
- Created a Raspberry Pi demo. Read about it here
- Added a tutorial here
- Updated Svc/BufferManager with bug fix
- Fixed a bunch of shell permissions
- Better MagicDraw Plugin
- Prototype CMake build system. See: CMake Documentation
- Mars Helicopter Project fixes migrated in
- Python 3 support added
- Gse refactored and renamed to Gds
- Wx frontend to Gds
- UdpSender and UdpReceiver components added
- Purged inaccurate ITAR and Copyright notices
- Misc. bug fixes
- New prototype HTML GUI
- Python packages Fw/Python and Gds
- Refined CMake and fprime-util helper script
- Better ground interface component
- Integration test API
- Baremetal components
- Ref app no longer hangs on Linux exit
- GDS improvements:
- File Uplink and Downlink implemented
- GDS supports multiple active windows
- Usability improvements for EVRs and commands
- CMake improvements:
- Baremetal compilation supported
- Random rebuilding fixed
- Missing Cheetah templates properly rebuild
- Separate projects supported without additional tweaks
- Updated MemAllocator to have:
- "recoverable" flag to indicate if memory was recoverable across boots
- size variable is now modifiable by allocator to indicate actual size
- This will break existing code that uses MemAllocator
- Updated CmdSequencer
- Uses new MemAllocator interface
- Documentation improvements
- New user's guide containing considerable content: https://nasa.github.io/fprime/UsersGuide/guide.html
- Auto-generated API documentation
- Rewrites, edits, improvements across the board
- F´ Project restructuing
- Projects may now link to F´ and F´ library packges, without needing to keep the framework code in the same source tree
- Usage of framework can be out-of-source
settings.iniIntroduced- Example: https://github.com/fprime-community/fprime-arduino
- Refactored
fprim-util- Replaced redundant targets with flags e.g. build-ut is now build --ut
- Added
infocommand - Bug and usability fixes
- GDS Improvments
- Prototype GDS CLI tool
- Project custom dashboard support
- Array, Enum type support and examples
- Code linting and bug fixes