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

XDC constraints attributes on cells/ports missing from the netlists #109

Open
acomodi opened this issue Jul 12, 2021 · 1 comment
Open

Comments

@acomodi
Copy link
Contributor

acomodi commented Jul 12, 2021

While dealing with #108 I have bumped into one issue which has many ways of being solved IMO.

The problem is that the XDC constraints that add attributes do not reflect outside of nextpnr, as the XDC parser is embedded within. This means that the logical netlist won't have information, for instance, on the IOSTANDARD attribute of a pad, unless this is specified in the design.

The attributes are quite important when, for instance, writing the FASM features.

Some of the possible solutions:

  1. enhance the physical netlist schema to include information on additional attributes assigned to the cells during p&r (e.g. when reading the XDCs)
  2. read the XDC file once again alongside with logical and physical netlists
  3. add the attributes when generating the logical netlist and read the XDC at that step
@gatecat
Copy link
Contributor

gatecat commented Jul 12, 2021

Another option would be to write out a new logical netlist from nextpnr.

In the long-long term, this would be needed if a place and route tool wanted to perform optimisations that manipulate the netlist, such as retiming, resynthesis, or control set remapping.

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

2 participants