• 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. Multiple interfaces with single driver in SV

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 64
  • Views 13404
  • 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

Multiple interfaces with single driver in SV

archive
archive over 18 years ago

I have one interface with multiple clocking blocks which are actually different interfaces of the DUT.These interfaces differ their properties depending on the interface. for one interface the port is input for other same port is output. To solve this in SV, I can have an interface with different clocking block which defines the properties of different interface. Now the problem is I have a common driver which supports all these interfaces, so I should have a common interface instantiated inside the driver. Based on different modports,which is being passed through the construct of the driver, it should take the modport of that interface and work accordingly. Please let me know, how can I pass different modports of an interface through the construct to behave the mutiple instantiation of the driver accordingly? Sam


Originally posted in cdnusers.org by sam_kishore
  • 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