Remove Internal Flash storage method #6
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
giulcioffi
force-pushed
the
NoInternalFlash
branch
from
d0b90f1 to
f1ad1a4
Compare
aentinger
approved these changes
Feb 8, 2021
Contributor
aentinger
left a comment
aentinger
left a comment
There was a problem hiding this comment.
LGTM 👍 Thank you @giulcioffi 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Internal Flash could be used as OTA storage method by specifying an offset and storing the binary starting from there.
Since the library currently supports only the filesystem-based methods, the Internal Flash storage method can be entirely removed.
The available OTA storage methods will be: