File System Tasks #40

New Issue

muellerr · 2021-05-27T17:14:39+02:00

muellerr commented

2021-05-27 17:14:39 +02:00

Various tasks for file system handling:

CoreController which performs various CPU/Core related tasks. Manages the critical data black in a thread-safe way, using a Mutex and a critical data struct. This struct will be backed up to NVM regularly.
SdCardManager class which manages opening and closing the filesystem if it is used by multiple threads concurrently. Does so by using mutex and counter for each SD card. If a SD card is not used (counter == 0), SD card access will be closed.
SdCardAccess token class, RAII conformant, created on stack to get access to the currently active preferred SD Card. In normal cases, preferred SD card will be opened. Preferred SD Card will be part of critical data, kept in RAM but backed up to NVM memory regularly. Reading and updating it will be thread-safe as well, using the CoreController
Get Service 15 prototype developed for SOURCE into FSFW ASAP so it can be used and tested by EIVE as well. It will probably be the primary user of the file system, backing up TM to the mass memory.
CFDP: Manage C++ or Python side, other side made by student as part of SOURCE
Using the C++ std::ifstream and std::ofstream. Those are threadsafe, as long as the error flags are checked after each read function

Various tasks for file system handling: - `CoreController` which performs various CPU/Core related tasks. Manages the critical data black in a thread-safe way, using a Mutex and a critical data struct. This struct will be backed up to NVM regularly. - `SdCardManager` class which manages opening and closing the filesystem if it is used by multiple threads concurrently. Does so by using mutex and counter for each SD card. If a SD card is not used (counter == 0), SD card access will be closed. - `SdCardAccess` token class, RAII conformant, created on stack to get access to the currently active preferred SD Card. In normal cases, preferred SD card will be opened. Preferred SD Card will be part of critical data, kept in RAM but backed up to NVM memory regularly. Reading and updating it will be thread-safe as well, using the `CoreController` - Get Service 15 prototype developed for SOURCE into FSFW ASAP so it can be used and tested by EIVE as well. It will probably be the primary user of the file system, backing up TM to the mass memory. - CFDP: Manage C++ or Python side, other side made by student as part of SOURCE - Using the C++ `std::ifstream` and `std::ofstream`. Those are threadsafe, as long as the error flags are checked after each `read` function

muellerr added the

documentation

label 2021-05-27 17:38:55 +02:00

muellerr commented

2021-07-12 17:51:10 +02:00

SdCardAccess will not be used

`SdCardAccess` will not be used

muellerr commented

2022-10-14 09:49:47 +02:00

The SdCardManager is a globally usable singleton to make using the SD card easier

The `SdCardManager` is a globally usable singleton to make using the SD card easier

muellerr closed this issue