Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 2660
  • 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

generic task for hdl node force/release in system verilog

archive

i want to develop a generic task to force an hdl node inside the rtl.
the hdl path will be passed as a string to the task
eg: string s = "top.u_block1.u_block2.node_a";

this string will be passed as input to a task and the task should either force the value of the hdl path.
the hdl path should not be hardcoded. it should be only passed as a string. the string format can vary but it should only be a string.

is there any way to do this? i am using IUS583-s001. i don't see any example to do this in the documentation. also i am only using modules and not classes.

thanks and best regards

   Unmesh

Staff Engineer, Broadcom.
+91-9886404415


Originally posted in cdnusers.org by unmesh

  • Hi Unmesh,
          I believe you posted this in vguild as well: Here is a consolidated reply from my end:

     I believe this is doable with VPI - through vpi_handle_by_name and vpi_put in combination.

    Are there good reasons to do this? ANy run time path generation sounds fancy, but can get you into trouble - imagine:

    1. You run a sim till 100ms,
    2. Do a fancy force like this and got a typo error
    3. Bang! You hit an error and tool exits! Or sim fails!

    It is better to let the path be statically checked at elaboration and let the sim run peacefully - Just MHO.
    In any case I see 2 choices:

    1. Use VPI as I suggested - IMHO, your best bet to be tool independent
    2. Use TCL interface and get this done, fairly straight forward to do, though may not be as optimal as #1. This will be lot less work from your end:
      
    HTH
    Ajeetha, CVC
    www.noveldv.com




    Originally posted in cdnusers.org by ajeetha

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.