analog-hw-tuning-loop

Iterates SPICE sizing, hardware build, and measurement until analog hardware matches simulation and spec.

26|8|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/vibeic/vibe-ic --skill analog-hw-tuning-loop-vibeic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analog-hw-tuning-loop
Source: https://github.com/vibeic/vibe-ic/tree/main/vibe-ic-marketplace/plugins/vibe-ic/skills/analog-hw-tuning-loop
Command: npx skills add https://github.com/vibeic/vibe-ic --skill analog-hw-tuning-loop-vibeic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Analog designs that converge in SPICE simulation often fail on real hardware due to model inaccuracies, and manually reconciling simulation, bench measurements, and spec targets is slow and error-prone. This Skill closes that loop by orchestrating a two-phase convergence process that validates SPICE results against physical measurements. ## Core Features & Use Cases - Two-phase convergence: First converges sizing in SPICE across all PVT corners, then validates on real hardware with a maximum of 3 hardware iterations. - Three-way verdict logic: Compares SPICE-vs-spec, hardware-vs-spec, and hardware-vs-SPICE discrepancy to produce CONVERGED, CONVERGED_WARNING, MODEL_INACCURACY, or BACK_TO_PHASE1 verdicts enforced by deterministic checker programs. - Human-in-the-loop bench setup: Generates FPGA stimulus, displays the component BOM and wiring diagram, and waits for user confirmation before capturing scope and ADC measurements. - Use Case: After an LDO design passes simulation, use this Skill to program a DE10-Lite FPGA, build the breadboard circuit, measure output voltage, and iterate component sizing until hardware readings fall within spec and within 20% of SPICE predictions. ## Quick Start Tune the LDO on hardware using the converged sizing in analog/ldo_1v8/sizing_final.json and verify the bench measurements against the SPICE results.

Frequently Asked Questions about analog-hw-tuning-loop

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

FAQPage Schema
How do I verify an analog design on real hardware after SPICE simulation?▼

Run a two-phase loop: first converge sizing in SPICE across all PVT corners, then generate FPGA stimulus, build the breadboard circuit, and capture scope and ADC measurements. Compare hardware readings against both SPICE predictions and the spec each iteration.

What is hardware-in-the-loop tuning for analog circuits?▼

Hardware-in-the-loop tuning iterates between simulation and physical measurement until hardware, SPICE, and spec agree. Each cycle programs an FPGA for stimulus, measures the real circuit, and adjusts one component per iteration based on a three-way comparison verdict.

How many hardware iterations are allowed before escalating?▼

The loop caps hardware iterations at 3, enforced by a checker program. If convergence is not reached, the issue is escalated as a model-accuracy problem rather than continuing to iterate, and only one component may be adjusted per iteration.

What happens when hardware measurements disagree with SPICE results?▼

If hardware is in spec but differs from SPICE by 20% or more, the verdict is CONVERGED_WARNING indicating a model-accuracy concern. If hardware is out of spec while SPICE passes, the verdict is MODEL_INACCURACY, requiring added margin, re-simulation, and re-measurement.

When should I not use a hardware tuning loop?▼

Do not start hardware tuning before the design has fully converged in SPICE simulation across all PVT corners. Skipping Phase 1 wastes bench time, since a FAIL on SPICE-vs-spec routes the flow back to simulation-only convergence.