• 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. In AMS simulation, for verilog, how to use a module in a...

Stats

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

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

ychenanalog
ychenanalog over 5 years ago

I write a verilog module, in which use another module,like:

module A();

B U1();

endmodule

while B is another module:

I bulid a AMS simulation but it can't run, even the two module are in one library, and the hierarchy editor can't find module B.

So i hope to get a solution from you.

Thinks

  • Cancel
  • MarcelAhmedzai
    MarcelAhmedzai over 5 years ago

    Hi ychenanalog,

    You need to add the name of the library in the Hierarchy Editor Library List. This will then allow the Hierarchy Editor to find the module instantiated within another textual cellview.

    Kind regards

    Marcel

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • ychenanalog
    ychenanalog over 5 years ago in reply to MarcelAhmedzai

    Hi Marcel

    I had add the library name in library list, but there are still no library for the module in the table view. like what i show in the picture, is there something else i should do to solve it?

    aa

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 5 years ago in reply to ychenanalog

    Dear Marcel,

    ychenanalog said:
    I had add the library name in library list, but there are still no library for the module in the table view. like what i show in the picture, is there something else i should do to solve it?

    1. I cannot see the full list of your "View list". Did you include the view you defined for your module "spi_slave" in the "View list"?

    2. Have you considered the solution to a similar problem described in the Cadence support article at URL:

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

    I hope these provide some useful information Marcel.

    Shawn

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

    Please excuse my response - I accidentally addressed it to Marcel and it should have been addressed to Mr. ycheckanalog. My apologies for the oversight!

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ychenanalog
    ychenanalog over 5 years ago in reply to ShawnLogan

    I am sorry i don't understand what's the view of the "spi_slave"? 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ychenanalog
    ychenanalog over 5 years ago in reply to ShawnLogan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to ychenanalog

    What is needed is the name of the library containing the cell spi_slave to be in the global library list. Since it's very hard to see what you've got (especially as you've redacted some of the information), it would be much wiser to contact customer support so that an application engineer can look at your setup and get this resolved.

    Andrew.

    • 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