-
Notifications
You must be signed in to change notification settings - Fork 2
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
Certain terminals for ports/channels/nodes cause source/sink error (probably an autoplacement issue) #10
Comments
As an update to this, I learned that autoplacement isn't the direct cause of this issue, as it worked fine with other designs. It does seem, however, that terminals 3 and 4 on nodes and ports are unavailable. Because of this, my design was able to compile, but only about 1/3 of the channels could actually be routed by the tool. Here is the full file I used to come to this conclusion:
And here is the log output:
|
I had the same issue while using the Neptune UI:
When trying to specify terminals on the PORT and NODES, we had compile issues. We could specify only terminal 1 on PORTS and NODES, but we could specify both terminal 1 and 2 on other components, such as MIXER. |
When trying to compile my design, I noticed that outputting from terminals 3 and 4 for any node/port resulted in a source/sink error during routing. I created a small example to test this, and it seems that most source/sink pairs will fail except when connecting from terminal 1 on one component to terminal 1 on the other component (again, only with nodes/ports).
This seems to be because the automatic placement of parts defaults to the same position for each component, causing the routing algorithm to not be able to find a path from input to output. However, as none of the examples show a position for any part and the documentation, itself, states that setting a position is optional, this seems to be an issue with the algorithm to determine component placement.
Here is the test code I made:
And here is the output:
The text was updated successfully, but these errors were encountered: