-
|
I'm trying to understand whether OpenROAD has a built-in ECO (Engineering Change Order) flow, or if this is primarily an OpenLane feature that uses OpenROAD commands underneath. What I've found: OpenLane has a documented ECO flow (link) that iteratively fixes hold violations by parsing timing reports, inserting buffers, resizing cells, and rerunning placement/routing until violations are gone. OpenROAD has individual commands like repair_timing -hold, repair_timing -setup, and repair_design that can perform ECO-like operations. I found a discussion about resizer refactoring My questions: Does OpenROAD itself have a documented ECO flow, or is OpenLane the primary tool for running ECO flows on top of OpenROAD? Are the repair_timing commands considered OpenROAD's ECO capability, or is there a higher-level ECO flow I'm missing? I'd appreciate any clarification about what exactly constitutes OpenROAD's native ECO capabilities versus flow-level features in OpenLane. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
OL is one flow that uses OR. OpenROAD-flow-scripts and siliconcompiler are others. OR provides the toolbox and the flow decides how to apply them. Are you looking for something specific? ECO capability can have various meanings. |
Beta Was this translation helpful? Give feedback.
You might read the section starting at https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/blob/df27ce67c722868238061fc9b9ce39b2a61356e3/flow/scripts/global_route.tcl#L51