[chip-test] chip_sw_alert_handler_escalation_nmi_reset
- 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_nmi_reset
### Host side component
Rust?
### Opentitantool infrastructure implemented
Yes
### Silicon Validation (SiVal)
Yes
### Emulation targets
- [ ] None
- [ ] CW310
- [ ] Hyperdebug + CW310
### Contact person
### 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
- [ ] Test added to dvsim nightly regression (and passing at time of checking)
- [ ] For SiVal test cases, test is running relevant FPGA or silicon regression
Contributor guide
Research direction
Start by checking whether an existing test covers the chip_sw_alert_handler_escalation_nmi_reset test point. Work through the checklist for the device-side C component, Bazel build rules, host-side component, dvsim nightly regression, and relevant FPGA or silicon regression, linking PRs and issues as appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- 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