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

Closed
olofk opened this issue Jul 18, 2019 · 3 comments
Closed

Allow multiple PCF files #303

olofk opened this issue Jul 18, 2019 · 3 comments

Comments

@olofk
Copy link

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
Copy link

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?

@nmz787
Copy link

nmz787 commented Aug 2, 2020

Is it possible to include/import/inherit PCF files from inside another?

@umarcor
Copy link

umarcor commented Oct 28, 2020

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.

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)

Precisely... https://github.com/hdl/constraints/#short-term-goal

/cc @Paebbels

@gatecat gatecat closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants