• 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 union usage

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 66
  • Views 13084
  • 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 union usage

jzingman
jzingman over 16 years ago

We are trying to use union to get an estimate of coverage in our tests.  However, we've run into the problem that the design must be identical over all of the tests.  Our test bench uses `DEFINEs fairly extensively, and apparently this prevents us from merging the coverage databases.  Is there any way around this problem? For instance, if we use deselect_coverage on the test bench, will that allow us to use union?

 Thanks

  • Cancel
  • nlin
    nlin over 15 years ago

    Hi,

    The union command requires that the design is identical.  I think what you would like to accomplish can be done with the merge command.  The merge command will merge what is identical in primary and secondary databases, and ignore items in the secondary database that's not in the primary database.  There is also a union merge, which will create a merged database with all components of primary and secondary databases.  This is only available in IUS8..2, and I recommend using IUS8.2-s015 if you are planning to do a union merge.

     To do a union merge

     set_merge -union

    merge test1 test2 -output merged

     If you need more details, feel free to contact me at nlin@cadence.com.

     In the future, if you have any questions about the usage of the tool, be sure to file a Service Request via Cadence Online Support (http://support.cadence.com)

     Regards,

    Nancy 

    • 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