• 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. Set UNIX environment variable through in Cadence environment...

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 149
  • Views 29674
  • 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

Set UNIX environment variable through in Cadence environment through skill

rajs
rajs over 9 years ago

Cadence version using=IC616.

Hi ,

I have two questions which i have listed below

a)Not able to set PVDIR variable in unix through skill command.

system("setenv PVDIR /home/data/")

error message in unix terminal: sh: setenv: command not found

b)I want to streamout the gds and then execute skill code sequentially, if the error not exist in streamout or else terminate with error message.

   1)How to wait till streamout is done & How to check for error message. There is a user defined function "xstOutOnCompletion()", How to use 

         along with procedure.

envSetVal("xstream" "xstShowCompletionMsgBox" 'boolean nil)

xstSetField("library" libname)
xstSetField("topCell" cellname)
xstSetField("strmFile" strcat(cellname ".gds"))
xstSetField("attachTechFileOfLib" "tsmc90_tech")
xstSetField("view" "layout")
xstSetField("runDir" path)
xstSetField("summaryFile" "strmOut.sum")
xstSetField("virtualMemory" "true")
xstSetField("logFile" "strmOut.log")
xstOutDoTranslate()

 

Thanks,

rajs

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Harsha,

    For the first question, I don't know what you mean. You can run DRC and LVS in parallel, but I don't see what this has to do with the terminal you launched virtuoso from or how that relates to wanting to run commands in a terminal that you've launched. 

    For the second one, you could solve that by running some code which finds all things that needs saving and saves them. I'm not sure why you'd have unsaved items after a stream in, but perhaps you're doing some other manipulation in your code. If you are, you should remember to do dbSave() on each cellView when you've done.

    You could do something like this:

    (foreach cv (abGetModifiedCellViews) (dbSave cv))

    where abGetModifiedCellViews is this:

    /***************************************************************
    *                                                              *
    *                   (abGetModifiedCellViews)                   *
    *                                                              *
    *               Find all the modified cell views               *
    *                                                              *
    *    Note that this uses a couple of db calls which aren't     *
    *                        in the manual                         *
    *                                                              *
    ***************************************************************/
    
    (procedure (abGetModifiedCellViews)
      (let (cellViews)
           (foreach cellView (dbGetOpenCellViews)
                    (when (and
                           (dbIsCellViewModified cellView) 
                           /* cell can appear modified, even if read only (why?) */
                           (or 
                            (equal (dbGetq cellView mode) "a")
                            (equal (dbGetq cellView mode) "w")))
                          (setq cellViews (cons cellView cellViews))))
           cellViews))

    Regards,

    Andrew

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

    Harsha,

    For the first question, I don't know what you mean. You can run DRC and LVS in parallel, but I don't see what this has to do with the terminal you launched virtuoso from or how that relates to wanting to run commands in a terminal that you've launched. 

    For the second one, you could solve that by running some code which finds all things that needs saving and saves them. I'm not sure why you'd have unsaved items after a stream in, but perhaps you're doing some other manipulation in your code. If you are, you should remember to do dbSave() on each cellView when you've done.

    You could do something like this:

    (foreach cv (abGetModifiedCellViews) (dbSave cv))

    where abGetModifiedCellViews is this:

    /***************************************************************
    *                                                              *
    *                   (abGetModifiedCellViews)                   *
    *                                                              *
    *               Find all the modified cell views               *
    *                                                              *
    *    Note that this uses a couple of db calls which aren't     *
    *                        in the manual                         *
    *                                                              *
    ***************************************************************/
    
    (procedure (abGetModifiedCellViews)
      (let (cellViews)
           (foreach cellView (dbGetOpenCellViews)
                    (when (and
                           (dbIsCellViewModified cellView) 
                           /* cell can appear modified, even if read only (why?) */
                           (or 
                            (equal (dbGetq cellView mode) "a")
                            (equal (dbGetq cellView mode) "w")))
                          (setq cellViews (cons cellView cellViews))))
           cellViews))

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information