• 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. Issues in merging coverage using iccr

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 13254
  • 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

Issues in merging coverage using iccr

Oragniz
Oragniz over 13 years ago

Hi All,

        I would first like to bring to your notice that i'm very new to iccr. I face problem in merging coverage data from two rtl releases.

        On the first, i'm not sure whether i can merge data from two different rtl releases. If possible, then i've issue in doing so.. 

        The error message that it's showing is:

         iccr "Library name of this test does not match that of primary test. To merge tests where the same code is compiled into different libraries, elaborate with CCF command "set_ignore_library_name" and then resimulate. This will allow merge of data."

        I even tried setting  set_ignore_library_name option in my compile script and then resimulated and again tried to merge, but, stil i face the same issue..

      Can anyone please help me resolve this issue.

  • Cancel
Parents
  • pcarzola
    pcarzola over 13 years ago

    set_ignore_library_name should work.  Try and compile into the same library and see if that works.

    If you still have issues, please file a support ticket

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • pcarzola
    pcarzola over 13 years ago

    set_ignore_library_name should work.  Try and compile into the same library and see if that works.

    If you still have issues, please file a support ticket

    • 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