sdc-sta

Provide OpenSTA and SDC command syntax for static timing constraints.

36|13|Updated Jun 8, 2025
One-click install
npx skills add https://github.com/VLSIDA/HighTide --skill sdc-sta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdc-sta
Source: https://github.com/VLSIDA/HighTide/tree/main/.claude/skills/sdc-sta
Command: npx skills add https://github.com/VLSIDA/HighTide --skill sdc-sta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Static timing designers often struggle to remember the exact OpenSTA and SDC syntax needed to constrain paths, define clocks, and debug unconstrained endpoints, so this reference provides the missing command-level clarity.

Core Features & Use Cases

  • Detailed Command Coverage: Summaries of create_clock, set_input_delay, set_false_path, report_checks, set_timing_derate, and other timing commands keep every argument and option at hand while editing SDC files or Tcl scripts.
  • Authoritative References: Links to refs OpenSTA pdf, Sta.tcl, Variables.tcl, Property.tcl, and CmdArgs.tcl help you verify how commands and filters behave within OpenROAD and OpenSTA flows.
  • Use Case: When setting up multi-corner, multi-mode analysis, consult this skill to find scene definitions, report_checks flags, and filter expressions that catch unconstrained endpoints or disabled paths.

Quick Start

Request the arguments for a timing command such as create_clock while specifying the target port and desired period.

Frequently Asked Questions about sdc-sta

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

FAQPage Schema
How do I use OpenSTA commands to constrain timing paths in SDC files?

You use OpenSTA commands like create_clock, set_input_delay, and set_false_path to define clocks, constrain paths, and set timing exceptions in SDC files for static timing analysis.

What is the correct report_checks syntax for filtering unconstrained endpoints in OpenROAD?

The report_checks command in OpenSTA uses filter expressions and specific flags to catch unconstrained endpoints or disabled paths during multi-corner multi-mode timing analysis.

How do I set up multi-corner multi-mode static timing analysis using OpenSTA Tcl commands?

You set up multi-corner multi-mode analysis in OpenSTA by defining scene definitions, applying set_timing_derate, and using report_checks flags with filter expressions within your Tcl flow.

Can I use OpenSTA SDC command references for debugging unconstrained timing endpoints?

Yes, OpenSTA SDC command references clarify command arguments, filters, and variables for debugging unconstrained endpoints, verifying behavior using Sta.tcl and Variables.tcl documentation.

What are the limitations of using OpenSTA command references for complex timing constraints?

The OpenSTA command reference focuses on syntax and argument clarification for timing constraints, serving as a lookup guide rather than a tool that automatically generates or validates complete SDC files.

Why does set_input_delay require specific arguments when defining timing constraints in OpenROAD?

The set_input_delay command requires exact arguments for target ports and clock references to properly constrain input paths, and the OpenSTA reference clarifies these required options for Tcl scripts.