Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 14298
  • 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 command to check to an instance of pcell got PcellEvalFailed.

cessej

Hi,

I searched the Cadence Manual but I can't find the right command/solution to check if a pcell instance got PcellEvalFailed.

Please help.

Parents
  • Andrew Beckett

    Actually, pcellEvalFailed messages are added using "old school" markers (i.e. a shape on the marker/error layer) rather than using OA markers.

    car(exists(lpp car(geGetSelSet())~>master~>lpps lpp~>layerName=="marker" && lpp~>purpose=="error"))~>shapes

    If this is non-nil, there are shapes on the marker/error layer. You can do the above with ~>errorDesc on the end to get the description of the error:

    car(exists(lpp car(geGetSelSet())~>master~>lpps lpp~>layerName=="marker" && lpp~>purpose=="error"))~>shapes~>errorDesc

     ("(\"quotient\" 0 t nil (\"*Error* quotient: Attempted to divide by zero\" (0 0)))")

    (for example).

    Kind Regards,

    Andrew.

Reply
  • Andrew Beckett

    Actually, pcellEvalFailed messages are added using "old school" markers (i.e. a shape on the marker/error layer) rather than using OA markers.

    car(exists(lpp car(geGetSelSet())~>master~>lpps lpp~>layerName=="marker" && lpp~>purpose=="error"))~>shapes

    If this is non-nil, there are shapes on the marker/error layer. You can do the above with ~>errorDesc on the end to get the description of the error:

    car(exists(lpp car(geGetSelSet())~>master~>lpps lpp~>layerName=="marker" && lpp~>purpose=="error"))~>shapes~>errorDesc

     ("(\"quotient\" 0 t nil (\"*Error* quotient: Attempted to divide by zero\" (0 0)))")

    (for example).

    Kind Regards,

    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.