Stats

  • Locked Locked
  • Replies 10
  • Subscribers 127
  • Views 16393
  • 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

Assura LVS using: setenv OA_UNSUPPORTED_PLAT linux_rhel40_gcc44x

bartman

I am having an LVS problem and I noticed this post.  I am not sure if anyone is still around (based upon the 2010 responses) to reply.

At the end of the lvs report I have the following message:

Preprocessing layout network phase 2
*ERROR* Device 'pfet(Generic)' on Schematic is unbound to any Layout device.
*ERROR* Device 'nfet(Generic)' on Schematic is unbound to any Layout device.
*ERROR* UnBound devices found.
Info: All devices must be bound or filtered for comparison to be run.
Exiting nvn.

It implies that I have devices in the schematic which cannot be matched to a layout device.  I have tried this in calibre and succeeded in getting a clean LVS; so I know the layout and schematic do match.  I would like to have assura working as well.  One possible issue is in the use of multiplicity; m>1 for every transistor in the schematic.   The LVS checks using assura for devices which have m=1 have worked.  Is it possible to fix this problem ?

alan

Parents
  • bartman

    Hi Quek,

    I modified the compare rules via the assura menu; I paid special attention to what you had asked me to do and then realized that these rules were not 'activated'; once I activated them there was 'good news' & 'bad news'.

    The good news (from the tail of the log file) is that it ran without aborting; although the LVS dialog box still does not activate:

    Assura LVS terminated normally.

    Run ended: Mon May 16 10:10:51 2016
    *****  Assura terminated normally  *****

    The bad news is that the layout and schematic, according to assura, still do not match.  As I mentioned before it passed with calibre; I looked at the file inside the run directory (e.g. run.lvsdb/stat) and here is what I have:

    ; Assura generated file -- DO NOT EDIT --
    ; Do NOT rely on the content of this file, it may change.
    ;
    2 filter reduce swap match
    1 3 ( ( "nfet" "nfet" "Generic" 0 0 0 0) ( "nfet_m0" "nfet_m0" "Generic" 8 8 0 0) ( "pfet" "pfet" "Generic" 0 0 0 0) ( "pfet_m0" "pfet_m0" "Generic" 9 9 0 0) ( "subc" "subc" "Generic" 1 1 0 0))

    -----------
    This is difficult to read because it is not easily matched to particular schematic devices.  I am having difficulty, especially with subc, to understand if assura is talking about a 'single' device or multiple devices.  All subc devices have m=1.  "nfet_m0", is there a way, for example, to tie this one back to a particular nfet in the schematic ?


    best regards,

    alan

Reply
  • bartman

    Hi Quek,

    I modified the compare rules via the assura menu; I paid special attention to what you had asked me to do and then realized that these rules were not 'activated'; once I activated them there was 'good news' & 'bad news'.

    The good news (from the tail of the log file) is that it ran without aborting; although the LVS dialog box still does not activate:

    Assura LVS terminated normally.

    Run ended: Mon May 16 10:10:51 2016
    *****  Assura terminated normally  *****

    The bad news is that the layout and schematic, according to assura, still do not match.  As I mentioned before it passed with calibre; I looked at the file inside the run directory (e.g. run.lvsdb/stat) and here is what I have:

    ; Assura generated file -- DO NOT EDIT --
    ; Do NOT rely on the content of this file, it may change.
    ;
    2 filter reduce swap match
    1 3 ( ( "nfet" "nfet" "Generic" 0 0 0 0) ( "nfet_m0" "nfet_m0" "Generic" 8 8 0 0) ( "pfet" "pfet" "Generic" 0 0 0 0) ( "pfet_m0" "pfet_m0" "Generic" 9 9 0 0) ( "subc" "subc" "Generic" 1 1 0 0))

    -----------
    This is difficult to read because it is not easily matched to particular schematic devices.  I am having difficulty, especially with subc, to understand if assura is talking about a 'single' device or multiple devices.  All subc devices have m=1.  "nfet_m0", is there a way, for example, to tie this one back to a particular nfet in the schematic ?


    best regards,

    alan

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.