• 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. virtuoso stream in by SKILL code question

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 11803
  • 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

virtuoso stream in by SKILL code question

GGLin
GGLin over 4 years ago

importCommand = strcat("strmin -library " libName " -strmFile " layoutPath " -logFile " libName "_in.log" ) 

system(importCommand )

Currently I use the code above to import 2 GDS file into different lib then I want to create a new cell, which the 2 gds top cell are placed in this new cell. 

But I faced a problem that the the code after system command won't wait the system command completed and then I cannot get the cellview in the import lib.

and i also try the xstInDoTranslate and i found the same behavior

Is there any way to fix this problem or a better way to do this?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    I don't see why the system() command wouldn't be blocking - if you do system("sleep 30") it certainly blocks. Perhaps "strmin" is a wrapper which backgrounds the process? (that doesn't happen with the Cadence strmin as far as I know).

    If you look in the documentation, you can make xstInDoTranslate by doing:

    xstInSetField("virtualMemory" "true")
    xstInDoTranslate()

    There is also the xstInOnCompletion() callback you can defined which gets called when xstInDoTranslate has finished - so this could be an alternative way of achieving the same thing.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • GGLin
    GGLin over 4 years ago in reply to Andrew Beckett

    thanks!

    • 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