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.

Encounter DEF & Design Compiler

Status
Not open for further replies.

eeStud

Member level 1
Member level 1
Joined
Feb 17, 2011
Messages
37
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,286
Activity points
1,527
Hi all,
Can i read def file created from SOC Encounter into DC using extract_physical_constraints?
i have tries but got link error.

Thanks.
 

The DEF should contain only the macros, pads placement, rows and power rings.
 
  • Like
Reactions: eeStud

    eeStud

    Points: 2
    Helpful Answer Positive Rating
It would help to know the exact message-code.
Suggestions ...
1) See if the man-page for the exact link-error you get (e.g. "man LINK-123" or "man DCT-456" in the DC-Topo console) gives more specific insight (but it might be too general).
2) Examine at the DEF contents in an editor (it's an ASCII text file) to see if the top-level "DESIGN" name or any of the macros' hierarchical paths are wrong w.r.t. your netlist hierarchy.
3) Maybe you are forgetting to include a link path to a macro that is in the netlist.
Or you might be missing a path to the MW/FRAM view for a macro in the create_mw_lib or set_mw_lib_reference command.
Or you might have a problem with FRAM view consistency versus the Liberty/DB view, in which case you need to scrub through the log errors/warnings, and also not be inadvertently suppressing important ones (the check_library command can help with this).
 
  • Like
Reactions: eeStud

    eeStud

    Points: 2
    Helpful Answer Positive Rating
Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top