• 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. Help needed in creating URM using SV

Stats

  • Locked Locked
  • Replies 15
  • Subscribers 64
  • Views 21564
  • 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

Help needed in creating URM using SV

archive
archive over 18 years ago

Hello friends!
I'm facing a problem while creating my Verification IP using SV language in URM environment.
Right now, I'm just trying to up my master agent with these files:

package.sv
dut_interface.sv
master_sequence_driver.sv
master_interface.sv
master_bfm.sv
master_monitor.sv
master_agent.sv
dut_dummy.v
dut_wrap.sv
bus_interface.sv

I got two errors"An interface connection must be connected to verilog parent" and "An interface port declaration must be connected".....

I couldn't able to go further....can anyone help me in this regards!?

Thanks in advance!
Regards,
Jalli


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

    Hi Jalli.

    You get these messages if you have not connected the SV interfaces correctly to your agent or DUT.
    If for example you DUT has a port declared as an interface, it must be connected to an interface of the same type.

    Without seeing your files it's hard to pinpoint the exact error, but I suggest you double check the connections from you top file going into the agent and DUT instances.

    You can send me the files if you don't manage to resolve it : stephenh cadence.com

    By the way, when you get an error message that you don't understand, try looking it up using the nchelp command. This usually gives some more details about the problem and how to solve it. For the two messages you described I pasted the nchelp commands and the output:

    [sve/main] $ nchelp ncelab CUINMD
    nchelp: 06.11-s003: (c) Copyright 1995-2007 Cadence Design Systems, Inc.
    ncelab/CUINMD =
    This is an incompatible connection. A Verilog interface must be connected
    to a port of a Verilog instance. All other languages and connection
    types are disallowed.

    [sve/main] $ nchelp ncelab CUIMBC
    nchelp: 06.11-s003: (c) Copyright 1995-2007 Cadence Design Systems, Inc.
    ncelab/CUIMBC = An interface port declaration may not be left unconnected.
    [sve/main] $


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

    Hi Jalli.

    You get these messages if you have not connected the SV interfaces correctly to your agent or DUT.
    If for example you DUT has a port declared as an interface, it must be connected to an interface of the same type.

    Without seeing your files it's hard to pinpoint the exact error, but I suggest you double check the connections from you top file going into the agent and DUT instances.

    You can send me the files if you don't manage to resolve it : stephenh cadence.com

    By the way, when you get an error message that you don't understand, try looking it up using the nchelp command. This usually gives some more details about the problem and how to solve it. For the two messages you described I pasted the nchelp commands and the output:

    [sve/main] $ nchelp ncelab CUINMD
    nchelp: 06.11-s003: (c) Copyright 1995-2007 Cadence Design Systems, Inc.
    ncelab/CUINMD =
    This is an incompatible connection. A Verilog interface must be connected
    to a port of a Verilog instance. All other languages and connection
    types are disallowed.

    [sve/main] $ nchelp ncelab CUIMBC
    nchelp: 06.11-s003: (c) Copyright 1995-2007 Cadence Design Systems, Inc.
    ncelab/CUIMBC = An interface port declaration may not be left unconnected.
    [sve/main] $


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