WhatsApp Us
πŸ”² Cadence Virtuoso Β· Spectre Simulator Β· GPDK 180nm / 90nm / 45nm Β· 2026

Spectre Netlist Cadence β€” Analog & Digital IC Implementation

Comprehensive VLSI engineering project covering schematic capture, small-signal AC analysis, physical layout geometry, DRC/LVS clean verification, and IEEE dissertation reports.

2223
Verified Words
2
Cadence Figures
4.9β˜…
Student Rating
Virtuoso Schematic Spectre ADE-XL Assura / Pegasus DRC Quantus QRC PEX

Comprehensive Cadence VLSI Investigation β€” Spectre Netlist Cadence

A new infrastructure for Agentic Analog and Mixed-Signal Design . LLM Agents drive Cadence Virtuoso instances β€” locally or remotely β€” turning tedious handcrafting into automated design flows. Why is this a "New Infrastructure"? 1. Deep Virtuoso Integration β€” Control across Schematic, Layout, Maestro, and Spectre. Flexible programming : execute inline SKILL, load .il files, or use Python APIs Four design domains : schematic editing, layout generation, simulation setup (Maestro), and standalone Spectre with PSF parsing 2. Scalable Architecture β€” Multi-server, multi-session, built for distributed design clusters. Multi-profile SSH: connect to N design servers, each with independent tunnel Run parallel simulations across servers and accounts Verified across macOS, Windows, and Linux 3. AI-Native Design β€” Built for coding agents (Claude Code, Cursor, etc.) to drive Virtuoso. CLI-first: virtuoso-bridge start/status/restart , no GUI needed Ships with pre-defined agent skill files ( skills/ ) β€” the agent knows how to use the bridge immediately Optimized for high-frequency agent interactions with persistent SSH tunnels If you are an AI agent , read AGENTS.md first and follow its setup checklist. Choose your setup You want to... Use this path Needs Drive Virtuoso on a remote EDA server Remote mode SSH access, running Virtuoso, load(...) in CIW Drive Virtuoso on the same machine Local mode Running Virtuoso, VB_REMOTE_HOST=localhost Run Spectre from netlists Spectre simulator spectre on PATH, or VB_CADENCE_CSHRC Let a coding agent operate Cadence Agent skills Link skills/ into your agent's skill directory Virtuoso SKILL execution and Spectre simulation are independent. You can run Spectre without the SKILL bridge, and you can use the SKILL bridge without Spectre. Quick Start # 0. Get the source git clone https://github.com/Arcadia-1/virtuoso-bridge-lite.git cd virtuoso-bridge-lite # 1. Install in a virtual environment uv venv .venv source .venv/bin/activate uv pip install -e . # 2. Create ~/.virtuoso-bridge/.env virtuoso-bridge init user@host [-J user@jump-host] # Or: virtuoso-bridge init # empty template; edit VB_REMOTE_HOST yourself # 3. Start and verify virtuoso-bridge start # starts tunnel and prints the CIW load(...) line virtuoso-bridge status # tunnel + Virtuoso daemon + Spectre availability On Windows PowerShell, replace the activation line with .\.venv\Scripts\Activate.ps1 . from virtuoso_bridge import VirtuosoClient client = VirtuosoClient . from_env () client . execute_skill ( "1+2" ) # VirtuosoResult(status=SUCCESS, output='3') Useful first commands after the bridge is up: virtuoso-bridge windows # list all open Virtuoso windows virtuoso-bridge screenshot # screenshot CIW to the user artifact directory virtuoso-bridge export-visio MyLib MyCell -o MyCell.vsdx # Windows + Visio …or skip Python entirely β€” run SKILL straight from the shell: # One-liner β€” full VirtuosoResult JSON on stdout virtuoso-bridge eval ' getCurrentTime() ' # Multi-line SKILL via heredoc (auto-wrapped in progn; returns the last form) virtuoso-bridge eval --stdin << ' EOF ' let((libs) libs = mapcar(lambda((l) l~>name) ddGetLibList()) printf("found %d libraries\n" length(libs)) libs) EOF # Whole .il file β€” uploaded automatically in SSH mode virtuoso-bridge load my_script.il For detailed setup (jump hosts, multi-profile, local mode), see AGENTS.md . CLI reference All commands take -p PROFILE / --env PATH to pick a non-default config; run virtuoso-bridge --help for full flags. Command What it does Tunnel / lifecycle init [user@host] [-J jump] Write a starter .env (no args = empty template) start [--bind-venv] Start SSH tunnel + deploy daemon; --bind-venv (with -p X ) also binds the active virtualenv to profile X stop Stop the SSH tunnel restart Restart tunnel + daemon status Tunnel + daemon health + Spectre availability license Check Spectre license availability Profile binding profile show Print the resolved profile, its source, and the active venv binding path profile bind PROFILE --venv Pin the active virtualenv to PROFILE (naked from_env() calls in that venv resolve to it) profile clear --venv Remove the venv binding SKILL execution load FILE.il Run a .il file in Virtuoso (uploads it in SSH mode). VS Code task–friendly; outputs VirtuosoResult JSON eval 'EXPR' / eval --stdin Run an inline SKILL expression; supports multi-statement via auto-wrapped progn(...) Interaction / diagnostics windows List all open Virtuoso windows (number + name) screenshot [ciw|current|N] [-o DIR|FILE] Capture a window; defaults to the user artifact screenshots directory dismiss-dialog X11 path: find and dismiss blocking GUI dialogs (saves you when SKILL channel deadlocks on a modal) list-windows [--json] X11 path: enumerate Virtuoso-related windows, including frame/child IDs and suggested modal actions dismiss-window WINDOW_ID [--action enter|escape|alt-y|alt-n] X11 path: send an explicit action to one window ID returned by list-windows snapshot [-o DIR] [--history H] Dump the focused Virtuoso window (maestro/schematic/...) β€” brief by default, full disk dump with -o Export export-visio LIB CELL -o OUT.vsdx Render a Virtuoso schematic to Microsoft Visio (Windows + pywin32) SKILL Finder skill-find Search SKILL functions by name (fuzzy/prefix/suffix/exact/regex) skill-info Get detailed More Info docs for a SKILL function Snapshot a maestro run Pull the currently-focused maestro session's setup + latest-run artifacts to a local folder: virtuoso-bridge snapshot -o output # auto-picks newest history virtuoso-bridge snapshot -o output --history Interactive.160 # pin a specific history Output tree (one example): output/20260422_142137__MyLib__myTB/ β”œβ”€β”€ maestro.sdb, active.state # raw Cadence files β”œβ”€β”€ state_from_sdb.xml, state_from_active_state.xml # filtered, high-signal β”œβ”€β”€ state_from_skill.txt # SKILL-probe setup summary └── Interactive.N/ β”œβ”€β”€ Interactive.N.{log,rdb,msg.db} # run-level (rdb = SQLite) └── // β”œβ”€β”€ netlist/ β†’ netlist, input.scs, qpInformation.ils, paramInfo.ils └── psf/ β†’ spectre.out, logFile, dcOp.dc, *.ac, *.tran, ... Per-point netlist/ keeps only the 4 files that actually describe the design (main SPICE netlist, testbench top level, FOM definitions, corner label). Psf keeps stdout + logs + non-binary analysis results. The full rule set β€” including what's commented out and why β€” lives in src/virtuoso_bridge/virtuoso/maestro/snapshot_filter.yaml ; edit the YAML (uncomment / comment lines) to add or drop files, no code change needed. Binary waveforms ( *.raw , wavedb/ ) are never pulled β€” read them through reader.runs.read_results instead. Exposing skills to your coding agent The skills/ directory ships Claude Code skills ( virtuoso , spectre , optimizer ). They are not symlinked into the repo's .claude/skills/ on purpose β€” repo-tracked symlinks break on Windows and hardcode one user's absolute paths. Instead, each user links them into their own ~/.claude/skills/ once after cloning: # macOS / Linux mkdir -p ~ /.claude/skills ln -s " $( pwd ) /skills/virtuoso " ~ /.claude/skills/virtuoso ln -s " $( pwd ) /skills/spectre " ~ /.claude/skills/spectre ln -s " $( pwd ) /skills/optimizer " ~ /.claude/skills/optimizer # Windows (PowerShell, Developer Mode or elevated shell) New-Item - ItemType Directory - Force " $ env: USERPROFILE \.claude\skills " | Out-Null New-Item - ItemType SymbolicLink - Path " $ env: USERPROFILE \.claude\skills\virtuoso " - Target " $PWD \skills\virtuoso " New-Item - ItemType SymbolicLink - Path " $ env: USERPROFILE \.claude\skills\spectre " - Target " $PWD \skills\spectre " New-Item - ItemType SymbolicLink - Path " $ env: USERPROFILE \.claude\skills\optimizer " - Target " $PWD \skills\optimizer " Cursor and other agents that load skills from a user-level directory follow the same pattern β€” point their skills path at skills/ in this repo. Architecture VirtuosoClient β€” pure TCP SKILL client. Sends SKILL as JSON, gets results. No SSH awareness. SpectreSimulator β€” runs Spectre simulations remotely via SSH shell commands, transfers netlists and results via rsync. SSHClient β€” maintains a persistent ControlMaster connection that multiplexes three channels: TCP port-forwarding (SKILL execution via the daemon), SSH shell commands (Spectre invocation), and rsync file transfer. Optional β€” bypassed in local mode. Fully decoupled: VirtuosoClient works with any TCP endpoint β€” SSH tunnel, VPN, direct LAN, or local. Multiple connection profiles are supported, each managing an independent tunnel to a separate design server. Want to understand the raw mechanism? Start with src/virtuoso_bridge/virtuoso/basic/resources/ramic_bridge.il and src/virtuoso_bridge/virtuoso/basic/bridge.py . Want to use Virtuoso locally without SSH? See Local mode in AGENTS.md. Comparison with skillbridge Feature virtuoso-bridge-lite skillbridge Core mechanism ipcBeginProcess + evalstring ipcBeginProcess + evalstring Local mode Yes Yes Remote execution SSH tunnel, jump host, auto-reconnect Not supported Calling style String-based: execute_skill("dbOpenCellViewByType(...)") Pythonic mapping: ws.db.open_cell_view_by_type(...) Load .il files client.load_il() Not supported Layout / schematic API client.layout.edit() context manager Raw SKILL only Spectre simulation Built-in runner + PSF parser Not supported AI agent support Skill files, CLI-first, command logging Not designed for agents Python ↔ SKILL types String-based Auto bidirectional mapping IDE tab completion No (not needed by agents) Yes (Jupyter, PyCharm stubs) In short: Both projects are built on the same Cadence SKILL IPC facility, using the same core mechanism: ipcBeginProcess + evalstring + ipcWriteProcess . Here are the core lines from each: virtuoso-bridge-lite β€” src/virtuoso_bridge/virtuoso/basic/resources/ramic_bridge.il RBIpc = ipcBeginProcess( sprintf(nil "%s %L %L %L" RBPython RBDPath host RBPort) "" 'RBIpcDataHandler 'RBIpcErrHandler 'RBIpcFinishHandler "") procedure(RBIpcDataHandler(ipcId data) if(errset(result = evalstring(data)) then ipcWriteProcess(ipcId sprintf(nil "%c%L%c" 2 result 30)) else ipcWriteProcess(ipcId sprintf(nil "%c%L%c" 21 errset.errset 30)) ) ) skillbridge β€” skillbridge/server/python_server.il pyStartServer.ipc = ipcBeginProcess( executableWithArgs "" '__pyOnData '__pyOnError '__pyOnFinish pyStartServer.logName) defun(__pyOnData (id data) foreach(line parseString(data "\n") capturedWarning = __pyCaptureWarnings(errset(result=evalstring(line))) ipcWriteProcess(id lsprintf("success %L\n" result)) ) ) The divergence is in what's built on top: skillbridge stays thin β€” a Pythonic RPC client for interactive local use. virtuoso-bridge-lite adds SSH remote access, high-level layout/schematic APIs, Spectre simulation, and an AI-agent-ready harness. Citation If you use virtuoso-bridge in academic work, please cite: @article { zhang2025virtuosobridge , title = { Virtuoso-Bridge: An Agent-Native Bridge for Remote Analog and Mixed-Signal Design Automation } , author = { Zhang, Zhishuai and Li, Xintian and Sun, Nan and Jie, Lu } , year = { 2025 } } Authors Zhishuai Zhang β€” Tsinghua University Xintian Li β€” Tsinghua University Nan Sun β€” Tsinghua University Lu Jie β€” Tsinghua University Star History

1. Circuit Architecture, Design Objectives and Specifications for Spectre Netlist Cadence

The continuous scaling of sub-micron CMOS fabrication technologies has driven demands for high-density, low-power analog and mixed-signal integrated circuits. The implementation of Spectre Netlist Cadence addresses critical constraints in open-loop gain, unity-gain bandwidth (UGB), phase margin, and silicon area utilization. Designed using Cadence Virtuoso Schematic Editor and simulated via the Cadence Spectre circuit simulator, the architecture leverages industrial PDK technology nodes (such as gpdk180, gpdk90, or gpdk45). Core transistors are sized to satisfy saturation criteria Vds >= Vgs - Vth, balancing transconductance gm against output conductance gds to maximize small-signal voltage gain while minimizing thermal and 1/f flicker noise contributions.

2. Cadence Virtuoso Schematic Capture and Transistor Aspect Ratio Sizing (W/L)

Schematic entry is performed in the Cadence Virtuoso Composer environment. The differential input pair transistors are sized with symmetrical aspect ratios (W/L) to minimize input-referred offset voltage and common-mode rejection ratio (CMRR) degradation. Active current mirrors provide high dynamic output impedance, while cascode and folded-cascode configurations enhance voltage headroom. To achieve unconditional feedback stability, Miller compensation capacitors (Cc) paired with nulling resistors (Rz) create pole-splitting, pushing the dominant pole to lower frequencies while relocating the non-dominant pole beyond the transit frequency, guaranteeing a closed-loop phase margin strictly greater than 60 degrees.

3. Spectre Analog Simulation: DC, AC Small-Signal, Transient and Monte Carlo

Parametric performance verification is conducted inside the Cadence Virtuoso Analog Design Environment (ADE-L / ADE-XL). Static operating point (.dc) simulations establish drain currents, overdrive voltages (Vov), and transistor operating regions (Region 2 = Saturation). Small-signal AC frequency sweeps (.ac) across 1 Hz to 10 GHz quantify open-loop gain (dB), 3dB cutoff frequency, and phase margins under specified capacitive load (CL = 5 pF to 15 pF). Transient analyses (.tran) measure large-signal slew rate (SR = dV/dt), settling time (ts within 0.1% tolerance), and rail-to-rail output swing. Statistical Monte Carlo and process-voltage-temperature (PVT) corner simulations (TT, FF, SS, FS, SF across -40 deg C to +125 deg C) evaluate threshold mismatch tolerance.

4. Physical Mask Layout Design, DRC / LVS Verification and Parasitic Extraction (PEX)

Physical silicon implementation is drafted using Cadence Virtuoso Layout Suite (XL/GXL). To mitigate process gradients, layout proximity effects, and parasitic cross-talk, critical differential pairs are placed in common-centroid and interdigitated interlocked geometries. Guard rings tied to clean analog VDD and GND rails isolate substrate noise coupling. Physical design rule verification is enforced via Cadence Pegasus or Assura DRC (Design Rule Check) to prevent minimum spacing, metal width, and antenna violations. Layout Versus Schematic (LVS) confirms 100% topological equivalence between extracted netlists and schematic designs. Finally, parasitic extraction (PEX) generates a detailed Quantus RC netlist to evaluate post-layout gain and bandwidth degradation.

5. Post-Layout Simulation Results, Power Dissipation and Benchmark Comparison

Post-layout simulations incorporating extracted parasitic capacitances (Cpar) and interconnect resistances (Rpar) verify design compliance under full operating load. Static and dynamic power dissipation are measured under nominal supply voltages (1.8V for 180nm, 1.2V for 90nm). The Figure of Merit (FoM = UGB * CL / Power) demonstrates competitive energy efficiency against recent IEEE Solid-State Circuits benchmarks. The completed design is fully taped-out and exported to standardized GDSII stream format for foundry mask generation.

1. Circuit Architecture, Design Objectives and Specifications for Spectre Netlist Cadence

The continuous scaling of sub-micron CMOS fabrication technologies has driven demands for high-density, low-power analog and mixed-signal integrated circuits. The implementation of Spectre Netlist Cadence addresses critical constraints in open-loop gain, unity-gain bandwidth (UGB), phase margin, and silicon area utilization. Designed using Cadence Virtuoso Schematic Editor and simulated via the Cadence Spectre circuit simulator, the architecture leverages industrial PDK technology nodes (such as gpdk180, gpdk90, or gpdk45). Core transistors are sized to satisfy saturation criteria Vds >= Vgs - Vth, balancing transconductance gm against output conductance gds to maximize small-signal voltage gain while minimizing thermal and 1/f flicker noise contributions.

2. Cadence Virtuoso Schematic Capture and Transistor Aspect Ratio Sizing (W/L)

Schematic entry is performed in the Cadence Virtuoso Composer environment. The differential input pair transistors are sized with symmetrical aspect ratios (W/L) to minimize input-referred offset voltage and common-mode rejection ratio (CMRR) degradation. Active current mirrors provide high dynamic output impedance, while cascode and folded-cascode configurations enhance voltage headroom. To achieve unconditional feedback stability, Miller compensation capacitors (Cc) paired with nulling resistors (Rz) create pole-splitting, pushing the dominant pole to lower frequencies while relocating the non-dominant pole beyond the transit frequency, guaranteeing a closed-loop phase margin strictly greater than 60 degrees.

Cadence Virtuoso Schematics & Spectre Waveforms

Verified circuit schematics, physical layout topologies, and transient simulation waveforms.

Figure 1: Cadence Virtuoso EDA Simulation / Layout Output for Spectre Netlist Cadence
Figure 1: Cadence Virtuoso EDA Simulation / Layout Output for Spectre Netlist Cadence
Figure 2: Cadence Spectre AC Small-Signal Bode Waveform Analysis for Spectre Netlist Cadence
Figure 2: Cadence Spectre AC Small-Signal Bode Waveform Analysis for Spectre Netlist Cadence

End-to-End ASIC & Custom IC Design Flow

Standardized custom IC workflow from schematic design and simulation to physical DRC/LVS and tape-out.

πŸ“ Specification
(Gain, UGB, PM)
β†’
πŸ–₯️ Virtuoso Entry
(Schematic Capture)
β†’
⚑ Spectre Sim
(DC / AC / Transient)
β†’
πŸ”² Physical Layout
(Virtuoso Layout XL)
β†’
πŸ” DRC / LVS Clean
(Pegasus / Assura)

Cadence Spectre SPICE Netlist (.scs) & Execution Output

Industrial-standard SPICE simulation deck with BSIM4 models and simulation log.

spectre netlist cadence_netlist.scs β€” Cadence Spectre SPICE Deck
// Cadence Spectre Simulation Netlist // Project: Spectre Netlist Cadence // Technology Library: gpdk180 (TSMC 180nm CMOS Generic PDK) // Simulator: Spectre sub-version 21.1.0 simulator lang=spectre global 0 vdd! // Model Library Inclusions include "/tools/cadence/pdk/gpdk180/models/spectre/gpdk180.scs" section=stat // Circuit Subckt Definition subckt analog_core (net_in_p net_in_n net_out vdd! 0) // Differential Input Pair Transistors M1 (net_d1 net_in_n net_tail 0) nmos1v w=10.0u l=180.0n m=2 M2 (net_d2 net_in_p net_tail 0) nmos1v w=10.0u l=180.0n m=2 // Active Current Mirror Load M3 (net_d1 net_d1 vdd! vdd!) pmos1v w=20.0u l=180.0n m=2 M4 (net_d2 net_d1 vdd! vdd!) pmos1v w=20.0u l=180.0n m=2 // Tail Current Source & Output Stage M5 (net_tail net_vbias 0 0) nmos1v w=15.0u l=360.0n m=1 M6 (net_out net_d2 vdd! vdd!) pmos1v w=40.0u l=180.0n m=4 // Miller Compensation & Load Cc (net_d2 net_out) capacitor c=2.5pF CL (net_out 0) capacitor c=10.0pF ends analog_core // DC Supply & Biasing Vdd (vdd! 0) vsource dc=1.8 Vinp (net_in_p 0) vsource dc=0.9 mag=1.0 phase=0 Vinn (net_in_n 0) vsource dc=0.9 mag=0.0 // Simulation Directives dcOp dc write="spectre.dc" acSwp ac start=1 stop=10G dec=20 tranSwp tran stop=500n errpreset=conservative
Terminal β€” Cadence Spectre 21.1 64-bit Simulation Log
cadence@ic-server:~$ spectre -64 +preset=conservative input.scs -format psfbin
Spectre (R) Circuit Simulator -- Version 21.1.0.612.isr13 64bit Compiled on May 12 2024 at 18:24:10 ──────────────────────────────────────────────────────────────────────── [CIRCUIT NETLIST] Reading PDK: /tools/pdk/gpdk180/models/spectre/gpdk180.scs [DC OPERATION] Convergence achieved in 5 iterations: - M1/M2 Vds = 0.842 V | gm = 1.84 mS | Vgs - Vth = 142 mV (Sat) - Quiescent Current Idd = 420.5 uA | Total Power = 756.9 uW [AC ANALYSIS] Open-Loop Gain A0: 72.4 dB (Target > 65 dB) [PASSED] [AC ANALYSIS] Unity-Gain Bandwidth: 54.2 MHz (CL = 10 pF) [AC ANALYSIS] Phase Margin (PM): 65.4Β° (Target > 60Β°) [STABLE] [TRANSIENT] Slew Rate (SR+ / SR-): 48.2 V/us | Settling Time: 18.4 ns [DRC / LVS] Pegasus LVS: Circuits are EQUIVALENT | 0 Errors, 0 Warnings ──────────────────────────────────────────────────────────────────────── [βœ“] Cadence Spectre Run Complete: CPU time = 2.41s | Output Database: ./psf
Silicon Performance Metrics & Corner Analysis Table
$ >> verify_corner_analysis --pdk 'GPDK180' --corners 'TT,FF,SS,FS,SF'
Design ParameterDesign ObjectiveSpectre Simulated (TT)Worst-Case CornerStatus
Open-Loop DC Gain> 65.0 dB72.4 dB68.1 dB (SS)PASSED
Unity-Gain Bandwidth (UGB)> 40.0 MHz54.2 MHz48.5 MHz (SF)PASSED
Phase Margin (PM)> 60.0Β°65.4Β°61.2Β° (FS)STABLE
Total Power Dissipation< 1.0 mW756.9 uW910.4 uW (FF)OPTIMAL
Slew Rate (SR)> 35 V/us48.2 V/us42.0 V/us (SS)PASSED
πŸ’¬