Top level DV - Clock-gating and power-management tests
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 38
- Forks
- 21
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 14
Description
Chip-level tests for the clock and power managers, backed by bound clock-activity assertions (relates to #152). All V2, placeholders registered in hw/top_chip/dv/top_chip_sim_cfg.hjson.
Testpoints:
chip_clkmgr_clock_gating: SW gates the gateable peripheral clock and hints the hintable main clock; a bound assertion sampled on an always-on reference clock confirms each clock output goes flat while gated and toggles again once re-enabled.chip_pwrmgr_wakeup: SW enters low power, the sequence injects a wakeup, and the test confirms the chip exits low power, the wakeup interrupt is delivered via the PLIC, andPWRMGR_WAKE_INFOidentifies the source.chip_pwrmgr_lowpower_quiescent: during low power, bound assertions confirmclk_main_infraandclk_io_infrashow no edges whileclk_io_powerupkeeps toggling, then all resume after wakeup.
Note: RTL functional simulation cannot measure power; the clock-flat check is the RTL-level proxy. True power-off (isolation, retention, leakage) is a power-aware gate-level signoff activity, out of scope here.
Contributor guide
No contributing guide indexed for this repository
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 V2 placeholders in hw/top_chip/dv/top_chip_sim_cfg.hjson and review related issue #152. Implement the three named top-level testpoints for clock gating, wakeup delivery and low-power quiescence, using bound clock-activity assertions. Done means the tests cover the listed behaviors and resume conditions without claiming true power-off signoff.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100