Stats

  • Locked Locked
  • Replies 6
  • Subscribers 65
  • Views 16473
  • 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

casting problem

mwhite

I modified the SPI OVM testbench that can be downloaded from Mentor's web site.  The testbench is customized to test our design.  I have been using Mentor's Questa tool to run simulation while we evaluate the tool.  The testbench has worked with Questa.  We are also evaluating Cadence's Incisive.  I started to compile and run simulation with Incisive.  It apprears to compile OK but $cast does not seem to work right.

    seq_item_port.get_next_item(req);
    $cast(cloned_item, req.clone());
    ap.write(cloned_item);

This works fine with Questa but not with Incisive.  The data members in req are defined but not cloned_item after $cast.

Is there any reason that this does not work with Incisive?  Questa was sourceing OVM-2.1.2 source code.

Thank you!

 

Parents

  • If I recall correctly (it's a while since I looked at the OVM code), clone() just wraps around copy(), simply adding the new() to create a new object. Otherwise you'd new() your class yourself and call copy().

    Regarding SV construct support, do make sure you're using the very latest Incisive version as R&D are rapidly filling in the remaining gaps where we're missing bits. The latest is 10.20.034 if you're looking for SV support. Oh, and make sure you bug your local Cadence AE about any missing SV constructs; the more we hear about what's a priority for users, the sooner we fix the problems ;-)

    BTW, if you're looking at Mentor code, be aware that they prefer not to use the OVM macros, so you're left doing more of the boiler-plate code yourself (e.g. implementing do_copy()). If you use the OVM automation macros like `ovm_field_* then much of the boiler-plate is taken care of, which saves you a lot of extra code (thus less risk of bugs in your TB). Either approach is valid, with or without macros, but Cadence always recommends to use the macros.

Reply

  • If I recall correctly (it's a while since I looked at the OVM code), clone() just wraps around copy(), simply adding the new() to create a new object. Otherwise you'd new() your class yourself and call copy().

    Regarding SV construct support, do make sure you're using the very latest Incisive version as R&D are rapidly filling in the remaining gaps where we're missing bits. The latest is 10.20.034 if you're looking for SV support. Oh, and make sure you bug your local Cadence AE about any missing SV constructs; the more we hear about what's a priority for users, the sooner we fix the problems ;-)

    BTW, if you're looking at Mentor code, be aware that they prefer not to use the OVM macros, so you're left doing more of the boiler-plate code yourself (e.g. implementing do_copy()). If you use the OVM automation macros like `ovm_field_* then much of the boiler-plate is taken care of, which saves you a lot of extra code (thus less risk of bugs in your TB). Either approach is valid, with or without macros, but Cadence always recommends to use the macros.

Children
No Data

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.