Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

What happens in extract RC in relation to SOC encounter?

Status
Not open for further replies.
P

p_shinde

Full Member level 5
Joined
Feb 25, 2006
Messages
292
Helped
6
Reputation
12
Reaction score
2
Trophy points
1,298
Location
tokyo
Activity points
3,455
extract RC

hey,

can anyone tell exactly wat happens in extract RC...in relation with SOC encounter..........????
wat r the inputs we r going to give???

reply soon


prasad
 

Re: extract RC

hi u need to import your design file after layout.. since celtic ic is integrated with encounter so you no need to import some file.. after finishing place and route run celtic ic it will extract and resistor and capactor values for each net this between nodes then u generate spef file from it and import it into timing analysis tool prime time for post layout timing analysis and do sign off..

ensure that the layout is drc and lvs clean..


Regards
Shankar
 

Re: extract RC

Hi,

if we extract resistor and cap values in cetlic then what we do using Fire and Ice /Star-RCXT which is used for RC extraction????????



thanks,
Prasad
 

Re: extract RC

Celtic is used to do noise and crosstalk analysis. You cant use it for extraction
 

Re: extract RC

You can perform two types of extraction in Encounter:
Native RC ExtractionUsed to provide quick parasitic extraction (default mode) for design prototyping, or to generate more accurate parasitics (detailed mode) for cross-coupling and signal integrityanalysis.

Sign-Off RC Extraction using Fire & Ice® QX
Used to obtain the most accurate detailed parasitic extraction. Fire & Ice can also beused with native extraction to generate RC scaling factors.

Native (Default) Used during optimization both before and after clock
tree synthesis.
Native (Detailed) Used during post-route optimization.
Sign-Off (Fire & Ice) Used during chip assembly and timing sign-off
processes.

Hope it Helps.
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top