• 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. Custom IC SKILL
  3. leLayerSize didn't work for pcell, is there any way around...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 2658
  • 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

leLayerSize didn't work for pcell, is there any way around it?

kpai
kpai over 15 years ago

Hi,

My current pmos pcell came with a fix NW around it, but due to our design need, we need to have an extra large NW from OD outward.

Therefore, I've use leLayerSize as following and hope that it will work.

cv=geGetEditCellView()

leLayerSize(cv list("OD" "drawing") 1.5 list("NW" "drawing"))

But, as the result, leLayerSize command didn't recoganize pmos and return me a nil.

As I tried to change the "display level" to 2 and wonder if leLayerSizer will work.  Still, it didn't work.

But, as I tried to cover the pmos device with OD over to whatever it came with it then set the leLayerSize command again.

This time it works and I saw the extra NW layer over it as I want to.

From this, I realized that leLayerSize didn't work on pcell.   Is there any way around it?

By the way, I'm using 5.10.41 version.

Thanks,

Kathy

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    Kathy,

    I think it would be wise to go on a SKILL course - you've managed to significantly change my suggestion so that it wouldn't work...

    Various things you've done wrong:

    1. inst in your case is a list of instances, rather than a single instance in my case
    2. You are looking for the OD layer purpose pair object in the top level cellView, rather than in the master for the pcell instance
    3. It probably therefore doesn't find any OD shapes.
    4. And hence no NW gets created
    5. Not sure why you changed it the way you did. It suggests you really don't understand what an instance is.

    If you want to process all the instances, you could do:

    cv=geGetEditCellView()
    foreach(inst cv~>instances
      master=inst~>master
      ; find the LPP object within the pcell instance
      OD=car(exists(lpp master~>lpps lpp~>layerName=="OD" && lpp~>purpose=="drawing"))
      ODshapes=foreach(mapcar shape OD~>shapes
        dbCopyFig(shape cv inst~>transform)
      )
      dbLayerSize(cv "NW" ODshapes 1.5)
      ; remove the temporary copy of OD shapes into the cellView
      foreach(shape ODshapes dbDeleteObject(shape))
    ) ; foreach inst

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    Kathy,

    I think it would be wise to go on a SKILL course - you've managed to significantly change my suggestion so that it wouldn't work...

    Various things you've done wrong:

    1. inst in your case is a list of instances, rather than a single instance in my case
    2. You are looking for the OD layer purpose pair object in the top level cellView, rather than in the master for the pcell instance
    3. It probably therefore doesn't find any OD shapes.
    4. And hence no NW gets created
    5. Not sure why you changed it the way you did. It suggests you really don't understand what an instance is.

    If you want to process all the instances, you could do:

    cv=geGetEditCellView()
    foreach(inst cv~>instances
      master=inst~>master
      ; find the LPP object within the pcell instance
      OD=car(exists(lpp master~>lpps lpp~>layerName=="OD" && lpp~>purpose=="drawing"))
      ODshapes=foreach(mapcar shape OD~>shapes
        dbCopyFig(shape cv inst~>transform)
      )
      dbLayerSize(cv "NW" ODshapes 1.5)
      ; remove the temporary copy of OD shapes into the cellView
      foreach(shape ODshapes dbDeleteObject(shape))
    ) ; foreach inst

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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