[BUSKEEPER] add memory-mapped status register #191
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
stnolting
added
enhancement
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 add a read-only memory-mapped status register to the
BUSKEEPERmodule. The status register gives additional information regarding the actual cause of an instruction / data-load / data-store bus access fault exception:BUSKEEPER_ERR_TYPE=0: error caused by device itself (by asserting theerr_osignal)BUSKEEPER_ERR_TYPE=1: error caused by bus timeout (accessed device is not responding at all)BUSKEEPER_ERR_SRC=0: error caused during access to processor-internal moduleBUSKEEPER_ERR_SRC=1: error caused during access via processor-external bus interface✔️ This PR is fully backwards compatible - the memory-mapped BUSKEEPER register uses a previously unused IO space address (
0xffffff7C).