Stats

  • Replies 1
  • Subscribers 132
  • Views 544
  • Members are here 0

Re: Saving nets that are compatible between schematic and idspf netlists

SL20260319720

Within a DUT, I would like to save and plot the voltage applied to the gate terminal of an inverter. On the schematic, the net is call INT_CLK and would have this in a file like below:

simulator lang = spectre

save DUT*STAGE01*INT_CLK* filter=rc

Assuming that there is no other nets or hierarchy name with INT_CLK, this setup allowed me to limit the number of nets being saved in Spectre simulation. The same setup is compatible between schematic and SPICE extraction netlist. Recently, we group moved to idspf for extraction simulation and the idspf netlist generated by Quantus has the following format:

XXSTAGE01/MM1_2 XXSTAGE01/MM1_2#d XXSTAGE01/MM1_2#g XXSTAGE01/MM1_2#s XXSTAGE01/MM1_2b pch_lvt_mac ....  

the same output from SPICE would be 

XXSTAGE01/MM1_2 OUT#14 IN_CLK#12 VSS#1877 VSS ...

Is there a switch or configuration in the Quantus extraction setup such that the output of the idspf netlist for the transistors have schematic netname follow #<Num>? Or how should change my save statement to allow for easy compatibility between schematic and idspf format?

Regards,

sulim

Parents
  • Andrew Beckett

    Sulim,

    The best thing to do would be to contact customer support (use the Case menu to submit a support case after logging in). If you can define the save from within ADE (rather than an include file) it should map the schematic name to the corresponding name in the DSPF; rather than me trying to cover every possibility here, I suggest speaking to an Application Engineer would be the best option. Then we can check together what you are doing and make sure this works correctly.

    Andrew

Reply
  • Andrew Beckett

    Sulim,

    The best thing to do would be to contact customer support (use the Case menu to submit a support case after logging in). If you can define the save from within ADE (rather than an include file) it should map the schematic name to the corresponding name in the DSPF; rather than me trying to cover every possibility here, I suggest speaking to an Application Engineer would be the best option. Then we can check together what you are doing and make sure this works correctly.

    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.