• 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. textTopin issue

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 14737
  • 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

textTopin issue

mfaisal
mfaisal over 5 years ago

Hi 

In assura they using textTopin,  may I know what is textTopin equivalent to PVS ?

please advice

regards

faisal

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    If in Assura you are doing:

    in the geomConnect statement

    label(metal4_conn_text metal4_conn)

    and then:

    metal4_conn_text=textToPin( 31 type(0) )

    Then the equivalent in PVL is :

    layer_def metal4_conn_text 1067;
    layer_map 31 -texttype 0 1067;
    text_layer metal4_conn_text;
    port -text_layer metal4_conn_text;

    attach metal4_conn_text metal4_conn;

    The attach is like the label() in the geomConnect.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    If in Assura you are doing:

    in the geomConnect statement

    label(metal4_conn_text metal4_conn)

    and then:

    metal4_conn_text=textToPin( 31 type(0) )

    Then the equivalent in PVL is :

    layer_def metal4_conn_text 1067;
    layer_map 31 -texttype 0 1067;
    text_layer metal4_conn_text;
    port -text_layer metal4_conn_text;

    attach metal4_conn_text metal4_conn;

    The attach is like the label() in the geomConnect.

    Andrew.

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

    Hi Andrew,

    by original file, will get lvs result like below:
    we have extra pins.
    after add this command
    layer_def m1_textt 1098; // layer def ME1 1098
    layer_map 46 -texttype 0 1098; // layer_map 46-datatype 0 1098
    text_layer m1_textt;
    port -text_layer m1_textt;
    attach m1_textt ME1;
     now lvs result like below:
    now lvs show unattached label,
    I think I do wrong with my attach command.
    please advice.
    regards
    Faisal.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to mfaisal

    Faisal,

    I would suggest you contact customer support. Trying to debug what's wrong with little snippets of your rule deck and no visibility of the data, is rather hard!

    Andrew.

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

    Thanks Andrew for the great advice so far.

    Actually the problem statement is pretty straight forward...

    1.  This is my current layer definition for lvs recognition e.g. for metal 1

    -->  layer_def ME1 1022;  //Metal 1 polygon

          layer_map 31 -datatype 0 1022

    --> layer_def M1_TEXT 1023  //Metal 1 text

         layer_map 32 -texttype 0 1023

    --> port -text_layer M1_TEXT

    --> text_layer M1_TEXT

    2. What we want to achieve is to make the Metal1 drawing layer to be recognized by LVS as a text instead of the M1_TEXT layer.

         This is to allow us to use the same layer to draw Metal 1 polygon and also as a text layer.

    3. We tried the suggestions you gave earlier and it looks like it can either recognize the text or the polygon and not both at the same time.  So it will

        either result as a missing port (metal polygon over rule) or as unattached port (metal text over rule)

    Any more ideas to share ?

    Thank you

    Faisal

    • 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