[dv/alert_handler] remove chip level CSR exclusion for `loc_alert_cause`
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Description
In alert_handler.hjson we added an exclusion for loc_alert_cause register.
Because in top level CSR automation test, CPU clock is disabled, so escalation will not send back any response to alert_handler. This will cause local alert error.
The current solution is to exclude this register from reading.
But a better solution would be add an escalation_agent and enable the agent to response when stub_cpu mode is on.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with alert_handler.hjson and the top-level CSR automation test described in the issue. Trace how stub_cpu mode handles escalation and how loc_alert_cause is currently excluded from reads. Done means an escalation_agent responds when stub_cpu is enabled, allowing the chip-level CSR test to read loc_alert_cause without the exclusion.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100