• 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. Testbench with non-unique module names in sub-blocks

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 66
  • Views 17666
  • 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

Testbench with non-unique module names in sub-blocks

mattyc
mattyc over 15 years ago

I have a testbench where I am trying to simulate two separate designs that share some module names within their designs.  For example, one is a bus controller and the other is bus master and each has a module named InterfaceIo.  When I try to simulate there is a conflict of multiple modules with the same name.  I have tried compiling and elaborating them separately and then referencing the libraries but I still get the error.  Is there a way to black-box a module or to get around the conflict I am experiencing?  Note that this is an overly simple example of the conflict in names so please don't respond with "just change the names!"  This doesn't seem like it should be so difficult but I am not figuring out how to get things going.  Any help will be greatly appreciated!

  • Cancel
Parents
  • muffi
    muffi over 15 years ago
    If you are using irun, adding -allowredefinition allows irun to compile and take the second module encountered.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • muffi
    muffi over 15 years ago
    If you are using irun, adding -allowredefinition allows irun to compile and take the second module encountered.
    • 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