PLIC DV - Top-level priority-arbitration test
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 38
- Forks
- 21
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 14
Description
Implement `chip_rv_plic_priority` (`rv_plic_priority_test` / `rv_plic_priority_test_cheri`, V2, placeholder registered).
SW configures distinct priorities for several interrupt sources (for example UART, SPI device, GPIO, mailbox) and a non-zero threshold, then forces all of them simultaneously. The test confirms that only the highest-priority source above the threshold is delivered first, and that after each claim/complete the next-highest follows in strict priority order. The sequence is then repeated with the priority assignments rotated, to confirm the ordering is driven by the configured priority values and not by the interrupt ID.
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 chip_rv_plic_priority entry point and its rv_plic_priority_test and rv_plic_priority_test_cheri variants; no source file or test command is named. The test is done when both variants verify threshold filtering, strict configured-priority ordering across claim/complete cycles, and the rotated-priority sequence.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100