• 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. Custom IC Design
  3. Ordered connection in AMS netlist

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 15980
  • 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

Ordered connection in AMS netlist

Finn
Finn over 15 years ago

I am simulating a very simple circuit using AMS designer. The circuit has a subcircuit AAA which is generated by ADS. I first created schematic view for AAA, where there are only pins without any connections. I then generated symbol view for it and saved it as spectre view also. In AMS designer, I added the path to the subcircuit netlist to analog model. It's fine when I run design prep. But when I run simulation, it reports an error saying:

ncelab: *E,SPPBYN (****/verilog.vams,17|68): Named port connections for analog primitives are not supported.

I checked the AMS netlist. AAA is indeed netlisted using named connection. Can anyone tell me how to tell AMS to netlist this block using ordered connection? Or is it caused by any other possible things?

  • Cancel
  • archive
    archive over 15 years ago
    Instead of including the subckt netlist as analog model, use “Source File” option in HED. For subckt AAA, in HED config, right click on “View To Use”, Set Cell View -> Source File and specify the path to subckt netlist here.

    Are you running from AMS from Hierarchy Editor or from ADE?

    Regards,

    Ramkumar
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Finn
    Finn over 15 years ago
    Hi Ramkumar,

    Thanks a lot for your reply. It solves the problem!

    I am using Hierarchy Editor. It seems I must remove the subckt definition from analog models  otherwise the netlister still give the same error.

    Also another strange happened as I played around. If I have “spectre” in my view list, I will get the messages below:

    Ncelab: *W,CUNOUN: Cannot find any unit under libname:AAA:spectre in the design libraries.

    Ncelab: *E,CUCFUN: instance “I49” of the unit AAA is unresolved in …..

    It seems the netlister or the elaborater ignores the source file and still tries to use the spectre view according to the view list. I have to remove “spectre” from the view list. Is there any explanation?

    By the way, does ams netlister respect what I have in the CDF? I played a little with CDF of AAA, but it so far doesn’t help.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 15 years ago
    Hi,

    Having “spectre” in view list in HED should not create any problem here. As long as the “View to Use” is pointing to the spice netlist path for the spice instance elaborator should pass.

    AMS netlister does read CDF. What problem are you facing here?

    Regards,
    Ramkumar
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Finn
    Finn over 15 years ago
    No I don’t have any problem in CDF. I just thought the netlister may respect the settings in CDF, especially those for ams and spectre. But as you said, it doesn’t  read CDF.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago
    Ramkumar said that it _does_ read the CDF.

    So what exactly is the problem you're seeing.

    Regards,

    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Finn
    Finn over 15 years ago
    Hi Andrew,

    Guess it’s a little confusing. I DON’T have any problem with CDF or the simulation now.

    At first, I thought CDF will affect amsdesigner. So when I was trying to make things work I changed CDF. Of course it didn’t work. Then I concluded that amsdesigner doesn’t read CDF. The reason I asked Ramkumar about CDF in my post was just to make sure my conclusion is correct.
    • 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