Home > Community > Forums > Functional Verification > generic task for hdl node force/release in system verilog

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 generic task for hdl node force/release in system verilog 

Last post Mon, Apr 16 2007 8:12 AM by archive. 1 replies.
Started by archive 16 Apr 2007 08:12 AM. Topic has 1 replies and 1783 views
Page 1 of 1 (2 items)
Sort Posts:
  • Mon, Apr 16 2007 8:12 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,910
    generic task for hdl node force/release in system verilog Reply

    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
    • Post Points: 0
  • Mon, Apr 16 2007 10:41 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,910
    RE: generic task for hdl node force/release in system verilog Reply

    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
    • Post Points: 0
Page 1 of 1 (2 items)
Sort Posts:
Started by archive at 16 Apr 2007 08:12 AM. Topic has 1 replies.