• 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. Assura QRC run problem

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 126
  • Views 14558
  • 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 QRC run problem

emax
emax over 12 years ago

The Assura QRC run fails after LVS match. The QRC was setup using QRC -> Setup QRC
In the Setup tab all Output Formats are selected and Set As Default is Extracted View. The Technology and Rule Set is selected correctly using drop down menu and Template File is not selected.
For the Extraction tab all Allow Extraction Types are selected and Set as Default is RC. Nothing is changed in rest of the tabs. Selecting OK pops up a message to overwrite Template File /opt/<design kit installation directory>/assura_<design kit >_tech/rcx/.rcx_setup.tpl

Everything seems ok till now, but when QRC is run... a pop up message says: No technology directory found. and next the Run Form opens with Technology selection disabled. The QRC fails after run with the following error log

INFO (EXTQRCXOPT-243) : For Assura inputs, if the "output_setup -directory_name" option was not specified, it is automatically set to the input directory.
INFO (LBRCXU-108): Starting
/opt/assura412/tools/assura/bin/rcxToDfII /home/rusr/cds_130n/lvs_run/inverter2/__qrc.rcx_cmd -t -f /home/rusr/cds_130n/lvs_run/inverter2/extview.tmp -w /home/rusr/cds_130n/lvs_run/inverter2 -cdslib /home/rusr/cds_130n/cds.lib
Virtuoso Framework License (111) was checked out successfully. Total checkout time was 0.05s.
@(#)$CDS: rcxToDfII version av4.1:Production:dfII6.1.5:IC6.1.5.500.10 06/06/2012 18:36 (usimlx115) $
sub-version 4.1_USR2_HF17, integ signature 2012-06-06-0926
run on xyz.localdomain from /opt/assura412/tools.lnx86/assura/bin/32bit/rcxToDfII on Wed Jun 12 06:40:25 2013
Loading <design kit>/libInit.il ...
Loading <design kit>/loadCxt.ile ... done!
Loading context <design kit>' from library '<design kit>' ... done!
Loading context 'pdkUtils' from library '<design kit>' ... done!
Loading <design kit>/libInitCktPro.il ... done!
Loading <design kit>/libInitCustomExit.il ... Loading libInitCustomExit.il for <design kit> ... done!
Loaded <design kit>/libInit.il successfully!
INFO (LBRCXU-114): Finished /opt/assura412/tools/assura/bin/rcxToDfII
INFO (LBRCXM-642): Constructing the RCX run script
INFO (RCXSPIC-27050): Could not open file /home/rusr/cds_130n/lvs_run/RCXspiceINIT for reading
ERROR (LBRCXM-644): Bad return status from RCX script generator. 0x100
INFO (LBRCXM-709): ***** QRC terminated abnormally *****

The actual name of pdk is replaced with <design kit> in the above log. I suppose some configuration is not correct as the same set of tools works fine with Cadence gpdk045. Please help to resolve this issue.

  • Cancel
  • berndfi
    berndfi over 12 years ago

    I'm pretty sure you are pointing to the wrong technolgy directory
    The file "RCXspiceINIT" should be taken from the technology directory.
    Have you checked if it exist in the directory mention in the info message and if you have read access to it?
    "INFO (RCXSPIC-27050): Could not open file /home/rusr/cds_130n/lvs_run/RCXspiceINIT"
    You probably should not overwitre the PDK setup template with your settings.

    • 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