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.

Liberty interface_timing attribute

Status
Not open for further replies.

k31th1408

Newbie level 1
Joined
Apr 9, 2010
Messages
1
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Location
California
Activity points
1,290
Someone suggested to use interface_timing=true for latches in .lib file. I cannot find info on what this attribute really does. In the Liberty reference manual, it says

Indicates that the timing arcs are interpreted according to interface timing specifications
semantics. If this attribute is missing or its value is set to false, the timing relationships
are interpreted as those of a regular cell rather than according to interface timing
specification semantics.

The problem is that this definition does not describe what "interface timing specifications
semantics" are and how it affects timing reports. Anyone have more info on this? Thanks!
 

Someone suggested to use interface_timing=true for latches in .lib file. I cannot find info on what this attribute really does. In the Liberty reference manual, it says

Indicates that the timing arcs are interpreted according to interface timing specifications
semantics. If this attribute is missing or its value is set to false, the timing relationships
are interpreted as those of a regular cell rather than according to interface timing
specification semantics.

The problem is that this definition does not describe what "interface timing specifications
semantics" are and how it affects timing reports. Anyone have more info on this? Thanks!

interface_timing=true is used for arbitrary cells that don't have a function or state table description. The timing arcs are used as-is with no attempt to validate them against a function. As such, this is not the best way to model a latch. If it's simple just use a "latch" group. If you need something more complex you can model it with a state table.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top