Back annotate the extracted parasatics from layout to schematic

Don't know if assura has it, but pvs provides schematic probes to read parasitic elements. Under menu launch->plugins->pvs->parasitic.
Old Diva tool was provided back annotation as labels on the schematic, so assura should have sthing similar. What user guide is saying about this?

Back-annotating parasitics to the schematic may help you run post-layout-like simulations faster, but may not help you debug the root causes of parasitic issues - i.e. what net, layer and polygon(s) are causing you a trouble.

First question to you - do you need this (back-annotation) to be able to run circuit simulations accounting for parasitics, or is your primary goal - to identify and exterminate the root causes of parasitics problems?

Each company has its own set of scripts and tricks for parasitics debugging.
You can follow them, or you can use commercial tool to do that for you.

Our company, Diakopto Inc., developed an EDA tool, ParagonX, specifically to help debug parasitics problems, you can read more here:

Dominik Przyborowski said:

Don't know if assura has it, but pvs provides schematic probes to read parasitic elements. Under menu launch->plugins->pvs->parasitic.
Old Diva tool was provided back annotation as labels on the schematic, so assura should have sthing similar. What user guide is saying about this?

Click to expand...

Thank you Dominik for your reply,

I have also PVS installed on my Cadence, but I am using the Assura,
indeed my team leader never told me about the PVS tool and it is interesting to know from you why you prefer it.

Last time I talked to him he advised me to use the "Parasitic Aware Design (PAD) Flow" as well

timof said:

Back-annotating parasitics to the schematic may help you run post-layout-like simulations faster, but may not help you debug the root causes of parasitic issues - i.e. what net, layer and polygon(s) are causing you a trouble.

Click to expand...

will it give the same result as simulating with the extracted view ?

timof said:

First question to you - do you need this (back-annotation) to be able to run circuit simulations accounting for parasitics, or is your primary goal - to identify and exterminate the root causes of parasitics problems?

Click to expand...

My intention is both of them

timof said:

Each company has its own set of scripts and tricks for parasitics debugging.
You can follow them, or you can use commercial tool to do that for you.

Our company, Diakopto Inc., developed an EDA tool, ParagonX, specifically to help debug parasitics problems, you can read more here:

Circuit simulation and parasitics: do we need more speed, or more insight (or both)?

I recently read John Cooley’s interesting article on the Troublemakers panel discussion at DAC 2020 between Mentor’s Joe Sawicki and Cadence’s Anirudh Devgan. They were talking about Mentor’s AFS-XT SPICE simulator beating Cadence’s Spectre-X in speed by a factor of 3x-10x.

www.linkedin.com

Overview – Diakopto Inc.

diakopto.com

Click to expand...

Thanks for the link, i read it and I enjoyed the article, unfortunately I am restricted to work with Cadence tools only

I have seen schematics in which this had been done, but have
not done it myself to know the steps.

A concern can be the "double counting" of extracted parasitics if
you use the "wrong" model branch (presuming there is one) -
I've seen RF CMOS flows' PDKs that "keep two sets of books",
a model set for schematics based simulation in which the FETs
have full overlap / adjacent capacitances and maybe even
runt inductors, and a model set which expects these to be
carried in all those pacpacitors and so reduces the intra-FET
cXYo params to achieve a godo match between schematic
predicted, and layout extracted frequency response.

If you push all the extracted Cs into the schematic, then it
probably wants the "post-layout model chain" (if there is).

You likely want to "refine" and drop any sub-fF capacitors as
there's a lot of them and they mean nothing except netlist
bloat and run-time baggage.