[tl_reg_adapter] Fix bus2reg to throw an error when d_error is returned
Open
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Description
tl_reg_adapter::bus2reg only reports UVM_NOT_OK when the request didn't complete, it never looks at d_error, so an unmapped access still comes back OK. That also means the uvm_reg::read + status approach can't work. It'll need an expected-error knob in csr_utils to go with it.
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 tracing tl_reg_adapter::bus2reg and how it handles d_error versus UVM_NOT_OK. Then inspect csr_utils and the uvm_reg::read status path to understand the expected-error requirement. Done means unmapped accesses report an error and expected errors can be handled through csr_utils.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100