• 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. Issue with DRC - "run is invalid"

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 126
  • Views 4513
  • 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

Issue with DRC - "run is invalid"

apaj
apaj over 11 years ago

Hello,

when I try to run BEOL DRC everything seems to be in order. I don't get any errors, Assura successfully loads .rul and .rsf files, and .log file keeps feeling up normaly. I see all the errorchecks being performed and in the end I get "Assura terminated successfully!" message.

Nevertheless, it asks me whether I want to see the output and when I click Yes (or Ok, or whatever is there) it starts a window with a message (the same appears in CIW):

"The run "nameOfMyRun" in "myFolder" is invalid!"

and it offers me to click Ok. When I do - nothing else happens.

Please, would anybody have an idea what is going on?

Thank you very much.

  • Cancel
  • Quek
    Quek over 11 years ago

    Hi apaj

    Would you please try the following and update us on the results?

    a. Use a new run directory. Does it resolve the problem?

    b. Open up Assura DRC form and save the rsf file as "drc.rsf". Execute it in a terminal window using:
    terminal>assura drc.rsf | tee assura.log

    Open up the run data manually using "Assura->Open Run".

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • apaj
    apaj over 11 years ago

    Thank you for your time and effort.

    I had already tried creating a new folder and choosing it as a Run Directory - the result was the same ("run invalid").

    Now, the other thing you mentioned gave some feedback. I saved drc.rsf in the folder from which I run icfb (correct or shoud I have chosen a different place?) and run your command. What I get is pretty much the same like what happens in the .log file when I just run DRC through Assura.

    Nevertheless, I did notice something I did not see earlier. Somewhere in the begining of listing, it gives me:

    *WARNING* Cannot find <ASSURAHOME>/tools.lnx86/dfII/etc/tools/layoutXL directory to load environment variables
    Compiling rules...

    WARNING Undefined purpose in dfII.
        Purpose name 'CUST_2' doesn't exist, ignoring this purpose.
        SPHD_2 = layer("SP" type("CUST_2")) 

    Could these two warnings make problems?

    It seems to me that it ends as it should, but here is what happens at the end:

     Finished <ASSURAHOME>/assura//tools/assura/bin/avrpt

    Starting
    <ASSURAHOME>/assura//tools/assura/bin/avcallproc drc.rsf

    Loading tech rule set file :
    <PROCESSHOME>/RuleDecks/Assura/techRuleSets

    Finished
    <ASSURAHOME>/assura//tools/assura/bin/avcallproc

    Starting
    <ASSURAHOME>/assura//tools/assura/bin/avToGdsII drc.rsf
    @(#)$CDS: avToGdsII version av4.1:Production:dfII5.1.41:5.10.41.500.6.144 08/01/2012 07:01 (logavt05) $
    sub-version 4.1_USR2_HF20, integ signature 2012-08-01-0707

    run on <HOSTNAME> from
    <ASSURAHOME>/assura/tools.lnx86/assura/bin/32bit/avToGdsII on Thu May  1 09:34:50 2014


    Loading tech rule set file :
    <PROCESSHOME>/RuleDecks/Assura/techRuleSets

       Reading VDB ...
       Completed reading VDB.

       Writing stream file drc.gds...
       See assura_drc_fdk.gsm for statistics.
       Completed writing stream file.

    Finished
    <ASSURAHOME>/assura//tools/assura/bin/avToGdsII

    Starting
    <ASSURAHOME>/assura//tools/assura/bin/avcallproc drc.rsf -postCB

    Loading tech rule set file :
    <PROCESSHOME>/RuleDecks/Assura/techRuleSets

    Finished
    <ASSURAHOME>/assura//tools/assura/bin/avcallproc

    Run ended: Thu May  1 09:34:50 2014

    *****  Assura terminated normally  *****
     

    Regards.

    p.s. In the first warning there was a full absolute path, but I changed it when typing here and put <ASSURAHOME> instead. The same goes for <PROCESSHOME> and <HOSTNAME>

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • apaj
    apaj over 11 years ago

     Hm... Somehow I completely neglected your last sentence... I just saw that you are telling me to open the run manually in the end.

    And yes... I do get the Error Layer Window - thank you very much!

    But, since we are already here - what do you think, why does any of this happen? I mean, why not open it normally?

    Also, rereading my post, I noticed one more thing. When Assura is printing some path within <ASSURAHOME> it puts two slashes one after another, e.g.:

    <ASSURAHOME>/assura//tools/assura/bin/avcallproc

    What is that?

    Regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago

    Hi apaj

    The warnings in the log file and the double slashes (//) in the paths are not the cause of the problem. Although this should not be the cause of the error, would you please try disabling ?outputErrorLayers avParameter to see if it helps? This option generates an error gds file.


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • apaj
    apaj over 11 years ago

    Hello Quek.

    I looked for that variable in my .rsf file, but no such thing exist - so, I should be looking somewhere else, probably. Could you be more specific, please?

    Regards.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago

    Hi apaj

    The cmd can exists in 1 of the following 3 locations:
    - DRC form
    - Included rsf file
    - compare.rul file

    I think you are using this cmd because your log file states that an error gds file has been generated.


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • apaj
    apaj over 11 years ago

     Hello Quek,

    the command you mention, does not exist in DRC Run window nor in .rul file.

    Did you maybe mean ?outErrorLayers avParameter?  Because that one appears, but - it has been disabled all along (Use in Run unchecked). Also, the option Store all error layers to a gds file has also been disabled all along.

    The only one of avParameters that is enabled is ?avrpt.

    Regards.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago

    Hi apaj

    Yes, I meant "?outErrorLayers". Sorry about the typo. I think it is not disabled because the log file indicates that it is in use:

      Writing stream file drc.gds...
       See assura_drc_fdk.gsm for statistics.
       Completed writing stream file.


    Would you please search for it in the compare rules file or any included rsf file?

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • apaj
    apaj over 11 years ago

    Nope, the only thing containing "?out" in both .rsf and .rul files is:

    ?outputErrorLib t

    Regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago

    Hi apaj

    If setting outputErrorLib to nil does not help, I think it might be good to try a newer version of Assura and Virtuoso.

    Best regards
    Quek

    • 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