DMI NOP operation should never cause busy status #2132
Merged
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
See RISC-V Debug Specification Version 1.0 [6.1.5. Debug Module Interface Access (`dmi`, at 0x11)], `op` field description: > 0 (nop): Ignore data and address. Don’t send anything over the DMI during Update-DR. This operation should never affect DMI busy or error status.
Collaborator
|
LGTM |
aswaterman
approved these changes
Nov 11, 2025
Collaborator
aswaterman
left a comment
aswaterman
left a comment
There was a problem hiding this comment.
Merging on the basis of @arrv-sc's review.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
See RISC-V Debug Specification Version 1.0 [6.1.5. Debug Module Interface Access (
dmi, at 0x11)],opfield description: