• 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 SKILL
  3. how to return from the long run time jobs

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 13891
  • 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

how to return from the long run time jobs

acom
acom over 9 years ago

Hello ,

I am trying to write some skill code to run "oaScan -lib -cell -view" for the cell hierachically.

For example, there is a chip A which includes Block B1 and B2.Block B1 includes Cell C11,C12; Block B2 includes Cell C21,C22.

cellList=list(C11,C12,C21,C22).

foreach(cellName cellList

csh(strcat("oaScan -lib testlib -cell " cellName " -veiw layout" " >> " rstFile)

) 

But i found the "oaScan -lib -cell -view" runs a long time for some cells without outputting anything.For example, it runs a long time for C11.

My issue is how i could tell the foreach to jump out for C11 and printf("the c11 couldn't be run) after a long time running (eg. 10 minutes).And begin to run for C12,C21,C22.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Rather than writing your own, you could use the utility provided in the IC617 installation which does this for you.

    load(prependInstallPath("etc/tools/cdba/cdsScanHier.il"))

    then:

    cdsScanHier(libName cellName viewName scriptName
               [?repair t/nil] [?logfile oaScan_logFileName] [?runScript t/nil])

    Finds all cells used in the hierarchy and generates a shell script. The shell script will do the actual oaScan runs.

      libName    The library name of the top cellView
      cellName   The cell name of the top cellView
      viewName   The view name of the top cellView
      scriptName The name or full path to where the oaScan commands will be written
     ?repair    When specified, the oaScan command will have the -repair switch
     ?logFile   When specified, the cumulative oaScan logs will be appended to  this file. Otherwise, the name "scanHier.log" will be used.
     ?runScript When specified, will execute the generated script and display the  output in a view window (if this function was run from DFII; no viewFile is shown if run from dbAccess).

    Alternatively, from UNIX, you can use:

    $CDSHOME/tools/dfII/etc/tools/cdba/scanHier.sh  

    e.g. scanHier.sh libName cellName viewName scriptName

    To fix  your code, you'd have to use ipcBeginProcess rather than csh, so that you can have something non-blocking - although it's not going to be entirely trivial to fix (without rewriting the code for you, which I don't have the time to do).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • acom
    acom over 9 years ago

    Hello Andrew,

    I have given this a simply try.Does this only generate the run file?And then i should use the run file to run?

    Thanks

    acom

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • acom
    acom over 9 years ago

    Hello Andrew, i have run the shell file generated by the cdsScanHier.

    And the shell script also is running for a specific cell for a long time without any output.:(

    As a result, oaScan for all other cells couldn't proceed.:(

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Perhaps you should contact customer support?

    Andrew.

    • 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