sys/suit: save seq_number when parsing manifest #17939
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
At the end of an update the manifest
seq_no
should set "somewhere". For firmware update, this is done implicitly since theseq_no
is contained in the firmware update. But for other storage units, it needs to be obtained from the manifest.Therefore when parsing the manifest save the sequence number, and for
ram
storage set it duringinstall
.Testing procedure
In master, the
sequence_no
is never checked when using RAM storage, with this PR it is (although only ephemerally). Follow the README.native.mdOr alternatively, leverage #16771.