-
Notifications
You must be signed in to change notification settings - Fork 112
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
IDELAYCTRL ignored by VPR #1207
Comments
I took a look at Vivado, and the path from |
@acomodi Have you create an upstream VTR issue on this problem yet? |
Not yet, I can open it right now. |
To be clear, the issue is VPR not pruning BELs with inputs and no outputs. The failure to route issue is a graph issue as a result of an issue in the symbiflow-arch-defs graph import. |
@acomodi : I just remembered:
Try turning off |
Right, I think I had already tried this, but I need to double-check. |
@litghost IDELAYCTRL is there, but VPR failed on VCC blocks. It seems there are too many of them packed, therefore VPR cannot find a suitable device |
Maybe we can change the sweep logic to only sweep if there are 0 inputs and 0 outputs? That second VCC is likely totally disconnected? |
I'll look into that |
@litghost I believe is easily doable actually, the sweeping mechanism checks only if the block has no outputs. I'll change, that, make a wip branch if it works, and integrate it. |
Before you do all that, make sure it fixes our immediate issue. |
Sure |
I've identified a bug in the routing import that will prevent both IDELAYCTRL RST and RDY from being connected to the graph. I'm looking into a fix. |
I've isolated the issue to be an error in the aliveness check. |
The IDELAYCTRL can now be correctly placed and routed, closing this issue. Fixing PRs: |
The current LiteX design instantiates the IDELAYCTRL with inputs only. This causes VPR to ignore the relative nets.
By driving the output signal (
RDY
) to logic, VPR fails to route due to some issues with therr_graph
, ending in an unroutable situation:the
rr_graph_walk
tool did not find a possible route between the SOURCE and SINK nodesThe text was updated successfully, but these errors were encountered: