• 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. PG Text

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 126
  • Views 16367
  • 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

PG Text

icartist
icartist over 6 years ago

I am on 6.1.7.

I've been away from Virtuoso for a number of years and now need to create Rev marks, etc but find no way to do so in the newest version of the tool.

It used to be that there was a PG text script so the layout designer could easily create copyright, rev marks, etc.

What happened?

Is there an equivalent solution in the 6x versions?

Do I have to go find an ancient program and try to make it work?

Yes I suggest Cadence add this in the Tools Menu!

Katy

  • Cancel
  • Quek
    Quek over 6 years ago

    Hi Katy

    Hope that the info in COS article 11380652 can help to resolve your problem.


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quantum Chip
    Quantum Chip over 5 years ago in reply to Quek

    It seems like this does not work in 6.18. The PG Text window works, but after hitting ok, the following error message is given:

    "*Error* quotient: can't handle (555.0 / nil)" 

    Is there any workaround, or is this just no longer a feature in 6.18? 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 5 years ago in reply to Quantum Chip

    Hi Quantum Chip

    I have just done some testing using IC618-500-5. PG text is still working fine. You might want to provide more details on the problem or to file a case to your local support centre so that they can check on it.


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Quek

    In addition, it might give some useful clues if you do:

    _stacktrace=50
    tracelength=50

    and then you will hopefully get a stack trace in the CIW with more detail that might help debug the issue.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quantum Chip
    Quantum Chip over 5 years ago in reply to Andrew Beckett

    Hi Andrew, Quek,

    Thanks for your response. Doing some further debugging, it seems that this function does work when I use it in a 65nm TSCM tech file layout, but is not working when done using my much simpler 7-layer custom MEMS tech file. I'm not sure why. This is using IC6.1.8-500-5. Running the suggested stack trace gives: 

    *Error* quotient: can't handle (572.0 / nil)
    <<< Stack Trace >>>
    (... in _leTbPointSnap ...)
    (... in _leTbPenStroke ...)
    (... in _leTbVectorText ...)
    (... in _leTbPGTextInternal ...)
    (... in _leCreatePGText ...)
    _leCreatePGText()

    Could be something related to the manufacturing grid?

    However, I ended up throwing together some alternative custom code for this purpose over the weekend as I wanted a pcell implementation of this anyway. This is meeting my needs at this point, so it may not be worth your time to try and debug a somewhat niche bug here. Thanks for your help, regardless. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 5 years ago in reply to Quantum Chip

    Hi Quantum Chip

    I think you may be right about the manufacturing grid. Assuming that the manufacturing grid for the MEMS techfile is 0.001, would you please execute the following in CIW and let us know if it helps?

    a. Execute the following in CIW
    tf=techGetTechFile(ddGetObj("yourMemsTechLib"))
    techSetMfgGridResolution(tf 0.001)

    b. Re-try PG text


    Best regards

    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quantum Chip
    Quantum Chip over 5 years ago in reply to Quek

    That fixed it! Thanks a lot.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 5 years ago in reply to Quantum Chip

    That's great. : )   A more complete fix would be to add the grid value to the "controls' section of your MEMS techfile and re-compile it. E.g.

    controls(
       ...
       mfgGridResolution( (0.001) )
       ...
    )

    • 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