openlane-sky130-flowlisted
Install: claude install-skill Premchand006/AI-assistant-skills
# OpenLane 2 on Sky130
A full run takes minutes to hours and most failed runs die in the first minute
on something a file check would have caught. So: validate the config, run with
a narrow scope, read the metrics, change one thing at a time.
## Before starting a run
```bash
python3 scripts/check_config.py config.json --pdk-root ~/.volare
```
This checks the things that cost a whole run when wrong: paths that do not
resolve, a `CLOCK_PORT` that is not a port of the RTL, a PDK family name where
a variant is needed, a utilisation the router will not survive, and `DIE_AREA`
set without `FP_SIZING: "absolute"`, which silently does nothing.
A minimum viable config, with the parts that matter:
```json
{
"meta": { "version": 2 },
"DESIGN_NAME": "my_design",
"VERILOG_FILES": ["dir::src/my_design.v"],
"CLOCK_PORT": "clk",
"CLOCK_PERIOD": 20,
"PDK": "sky130A",
"FP_CORE_UTIL": 40
}
```
Three details that account for a large share of first-run failures:
- `dir::` resolves paths against the config file. A bare relative path resolves
against the working directory, so the run breaks the first time someone
starts it from somewhere else.
- `PDK` takes a variant (`sky130A`), not a family (`sky130`).
- `CLOCK_PORT` has to be a real port of the top module. If it is not, static
timing runs with no clock, every path passes, and you find out at sign-off.
A fuller starting config with the reasoning inline is in
[references/config-template.json](references/config-template