• 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. pointers in sequence items

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 13506
  • 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

pointers in sequence items

kabb
kabb over 16 years ago

 Hello

Is it possible to have a pointer field in a sequence item, that points to a data structure in the bfm ?

 If so, then is the initialization of the pointer to be performed via the init() pre-defined method of the structure or the pre-generate() pre-defined method ?

  • Cancel
  • tpylant
    tpylant over 16 years ago

    The sequencer and BFM only communicate through the get_next_item() task, so I don't think you can have a pointer in one that references the other. However, give more details of what you're wanting to accomplish and perhaps someone could comment on how to achieve that.

     Tim

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kabb
    kabb over 16 years ago

    Hello Tim, 

    Actually, what I need to do is to keep track of some constraint ranges that alter during the simulation. This "simulation feedback" information need not reside in the bfm i suppose -  it could be a part of the agent or env. To this end, I am trying to find when a pointer in a generated item can be initialized.

    thanks and regards

     kabb

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Hilmar
    Hilmar over 16 years ago

     Hi kabb,

    Sorry for the later response, but I didn't see your question answered yet.

     

    You could use the driver to get the information out of the agent or monitor. Let's assume the driver has a pointer to the agent and the agent (or even its monitor) has ports to the required signals, you can do the following in the body() of your sequence:

     

    body()@driver.clock is {

    do item keeping {

    .min_range == driver.agent.lower_bound$;

    .max_range == driver.agent.upper_bound$;

    };

    };

     

    If this brings timing problems (with regards to the changes of your constraints) and you really need to have direct access to HDL values at a later stages, you're doomed to (well, it's not that bad, but I'm a big fan of ports ;)) tick access. Fortunately, since you have the ports available already, you can easily give the location in the simulator to the sequence item, so it can access the HDL values whenever deemed necessary:

     

    body()@driver.clock is {

    do item keeping {

    .min_range_location_string == driver.agent.lower_bound.full_hdl_path();

    .max_range_location_string == driver.agent.upper_bound.full_hdl_path();

    };

    };

     

     

    I hope this helps you a bit forward.

     

    Good luck,

    Hilmar

    • 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