[chip-test] chip_sw_alert_handler_escalation_methods
Open
Nobody has claimed this yet.
Component:ChipLevelTest
Component:SiliconValidation
SiVal:draft/WIP
SiVal:NewTest
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Test point name
chip_sw_alert_handler_escalation_methods
Host side component
None
OpenTitanTool infrastructure implemented
None
Silicon Validation (SiVal)
Yes
Emulation Targets
- None
- CW310
- Hyperdebug + CW310
Contact person
@msfschaffner
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.
- Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
- Device-side (C) component developed
- Bazel build rules developed
- Host-side component developed
- HJSON test plan updated with test name (so it shows up in the dashboard)
- Test added to dvsim nightly regression (and passing at time of checking)
- For SiVal test cases, test is running relevant FPGA or silicon regression
estimate 2
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 the chip_sw_alert_handler_escalation_methods entry in hw/top_earlgrey/data/ip/chip_alert_handler_testplan.hjson and review the checklist. Determine the required device-side C component, Bazel rules, test-plan update, and CW310 regression coverage. Done means the test appears in the dashboard and runs in the relevant regression.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100