cov-reader

Reads chip verification coverage databases from UCIS XML, Synopsys VDB, Cadence UCD, Siemens formats.

1|1|Updated Jun 15, 2023
One-click install
npx skills add https://github.com/Paradicat/demo --skill cov-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cov-reader
Source: https://github.com/Paradicat/demo/tree/main/agent_pack/skills/cov-reader
Command: npx skills add https://github.com/Paradicat/demo --skill cov-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the analysis of complex chip verification coverage databases, helping engineers identify and address verification gaps efficiently.

Core Features & Use Cases

  • Multi-format Support: Reads UCIS XML, Synopsys VDB, Cadence UCD, and Siemens UCDB.
  • Coverage Analysis: Provides detailed insights into line, toggle, branch, FSM, covergroup, and assertion coverage.
  • Use Case: When verification coverage reports show low scores in critical modules, use this Skill to pinpoint specific uncovered bins or signals and understand the root cause. It also supports a waiver system to exclude known untestable items.

Quick Start

Use the cov-reader skill to open the coverage database located at '/path/to/coverage.xml' and then display the overall summary.

Frequently Asked Questions about cov-reader

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

FAQPage Schema
How do I analyze chip verification coverage across different EDA vendor formats?

To analyze chip verification coverage across vendor formats, use a unified reader that ingests UCIS XML, Synopsys VDB, Cadence UCD, and Siemens UCDB, normalizing them into a single YAML format for consistent querying of line, toggle, branch, and FSM coverage metrics.

Can I identify coverage holes in specific hierarchy scopes of a VDB database?

Yes, you can identify coverage holes in specific hierarchy scopes of a VDB database by querying targeted scopes and analyzing uncovered bins or signals, helping pinpoint exact verification gaps and root causes within your design modules.

What is the best way to manage verification coverage waivers for untestable items?

The best way to manage verification coverage waivers for untestable items is through a unified YAML format that systematically excludes known untestable items, ensuring coverage reports accurately reflect genuine verification gaps without manual filtering.

Does this coverage analysis approach support both covergroup and assertion coverage types?

Yes, this coverage analysis approach supports detailed insights into both covergroup and assertion coverage types, alongside line, toggle, branch, condition, FSM, and expression coverage, providing a comprehensive view of chip verification completeness.

How do I navigate design hierarchy to query specific coverage scopes in a UCDB file?

To navigate design hierarchy and query specific coverage scopes in a UCDB file, utilize a coverage reader that supports hierarchical navigation, allowing you to drill down into modules and extract targeted coverage summaries for detailed analysis.