Another annoying TM store bug #645
@ -68,6 +68,8 @@ will consitute of a breaking change warranting a new major release:
|
|||||||
- PLOC MPSoC special communication is now scheduled, which allows flash read and flash write
|
- PLOC MPSoC special communication is now scheduled, which allows flash read and flash write
|
||||||
commands to work.
|
commands to work.
|
||||||
- Fixed the MPSoC flash write command.
|
- Fixed the MPSoC flash write command.
|
||||||
|
- When a PUS parsing error occured while parsing a TM store file, the dump completion procedure
|
||||||
|
was always executed.
|
||||||
|
|
||||||
# [v2.0.5] 2023-05-11
|
# [v2.0.5] 2023-05-11
|
||||||
|
|
||||||
|
@ -140,7 +140,7 @@ ReturnValue_t TmStoreTaskBase::performDump(PersistentTmStoreWithTmQueue& store,
|
|||||||
ReturnValue_t result = store.getNextDumpPacket(tmReader, fileHasSwapped);
|
ReturnValue_t result = store.getNextDumpPacket(tmReader, fileHasSwapped);
|
||||||
if (result != returnvalue::OK) {
|
if (result != returnvalue::OK) {
|
||||||
sif::error << "PersistentTmStore: Getting next dump packet failed" << std::endl;
|
sif::error << "PersistentTmStore: Getting next dump packet failed" << std::endl;
|
||||||
} else if (fileHasSwapped or result == PersistentTmStore::DUMP_DONE) {
|
} else if (fileHasSwapped and result == PersistentTmStore::DUMP_DONE) {
|
||||||
// This can happen if a file is corrupted and the next file swap completes the dump.
|
// This can happen if a file is corrupted and the next file swap completes the dump.
|
||||||
dumpDoneHandler();
|
dumpDoneHandler();
|
||||||
return returnvalue::OK;
|
return returnvalue::OK;
|
||||||
|
Loading…
x
Reference in New Issue
Block a user