Tuesday, January 06, 2009     Register | Login | Search | Contact Us
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Subject: RC extraction mode for postRoute timing analysis
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
clsantos
Posts: 31
Online: User is Offline
6/18/2007 1:01 PM  
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.

lisiang
Moderator
Posts: 48
Online: User is Offline
6/19/2007 4:32 PM  
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
clsantos
Posts: 31
Online: User is Offline
6/20/2007 6:24 AM  
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.
lisiang
Moderator
Posts: 48
Online: User is Offline
6/20/2007 11:20 PM  
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
Posting to forums is available to community members only.
Login or Register

Forums > Digital IC > Floorplanning, Place and route > RC extraction mode for postRoute timing analysis


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.