• 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. Problem Changing Resistor Parameters: Not Visible

Stats

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

Problem Changing Resistor Parameters: Not Visible

Jake98
Jake98 over 11 years ago

Hello and thank you for any help in advance,

I am having an issue with my Cadence environment/setup that will not allow me to see any of the parameter options for resistors (I have tried k1res, and multiple op resistors).  Object properties only shows Library Name, Cell Name, View Name.  No parameter options are available.  

 

The CIW shows the following:

 

schHiObjectProperty()

*Error* putprop: first arg must be either symbol, list, defstruct or user type - nil

<<< Stack Trace >>>

(... in bicmos7wlresOParea ...)

(... in bicmos7wlresLength ...)

(... in bicmos7wlresGeom ...)

(... in bicmos7wlResCB ...)

(... in bicmos7wlsetDefaultsCB ...)

(... in cmrf7sfsetDefaultsCB ...)

(... in cdfAppendParamFields ...)

(... in unknown ...)

funobj@0x20280e80()

(... in schiLoadParamFields ...)

(... in schPostInsertRegions ...)

(... in schShowCB ...)

(... in schUpdateShowField ...)

(... in schInsertDefaultRegions ...)

(... in schObjectChangeCB ...)

(... in schObjEventCB ...)

(... in geEcEventCB ...)

apply('geEcEventCB '("schHiObjectProperty" "setup" ptrnum@0x1fd37860 2))

(... in geEcStartCmd ...)

(... in schHiObjectProperty ...)

schHiObjectProperty()

*WARNING* (SCH-1156): CDF parameter function has problem. 

 

Can anyone diagnose my issue?  I am running Cadence 6.1.6 and am in IBM 7RF.

 

Thank you,

Jake 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Jake,

    The stacktrace indicates that it's a function in the PDK that is causing the problem, so you should contact IBM.

    Regards,

    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