-
Notifications
You must be signed in to change notification settings - Fork 383
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
yosys/synth.tcl: migrate to newer supported drw & drf commands #2051
Conversation
Re Yosys commands: rewrite & refactor These commands are considered obsolete and unmaintained by Yosys Replacement commands exist in the form of: drw & drf See also: YosysHQ/yosys#4039 The-OpenROAD-Project#1523
FWIW |
I just noticed that while |
@dlmiles Would you happen to have a test design on hand? We'd like to add it to our test sets if possible. |
Do you have a link to the format you require the design to be in ? Maybe you just want a ZIP with *.tcl and *.def and *.v and *.vh ? What are you testing, just getting to the "[SUCCESS] Flow Complete" ? any post-implementation testing ? The design is actively maintained here https://github.com/dlmiles/tt05-i2c-bert and Apache2 and has a GDS version included in efabless 2311 shuttle in TT05 and the design is at prototype status (the github version has a number of open-source github CI automations including post-implementation gate-level testing, but no open-source SDF/back-annotation testing yet) Does the project need to work on gf180, currently it does not. The project uses a few directly instantiated sky130 cells MAJ3/LATCHES. Note the design (dlmiles/tt05-i2c-bert@08a437f) in question has the following results on these OPENLANE_TAG:
The recent period of LVS errors is this something OpenLane is aware of? it looks like the design had 3 steps added during that period, it looks like those steps are not included in the current flow, it is not clear when they were reverted/removed as STEP1 failures hide any STEP39 failures. Is there any merit to request efabless build a hub.docker.com for @jix Can you confirm the patch in the current form make sense for |
Minimal Project. OPENLANE_TAG=2023.09.25 [Last known success]
|
would it be an idea to add a lot more of the tinytapeout designs to the openlane regression? It seems like a great resource that would easily improve the tests. |
@mattvenn Agreed. Can you get in touch with @kareefardi over Slack? He's currently gathering designs we can add to the CI. |
Thank you so much for looking into this @dlmiles. Intensely appreciated. |
* Updated `Yosys.Synthesis`, `Yosys.VHDLSynthesis` per comments from Yosys team [(1)](YosysHQ/yosys#4039 (comment)) [(2)](The-OpenROAD-Project/OpenLane#2051 (comment)) * Replaced instances of ABC command `rewrite` with `drw -l` with new variable `SYNTH_ABC_LEGACY_REWRITE` being set to `true` restoring the older functionality (`false` by default) * Replaced instances of ABC command `refactor` with `drf -l` with new variable `SYNTH_ABC_LEGACY_REFACTOR` being set to `true` restoring the older functionality (`false` by default)
Also update the PDK to the respective version. This solves the OpenLane ABC issue: The-OpenROAD-Project/OpenLane#2051
~ Replace instances of ABC command
rewrite
withdrw -l
withSYNTH_ABC_LEGACY_REWRITE
being set to1
restoring the older functionality (0
by default)~ Replace instances of ABC command
refactor
withdrf -l
withSYNTH_ABC_LEGACY_REFACTOR
being set to1
restoring the older functionality (0
by default)~ Added
delete t:\$print
tosynth.tcl
to fix designs such as PPU with synthesized prints (as in Update Yosys, Add EQY/SBY efabless/openlane2#189)Original PR body follows:
Re Yosys commands: rewrite & refactor
These commands are considered obsolete and unmaintained by Yosys
Replacement commands exist in the form of: drw & drf
See also:
YosysHQ/yosys#4039
#1523
[ci ets]
Resolves #2052
Depends on efabless/openlane-ci-designs#3