• 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. Is it possible to connect two workspace/simulations via...

Stats

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

Is it possible to connect two workspace/simulations via DPI-C?

mxlusereight
mxlusereight over 2 years ago

I have two projects, both are very large and are the two sides of a serial transceiver, each has billions of gates.

The two projects simulate in the respective databases so merging database is not possible. The two projects have conflicting some submodules which are of different versions, so the module names and library names are the same but interface differ slightly. Thus calling the two DUT in the same TB won't work in the conventional xcellium sim flow.

Would it be possible/practical to connect the serial interface of the two projects together via DPI-C and run two simulation in a system? 

Are there any other proven means I can use to achieve that goal? Would MSIE get rid of the issue of conflicting module/library names? 

Thank you in advance. 

  • Cancel
  • StephenH
    StephenH over 2 years ago

    Xcelium has the Mutli-Snapshot Incremental Elaboration flow to support flows where IPs use conflicting library cell versions - this is primarily intended for supporting multi-die simulations.

    There is no way to connect to separate simulation processes, the synchronisation overhead and complexity would be very significant.

    • 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