-
Notifications
You must be signed in to change notification settings - Fork 211
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
klayout import def warns about "Cannot determine routing layers for via" #1457
Comments
The “turn” via is something that seems to be not used any more. |
strm2oas --lefdef-lefs sky130_fd_sc_hd.tlef turn_via.def a.oas |
I missed that on 0.28.12. Will try to do it in the next minor release. |
I only get this warning if the LEF is not seen. In the "strm2oas --lefdef-lefs sky130_fd_sc_hd.tlef turn_via.def a.oas" the LEF is explicitly given. When I load with KLayout, by default all LEFs beside the DEF are read, but KLayout checks for Is "tlef" a common extension for technology LEF? In that case I'd just add "tlef" as a recognized LEF extensions. Matthias |
It seems that OpenLane with it’s sky130 process uses tlef as extension for their technology lef
I’ve seen .lef_5.6, .lef_5.7, .lef_5.8 in the wild ….
And while we’re at this topic …. “don’t shoot the messenger”:
Si2 has ratified lefdef 6.0 and that changed (aka “made better”) the def PINS placement, among some other syntax changes.
… On Oct 6, 2023, at 2:03 AM, Matthias Köfferlein ***@***.***> wrote:
I only get this warning if the LEF is not seen.
In the "strm2oas --lefdef-lefs sky130_fd_sc_hd.tlef turn_via.def a.oas" the LEF is explicitly given. When I load with KLayout, by default all LEFs beside the DEF are read, but KLayout checks for ".lef", not ".tlef" and this warning happens. It disappears when I add the *.tlef file to the reader options.
Is "tlef" a common extension for technology LEF? In that case I'd just add "tlef" as the recognized LEF extensions.
Matthias
—
Reply to this email directly, view it on GitHub <#1457 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGFBQUD3XMIF6VXS2PVJGI3X57COBAVCNFSM6AAAAAA3KZJ4JKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJQGIZTSMJTGU>.
You are receiving this because you authored the thread.
|
fixes this issue too. |
The lef contains TYPE CUT/TYPE ROUTING for the via/metal layers.
The import looks ok because there are no path segments following the via references anyways.
So why the warnings ?
The order of the layers in a via definition is not guaranteed, so should be derived from the lef layer definitions.
test_turn_via.tgz
The text was updated successfully, but these errors were encountered: