Stats

  • Locked Locked
  • Replies 6
  • Subscribers 127
  • Views 17615
  • 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 error

jdgriggs
attached are screen shot of a simple inverter and the layout is drc clean but debug says there is a bad net when the nets match for both...I've done this design 4 times each from scratch and generate the same errors. I have tried using th permute tool but does not seem to help LVS issue. Your assitance is appreciated Regards James
  • Quek

    Hi jdgriggs

    Your mos devices have been extracted as generic devices. Hence source and drain pins will not be automatically permuted. VXL layout pin permutation is not related to Assura LVS, hence it will not resolve the problem. You can resolve the problem as follows:

    a. In Assura LVS form, go to "avCompareRules"
    b. Select "Network"
    c. Select "swapPins" and add the following expression for schematic side:
    swapPins("pfet(Generic)" "(p S D)")
    d. Run LVS

    Best regards
    Quek

  • 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

  • Quek

    Hi Alan

    Would you please kindly start a new post for your issue? This thread has already ended in 2010.

    Thanks
    Quek

  • bartman

    Hi Quek,


    I created a new post this morning.  But, I am not sure if I did it correctly.  I am checking it now.

    best regards,

    alan

  • bartman
    The title of the new post, dated today: Assura LVS using: setenv OA_UNSUPPORTED_PLAT linux_rhel40_gcc44x

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.