Tolerate 0x prefixes before hex data #3
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
be verbose if set
Updated readme information
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.
Hi Matt,
I just have a fritz box firmware dump which has this format:
Eva_AVM >dm 0x90000000 0x100
0x90000000: 0x40809000 0x40809800 0x401A6000 0x241BFFFE
0x90000010: 0x035BD024 0x3C1BFFBF 0x377BFFFF 0x035BD024
...
so I just added tiny stuff in your script to tolerate the 0x prefixes.
Happy coding, Jens