Google Git
Sign in
opensecura / 3p / lowrisc / opentitan / 769540539822e0d64a6e815d6a7aa5f68c2ebd7a / . / hw / dv / sv / alert_esc_agent
tree: 36780fcdb1f443c04a67da97d6c0c106ba6de5af [path history] [tgz]
  1. data/
  2. seq_lib/
  3. alert_esc_agent.core
  4. alert_esc_agent.sv
  5. alert_esc_agent_cfg.sv
  6. alert_esc_agent_cov.sv
  7. alert_esc_agent_pkg.sv
  8. alert_esc_base_driver.sv
  9. alert_esc_base_monitor.sv
  10. alert_esc_if.sv
  11. alert_esc_probe_if.sv
  12. alert_esc_seq_item.sv
  13. alert_esc_sequencer.sv
  14. alert_monitor.sv
  15. alert_receiver_driver.sv
  16. alert_sender_driver.sv
  17. esc_monitor.sv
  18. esc_receiver_driver.sv
  19. esc_sender_driver.sv
  20. README.md
hw/dv/sv/alert_esc_agent/README.md

title: “ALERT_ESC Agent”

ALERT_ESC UVM Agent is extended from DV library agent classes.

Description

This agent implements both alert(alert_rx, alert_tx) and escalation (esc_rx, esc_tx) interface protocols, and can be configured to behave in both host and device modes. For design documentation, please refer to [alert_handler spec]({{< relref “hw/top_earlgrey/ip_autogen/alert_handler/doc/_index.md” >}}).

Alert Agent

Alert agent supports both synchronous and asynchronous modes.

Alert Device Agent

For IPs that send out alerts, it is recommended to attach alert device agents to the block level testbench. Please refer to [cip_lib documentation]({{< relref “hw/dv/sv/cip_lib/doc/index.md” >}}) regarding instructions to configure alert device agent in DV testbenches.

Escalation Agent