Clarify that RISC-V triggers are optional.
Change-Id: I3a1f5a30385969964351b6ccadf09a3796d34d6b Signed-off-by: Tim Newsome <tim@sifive.com>
This commit is contained in:
parent
fb3376b7f0
commit
7c3a77c37a
|
@ -10718,8 +10718,9 @@ Perform a 32-bit DMI write of value at address.
|
||||||
|
|
||||||
@subsection RISC-V Trigger Commands
|
@subsection RISC-V Trigger Commands
|
||||||
|
|
||||||
The RISC-V Debug Specification defines several trigger types that don't map
|
The RISC-V Debug Specification defines several optional trigger types that don't
|
||||||
cleanly onto OpenOCD's notion of hardware breakpoints. These commands let you
|
map cleanly onto OpenOCD's notion of hardware breakpoints. For the types that
|
||||||
|
the target supports, these commands let you
|
||||||
set those triggers directly. (It's also possible to do so by writing the
|
set those triggers directly. (It's also possible to do so by writing the
|
||||||
appropriate CSRs.)
|
appropriate CSRs.)
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue