Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 16364
  • 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

Include variable defined Spice netlist to the netlist created by AMS Simulator

AMSEngg

I am using Cadence IC617.  I want to simulate the extracted spice netlist with schematics, behavioral models uing Virtuoso AMS simulator and ADEXL.

I want the simulator to pick up the desired spice netlist based on the lib variable (ext1, ext2, ..., ext8) which has given as a variable in ADEXL.

spice netlist is like this

.LIB ext1
.include ./entrcp1
....
.LIB ext8
.include ./entrcp8s
....

I tried to set up a global variable and corner variable like
pick_netlist = ext1 in ADEXL

But AMS simulator interprets as real number variable and gives me the error. I was able to run the simulation with pick_netlist = "ext1", but it does not include the desired extracted netlist.

The flow I was looking for is working fine with spectre simulator but not with AMS.

Is there any alternative solution that I can use to include the spice netlist in verilog-ams netlist created by AMS?

Thanks in advance

  • How are you referring to the model file? In Setup->Model Libraries I would reference the model file and give the "section" name as VAR("pick_netlist") . If you do that, and have the variable pick_netlist set to "ext1" (with quotes) it should work - I've done this just now with both the UNL (Unified Netlister) and OSS. I even just checked it with the older CBN (CellView-based Netlister), and that works fine too.

    It generally helps to specify how you've set up the flow that you say works, as that might allow me to explain why it works in one case and not another. You also didn't mention any tool versions (see the Forum Guidelines (the first post in the forum) for suggestions on how to ask a good question).

    Kind Regards,

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    Thanks for your reply. I really appreciate your help.

    The tools that I am using are as follows

    irun(64) 15.20-s038
    Virtuoso ICADV12.3-64b.500.12
    spectre 16.1.0.319.isr4

    I want to include the extracted spice netlist by mentioning the file location in the config view file (i.e. Right click on View Found -> Specify SPICE Source File). I am able to run with Spectre but not with AMS.
    As a work around, I tried to edit CDF file to point out the extracted spice netlist. It works fine. But I want to have a work flow where I can specify the source spice netlist in the config file.

    Thanks in advance

  • in reply to AMSEngg

    I can't see how this would work in spectre either. When you include a file via the Specify SPICE Source File there's no option to give a "section" name, which is what the .LIB entries correspond to. You can give the file, but not the section. So what happens then is that nothing gets included from the file with the .LIB statements, and so you'd have a missing subckt/module definition.

    The only option here is really to stop at that cell (e.g. mark as a stop point in the hierarchy editor) and then reference it via the model files.

    I don't see how editing the CDF will help you here, since that wouldn't tell it how to include the file.

    I suspect there's some important bit of detail you've omitted from your explanation here, or it's set up differently to how you've explained. Perhaps you could go via customer support instead so that I'm not relying on guesswork?

    Regards,

    Andrew.

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.