• 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. Batch Oasis import problem and Library "refresh" using SKILL...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 511
  • 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

Batch Oasis import problem and Library "refresh" using SKILL code

vtboy51
vtboy51 11 months ago

I am working on a script to import multiple Oasis files into a single library, each file contains a single layers worth of data from our design, with hierarchy. My initial attempt was to use the "append" option on import, but some very odd things are happening to my data once in Cadence (broken pointers, data shifting, ..). I am seeing AREF/SNAME related errors in the import log, maybe related....?

My second attempt was to import a single file (still using the "append" option) then flatten the data, and then import the next file. Using this method things seem better, but some data seems to be missing.... I have confirmed, by doing the import from the gui, if I do a refresh on my library between each import things look good.

So a few questions, has anyone seen odd behavior like this and have a fix. Second, is it possible to call the refresh command from Skill after each file import?

  • Cancel
  • vtboy51
    vtboy51 11 months ago

    A correction to my original question. After some more testing I acutally need to do a "close data" after each oasis file import, not just a Library refresh. So I am also looking for the SKILL function to execute the close data routine.

    • 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