debug-design

Diagnose failing HighTide designs by correlating build artifacts, logs, and configuration files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineers through debugging failing HighTide builds by systematically locating the failed stage, reading the relevant artifacts, and ensuring fixes stay within flow parameters rather than modifying the fixed benchmark RTL.

Core Features & Use Cases

  • Stage & artifact triage: Detects whether Bazel or Make was used, enumerates available results/logs, and identifies the last successful and first failed stages by inspecting ODB and log files.
  • Config-aware diagnosis: Reviews config.mk, constraint.sdc, BUILD.bazel, pdn.tcl, io.tcl, and sram definitions to understand flow parameters, timing constraints, pin placement, and FakeRAM usage.
  • Stage-specific remediation: Provides targeted guidance for synthesis, floorplan, placement, CTS, routing, and final timing/DRC reports while showing how to generate layout snapshots, heatmaps, and congestion images for better visualization.
  • Testing & verification: Suggests rerunning Make or Bazel flows after adjustments and comparing metrics like WNS, TNS, Fmax, and DRC counts before recommending the /optimize-ppa step.

Quick Start

Use the debug-design skill for asap7/lfsr when Bazel or Make reports a build failure so you can gather artifacts, identify the failed stage, and recommend flow-parameter fixes without touching RTL.

Frequently Asked Questions about debug-design

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

FAQPage Schema
How do I debug HighTide build failures without modifying the RTL source?

To debug HighTide build failures without touching RTL, correlate build artifacts, logs, and configuration files to identify synthesis, placement, or routing issues. You can then recommend targeted adjustments to config.mk, constraint.sdc, and pdn.tcl.

How do I locate the failed stage in a Bazel or Make HighTide flow?

Locate the failed stage in a Bazel or Make HighTide flow by inspecting stage-specific directories in bazel-bin or results. You can identify the last successful and first failed stages by reading ODB outputs and log summaries.

What HighTide configuration files should I check when synthesis or routing fails?

When synthesis or routing fails, check configuration files like config.mk, constraint.sdc, BUILD.bazel, pdn.tcl, and io.tcl. Reviewing these files helps understand flow parameters, timing constraints, pin placement, and FakeRAM settings.

How do I fix timing or DRC violations in an OpenROAD HighTide design?

Fix timing or DRC violations in an OpenROAD HighTide design by reviewing final timing and DRC reports, then adjusting flow parameters in constraint.sdc or pdn.tcl. You can generate layout snapshots and congestion images to visualize issues before rerunning the flow.

Can I use this approach to debug both Bazel and legacy Make HighTide builds?

Yes, you can use this diagnostic approach for both Bazel and legacy Make HighTide builds. The process detects which build system was used, enumerates available results and logs, and inspects the corresponding stage-specific directories to read ODB outputs.