• 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. BFM written in class has to interface with phy signals

Stats

  • Locked Locked
  • Replies 16
  • Subscribers 65
  • Views 24106
  • 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

BFM written in class has to interface with phy signals

archive
archive over 18 years ago

Hi,

I'm new to systemverilog ..and using NCVLOG...and i'm trying interface my BFM modelled using classes with the interface (phy signals)...cadence is not supporting keyword virtual to do this...can anyone help me on how to do this....i want to keep my classes in a separate file...and the top module in a separate file....also have trouble calling the top module from program file....please help ASAP 

Cheers


Originally posted in cdnusers.org by chaitu2k
  • Cancel
Parents
  • archive
    archive over 18 years ago

    Hi Davy,

    It would probably make sense for you to read the documentation on http://myipcm.cadence.com
    SV is just another language and like all languages there will be some constructs and applications that you will find easy and intuitive and other syntax/semantics will appear difficult.

    Like Ajeeta said its all about having the correct methodology for achieving your solutions, then you can implement the solution using constructs which make sense to you.

    Within the Universal Reuse Methodology there are already various styles of implementation for creating powerful reusuable components.
    If you are not very familiar with OO or simply dont want to stray too far from the style of constructs typically used by design engineers then I would suggest you choose the Designer Orientated: "Module Based with classes" implementation for your verification components.
    thanks
    Adiel


    Originally posted in cdnusers.org by adielkhan
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    Hi Davy,

    It would probably make sense for you to read the documentation on http://myipcm.cadence.com
    SV is just another language and like all languages there will be some constructs and applications that you will find easy and intuitive and other syntax/semantics will appear difficult.

    Like Ajeeta said its all about having the correct methodology for achieving your solutions, then you can implement the solution using constructs which make sense to you.

    Within the Universal Reuse Methodology there are already various styles of implementation for creating powerful reusuable components.
    If you are not very familiar with OO or simply dont want to stray too far from the style of constructs typically used by design engineers then I would suggest you choose the Designer Orientated: "Module Based with classes" implementation for your verification components.
    thanks
    Adiel


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