Stats

  • Locked Locked
  • Replies 21
  • Subscribers 126
  • Views 21971
  • 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 problem in ibm 90nm pdk

iamlearning
Hi all,
Inspite of 'check and save'ing my schematic from the schematic window and recreating the cdl netlist several times, I am getting the following error when doing the LVS of a mimcap of ibm 90nm process with assura32-cadence ic613.

Loading IBM PDK cms9flp Procedures for Cadence Version

"av3.2:Production:dfII6.1.3:IC6.1.3.500.4"
Net Listing Mode is Analog
*Error* schematic cell: rf9flp mimcap symbol
The schematic was never extracted or is not current in the schematics editor.
Use the `Check and Save' operation in the schematics editor to correct this.
The lastSchematicExtraction property is missing.
1 error(s) encountered, vldb not generated
Error - dfIIToVldb failed to execute

*WARNING* /usr/local/cadence/assura32/tools/assura/bin/nvn exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated

This problem is only for the cells containg mimcap and iductor, because I could complete the lvs of an inverter successfully. Even, this error does not apear when I use assura317 instead of assura32.

Can anyone please give me any clue to get out of this strange error?
Thank You ...
Parents

  • Thank you Quek for your reply. But, both of my layout and schematic cells are named as 'caps' and the shcematic and layout 'cell name' fields of the lvs form are filled with this name. The library names are also same, the only difference is the 'view' fields of the lvs form- one is 'schematic' and another is 'layout'.

    I have another strange observation. This error did not appear when I checked lvs by assura317 first time. Then I checked the lvs again with assura32 and with the lvs form untouched. This error came that time. Next, I ran lvs once more with assura317 and with the lvs form still untouched, but strangely, this error appeared then. I followed these three steps for another cell and the story is exactly same. So, now I am getting this error both with assura317 and with assura32, whereas assura317 worked well previously.

    This seems strange to me ! Can you guess anything in it?

    Thank You,

    Best Regards

Reply

  • Thank you Quek for your reply. But, both of my layout and schematic cells are named as 'caps' and the shcematic and layout 'cell name' fields of the lvs form are filled with this name. The library names are also same, the only difference is the 'view' fields of the lvs form- one is 'schematic' and another is 'layout'.

    I have another strange observation. This error did not appear when I checked lvs by assura317 first time. Then I checked the lvs again with assura32 and with the lvs form untouched. This error came that time. Next, I ran lvs once more with assura317 and with the lvs form still untouched, but strangely, this error appeared then. I followed these three steps for another cell and the story is exactly same. So, now I am getting this error both with assura317 and with assura32, whereas assura317 worked well previously.

    This seems strange to me ! Can you guess anything in it?

    Thank You,

    Best Regards

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.