Skip to content
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

Merged
merged 1 commit into from
Apr 9, 2021
Merged

Conversation

msfschaffner
Copy link
Contributor

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.

Copy link

@tjaychen tjaychen left a 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!

@tjaychen
Copy link

tjaychen commented Apr 9, 2021

btw, side question... do you think these kinds of scenarios will still be covered by Phil's aliasing proposal?
Or would we still need the fileset_partner switch long term?

@msfschaffner
Copy link
Contributor Author

btw, side question... do you think these kinds of scenarios will still be covered by Phil's aliasing proposal?
Or would we still need the fileset_partner switch long term?

The aliasing proposal from Phil will probably work for this as well, yes.

@msfschaffner
Copy link
Contributor Author

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]>
@msfschaffner msfschaffner deleted the scan-role branch February 18, 2022 00:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants