• 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. generate over a loop the same module with different parameter...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 13584
  • 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

generate over a loop the same module with different parameter and maintain it in systemverilog UVM environment

EranW
EranW over 5 years ago

Hi,

I've encountered in an issue that I'm trying to generate an interface with different parameter (DW) over a loop.

Therfore, I found that I've two problems;

1. How to generate the block (interface in my case) with a different parameter  (between each interface) over a loop?  I've tried generate block. 

2. How to maintain the data through config_db (set and get), virtual_interfaces, agents - same type with different parameters over the environment?

In case I've a chain of passive agents I don't like to duplicate the code so many times in my environment.

Regards,

Tomer

  • Cancel
  • StephenH
    StephenH over 5 years ago

    Parameters in classes are somewhat viral; once they get in, they tend to replicate very fast and end up everywhere!

    If you have a limited number of values needed for DW, you could consider using a typedef for each one, to simplify the code, but that won't help for the interface instances.

    I'm not sure how you intend to derive the DWW value for each interface - is it calculated somewhere? Is the number of interfaces known in advance? How do you plan to bind the interface signals / ports if the signals aren't statically known?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • EranW
    EranW over 5 years ago in reply to StephenH

    Hi,

    Thanks for your help.

    Regarding your question, I know the DataWidth (DW) per each interface/agent/monitor/item - You can think about it as a chain of checkers. Therefore, I know these numbers and they won't be changed for the entire project. It's not calculated and shouldn't be neither.

    The number of the interfaces is known.

    Currently, it runs well, but I duplicated the code per each interface/agent/monitor/item/scoreboard/environment - It's not nice at all to duplicate the code so many times.

    Actually, I didn't find how to create all the components over loop in a kindly way.

    • 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