eive/fsfw
eive
/
fsfw
forked from fsfw/fsfw
14
1
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity
fsfw/src/fsfw/cfdp/pdu/MetadataGenericInfo.h

36 lines
1.0 KiB
C
Raw Normal View History

Added CFDP packet stack This PR adds the packet stack for the CCSDS File Delivery Protocol. It also refactors the existing TMTC infastructure to allow sending of CFDP packets to the CCSDS handlers. This includes the whole PDU (Protocol Data Unit) stack: - File Data PDUs and all file directive PDUs - ACK PDU - NAK PDU - Metadata PDU - Finished PDU - Prompt PDU - Keep Alive PDU - EOF PDU The PR includes a full set of unittests for the packet stack with a coverage of 90+ %. The refactoring of the existing TMTC infastructure includes non-ideal solutions like diamond inheritance. Avoiding this solution would require refactoring the packet stack. This would be a good idea anyway because the existing stack is tightly coupled to the FSFW, making reuse more difficult if only the stack is planned to be used without the store functionalities etc. The PDU implementation provided here is only weakly coupled to the FSFW, only using components like returnvalues or the Serialization modules. There are dedicated serializers and deserializers, which also helps in creating small focused modules which are easy to test. Some of the modules here were provied by Matthias Tompert.
2021-12-03 15:37:49 +01:00
#ifndef FSFW_SRC_FSFW_CFDP_PDU_METADATAINFO_H_
#define FSFW_SRC_FSFW_CFDP_PDU_METADATAINFO_H_
continue dest handler
2022-08-23 19:37:30 +02:00
#include <optional>
implemented fle data PDUs
2023-07-19 13:44:52 +02:00
#include "fsfw/cfdp/Fss.h"
Added CFDP packet stack This PR adds the packet stack for the CCSDS File Delivery Protocol. It also refactors the existing TMTC infastructure to allow sending of CFDP packets to the CCSDS handlers. This includes the whole PDU (Protocol Data Unit) stack: - File Data PDUs and all file directive PDUs - ACK PDU - NAK PDU - Metadata PDU - Finished PDU - Prompt PDU - Keep Alive PDU - EOF PDU The PR includes a full set of unittests for the packet stack with a coverage of 90+ %. The refactoring of the existing TMTC infastructure includes non-ideal solutions like diamond inheritance. Avoiding this solution would require refactoring the packet stack. This would be a good idea anyway because the existing stack is tightly coupled to the FSFW, making reuse more difficult if only the stack is planned to be used without the store functionalities etc. The PDU implementation provided here is only weakly coupled to the FSFW, only using components like returnvalues or the Serialization modules. There are dedicated serializers and deserializers, which also helps in creating small focused modules which are easy to test. Some of the modules here were provied by Matthias Tompert.
2021-12-03 15:37:49 +01:00
#include "fsfw/cfdp/definitions.h"
reapply clang format
2022-02-02 10:29:30 +01:00
#include "fsfw/cfdp/tlv/Lv.h"
continue dest handler
2022-08-23 19:37:30 +02:00
#include "fsfw/cfdp/tlv/StringLv.h"
reapply clang format
2022-02-02 10:29:30 +01:00
#include "fsfw/cfdp/tlv/Tlv.h"
Added CFDP packet stack This PR adds the packet stack for the CCSDS File Delivery Protocol. It also refactors the existing TMTC infastructure to allow sending of CFDP packets to the CCSDS handlers. This includes the whole PDU (Protocol Data Unit) stack: - File Data PDUs and all file directive PDUs - ACK PDU - NAK PDU - Metadata PDU - Finished PDU - Prompt PDU - Keep Alive PDU - EOF PDU The PR includes a full set of unittests for the packet stack with a coverage of 90+ %. The refactoring of the existing TMTC infastructure includes non-ideal solutions like diamond inheritance. Avoiding this solution would require refactoring the packet stack. This would be a good idea anyway because the existing stack is tightly coupled to the FSFW, making reuse more difficult if only the stack is planned to be used without the store functionalities etc. The PDU implementation provided here is only weakly coupled to the FSFW, only using components like returnvalues or the Serialization modules. There are dedicated serializers and deserializers, which also helps in creating small focused modules which are easy to test. Some of the modules here were provied by Matthias Tompert.
2021-12-03 15:37:49 +01:00
seems to work well
2023-07-27 14:55:46 +02:00
class MetadataGenericInfo {
reapply clang format
2022-02-02 10:29:30 +01:00
public:
start verifying metadata PDU
2023-08-03 13:57:55 +02:00
MetadataGenericInfo() = default;
seems to work well
2023-07-27 14:55:46 +02:00
explicit MetadataGenericInfo(cfdp::Fss fileSize);
MetadataGenericInfo(bool closureRequested, cfdp::ChecksumType checksumType, cfdp::Fss fileSize);
reapply clang format
2022-02-02 10:29:30 +01:00
seems to work well
2023-07-27 14:55:46 +02:00
static size_t getSerializedSize(bool fssLarge = false);
reapply clang format
2022-02-02 10:29:30 +01:00
use singular enum names
2022-09-15 18:41:15 +02:00
[[nodiscard]] cfdp::ChecksumType getChecksumType() const;
void setChecksumType(cfdp::ChecksumType checksumType);
add CFDP unit tests
2022-08-08 17:53:42 +02:00
[[nodiscard]] bool isClosureRequested() const;
reapply clang format
2022-02-02 10:29:30 +01:00
void setClosureRequested(bool closureRequested = false);
API improvements
2023-08-30 11:18:49 +02:00
[[nodiscard]] const cfdp::Fss& getFileSize() const;
cfdp::Fss& getMutFileSize();
reapply clang format
2022-02-02 10:29:30 +01:00
private:
bool closureRequested = false;
use singular enum names
2022-09-15 18:41:15 +02:00
cfdp::ChecksumType checksumType = cfdp::ChecksumType::NULL_CHECKSUM;
seems to work well
2023-07-27 14:55:46 +02:00
cfdp::Fss fileSize;
Added CFDP packet stack This PR adds the packet stack for the CCSDS File Delivery Protocol. It also refactors the existing TMTC infastructure to allow sending of CFDP packets to the CCSDS handlers. This includes the whole PDU (Protocol Data Unit) stack: - File Data PDUs and all file directive PDUs - ACK PDU - NAK PDU - Metadata PDU - Finished PDU - Prompt PDU - Keep Alive PDU - EOF PDU The PR includes a full set of unittests for the packet stack with a coverage of 90+ %. The refactoring of the existing TMTC infastructure includes non-ideal solutions like diamond inheritance. Avoiding this solution would require refactoring the packet stack. This would be a good idea anyway because the existing stack is tightly coupled to the FSFW, making reuse more difficult if only the stack is planned to be used without the store functionalities etc. The PDU implementation provided here is only weakly coupled to the FSFW, only using components like returnvalues or the Serialization modules. There are dedicated serializers and deserializers, which also helps in creating small focused modules which are easy to test. Some of the modules here were provied by Matthias Tompert.
2021-12-03 15:37:49 +01:00
};
#endif /* FSFW_SRC_FSFW_CFDP_PDU_METADATAINFO_H_ */