• 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. Problem in running LVS in Assuran

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 125
  • Views 16065
  • 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

Problem in running LVS in Assuran

behrooz
behrooz over 14 years ago

Hi all,

I'm using IBM design kit for Cmrf8sf (V1.4.0.7DM), Assura version 3.2-5141, and Cadence version ic5.141USR5. A couple of month ago, I drew the layout of a big circuit and ran DRC/LVS/RCX and after cleaning up every error, I submitted the layout to Mosis for fabrication. The chip has been fabricated and now I'm measuring it. I'm skeptic regarding one part of the chip, so that's why I tried to repeat the whole process(DRC/LVS/RCX), again. As, the former server is not functioning any more, i copied whole the library (schematic/layout), to a new server, with the same bashrc, cds.lib, and other configurations. The problem is that, DRC works fine, and gives to error, but LVS doesn't complete completely, and returns back with the below errors:

 "Error:  There are two or more descriptions of the device with identical type ('Generic'), and name ('nfet_rf'), however number of terminals are not the same, details are given below.

'nfettw_rf aulvs cmrf8sf' pin names : [D G S B PI sx]  dfII terminal names: [D G S B PI sx]

'nfet_rf aulvs cmrf8sf' pin names: [D G S B]  dfII terminal names: [D G S B]

1 error(s) encountered, vldb not generated

Error- dfIITovldb  failed to execute

 

and then after some warnings:

*Warning* An error occured during Nvn PreExtraction. 

aveng terminated abnormally"

As I told, layout had already passed LVS, with no error, and I've not changed anything. Now even LVS doesn't run completely. If anybody has an idea, I'd be grateful if let me know about it.

 

Thanks

  • Cancel
Parents
  • behrooz
    behrooz over 14 years ago

    Thanks for the reply.

    You're right. On the new server I have access to PDK version,V.1.8.0.1 also. But, because on the former server(as I explained in my first posting), I created the schematic and layout using kit version 4, I'm continuing working with that version on the current server. Actually, I tried to set the configuration to newer design kits (compared to version 4) by changing the cds.lib, and .cdsenv files to point to new kits, but it gives error and doesn't open even the schematics of my circuit which its library had been created by V1.4.0.7DM. Do, you think that we can open libraries which have been created with older design kits with newer design kits. If No, so, still my problem in my first posting is remained. Why I get those errors in lVS?

     

    Best

    Behrooz

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • behrooz
    behrooz over 14 years ago

    Thanks for the reply.

    You're right. On the new server I have access to PDK version,V.1.8.0.1 also. But, because on the former server(as I explained in my first posting), I created the schematic and layout using kit version 4, I'm continuing working with that version on the current server. Actually, I tried to set the configuration to newer design kits (compared to version 4) by changing the cds.lib, and .cdsenv files to point to new kits, but it gives error and doesn't open even the schematics of my circuit which its library had been created by V1.4.0.7DM. Do, you think that we can open libraries which have been created with older design kits with newer design kits. If No, so, still my problem in my first posting is remained. Why I get those errors in lVS?

     

    Best

    Behrooz

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information