Consider adding explicit enable for qualifying DBG_CAUSE
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
https://github.com/lowRISC/ibex/pull/1816#pullrequestreview-1142572997
https://github.com/lowRISC/ibex/pull/1816#discussion_r995853633
The RTL change in the linked PR was to address incorrectly recording the cause when entering debug_mode.
Other regressions have indicated there are some race-conditions around multiple stimuli to enter debug_mode arriving in close proximity to each other. This change would also go towards better understanding those issues.
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 with the linked pull request review and discussion, then examine the RTL change that addressed incorrect DBG_CAUSE recording when entering debug_mode. Determine the intended explicit enable behavior for qualifying DBG_CAUSE and how closely timed debug_mode stimuli should be handled; completion requires an agreed design and corresponding verified RTL change.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100