Stats

  • Locked Locked
  • Replies 15
  • Subscribers 64
  • Views 21571
  • 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

Help needed in creating URM using SV

archive

Hello friends!
I'm facing a problem while creating my Verification IP using SV language in URM environment.
Right now, I'm just trying to up my master agent with these files:

package.sv
dut_interface.sv
master_sequence_driver.sv
master_interface.sv
master_bfm.sv
master_monitor.sv
master_agent.sv
dut_dummy.v
dut_wrap.sv
bus_interface.sv

I got two errors"An interface connection must be connected to verilog parent" and "An interface port declaration must be connected".....

I couldn't able to go further....can anyone help me in this regards!?

Thanks in advance!
Regards,
Jalli


Originally posted in cdnusers.org by jaally
Parents

  • Hi Jalli.

    Is there any particular reason why you're not using the URM library functions?
    If you're worried about portability, note that the URM library is open source (i.e. you can see the code and compile it on other platforms).

    I assume that you just want access to the various constants and enum types that URM defines.
    In this case, I'd still suggest that you compile the whole URM library as Zeev showed you. This would help ensure that if you integrate a URM component from another team or vendor then it'll compile smoothly alongside your code.

    If you really cannot live with compiling all the URM files, and you are absolutely certain that you'll never ever need to integrate any other UVCs, then I suggest you look at the urm_util_pkg.sv and copy out the definitions that you require. Put them into a new file of your own, and just compile that.

    We really can't emphasise enough thought, that where customers do selectively apply bits of URM (and eRM before it), they tend to get into problems later on as their environments get bigger, or when they try to make legacy components fit with newer components later on...
    Always try to think about reuse and how your decisions may come back to haunt you later!


    Originally posted in cdnusers.org by stephenh
Reply

  • Hi Jalli.

    Is there any particular reason why you're not using the URM library functions?
    If you're worried about portability, note that the URM library is open source (i.e. you can see the code and compile it on other platforms).

    I assume that you just want access to the various constants and enum types that URM defines.
    In this case, I'd still suggest that you compile the whole URM library as Zeev showed you. This would help ensure that if you integrate a URM component from another team or vendor then it'll compile smoothly alongside your code.

    If you really cannot live with compiling all the URM files, and you are absolutely certain that you'll never ever need to integrate any other UVCs, then I suggest you look at the urm_util_pkg.sv and copy out the definitions that you require. Put them into a new file of your own, and just compile that.

    We really can't emphasise enough thought, that where customers do selectively apply bits of URM (and eRM before it), they tend to get into problems later on as their environments get bigger, or when they try to make legacy components fit with newer components later on...
    Always try to think about reuse and how your decisions may come back to haunt you later!


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