• 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. PEX error in Assura

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 14341
  • 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

PEX error in Assura

whitefan
whitefan over 11 years ago

Hello,

     I am using Virtuoso front to back design environment 5.1.41 and Assura version av3.1 (sub version 3.1.7_USR1_HF5) . I created 2 cellviews. First is simple inverter where I generated its layout , DRC and LVS clean_ PEX was also successfully completed. Second cellview is of power amplifier where its DRC and LVS is clean i..e. schematic and layout is match but I stuck at PEX generation. Here I attached the pcx log file in .doc version(as it only allows to attach files with known formats) and one more thing is my working directory of cellview and layout is 'my file' and for LVS run directory is 'test2' and run name is 'ex2'. If anyone can suggest me on this then I will be very greatful. Thank you. 

Untitled 1.doc
  • Cancel
  • Quek
    Quek over 11 years ago

    Hi whitefan

    Your RCX log file terminated with the following list of missing library model warnings: Normal 0 false false false EN-US ZH-CN X-NONE MicrosoftInternetExplorer4

    /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:SimSun; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

    *WARNING* No library model for device "N_18_G2".
    *WARNING* No library model for device "P_18_G2".
    *WARNING* No library model for device "N_33_G2".
    *WARNING* No library model for device "P_33_G2".
    ...


    This means that the required symbol or auLvs views cannot be found in your technology library. There are 2 ways to resolve this:
    a. If you do not use those cells, you can simply disable "Cellview check" option in QRC "Setup" tab.
    b. If you need those cells, you will need to ensure that the necessary views (symbol or auLvs) are present. You can check the required view by examining the extractDevice, extractMOS, etc cmd in the Assura extract rules file.

    Best regards
    Quek

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • whitefan
    whitefan over 11 years ago
    hello Quek, Thank you very much for your replay, I like to mention one thing here: I have a little problem with my FDK of UMC here. There are several models in library which are not shown in their respective categories, what I mean is that I have 6-7 models of resistors in my library, but when in schematic window create instance>browse>UMC it shows only one model of resistor in resistor category all other resistors are in the category of everything. These happens with some other models too which shown as "No library model for device "XXXXXX" in rcx.log file. I think the problem is related with this thing now and I don't whether it's a problem with my cadence installation or UMC library installation. If you have any idea about this then it will be very helpful to me, thank you once again. Here I am attaching 2 snapshots of my resistor problem in library (to give you an idea about what I am saying in this post.)
    • Untitled.png
    • View
    • Hide
    • 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