Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronic 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

How to use hard IP timings information in top module timing constraints

Status
Not open for further replies.

javi

Junior Member level 1
Joined
Feb 1, 2005
Messages
19
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
173
Hi,

I have an hard IP ( in Netlist form) with the timing information setup/hold to clock , clock to output delay , pad to pad delay and the maximum operating frequency. The given information looks likes a data-sheet report or say overall IP interface timing budget.

Now , when I integrate it into my top module with dont_touch options , how do I specify my top module clock timing constraints while taking considerations of the hard IP timings.

1. How to consider the setup_clock timing information of the IP. Will it affect the top module clock period specification? .
2. Similarly which portion (AT or RT ) of the top module timing analysis is affected by the clock to output delay of the IP.

I hope this is common flow query irrespective of the tools being used.
Is their any good document for any ASIC flow specifies IP FLOW integration / Timing constraints aspects.

Thanks,
Javi
 

feel_on_on

Full Member level 5
Joined
Apr 29, 2005
Messages
284
Helped
6
Reputation
12
Reaction score
4
Trophy points
1,298
Activity points
3,234
I think :

hard ip will communication with other module ,and if the same clock domain, you will check
the timing in the clock period constraint .
 

lostinxlation

Advanced Member level 3
Joined
Aug 19, 2010
Messages
701
Helped
197
Reputation
394
Reaction score
184
Trophy points
1,323
Location
San Jose area
Activity points
5,051
Standard cells are hard IPs. flops have setup/hold time, combinatorial std cells have input to output delay. Hard IPs are nothing different from those std cells in the design flow and you can treat them as large std cells.
 

Status
Not open for further replies.
Toggle Sidebar

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Top