[dv] Remove cp_insn_trigger_exception coverpoint

This coverpoint does not make sense. The hardware breakpoint is
triggered as the instruction moves into the ID/EX stage so it never has
a chance to take an exception (it effectively never begins executing).
This commit is contained in:
Greg Chadwick 2022-10-25 17:22:55 +01:00 committed by Greg Chadwick
parent 1851e86113
commit bfe71faf5f
2 changed files with 0 additions and 5 deletions

View file

@ -223,9 +223,6 @@ Furthermore they can all occur together and must be appropriately prioritised (c
* ``cp_debug_req`` - External debug request.
* ``cp_single_step_taken`` - Instruction executed when debug single step enabled.
* ``cp_insn_trigger_enter_debug`` - Instruction matches hardware trigger point.
* ``cp_insn_trigger_exception`` - Instruction matching trigger point causes exception
* ``cp_debug_mode`` - Ibex operating in debug mode.
* ``irq_wfi_cross``, ``debug_wfi_cross`` - Debug and Interrupt whilst sleeping with WFI

View file

@ -499,8 +499,6 @@ interface core_ibex_fcov_if import ibex_pkg::*; (
`DV_FCOV_EXPR_SEEN(pipe_flush, id_stage_i.controller_i.fcov_pipe_flush)
`DV_FCOV_EXPR_SEEN(single_step_taken, id_stage_i.controller_i.fcov_debug_single_step_taken)
`DV_FCOV_EXPR_SEEN(insn_trigger_enter_debug, instr_id_matches_trigger_q)
`DV_FCOV_EXPR_SEEN(insn_trigger_exception, instr_id_matches_trigger_q &&
id_stage_i.controller_i.fcov_pipe_flush)
cp_nmi_taken: coverpoint ((fcov_irqs[5] || fcov_irqs[4])) iff
(id_stage_i.controller_i.fcov_interrupt_taken);