[chip dv] Deprecate jtag_riscv_agent
Open
Nobody has claimed this yet.
Component:DV
Earlgrey-PROD Candidate
Milestone:V2
Priority:P2
TOP:earlgrey
Type:Cleanup
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
The jtag_dmi_agent supercedes the jtag_riscv_agent work and provides a more ergonomic way to access the chip over JTAG. As a step towards tech debt reduction, we should replace it with jtag_dmi_agent / sba_access_utils_pkg methods at the chip level soon.
The replacement should be hopefully straightforward, and should take about a day to complete.
@cindychip @tjaychen
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 by locating chip-level uses of jtag_riscv_agent and reading the jtag_dmi_agent and sba_access_utils_pkg interfaces. Replace the existing chip-level access with the newer methods, then verify that no chip-level jtag_riscv_agent use remains and run the relevant chip DV checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100