chipyard-pnr-docker

Run Chipyard RTL-to-GDS place-and-route flows in Docker containers.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xsw632/ChipAgent --skill chipyard-pnr-docker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chipyard-pnr-docker
Source: https://github.com/xsw632/ChipAgent/tree/main/skills/chipyard-pnr-docker
Command: npx skills add https://github.com/xsw632/ChipAgent --skill chipyard-pnr-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running Chipyard-generated RTL through the ORFS place-and-route flow traditionally requires local installation of complex EDA toolchains, manual SRAM macro replacement, and iterative parameter tuning to meet timing, area, and power targets — all of which are time-consuming and error-prone for hardware designers.

Core Features & Use Cases

  • Fully Dockerized Flow: No local Chipyard or ORFS installation required; all tool execution runs in managed Docker containers.
  • Adaptive Multi-Round PnR Tuning: Automatically adjusts clock period, utilization, and placement parameters over 3+ rounds to meet timing and routability goals.
  • Automated SRAM Macro Handling: Replaces behavioral SRAM stubs with sky130_sram macros to avoid out-of-memory errors during routing.
  • Use Case: A hardware engineer working on a RISC-V core can use this skill to generate a production-ready GDS layout for sky130hd in hours instead of days, without managing complex EDA dependencies.

Quick Start

Use the chipyard-pnr-docker skill to run a full place-and-route flow for your Chipyard RISC-V design and receive an optimized GDS layout with timing, area, and power reports.

Frequently Asked Questions about chipyard-pnr-docker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Chipyard RISC-V place-and-route flow without installing local EDA toolchains?

You can run the Chipyard RISC-V place-and-route flow entirely within Docker containers, eliminating the need for local Chipyard or ORFS installations. This approach manages all tool execution internally to produce optimized layout artifacts.

What is the best way to fix out-of-memory errors during sky130hd routing for RISC-V cores?

To fix out-of-memory errors during sky130hd routing, you can use automated SRAM macro handling. This process replaces behavioral SRAM stubs with sky130_sram macros before routing, preventing memory exhaustion and ensuring successful layout generation.

How does adaptive tuning work for achieving timing closure in ORFS place-and-route?

Adaptive tuning for timing closure works by automatically adjusting clock period, utilization, and placement parameters over multiple rounds. It iteratively compares results round-by-round to meet timing and routability goals for your design.

Do I need local OpenROAD or Chipyard installations to generate a GDS layout for sky130hd?

No, you do not need local OpenROAD or Chipyard installations to generate a GDS layout for sky130hd. The entire RTL-to-GDS place-and-route flow executes inside managed Docker containers without requiring local EDA dependencies.

Can I automate multi-clock constraint generation for Chipyard RISC-V designs in Docker?

Yes, you can automate multi-clock constraint generation for Chipyard RISC-V designs in Docker. The flow handles constraint generation automatically, alongside SRAM macro replacement and iterative parameter tuning, to produce final GDS, SPEF, and Verilog netlists.