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
coyote_tc facing [ERROR GRT-0119] Routing congestion too high #1630
Comments
@eder-matheus |
@vijayank88 @maliberty I've run this design with the latest versions of our tools, and I found an odd thing about the nets with congestion. Some instances are not placed, and the nets with congestion are connected to pins of these instances: Are these instances expected to be not placed? Should GRT fail for instances like that? |
Unplaced IOs don't make sense but coyote_tc isn't really a working test case as io placment was never working for it. |
And who should be responsible for placing these instances? Is it PPL or a different tool? I see that the instance type of these is |
pad would place them |
Subject
[Stage]: Global Router.
Describe the bug
Built-in example
sky130hd/coyote_tc
facing global routing congestion issue.This is IO pad based test design. So it is good to find/fix what is causing routing congestion..
Expected Behavior
Complete coyote_tc RTL-GDSII generation
Environment
To Reproduce
Due large file size uploaded in drive and link: https://drive.google.com/drive/folders/18MfXxBJwwAFN0jRWOHnCBus0z1nf0YZy?usp=sharing
Relevant log output
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: