• 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. SKILL code to set y0 as valid layer

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 142
  • Views 15186
  • 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

SKILL code to set y0 as valid layer

mctang
mctang over 9 years ago

Hi All,

Is there any SKILL code to set y0 valid instead of using the instruction below ? The instruction below works, but I would like to set y0-y8 as valid layers by default when designers run my SKILL program. 

"Anyway, use the right mouse button menu in the palette (e.g. just to the right of the bit where you have the Valid, Used, Routing checkboxes) and pick Edit Valid Layers. You'll then see a "v" (lowercase) and "m" column appear in the main palette and a bunch of layers in red (make sure you turn off the "Used" checkbox too otherwise you may not see it - although if you've created the shape with SKILL, it would be in the cellView so it may be OK). Any of the non-valid layers will be in red - you can turn on the "v" checkbox and then do RMB->Edit Valid Layers again to exit the mode where you're editing the valid layers. It should now show up in the normal palette (you can of course filter for "y0" when in the edit valid layers mode)."

Thanks,

ManChak

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

    tf=techGetTechFile(ddGetObj("gpdk090")) ; or could use techGetTechFile(geGetEditCellView()) to get that associated with cellView
    ; next line is only needed if you want to permanently change the techFile on disk (you may not have permission)
    ; techReopenTechFile(tf "a")
    foreach(layer '("y0" "y1" "y2" "y3" "y4" "y5" "y6" "y7" "y8" "y9")
      LP=techGetLP(tf list(layer "drawing"))
      LP~>valid=t
    )
    ; if did the reopen earlier, then need to save too:
    ; techSaveTechFile(tf)

    If you change the tech file to append mode, you only need to do the above once (because it will be permanently saved). However, I suspect you won't have permission to change the tech library so most likely you'd need to run the above code in your SKILL code every time to ensure that the layers are valid in this session.

    Alternatively, if you have a layout editor window open, you could just use the leSetLayerValid() function:

    foreach(layer '("y0" "y1" "y2" "y3" "y4" "y5" "y6" "y7" "y8" "y9")
      leSetLayerValid(list(layer "drawing") t)
    )

    Regards,

    Andrew.

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

    tf=techGetTechFile(ddGetObj("gpdk090")) ; or could use techGetTechFile(geGetEditCellView()) to get that associated with cellView
    ; next line is only needed if you want to permanently change the techFile on disk (you may not have permission)
    ; techReopenTechFile(tf "a")
    foreach(layer '("y0" "y1" "y2" "y3" "y4" "y5" "y6" "y7" "y8" "y9")
      LP=techGetLP(tf list(layer "drawing"))
      LP~>valid=t
    )
    ; if did the reopen earlier, then need to save too:
    ; techSaveTechFile(tf)

    If you change the tech file to append mode, you only need to do the above once (because it will be permanently saved). However, I suspect you won't have permission to change the tech library so most likely you'd need to run the above code in your SKILL code every time to ensure that the layers are valid in this session.

    Alternatively, if you have a layout editor window open, you could just use the leSetLayerValid() function:

    foreach(layer '("y0" "y1" "y2" "y3" "y4" "y5" "y6" "y7" "y8" "y9")
      leSetLayerValid(list(layer "drawing") t)
    )

    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