Contest-specific DCP to FPGA Interchange Format Utility #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This utility is used to convert a fully-routed Vivado Design Checkpoint (DCP) into the FPGA Interchange Format's Logical and Physical Netlists compatible with the FPGA24 contest.
Specifically, in line with the competition format the Physical Netlist will only contain the inter-site routing (i.e. PIPs) for global and static nets. All other nets will have their inter-site routing removed. Intra-site routing (not within the scope of this contest) is left as-is.
Example usage:
Compared to the benchmarks released in v1.0, the benchmarks in the
upcomingv1.1 release contain nets with alternate sources set up, where available. Alternate sources typically refer to the ability for a LUT to exit its SLICE using up to 2 pins -- for anA6LUT
these pins areA_O
(always available) andAMUX
(available if not used for another purpose). Considering both pins, where available, can improve routability, though there are no restrictions on which of the two (or whether both) source pins are used to connect to which sink pins.Use of this utility is not necessary to enter the contest, though contestants may choose to use Vivado to compile additional benchmarks beyond those that we supply in order to increase test coverage/acquire more training data, etc.