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

Allow multiple PCF files #303

Open
olofk opened this issue Jul 18, 2019 · 1 comment
Open

Allow multiple PCF files #303

olofk opened this issue Jul 18, 2019 · 1 comment

Comments

@olofk
Copy link

@olofk olofk commented Jul 18, 2019

For larger designs it can be nice to split up the pin constraints into multiple files so that they can be swapped in or out together with the associated RTL. For that reason it would be nice to be able to specify multiple PCF files on the command-line

@Aclassifier

This comment has been minimized.

Copy link

@Aclassifier Aclassifier commented Dec 27, 2019

Maybe that could open for refining as well. Like some definition of a pin at the lowest level (and a lowest level pindef pcf file for the actual board) and functionality next level (like in a usagedef pcf file). Like io_icore_p54 at the lowest level and then when used as external_i2c_sda at the next. I learned in https://forum.mystorm.uk/t/hard-to-find-p16-p17-p20-p21-in-blackice-mx-pcf/771/5 that this is not possible with arachne-pnr at least. So I want multiple pcf files plus this hierarchical type system. I am surprised that Verlig does not need this info and surprised that it's not already defined? Or is it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.