• 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 Design
  3. Fluid Guard Ring porting can't show correct layer

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 3241
  • 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

Fluid Guard Ring porting can't show correct layer

Andy Su
Andy Su over 3 years ago

Hi! 

currently I tried use A foundry ported to B foundry,

and find abnormal from Fluid Guard Ring issue,

this Fluid Guard Ring just can't show the NPLUS layer 

I'm sure I recreate A and B foundry Fluid Guard Ring procedure(sorry I needed mark the foundry pdk name), 

is the foundry PDK cause or the my porting script mismatch?

or my create Fluid Guard Ring in CIW Technology File Manager procedure wrongs?

should I change any action?

the pic in layout ported from A to B foundry  like this show pcell Eval Failed


and zoom in like this, I know just the NPLUS can't thru the porting script(other layer ported and correct).

warning message as below 

I thought the layer lock before layer name data.
(in A foundry is "SN" layer, B foundry is "NPLUS" layer)
but another layer ported correct,
I'm confuse if my set wrong, should be all layer abnormal,
but just "SN" layer ported failed,
thanks tour reply!

Best Regards.

Andy Su

virtuoso version 

Loading techComp.cxt
*WARNING* (TECH-2000192): dbLayerOr: Invalid layer/purpose - ("SN" "drawing").
*WARNING* (TECH-2000192): dbLayerSize: Invalid layer/purpose - ("SN" "drawing").
Pcell evaluation for B/NW_RING/layout generated information. See layer/purpose "marker/error" shape with property "drcWhy" for description. You can get more details from file /tmp/_pcEvalq01489.
*WARNING* (DB-270001): Pcell evaluation for B/NW_RING/layout has the following error(s):
*WARNING* (DB-270002): ("error" 1 t nil ("*Error* Unable to create a device named 'NW_RING' because of (\"dbGetOverlaps\" 0 t nil (\"*Error* dbGetOverlaps: Invalid layer/purpose\" (\"SN\" \"drawing\"))). Redefine the device and try again.\n"))
*WARNING* (DB-270003): Error kept in "errorDesc" property of the label "pcellEvalFailed" on layer/purpose "marker/error" in the submaster.
*WARNING* (TECH-2000192): dbLayerOr: Invalid layer/purpose - ("SN" "drawing").
*WARNING* (TECH-2000192): dbLayerSize: Invalid layer/purpose - ("SN" "drawing").

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    It's almost certainly your porting script, but given that you've not shared that it's rather hard to know!

    You should check the parameters on the instance of the PCell:

    inst=car(geGetSelSet())
    foreach(mapcar prop inst~>prop list(prop~>name prop~>value))

    check whether any of those properties are referencing the original layers (my guess is that this might be the enclosingLayers parameter, but maybe there are others).

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andy Su
    Andy Su over 3 years ago in reply to Andrew Beckett

    Hi! Andrew, 
    I directly create  A and B foundry Fluid Guard Ring,
    and manual change library name from A fab to B fab,
    I have stupid question, how to use script like your mention as below?
    is in CIW interface?

    inst=car(geGetSelSet())

    foreach(mapcar prop inst~>prop list(prop~>name prop~>value))

    • 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