hi, I wonder what is the relation, of differences ...
# general
b
hi, I wonder what is the relation, of differences between siliconcompiler (https://github.com/siliconcompiler/siliconcompiler) and openroad, openlane? Is there anyone here used both or know about the concept differences? I am studying and had tape-out with openlane flow, but wonder about siliconcompiler and started to read about it. I have seen a project which generated gds with siliconcompiler in mpw-7, is it easier and faster than the openlane approach? in siliconcompiler github page in supported technologies it seems both approach are similar if not same related to the utilization of tools and infrastructures such as Yosys, OpenROAD, VPR, nextpnr, klayout, magic, sky130 any idea is appreciated, thanks in advance
m
openlane & silicon compiler are both EDA flows utilizing multiple EDA tools. Openroad is such a tool used by both flows (as is yosys)
Openroad-flow-scripts is a third such flow.
Silicon compiler can also run proprietary tools as well as open source ones so it is a bit of a bridge for those who care. It has a nice architecture but I'm more of a tool developer than user so I'll leave it to others to comment.
a
Well said @Matt Liberty. I generated my gds using siliconcompiler for mpw-7. Works well with flat design flows. I’d say if your looking to do any hierarchical flow or customization to your physical design look elsewhere as this tool will require you to modify the generated .tcl that it calls openRoad with. In other words if your looking for a fast solution you can cut out the siliconcompiler and work directly with the open-source tools that siliconcompiler uses.
m
Berkeley's chipyard is a fourth such flow (https://github.com/ucb-bar/chipyard/blob/main/docs/VLSI/Sky130-OpenROAD-Tutorial.rst) though I haven't seen any mpws using it