Overview
Use the registered soc-openroad MCP server. Keep OpenROAD-flow-scripts and OpenROAD source trees independent from the SoC repository; store design-owned handoff files under pd/openroad/<platform>/<design>/.
Layout contract
Use this scheme for vibe_soc-style projects:
<project>/
└── pd/openroad/
├── <platform>/<design>/
│ ├── config.mk
│ └── constraint.sdc
└── work/ # ORFS logs/objects/reports/results; ignored by Git
Do not copy RTL into OpenROAD-flow-scripts. The generated config.mk points back to project RTL via $(PROJECT_ROOT)/... paths.
MCP tools
| Tool | Purpose |
|---|---|
soc_openroad_init |
generate portable ORFS config.mk and constraint.sdc from project filelists |
soc_openroad_run |
run an ORFS Make stage through the MCP process |
soc_openroad_status |
summarize ORFS result/report/log files under pd/openroad/work |
Workflow
- Ensure RTL/lint/synthesis handoff is already valid through
soc-build. - Call
soc_openroad_initwithproject_dir,module_dir,design_name, platform, clock/reset ports, and period. For a top-levelvibe_socrun, usemodule_dir=chip/top,design_name=vibe_soc_top,platform=nangate45. - Review generated
pd/openroad/<platform>/<design>/config.mkandconstraint.sdc. Fix clock/reset constraints from design requirements, not guesses. - Call
soc_openroad_runwithorfs_dir=<OpenROAD-flow-scripts>/flowandstage=synth|floorplan|place|cts|route|finish|all. - Call
soc_openroad_statusand record real report/result paths inpipeline_state.json.
OpenROAD execution must remain in the registered MCP tool. Do not replace it with direct shell make or openroad commands from a stage agent.