[dv,pwrmgr] Fix incoming resets
Open
Nobody has claimed this yet.
Component:Darjeeling
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
There is a strange wiring of internal_reset_req as an input to the dut. Since this is driven by the DUT, it seems trying to drive it via pwrmgr_if ends up being a NO-OP, and pwrmgr_smoke gets hung waiting for a reset. I vaguely recall this strange configuration was meant as a temporary workaround, but perhaps its time is up?
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
Trace the internal_reset_req wiring between the DUT and pwrmgr_if, then inspect how pwrmgr_smoke drives it and where the reset wait occurs. Confirm why the drive is a no-op and consider the intended reset path; done means pwrmgr_smoke no longer hangs waiting for a reset.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100