-
Notifications
You must be signed in to change notification settings - Fork 253
Description
Is your feature request related to a problem? Please describe.
Current PC RTEMS workflow creates a fat32 disk image and QEMU command line drive option for runtime access. See:
https://github.com/nasa/cFS/blob/main/.github/scripts/rtems-test.mk
Flight systems often utilize flat nonvol memory for boot/startup which can be done using RTEMS support for linking a tared filesystem with the executable and populating the root file system from the tar file at startup.
Describe the solution you'd like
Add generic support for RTEMS tar filesystem
Describe alternatives you've considered
EEFS is an alternative simple file system, adding RTEMS tar filesystem support doesn't preclude using other options.
Additional context
None
Requester Info
Jacob Hageman - NASA/GSFC