Feature/address range overlap check - #9
Merged
liamkinne merged 2 commits intoJul 30, 2026
Conversation
- Add AddressRangeOverlap error variant to ReaderError - Modify verify() function to detect overlapping address ranges between blocks - Add comprehensive tests for overlap detection and adjacent ranges - Fix existing tests that had unintentional overlapping ranges This ensures that UF2 files with overlapping flash address ranges are properly rejected as invalid, preventing potential flash corruption.
Member
|
Thanks |
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
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.
Block::data().length should be equal to Block::data_len, but last one has less effort
Concat of two files with overlapping address range are ambigues, this means not valid.