• 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. (Bogus) Cadence error OSSGLD-19

Stats

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

(Bogus) Cadence error OSSGLD-19

dfreebird
dfreebird over 5 years ago

I am doing something I've done for a long time in IC5, with
no issue. IC6 however paints a whole bunch of this error text

ERROR (OSSGLD-19): A circular reference of property name was found in name ______

All over my schematics when I place a particular element. The
basic idea is, I am passing "location" info down deep through
the hierarchy using instance / CDF properties "section", "block",
"cell" and at intermediate stages I push through the hierarchy
by setting them to [@section], [@block], [@cell] until I get
down to the bottom where fixed values are assigned uniquely
(by hand) instead.

Now, the [@cell] ought to be "instance property value of 'cell'
pertaining to the present level and not at all circular. But it
flags with the remark, and it's doing this "checking" without
me asking it to. Probably some callback or something, it comes
when the instance is placed, not when schematic is checked.
The NLPexpr property "reflection texts" I placed are hijacked
with this error-barf despite having properties set from above.

Anybody recognize this "error" or know where it comes from
and how to defeat or retrain? It sure does ugly up my
schematics.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    The error is because of how it is trying to evaluate the labels - and looking through the source code it appears to be in where it handles inherited connection netSet/netExpr - which suggests that something in the NLP expressions are inherited connections (the lookup rules are slightly different than for conventional NLP expressions and properties).

    It's not a callback that is checking something - the whole point of these labels is that they are interpreted and hence it has to resolve them somehow.

    I've only found two references to the error reported (and one was internal) and neither were from use in label display. The only way to figure this out would be to see an example - assuming you can't upload a database here that shows this, customer support would be the best option (you can always suggest to whoever picks it up that they contact me on this one - I'm interested in figuring out what's going wrong).

    Andrew

    • 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