Skip to content

Commit

Permalink
Merge pull request #1009 from riscv/action_warl
Browse files Browse the repository at this point in the history
Simplify WARL description for dmode=0 and action=1.
  • Loading branch information
rtwfroody authored May 15, 2024
2 parents f659cd7 + 68a7eb8 commit 28aa582
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion Sdtrig.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,9 @@ Triggers can be configured to take one of several actions when they fire. <<tab:
^| Value | Description
|0 | Raise a breakpoint exception. (Used when software wants to use the trigger module without an external debugger attached.) `xepc` must contain the virtual address of the next instruction that must be executed to preserve the program flow.
|1 | Enter Debug Mode. {csr-dpc} must contain the virtual address of the next instruction that must be executed to preserve the program flow. +
This action is only legal when the trigger's {mcontrol-dmode} is 1. Since the `tdata` registers are *WARL*, hardware should clear the action field whenever the action field is 1, the new value of {mcontrol-dmode} would be 0, and the new value of he action field would be 1. +
This action is only legal when the trigger's {mcontrol-dmode} is 1. Since
{csr-tdata1} is WARL, hardware must prevent it from containing {tdata1-dmode}=0
and action=1. +
This action can only be supported if `Sdext` is implemented on the hart.
| 2 | Trace on, described in the trace specification.
| 3 | Trace off, described in the trace specification.
Expand Down

0 comments on commit 28aa582

Please sign in to comment.