Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 14718
  • 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

RC extraction mode for postRoute timing analysis

archive 

Hello,

I am using SOC62 and the problem is that I want to consider coupling
capacitances (not xtalk effects) during "timeDesign -postRoute", but the RC
extraction automatically performed by timeDesign
does not consider these capacitances.

1) How to force timeDesign to consider what is set by setExtractRCMode?


I tried the following commands:
######
setExtractRCMode -detail -noReduce -coupled -noise
extractRC
timeDesign -postRoute -reportOnly
timeDesign -postRoute -hold -reportOnly
######

But I'm not sure if using this option
(-reportOnly) timeDesign performs
delay calculation before timing analysis or if it
uses previous calculated timing data.

2) How to consider coupling capacitances, not crosstalking effects, during
timeDesign -postRoute (considering native extraction)?

Regards,
Cristiano.


Originally posted in cdnusers.org by clsantos

  • just make sure you have "setRCFactor -xcap ###".  You can play around with the number to see the effect on your timing.  You could use the spef from extractRC within SOC and the spef from you signoff tool and input both spefs into "ostrich" to get ###.

    li siang


    Originally posted in cdnusers.org by lisiang

  • Thanks lisiang,

    The fact is that command "timeDesign -postRoute" automatically set "setExtractRCMode -declouped" before running RC extraction and delay calculation.
    I did some tests and I think the only way to avoid it is running "timeDesign -postRoute -reportOnly" after extract coupling caps.

    Cristiano.


    Originally posted in cdnusers.org by clsantos

  • i am suprised that the -xcap will not have effect on time using just "timeDesign". Even with the -decoupled, the extraction should still calculate the xcap and then add it to the total gnd cap. Did you try different xcap value and check to see if it produce the same/different timing?

    li siang


    Originally posted in cdnusers.org by lisiang

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.