[BUSKEEPER] Add NULL address check option #247
Merged
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
Bus keeper can now optionally raise a bus exception if the CPU attempts to access address zero (for example by using an uninitailized pointer).
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.
This PR adds a new feature to the BUSKEEPER module (triggered by @emb4fun):
When setting bit 16 (NEORV32_BUSKEEPER) of the control register (
NEORV32_BUSKEEPER.CTRL) the BUSKEEPER will issue a bus exception for all accesses to address0x00000000(instruction fetch / load data / store data). This can help to identify program bugs where uninitialized pointers are used.