Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 4696
  • 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

layer num & layer ID

hi2yogi

I am checking layer ID in a layout data base with following command.

cv~>lpps~>layerHeader~>lpps~>layerNum

or

cv~>layerHeaders~>lpps~>layerNum

or

cv~>shapes~>layerNum

But it is not giving layer id as in *_Tech.layermap file.

i.e.  for  M2 pin & M2 drawing above command giving 15 15 , but in tech file  M2 pin  ..layer id is 17  32 &  for M2 drawing  layer id is 17 0.

please suggest me right way to check that ... 

Parents

  • The layerNum is the database layer number (there's a similar purpose number too which you can find with techGetPurposeNum()). However, that is the number used to store the layer in the database itself. The layerMap file is for the stream (or "GDSII") layer number - there is no requirement that this number is the same as the database number. So the technology database encodes the mapping from layer and purpose names to database layer numbers and purpose numbers. The layermap encodes the mapping from layer and purpose names to stream layer and datatype numbers.

    Regards,

    Andrew.

Reply

  • The layerNum is the database layer number (there's a similar purpose number too which you can find with techGetPurposeNum()). However, that is the number used to store the layer in the database itself. The layerMap file is for the stream (or "GDSII") layer number - there is no requirement that this number is the same as the database number. So the technology database encodes the mapping from layer and purpose names to database layer numbers and purpose numbers. The layermap encodes the mapping from layer and purpose names to stream layer and datatype numbers.

    Regards,

    Andrew.

Children
No Data

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.