• 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. How to mirror VHDL signal in verilog Top Test bench

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 66
  • Views 20119
  • 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

How to mirror VHDL signal in verilog Top Test bench

Sowmya Reddy
Sowmya Reddy over 17 years ago

Hi I am writing a test bench to test VHDL design For which I need to access few signals in the design hierarchy How to mirror them, I used nc_mirror, but got errors. Help me Thanking Venkat Reddy Uppala

  • Cancel
Parents
  • tpylant
    tpylant over 17 years ago

     A couple of clarifications:

    1. I assume you meant "$nc_mirror" instead of "nc_mirror" since "nc_mirror" is a VHDL command
    2. I assume "pali_digit_inst" is instantiated from the testbench and the testbench is "pali_epp_test"

     If those two assumptions are correct, then try using full pathnames for the $nc_mirror command:

    •  $nc_mirror("pali_epp_test.ba8p_ready", "pali_epp_test.pali_digit_inst:pali_inst:HS_P_TESTSITE_C:ba8p:hc:hssprtready", "");

    Here is the help message for your error in case it might provide more insight:

    % nchelp ncelab cuvmur
    ncelab/cuvmur =
            An instance of a unit could not be resolved in the libraries,
            where unit is defined in Verilog to be either a module,
            macromodule, primitive, interface or program block or a config.
            In VHDL a unit would be either an entity or a configuration.
            It is also possible that a 5.X configuration view could not be
            resolved in the libraries.
            The error could arise because the Verilog/VHDL unit or the
            5.X configuration view being instantiated in the Verilog
            module needs to be built. A rebuild is needed if a new
            version of the software was installed after the last build.
            Another reason for the problem could be an incorrect or missing
            library name, in which case it could be resolved by supplying
            the correct library name.

    Tim

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • tpylant
    tpylant over 17 years ago

     A couple of clarifications:

    1. I assume you meant "$nc_mirror" instead of "nc_mirror" since "nc_mirror" is a VHDL command
    2. I assume "pali_digit_inst" is instantiated from the testbench and the testbench is "pali_epp_test"

     If those two assumptions are correct, then try using full pathnames for the $nc_mirror command:

    •  $nc_mirror("pali_epp_test.ba8p_ready", "pali_epp_test.pali_digit_inst:pali_inst:HS_P_TESTSITE_C:ba8p:hc:hssprtready", "");

    Here is the help message for your error in case it might provide more insight:

    % nchelp ncelab cuvmur
    ncelab/cuvmur =
            An instance of a unit could not be resolved in the libraries,
            where unit is defined in Verilog to be either a module,
            macromodule, primitive, interface or program block or a config.
            In VHDL a unit would be either an entity or a configuration.
            It is also possible that a 5.X configuration view could not be
            resolved in the libraries.
            The error could arise because the Verilog/VHDL unit or the
            5.X configuration view being instantiated in the Verilog
            module needs to be built. A rebuild is needed if a new
            version of the software was installed after the last build.
            Another reason for the problem could be an incorrect or missing
            library name, in which case it could be resolved by supplying
            the correct library name.

    Tim

    • 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