Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 943
  • 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

Abstract Generator : 2 layouts of a same "Memory instance" identified as "Block" and "Core" why ?

samung

Hello,

I would like to understand one point : I have 2 layouts of a memory instance (array of bitcells, master control block, I/O ... which are not flatten), with a global PR Boundary all round the memory instance. Actually, that's two versions of the layout.

Abstract Generator consider one of the layout as a "Block cell" (ok this is expected) and the other as a "Core cell". Does anyone know how it happens ?

 I think, in my scripts I will force the cell to be either a "Block" either a "Core" depending if it is a Memory instance ("Block") or a standard cell ("Core"), in this way I will be sure of the operations which will occur with the layout as input and I will have a proper LEF file definition with "CLASS BLOCK" or "CLASS CORE". This is a weird behaviour ?

 

 

Thanking in anticipation.

 

P.

 

Tool :

 cadence_amsams2010.2c_mmsim/lnx/doc/abstract

IC6.1.5-64b.500.9 

  •  Hi,

    I just quickly checked this and it seems that any new view automatically gets put into the "core" bin.

    From an earlier post I suggested you move a cell from "core" to "block" so I believe this is O.K.

    I believe you moved one layout to "block" manually, the other was put into "core" automatically.I don't know any way that the tool would automatically put 2 different layouts into 2 different bins.

    Your last sentence is correct. Normally there are different rules controlling how the abstracts are generated (depending on the cell type).

    That is the reason for the different bin types.

     

    Colin

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.