-
Notifications
You must be signed in to change notification settings - Fork 111
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
Wire w/ Null Tile included in tile.getWireConnections(wire) for Wires with FAKE_SM_VALUE Speed Model #80
Comments
I can confirm the issue is present in RapidWright 2020.1.2, it looks to me an issue with something in the device model. This appears to a be a rare issue, but will need to get resolved. I will dive deeper during the next release to see if a quick fix can be applied. It is interesting to note that this issue appears to occur at the edge tile of the device. |
Thanks for confirming the issue is present! It's easy enough to work around for now as at least all the actual connections still seem to be represented. Thanks for being willing to look more into this. |
Looking at this again after a long while. Unfortunately, some of these rare exceptional cases are not as straightforward to fix. Running through all the devices, I get this number of invocations for the listed devices that have a null tile in the result:
I can target all of these cases with this code:
Some of these can be worked around by getting the |
I have encountered this problem with the RapidWright router when routeNode.getConnections() is called for certain wires. So far, I have encountered this error on a kintexu device (xcku025-ffva1156-2-e), but did not encounter the problem when using a Zynq Ultrascale device.
The problem is that the list of wires returned from tile.getWireConnections(wire) for these wires includes a wire with a null tile. This then leads to a null pointer exception in the router. Some example wires where this problem occurs are INT_X1Y179/BOUNCE_E_10_FTN, INT_X12Y179/BOUNCE_E_12_FTN, and INT_X12Y179/INODE_1_E_28_FTN. Each of these wires has a speed model of "FAKE_SM_VALUE" and the list of connections seems complete if the invalid one with a null tile is ignored.
This seems to be a different issue from #63 as these wires are all base wires.
The text was updated successfully, but these errors were encountered: