• 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. ICCR: toggle exclude for bits of a bus

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 67
  • Views 17714
  • 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

ICCR: toggle exclude for bits of a bus

Cadence Forum
Cadence Forum over 16 years ago

Dear Sirs,

could anyone give me an example on how to exclude a bit of an internal bus in the toggle exclude file for ncelab?

For instance, if I use

INSTANCE <pathname>:<bus_name>*

I exclude from the statistics all the bits of the bus, but specifying a single bit, it seems not working

INSTANCE <pathname>:<bus_name>(<bit_number>)

I tried also to escape the parenthesis with

INSTANCE <pathname><bus_name>\(<bit_number>\)

but without success.

Thanks in advance

Sergio

  • Cancel
Parents
  • Mickey
    Mickey over 16 years ago

     Hi Sergio,

    The bitexclude option is an argument to the set_toggle_excludefile option used in a coverage configuration file.  The description is as follows:

    set_toggle_excludefile [-nolog] [-bitexclude] <file>

    where

    • -nolog ensures that no log file is generated to dump the list of signals that were excluded for toggle coverage. In the absence of this option, a log file named toggle_exclude.log is generated.

    • -bitexclude allows exclusion of bit selects of vector signals. With this option, the patterns in the exclude file are matched against the expanded names of each vector bit.

    • <file> is the name of a file that contains a list of signal names that are to be excluded from toggle coverage. A warning is reported if <file> includes signals of instances/modules, which are deselected using the deselect_coverage command in the coverage configuration file.

    you can find specific documentation on how to write the excluded signals file by looking in the ICC User Guide (<install>/doc/iccug/iccug.pdf, look in chapter 8 "Generating Coverage Data"), or you can also open that document within cdnshelp.

    Hope that helps

    Micke

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Mickey
    Mickey over 16 years ago

     Hi Sergio,

    The bitexclude option is an argument to the set_toggle_excludefile option used in a coverage configuration file.  The description is as follows:

    set_toggle_excludefile [-nolog] [-bitexclude] <file>

    where

    • -nolog ensures that no log file is generated to dump the list of signals that were excluded for toggle coverage. In the absence of this option, a log file named toggle_exclude.log is generated.

    • -bitexclude allows exclusion of bit selects of vector signals. With this option, the patterns in the exclude file are matched against the expanded names of each vector bit.

    • <file> is the name of a file that contains a list of signal names that are to be excluded from toggle coverage. A warning is reported if <file> includes signals of instances/modules, which are deselected using the deselect_coverage command in the coverage configuration file.

    you can find specific documentation on how to write the excluded signals file by looking in the ICC User Guide (<install>/doc/iccug/iccug.pdf, look in chapter 8 "Generating Coverage Data"), or you can also open that document within cdnshelp.

    Hope that helps

    Micke

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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