We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
while adding one of the VPR7.0 benchmarks to Symbiflow setup, the design failed in routing with the following error:
Cannot route from SYN-GND.GND[0] (RR node: 444787 type: SOURCE location: (36,27) class: 0 capacity: 1) to SYN-OUTPAD.outpad[0] (RR node: 125935 type: SINK location: (10,29) class: 0 capacity: 1) -- no possible path
The added design was stereovision3 with some edits. The edits were serializing the multibit input ports, ORing and ANDing the multibit output port.
I think having an error of "no possible path" with a small design like that might mean that there something broken in the routing resource graph
The edited version of the benchmark and the pin assignment file are attached. rr_issue.tar.gz
The text was updated successfully, but these errors were encountered:
This is an artifact of the ROI and how the 7-series routing graph is designed. Possible solutions:
basys3-full
basys3
Example synthesis for a false LUT:
(* KEEP *) LUT1 #(.INIT(2'b00)) ( .O(signal_to_outpad) );
Sorry, something went wrong.
No branches or pull requests
while adding one of the VPR7.0 benchmarks to Symbiflow setup, the design failed in routing with the following error:
The added design was stereovision3 with some edits. The edits were serializing the multibit input ports, ORing and ANDing the multibit output port.
I think having an error of "no possible path" with a small design like that might mean that there something broken in the routing resource graph
The edited version of the benchmark and the pin assignment file are attached.
rr_issue.tar.gz
The text was updated successfully, but these errors were encountered: