-
Notifications
You must be signed in to change notification settings - Fork 802
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[padring] Scan role parameters #6024
Conversation
48371ce
to
670cd62
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i like this approach! thanks!
btw, side question... do you think these kinds of scenarios will still be covered by Phil's aliasing proposal? |
The aliasing proposal from Phil will probably work for this as well, yes. |
Rebased onto #6017 |
Ideally, the scan role (none, scan-in, scan-out) would be captured as part of the pinout Hjson description. However, due to the need to keep this information in the foundry repo, an approach with a separate SV package is taken. The open-source version is just a generic assignment of scan roles. The scan role parameters for the synthesized ASIC target are defined in the foundry repo and will be read in when the "fileset_partner" flag is defined in the build flow. Signed-off-by: Michael Schaffner <[email protected]>
Ideally, the scan role of the pads (
None
,ScanIn
,ScanOut
) would be captured as part of the pinout Hjson description.However, due to the need to keep this information in the foundry repo, this approach with a separate package is taken.
The open-source version is a generic assignment of scan roles (basically all are set to
None
).The scan role parameters for the synthesized ASIC target are defined in the ASIC repo and will be read in when the "fileset_partner" flag is defined in the build flow.
Note that this is dependent on #6017, so only the last commit is relevant here.