Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 15164
  • 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

VerilogAMS netlist from schematic

acook

Hello, 

I would like to create a verilogAMS netlist from a schematic as a post check and save trigger. I am not trying to do this hiearchtically, I just want to create a verilogAMS view representative of the schematic. I find this useful when creating mixed signals models as you can throw in a few spectre models easiy (like a diode). Usually I have to create a ADE AMS setup, netlist, and steal it from the netlist.vams that spits out.

As far at the netlist form, I would like exactly what ADE in AMS mode generates (with default options).

 I played with the command to create an AMS netlist, but I was unclear on how to set the default options correctly. When I tried one particular schematic, it failed complaing about little endian vs big endian.

Thank you,

Aaron

Parents

  • Hi Aaron,

    Are you using the Cell-Based netlister or OSS/irun in ADE? If using the cell-based netlister, you can probably just easily use the amsNetlist() function - this will netlist into the schematic cellView, but you could take the resulting file and use that.

    I'm not sure what you mean about little endian vs big endian (or rather I know what the difference is, but I'm not sure how you'd get the tools complaining about that).

    Regards,

    Andrew.

Reply

  • Hi Aaron,

    Are you using the Cell-Based netlister or OSS/irun in ADE? If using the cell-based netlister, you can probably just easily use the amsNetlist() function - this will netlist into the schematic cellView, but you could take the resulting file and use that.

    I'm not sure what you mean about little endian vs big endian (or rather I know what the difference is, but I'm not sure how you'd get the tools complaining about that).

    Regards,

    Andrew.

Children
No Data

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.