Stats

  • Locked Locked
  • Replies 6
  • Subscribers 149
  • Views 15524
  • 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

Error marker when gen. PCell

RVERP

When I generate a pcell,  it includes a marker error.

If I look up the explanation, it says:

location: ("testLib" "pcTest" "layout")
reason:   Generating Pcell for 'pcTest layout'.

 Any idea what this means? If this is'nt enough, I can always post the PCell code.

 Thanks

Parents
  • Andrew Beckett

    My guess (I can't run your code because it is not complete) is that this is caused by the call to icsMatchedCrossQuadUnit() in your code. I'm guessing that this function also generates a pcell - and so it will output a message telling you that it is building a new pcell - and that output (because it's on stdout) will appear as a marker.

    In general I really would not create a new pcell within a pcell evaluation. Fine to instantiate another pcell, but building it doesn't make so much sense to me. It's not obvious why you would want to do that, rather than creating the pcell up front (outside of the pcDefinePCell).

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    My guess (I can't run your code because it is not complete) is that this is caused by the call to icsMatchedCrossQuadUnit() in your code. I'm guessing that this function also generates a pcell - and so it will output a message telling you that it is building a new pcell - and that output (because it's on stdout) will appear as a marker.

    In general I really would not create a new pcell within a pcell evaluation. Fine to instantiate another pcell, but building it doesn't make so much sense to me. It's not obvious why you would want to do that, rather than creating the pcell up front (outside of the pcDefinePCell).

    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.