Repository navigation
Conversation
binary, instead of the end of flash area. bump version due to breaking changes.
doesn't seem to have watch dog registers... so manual registry address writes...
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Putting app version at the end of the flash storage means upload a firmware always taking the full flash capacity. CRC16 also has to churn through the entire flash space. This PR puts it right behind the app binary. However, this caused 22 bytes overflow and I had to do the unthinkable of shaving the custom runtime even more by removing the .data and .bss loops. But this is safe because we actually don't use any statics.