• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. Generating an ICCR output report with cumulative coverage...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 13416
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Generating an ICCR output report with cumulative coverage metrics

danlarkin
danlarkin over 16 years ago

Hi,

I'm using ICCR (6.20-s004)  and I'm trying to generate an output text or html report with cumulative block and expression coverage listed. When I use report_tabular_summary -instance <module_name>... or report_html -instance <module_name>... I seem to be getting the coverage metrics for each individual module in the hierarchy thats specified. This is almost what I want, but I'd like to be able to see the cumulative coverage details at each level of the hierarchy too.

Now I tried report_summary -module <module_name>  and that gives me the the cumulative coverage figures that I want, but this type of report doesn't list the submodules (short of generating -module reports for all the blocks thats of interest).

Am I missing something in the documentation? (and I'd really rather not use the gui)

 

  • Cancel
  • Mickey
    Mickey over 16 years ago

     Hi Dan,

     I believe what you are looking for can be found in the report_summary output.  Try using "report_summary -instance -be *..."

     The resultant output will be similar to the following snippet:

    cpu_test
    --------------------------------------------------
    B:  100% (4/4)           BC:   75% (92/122)
    E:   --% (0/0)           EC:   51% (104/204)

      cpu_test.cgen
      --------------------------------------------------
      B:  100% (6/6)           BC:  100% (6/6)
      E:  100% (8/8)           EC:  100% (8/8)

      .cpu1
      --------------------------------------------------
      B:   --% (0/0)           BC:   73% (41/56)
      E:  100% (8/8)           EC:   49% (48/98)

        cpu_test.cpu1.ac
        --------------------------------------------------
        B:   75% (6/8)           BC:   75% (6/8)
        E:   60% (3/5)           EC:   60% (3/5)

        .ir
        --------------------------------------------------
        B:  100% (8/8)           BC:  100% (8/8)
        E:   80% (4/5)           EC:   80% (4/5)

        .pc
        --------------------------------------------------
        B:   80% (4/5)           BC:   80% (4/5)
        E:  100% (2/2)           EC:  100% (2/2)

        .alu1
        --------------------------------------------------
        B:   38% (5/13)          BC:   38% (5/13)
        E:   11% (1/9)           EC:   11% (1/9)

        .u3
        --------------------------------------------------
        B:   --% (0/0)           BC:   --% (0/0)
        E:   67% (2/3)           EC:   67% (2/3)

        .smx
        --------------------------------------------------
        B:   --% (0/0)           BC:   --% (0/0)
        E:   75% (3/4)           EC:   75% (3/4)

        .mem1
        --------------------------------------------------
        B:    0% (0/1)           BC:    0% (0/1)
        E:   33% (1/3)           EC:   33% (1/3)

        .cntl
        --------------------------------------------------
        B:   86% (18/21)         BC:   86% (18/21)
        E:   41% (24/59)         EC:   41% (24/59)

      cpu_test.cpu2
      --------------------------------------------------
      B:   --% (0/0)           BC:   73% (41/56)
      E:  100% (8/8)           EC:   49% (48/98)

        cpu_test.cpu2.ac
        --------------------------------------------------
        B:   75% (6/8)           BC:   75% (6/8)
        E:   60% (3/5)           EC:   60% (3/5)

        .ir
        --------------------------------------------------
        B:  100% (8/8)           BC:  100% (8/8)
        E:   80% (4/5)           EC:   80% (4/5)

        .pc
        --------------------------------------------------
        B:   80% (4/5)           BC:   80% (4/5)
        E:  100% (2/2)           EC:  100% (2/2)

        .alu1
        --------------------------------------------------
        B:   38% (5/13)          BC:   38% (5/13)
        E:   11% (1/9)           EC:   11% (1/9)

        .u3
        --------------------------------------------------
        B:   --% (0/0)           BC:   --% (0/0)
        E:   67% (2/3)           EC:   67% (2/3)

        .smx
        --------------------------------------------------
        B:   --% (0/0)           BC:   --% (0/0)
        E:   75% (3/4)           EC:   75% (3/4)

        .mem1
        --------------------------------------------------
        B:    0% (0/1)           BC:    0% (0/1)
        E:   33% (1/3)           EC:   33% (1/3)

        .cntl
        --------------------------------------------------
        B:   86% (18/21)         BC:   86% (18/21)
        E:   41% (24/59)         EC:   41% (24/59)


    The left hand B/E rows indicate the block and expression cov stats for the specified instance.  The BC/EC on the right of each line provide the cumulative block/expression status for the specific instance and all instances found hierarchically below that instance.  In the example above, the hierarchy of the design is as follows:

    cpu_test

    cgen

    cpu1

    ac

    ir

    pc

    alu1

    u3

    smx

    mem1

    cntl

    cpu2

    ac

    ir

    pc

    alu1

    u3

    smx

    mem1

    cntl

    Note the cumulative coverage values for each instance and the hierarchy found below.

    Hope that helps.

    Mickey

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information