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.

grouping instances in SoC encounter

Status
Not open for further replies.

pavi622

Junior Member level 1
Joined
Apr 2, 2012
Messages
19
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,400
Hi,

I am working on a design, where i dont want to optimise a group of instances.
How can i go about doing this using SoC encounter
 

In your SDC input to encounter, you can add

set_dont_touch [get_cells instance1]
set_dont_touch [get_cells instance2]
set_dont_touch [get_cells instanceX]

This will prevent encounter from optimizing instance1, instance2, instanceX.

Usually, logic optimization is done during synthesis. In RC, 'set_attribute preserve true [find / -instance dut]' will be converted to 'set_dont_touch [get_cells dut]' in sdc.
 

What do you mean by optimize?
Not removed the logic
Don't change the driver
Don't changed the logic ???

Dont_touch will avoid to removed the logic but the driver could be changed.
 

the thing is the design contain some memory, but memory complier is not available for hardening the memory. While optimising the rest of the logic, the memory which is realised as flops are also optimised. Reason is SoC encounter see these flops as just instances/standard cell.
As a result, timing cant be closed at desired frequency & is also leading to very high setup & hold violations.

So how to optimise the rest of the design without touching the memory part.
 

you could not, because you surely need the specific memory timing model, that will impact your design.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top