Open acomodi opened 2 years ago
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.
While dealing with https://github.com/SymbiFlow/python-fpga-interchange/pull/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: