Q: How do I reuse this flow for my own design?

Place your RTL under `designs/ /rtl/*.v`, add a minimal `config.tcl` under `designs/ /` defining `TOP_NAME` and `RTL_LIST`, then update the REST calls or `run_pipeline.sh` with `design=" "`. No other path hard‑coding is required.

Question 1

What are the prerequisites to run MCP‑EDA Example Flow?

Accepted Answer

Synopsys Design Compiler V‑2023.12‑SP2, Cadence Innovus 21.1, Python 3.9+, and the FreePDK45 (Nangate OpenCell v1.3) library, which is already included. Valid licenses for DC and Innovus are required.

Question 2

How do I run the full flow?

Accepted Answer

Execute `./run_pipeline.sh` from the root directory. It starts all eight REST services in order, calls their endpoints sequentially, and logs output to `./logs/`. A success message indicates a routed and saved GDS/V file.

Question 3

How can I tune parameters without editing TCL scripts?

Accepted Answer

Edit the CSV files in `config/` (e.g., `placement.csv`, `cts.csv`). At runtime the Python server picks a row by index, exports the values as environment variables, and the stage‑specific TCL scripts reference them via `$env(...)`. Change a CSV cell, commit, and rerun the affected stage.

Question 4

How do I reuse this flow for my own design?

Accepted Answer

Place your RTL under `designs//rtl/*.v`, add a minimal `config.tcl` under `designs//` defining `TOP_NAME` and `RTL_LIST`, then update the REST calls or `run_pipeline.sh` with `design=""`. No other path hard‑coding is required.

Question 5

What happens if a stage fails?

Accepted Answer

Each stage logs its full tool stdout to `logs/<stage>/` with timestamps. The REST services return error messages (e.g., “enc.dat not found”) and indicate the dependency that likely caused the failure. Check the appropriate log file to diagnose and fix the issue before retrying.

MCP‑EDA Example Flow

About MCP‑EDA Example Flow