Added link to Memory Map spreadsheet #73
Open
Conversation
This file contains 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
An easy to use sectioned memory map for drilling down into the issue. Blank out or colour the regions that are not at fault to result in a specific RTC blacklist for the user.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
An easy to use sectioned memory map for drilling down into the issue. Blank out or colour the regions that are not at fault to result in a specific RTC blacklist for the user.
I found it a little difficult in this section without this spreadsheet. It was helpful so as to not waste time constantly calculating the next value, also my notepad got messy. I created the spreadsheet to visually track my progress in finding the RTC regions. I thought it would help others too.