DFT struct in Top and IP
Open
Nobody has claimed this yet.
Component:RTL
Component:Tooling
Earlgrey-PROD Triaged
Priority:P3
Type:Enhancement
Type:FutureRelease
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
ip.hjson can have scan field to define whether scanmode_i exists or not. There were comments on the PR #319 to be more flexible not only for scan but also all DFT related signals. So, the plan is to create DFT struct (in top_pkg) and use that struct to propagate all relevant information to the IPs.
This is related to #319
CC: @tjaychen @msfschaffner @sjgitty
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 reading the comments on PR #319, then inspect how ip.hjson defines the scan field and how top_pkg and the IPs currently handle DFT signals. The change is complete when a DFT struct in top_pkg propagates all relevant DFT information to the IPs, rather than handling only scanmode_i.
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