From b7df37d4af909450f4d71f8cf7f56945b91e8b81 Mon Sep 17 00:00:00 2001 From: Paul Donahue Date: Tue, 19 Nov 2024 17:29:28 -0800 Subject: [PATCH] Better description of how etrigger matches. --- xml/hwbp_registers.xml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/xml/hwbp_registers.xml b/xml/hwbp_registers.xml index a7b8a200..37553187 100755 --- a/xml/hwbp_registers.xml +++ b/xml/hwbp_registers.xml @@ -1252,11 +1252,13 @@ same project unless stated otherwise. This register is accessible as {csr-tdata1} when {tdata1-type} is 5. - This trigger may fire on up to XLEN of the Exception Codes defined in - `mcause` (described in the Privileged Spec, with Interrupt=0). Those - causes are configured by writing the corresponding bit in {csr-tdata2}. - (E.g. to trap on an illegal instruction, the debugger sets bit 2 in - {csr-tdata2}.) + This trigger can match when a trap is taken due to an exception. + + The trigger may be configured to match on up to XLEN of the Exception + Codes defined in `mcause` (described in the Privileged Spec, with + Interrupt=0). Those causes are configured by writing the corresponding + bit in {csr-tdata2}. (e.g. to have etrigger match on an illegal + instruction trap, the debugger sets bit 2 in {csr-tdata2}.) [NOTE] ====