Stats

  • Locked Locked
  • Replies 12
  • Subscribers 64
  • Views 20942
  • 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

Modularization of SystemVerilog

archive

Hi guys,

I have an question concerning modularization, but I have not found it in one of the following books: "Writing Testbenches using SystemVerilog" and "SystemVerilog for Verification". So, I hope you can help me.

I have written much classes, which are all in ONE file so far, but this is not the target state I wish for this project. The problem is, that for example, one class instantiates another class and I don't know, how to separate the classes.

Is a mechanism available, as C-Header-Files?

I hope you can help me, because several smaller files are much better than one singe huge file.

Thanks for your help!
If the answer should be in one of the itemized books, please sorry, I haven't found it!

Sebastian


Originally posted in cdnusers.org by sebastian
Parents

  • You need to compile the pkg.sv file first, i.e. "ncvlog -mess -status -sv pkg.sv testproam.sv".


    Since you are importing "pkg::*", I assume that the package name is "pkg", i.e. "package pkg; ... endpackage".


    The import statement does not have to be within the program block, however by putting it outside, all of the package declarations are visible to any modules/programs/etc. that follow the import statement. I personally do not recommend that because it follows poor coding guidelines and can cause unforseen problems. It is better to import the package into each module where you want to use it. However, if you want to ignore that advice for a legitimate reason, then you might as well put the import statemetn at the end of your package file, i.e. "package pkg; ... endpackage import pkg::*;"

    Tim


    Originally posted in cdnusers.org by tpylant
Reply

  • You need to compile the pkg.sv file first, i.e. "ncvlog -mess -status -sv pkg.sv testproam.sv".


    Since you are importing "pkg::*", I assume that the package name is "pkg", i.e. "package pkg; ... endpackage".


    The import statement does not have to be within the program block, however by putting it outside, all of the package declarations are visible to any modules/programs/etc. that follow the import statement. I personally do not recommend that because it follows poor coding guidelines and can cause unforseen problems. It is better to import the package into each module where you want to use it. However, if you want to ignore that advice for a legitimate reason, then you might as well put the import statemetn at the end of your package file, i.e. "package pkg; ... endpackage import pkg::*;"

    Tim


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