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.

SoC Encounter 4.2 warning: JKFFX1 and TBUFIXL modules not present in LEF file

Status
Not open for further replies.

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
hello,


after importing a design in SoC encounter 4.2 , i get an warning of 2 modules not present in the lef file, i.e JKFFX1 and TBUFIXL modules are not present in the lef file, which is rgt?

now whats the solution on this...?

thanks,
Prasad
 

Re: lef file

It means there is no LEF view for both the modules. Looks like either they are memory or custom blocks whose LEF has not been extracted or read into the tool. you can grep for these modules in both .lib and lef and see if they are missing in the lef file.
Have you read in all the lef files relevant to your design?
 

Re: lef file

ya those modules r not present in any of the lef files which we got from artisan libraries for TSMC 130nm tech?

so whats the soln on that?

thanks,
Prasad
 

Re: lef file

Where did your netlist come from? It seems like it was synthesized with libs other than those you are trying to do P&R with. Do you have a RTL for your design? If you do, it's worth trying to resynthesize the gate-level netlist with the libs that you have at your hand.
 

Re: lef file

First you have to establish the said modules are soft blocks or hard blocks. Two ways to check this -

1. check the .lib files. If the timing model of the block exist in the dot lib, then it is a hard block.

2. if a module is a hard block it sits in the RTL code as a black box.

If that s the case you should request lef of the blocks from the library vendor or IP provider (ie, the same folks who gave you the timing model of those blocks).

If the above is not true, then it is a soft block. You will have to resynthesize rtl bacause some where earlier you may have done synthesis incorrectly.
 

lef file

Hi,

I think they are std cell. If it is okay for you not to use it, then just mark it as don't use during synthesis.

Or you can simply comment it out from the .lib.

Regards,
Eng Han
www.eda-utilities.com
 

Re: lef file

I think this way may also work?

You specify whatever JKFF and the other one from the libraries you have on hand. Then resynthesis your RTL (if you don't have RTL, use synthesis tool to manipulate the cell reference to the ones you have). After synthesis, just forward the normal Encounter procedure.
 

lef file

How could I get the cell list which only in the timing library but not in the LEF ?
 

Re: lef file

In PKS there is a command called 'check_library' that crosschecks cells in LEF and .lib for consistency. cells whose LEF view is missing are reported. Not sure about SOC-E, but consult reference manual.
 

Re: lef file

the two modules are standard cells.. so you standard cell library got screwed up.. check you left and lib file that these cells are there... sometimes in lib it may be present and in lef is got missed up... so while synthesis it checks lib and puts the cell may be because of that you get error iwhen using lef file...

The solution is check the lef and if its not there while synthesis using don't use cells as these two cells... that easiest way..to get rid of problem..


Regards

Shankar
 

Re: lef file

Since its standard cell, and since LEF files only really give pin locations, you could always take a different JK cell with the same size and manually hack the pin locations to what they are in the actual GDS.

I've done it myself after receiving incomplete/unmatching versions of the cell libraries.

jelydonut
 

lef file

can any one provide th LEF specification?
 

lef file

specifications of lef .. :O

it contains physical information n matel info etc ..
thr r many lef lije
tech lef
std lef
macro lef
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top