• 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. Mixed-Signal Design
  3. AMS Simulation: Use SystemVerilog module instantiating other...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 4292
  • 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

AMS Simulation: Use SystemVerilog module instantiating other submodules in SystemVerilog

Mathieu Chene
Mathieu Chene 11 months ago

Hello,

First, thanks for reading this post !

I am working on a mixed signal simulation using ADE explorer and AMS simulator.

In the top design I have a module A I want to instantiate as a systemVerilog object. in the sv file this module include a submodule B also defined in sv.

Both modules are defined in the same file

/* Start file*/

module A();

  B(ports...)

endmodule

module B();

description ....

endmodule

/*end file*/

When I generate the netlist it fails telling that B (here muxReadX) is not defined in config view ....

Then I tryed to use a separate sv file for B in to use the `include "pathToB" method (adding the path to B in the ams simulator option) but I have the same error.

/* Start file*/

`include "path_to_B"

module A();

  B(ports...)

endmodule

/*end file*/

Then I created a library named SYSTEMVERILOG_lib in which I store the sv description. I added it in the library list of my config view but it still does not find it (address_decoder is found and I do not know why it is different here)

Do you have any idea on how to solve this ?

I have also to precise that I do not have this issue with sv module that does not call submodule.

I am using IC23.1

I have already seen this post but it was not helpful:

https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V000006DdhMUAS&pageName=ArticleContent

 How to include Verilog functional files in Virtuoso Hierarchy Editor for SDF Simulation 

 In AMS simulation, for verilog, how to use a module in a top module? 

I would be glad to give more precision if needed.

Thank you in advance for your help

Mathieu

  • Cancel
Parents
  • tpylant
    tpylant 11 months ago

    How about creating a systemverilog cellview for 'B' that has the module B code in it?

    Tim

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • tpylant
    tpylant 11 months ago

    How about creating a systemverilog cellview for 'B' that has the module B code in it?

    Tim

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Mathieu Chene
    Mathieu Chene 11 months ago in reply to tpylant

    Hi,

    Thank you for your answer. I did it, I have just created a dedicated library SYSTEMVERILOG_lib to store these cell views . It works for one module (address_decoder) but muxReadX is not linked...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett 11 months ago in reply to Mathieu Chene

    I'm not sure how you expect anyone to know why address_decoder is any different from muxReadX given that you've not shared either...

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Mathieu Chene
    Mathieu Chene 11 months ago in reply to Andrew Beckett

    I haven't shared it because it's not the main point of my question. My main concern is why doesn't the configuration view take into account the submodules described in the same systemverilog view as the main module? As this is accepted by xcelium, and virtuoso's systemverilog view is extracted using xrun as well, I don't really understand the difference on how the file is ‘parsed’ by the config view (I don't know if I'm clear).

    • 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