chipsalliance / chipsalliance/rocket-chip
Upgrading DebugModule to 1.0
- Dominant language
- Scala
- Stars
- 3.9k
- Forks
- 1.3k
- Avg merge
- 5d 13m
- Merged PRs (30d)
- 1
Description
RISC-V Debug Spec 1.0 has released for almost one years, It's reasonable to upgrade Rocket-Chip DM and Rocket Core to complain with 1.0
**Type of issue**: feature request
**Impact**: API modification | unknown
**Development Phase**: proposal
**Other information**
**If the current behavior is a bug, please provide the steps to reproduce the problem:**
**What is the current behavior?**
**What is the expected behavior?**
**Please tell us about your environment:**
**What is the use case for changing the behavior?**
Contributor guide
Research direction
Start by locating the Rocket-Chip DebugModule and Rocket Core implementations, then compare their current behavior with the RISC-V Debug Spec 1.0. The issue does not name files or tests; done means both components comply with the 1.0 specification, with the required API changes identified and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100