• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Cannot find a legal location....

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 92
  • Views 18004
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot find a legal location....

trigger
trigger over 15 years ago

 Hi there, 

 during floorplan using FE I get the following warning message :

**WARN: (SOCSP-270):    Cannot find a legal location for MASTER CELL BUX20. Check the library cell definition and floorplan.

Actually  I got plenty of these messages for a different cells...Could You point me to a document or guide where I'll be able to read more about this warning...or give some explanation about it?

I'm confused cause  when I'm running the script (I'm using scripts for every step for the digital flow - synthesis, floorplan, placement, etc...) on another machine which actually uses a little older version of the FE I do not get this message...so I do not know which one is correct and what causes the warning message...I'll be glad on any help...

Thanks for Your time,

Regards... 

 

 

  • Cancel
  • Kari
    Kari over 15 years ago

     Hi Trigger,

    Check the LEF for the BUX20 cell. What SITE is defined for it? Is that SITE defined in your tech LEF? And does your floorplan have rows made from that type of SITE? If so, is there open room to place cells (meaning, the rows are not covered by blockages, macros, etc.)?

    - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • trigger
    trigger over 15 years ago

     Hi Kari,

     thanks for the reply...

    The SITE defined is 'core'...it looks like:

    MACRO BUX20
        CLASS CORE ;
        FOREIGN BUX20 0 0 ;
        ORIGIN 0.000 0.000 ;
        SIZE 18.200 BY 13.000 ;
        SYMMETRY X Y ;
        SITE core ;

         ..... 

     ...but at the technology LEF file nothing is mentioned about SITE core...Does it has to be..? I get a warning about this:

    'Physical library does not contain description of any core site' 

    At the first look it seems that at the floorplan there isn't rows from that kind - SITE...about the open room place....You mean is there overlaping between rows and blockages for example..? If so...no..there is no overlaping

     

    During synthesis when LEF file is read I get another one info message :

    Not all cells of logical library exist in physical library.
    <PHY-291>.
     All cells of physical library exist in logical library. <PHY-294>

     

    I do not if this could be part of the problem..cause I get this message on the two machines...

     

    I'll be glad on any help from Your side...

     

    Thanks.... 

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 15 years ago

     Yes, you ABSOLUTELY have to have your SITE definitions in the tech lef. Sometimes they are in the macro lef along with the cells - it can be either place, but they do have to be defined somewhere. That's why you have no rows - Encounter doesn't have a SITE to build the rows with.

    The other warning means that you are reading in cells either in the design or in the .lib files that you are not reading in LEF for. The log file should list what cells these are. You will need to find the LEF for these cells. It's a separate problem from the row/SITE issue, but one that still needs to be fixed.

    Hope that helps,

    - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • trigger
    trigger over 15 years ago

     Hi,

    yes...as You are saying  it is defined at the library .lef file and not at the technology .lef file...about the rows...I have them..cause after executing the script I open the encounter graphically and I can see them...I have checked the cells height...I thought that it may be dfferent than that defined at the core..but it is the same....it is something with the cells that I'm missing cause I do not get it for every cell....is it possible that the space is not enought...I mean physically? 

    Abou the second one...I'm still investigating....

     

    Thanks a lot...

    Reagrds,Martin  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • TomBelpasso
    TomBelpasso over 15 years ago

    Strictly speaking, the SITE definintions do not have to be in the technology LEF, the first LEF file in the list of lefFiles.  But they must be defined before being used in any of the LEF files.  The site definition (from memory) would look like:

    SITE core

    CLASS CORE ;  # can be also be PAD or COVER, blocks nolonger need sites

    SIZE <x> <y> ;  # placer expects that x dimension will be smaller then y for horizonal row sites

    SYMMETRY Y ;   # legal values are X Y and R90, but only use Y for horizontal row libraries

    END core

     

    Note the SYMMETRY for sites has a different meaning then it has for cells.  Normally only use SYMMETRY Y, which would allow flipping (mirroring) in the Y dimension in rows.  If you specify X it would allow the cell to flip upside down in a North or R0 row , which can cause power shorts. 

    For cells it is a list of allowed orientations, so if you want cells to be placed in upside down rows, be sure to allow X  for cells.  If you want to allow mirroring of cells, then allow Y for cell symmetry.

    I know this is confusing, the developer of LEF want to save a token, so reused the SYMMETRY statement.  Not the best decision when viewed as a user.

    Regards,

    - Tom Belpasso

    Integrated-Vision.com

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information