• 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. Forcing a VHDL signal from a Verilog Test/Env

Stats

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

Forcing a VHDL signal from a Verilog Test/Env

ashfaqh
ashfaqh over 14 years ago

 I have a Testbench with a DUT which has VHDL and Verilog RTL modules.  The tb_top is verilog.  The test file is a verilog.  

 From the verilog test, I need to force a signal inside the DUT several hierarchies down.

 The signal I need to force is inside a VHDL module.   This signal is not available at the top level.

 How do I do it?

 I am using ncverilog/ncvhdl/irun version of 9.2.

 Any suggestions with some simple code example is going to be very helpful. 

 Thanks, 

 -Ashfaq Hossain 

  • Cancel
  • Mickey
    Mickey over 14 years ago

    Hi Ashfaq,

    You need to use $nc_force to force a vhdl down in the design hierarchy from a verilog testbench.  It's fairly simple.   


    $nc_force ("source", "value", "after_time", "rel_time", "repeat_time",  "cancel_time", "verbose");

    for example,
    $nc_force (path.to.r1, "'1'", "verbose");

    above example will force a '1' value (note that vhdl notation is used for the value to be assigned, if the destination was verilog you would use 1'b1) onto the hierarchical location, path.to.r1.  Additionally verbose is included to have the tools output a message to stdout when the code is encountered during simulation.

    If you would like more information regarding the other options, go to support.cadence.com and do a search using $nc_force as the search term. 

    Best regards,
    Mickey

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ashfaqh
    ashfaqh over 14 years ago

    Mickey:

     Thanks for your response.  I tried and got the following error msg.  Please suggest.

     Thanks,

     -Ashfaq

     

     Top level design units:
                    $unit_0x22e511b2
                    tb_test
              $nc_force(tb_test.u_tb_controller.u_hier1_top.hier2.hier3.hier4.hier5.signal_name[3], "'1'", "verbose") ;
                                                                                                                                                 |
    ncelab: *E,CUIOCP (./testbench/tb_test.v,109|141): Out-of-module reference terminating in a VHDL scope is not allowed (tb_test.u_tb_controller.u_hier1_top.hier2.hier3.hier4.hier5.signal_name[3]).
    ncelab: Memory Usage - 20.8M program + 170.3M data = 191.1M total
    ncelab: CPU Usage - 0.2s system + 1.2s user = 1.4s total (3.6s, 38.2% cpu)
    irun: *E,ELBERR: Error during elaboration (status 1), exiting.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tpylant
    tpylant over 14 years ago
    It looks like you did not put quotes around the signal name.  All the arguments need to be strings:

    $nc_force ("source", "value", "after_time", "rel_time", "repeat_time",  "cancel_time", "verbose");

    Tim
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ravisguptaji
    ravisguptaji over 13 years ago

    Hi,

    I was able to source to the signal of interest, but i have a requirement to keep giving different values to that signal of interest.

    I tried something like this, which din't work out.

    repeat(4) begin

    $nc_force("source", "reg") ;

    reg = reg+1'b1;

    end

    The reg value in my simulation keeps incrementing but the source signal of interest does not increment.

    Is there any other way to perform the same kind of operation??

    Regards,

    Ravi

    • 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