• 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. $Signal_force

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 15474
  • 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

$Signal_force

archive
archive over 17 years ago

Hi everyone,
I am trying to use $signal_force but i am running into some problems. I am not sure how to use this command to force a signal not directly to a value but actually to another signal.
to elaborate on this, i give an example.
within my test bench i have a logic signal of size 32 bits called data1 and its value gets updated on each clock cycle. i would like to force a std_logic_vector of 32 bits to data1. but i always get a erro. it seems like i am not allowed to pass a signal as the specified value within signal_force.

$signal_force ("/../../../../input_data", "data1",0,3, ,1)
$signal_force(,,other_options..)
this is where i get the error.
i would like to know if this is legal to do.


Originally posted in cdnusers.org by ROOZ
  • Cancel
  • archive
    archive over 17 years ago

    I believe the "$signal_force" command is modelsim specific. If you are using modelsim, please consult the modelsim documentation. Cadence Incisive supports a similar command called, "$nc_force()". This is documented in the
    "NC Verilog Simulator Help Manual" in Chapter 19 - Applications.

    Regards,

    Jim McGrath


    Originally posted in cdnusers.org by Jim McGrath
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    I did check the questasim documentation but it didn't have an answer to my question. that's the reason for posting the question here. but thanks for your response


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