• 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 16063
  • 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
  • tkhan
    tkhan over 14 years ago

     Firstly you're using a version of the kit that is nearly 3 years old. The PDK is up to V1.7.X.X last I used it. From there on you need Assura-41 for DRC/LVS and EXT91 for extraction.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • 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
  • tkhan
    tkhan over 14 years ago

    i have not used V1801DM myself, but in my experience with V1701DM:

    1. if you are using IC5141, make sure your new cds.lib points to the .../cdslib51 folder and not .../cdslib as the former is for CDB and the latter is for OA.

    2. you need to update your simulation files to include the "section" parameter, it is no longer set in the .scs file itself.

    these changes are explained in detail in the documentation. as far as your lvs issues go, i don't know. perhaps Zach will be able to help you on that one.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tkhan
    tkhan over 14 years ago

    Also are you doing Assura LVS CDL mode or VLDB mode? The PDK requires you make a CDL netlist (creates cellname.netlist), use the CDL preprocessor (creates cellname.netlist.lvs), and use the latter as the schematic netlist source in Assura CDL mode.

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

    Hello,

     Thanks alot for the reply.

    Well, I tried to do all the steps that you kindly offered. First, I don't see any cdslib51 in kit version V1.4.X.XDM. I do see that in newer kit version though (version 6, 7,8). So, I'm sticking to cdslib. For "section" parameter, I don't get it completely, but I tried to add some other model libraries, in ADE, besides "allmodels.scs", like "design.scs",.., but then simulation gives errors. I know that in newer technologies like CMRF9Sf, we need to add them, but am not sure about 8sf. Again I don't know whether I got your suggesstion, correctly.

     About cdl format, I changed compare and binding rules from vldb to cdl, in LVS setup window, but sttill am seeing those errors in running LVS. You suggessted to talk to Zack, could you please tell him, have a look on my problem.

     

    Truly Yours

    Behrooz  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tkhan
    tkhan over 14 years ago

    As I mentioned those were my experiences with V1701DM, not V14XXDM, and everything is elaborated in the release notes. Do not add design.scs if you using V14XXDM, only in V17XXDM (and newer).

    Zach posts on this forum as well and if you're lucky he will look at this thread and shed some light on your problem. Otherwise if you are a MOSIS customer you can file a support request and one of their engineers will address your case.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Zach
    Zach over 14 years ago

    First of all, forget about and delete V14xx.  That is years old.  The cardinal rule with IBM design kits is to use the most current version.  The model file methodology changes from time to time (PDK to PDK).  You need to review the Spectre release notes located in the Spectre/doc directory in the PDK to determine the supported version, then find the Spectre setup information in the model reference guide located in the /doc directory to determine what files are needed.  Regards, Zach.

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

    Thanks Zach for the reply.

    But as you have read, in my former posting, I'm doing DRC/LVS/RCX on a library which has already been created with design kit V1.4.0.7DM. I tried to change the design kit with settings pointing to newer ones, but then even I can't open ADE, it freezes. Can we simulate a schematic, created with an older design kit, with a newer version? I can't draw the whole circuit and layout from begginig, as circuit and layour are pretty big.

     

    Regards

    Berhooz 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tkhan
    tkhan over 14 years ago

    I never had issues working with old designs when kits were upgraded, so I don't know why your ADE is freezing. Maybe upgrade your IC to latest ISR in case there is a bug?

    What did you do to "change the design kit with settings pointing to newer ones" ? All you really need to do to change which kit you are using is change where the rel@ symbolic link points to... Refer to spectre user guide for how to specify the model files in the newer kits. If you really want to play it safe, make a new working directory and copy .cdsinit, .cdsenv and cds.lib from the V18XXDM folder over, and add your existing designs to cds.lib. Be sure that you are using the tool versions specified in the various release notes.

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

    Hello agian,

    I upgraded cadence version from USR5 to ISR, but still ADE freezes.

    What I do is that I change the cds.lib, to point to newer design kits, and also I change the .cdsenv files. Actually, I have attached those files in addition to my assura_tech.lib to this email, because this is much more effective if you have a look on files, possibly I'm missing something there. Please let me know if you want my .bashrc file also.

    One important point. I just saw that if in the RSF include section of LVS setup window, instead of LVSinclude.rsf, I put deviceinfo.rul, LVS works and layout passes the LVS but then RCX, gives error in "capgen". As I told the assura_tech.lib file is attached 

    I went to Spectre manual and didn't see anything regarding rel@symbolic link, so if it's different from what I have done in attcahed files, please let me know.

    Regards

    Behrooz Nakhkoob

    Documents.zip
    • 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