python-fpga-interchange icon indicating copy to clipboard operation
python-fpga-interchange copied to clipboard

Python interface to FPGA interchange format

Results 24 python-fpga-interchange issues
Sort by recently updated
recently updated
newest added

When VPR is loading the testarch it generates the following warnings: ``` # Loading Architecture Description Use FPGA Interchange device Warning 1: Model 'DFFS' input port 'C' has no timing...

A small script providing useful features when using python in REPL mode to explore interchange device data. Usage: ``` export FPGA_INTERCHANGE_SCHEMA_PATH=/path/to/interchange/schema/repository python3 -i interchange.py /path/to/device/file > # run your commandsd...

I built the repo and ran the command trying to convert a physical netlist IF to a .json file: ```python3 -m fpga_interchange.convert \ --schema_dir "/home/local/eda15/zhilix/projects/RapidWright/interchange/fpga-interchange-schema/interchange" \ --schema physical \ --input_format...

This PR continues the work towards timing driven routing by importing cell timings from prjxray-db to device resources database of a 7-series device. Cell timings are stored in SDF format...

At the moment, nextpnr-interchange can place and route LUTRAM macros, therefore support for them can be added for the FASM generator to have a complete flow down to the bitstream...

I am attempting to generate a YAML-equivalent version of an Interchange device file. I am following the example shown on the main [README.md ](https://github.com/SymbiFlow/python-fpga-interchange/blob/master/README.md): Annotated the xc7a35tcpg236-1 database with constraints:...

This currently imports a simplified set of routing delays to nextpnr. Remaining TODOs: - [x] site input timing - [ ] populating the cell pin timing structures

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...

In the context of being able to support the interchange format in multiple P&R tools, the next good candidate would be enabling place and route starting from an interchange device...