Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 15437
  • 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

Triggering callbacks

navi2582

Hi,

After loading the "CCSinvokeCdfCallbacks.il", I opened the schematic and again ran "CCSinvokeCdfCallbacks(geGetEditCellView())" but I am getting the following error messages,

\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* evalstring: argument #1 should be a string (type template = "ts") - nil
\e *Error* evalstring: argument #1 should be a string (type template = "ts") - nil
\e *Error* eval: unbound variable - process
\e *Error* eval: unbound variable - process
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil
\e *Error* putprop: first arg must be either symbol, list, defstruct or user type - nil

Am missing something?

I am using IC6.1.5-64b.500.9

Thanks,

Naveen

Parents
  • Andrew Beckett

    Naveen,

    If you run on the top level block, it's only going to call the callbacks for the instances placed - so if there's a failing there, it's because of any CDF callbacks on those devices. 

    The errors are probably coming as a consequence of the callbacks themselves. Seeing the data is probably the only way to debug this - but you could try typing:

    _stacktrace=50
    tracelength=50
    tracelevel=50

    and triggering the callbacks and seeing if the additional information makes it any clearer?

    Andrew.

Reply
  • Andrew Beckett

    Naveen,

    If you run on the top level block, it's only going to call the callbacks for the instances placed - so if there's a failing there, it's because of any CDF callbacks on those devices. 

    The errors are probably coming as a consequence of the callbacks themselves. Seeing the data is probably the only way to debug this - but you could try typing:

    _stacktrace=50
    tracelength=50
    tracelevel=50

    and triggering the callbacks and seeing if the additional information makes it any clearer?

    Andrew.

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.