-
Notifications
You must be signed in to change notification settings - Fork 92
Issues: riscv/riscv-debug-spec
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Tell external debugger whether mcontrol6.hit bits are supported
#1080
opened Nov 7, 2024 by
JanMatCodasip
Does setting mcontrol6 trigger to NAPOT limit the size of tdata2 due to maskmax restriction?
#1073
opened Oct 8, 2024 by
ThimayaPR
what is the behavior when tcontrol exists but mte/mpte behavior is not desired?
Clarification
#1069
opened Aug 30, 2024 by
rtwfroody
Question about Trigger Match Control Type6 CSR's "size" field function
#1058
opened Aug 13, 2024 by
micreven
Question about Trigger Match Control Type6 CSR's "match" field function
#1057
opened Aug 3, 2024 by
micreven
Question about trigger exceptions and other types of exceptions occurring at the same time
#1056
opened Jul 15, 2024 by
Wei-VV1995
Clarify apparent inconsistency of debug version read by registers
#1053
opened Jul 10, 2024 by
psherman42
Multiple mcontrol6 triggers match on same instruction with different actions and timings
#1043
opened Jun 5, 2024 by
tomaird
Hit bit interaction with action conflict when several triggers of the same priority match
#1018
opened Apr 25, 2024 by
en-sc
Timing requirements for a chain of
mcontrol
load address triggers
#1011
opened Apr 24, 2024 by
en-sc
Clarify effect of tdata1 write with zero when only one trigger type supported
#991
opened Mar 22, 2024 by
JamesKenneyImperas
asciidoc lacks lists of figures and tables
1.0
asciidoc
asciidoc conversion
#966
opened Feb 9, 2024 by
rtwfroody
Previous Next
ProTip!
Follow long discussions with comments:>50.