• 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. oasisin to multiple destination libraries

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 6612
  • 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

oasisin to multiple destination libraries

eggnog
eggnog over 2 years ago

Hello!

I have an .oas with a large hierarchy and I want to oasisin the design, but have certain cells go to one destination library and other to another. (there are some frequently shared cells that I would like to have appear in a separate library)

I have the full list of cells that need to go into the separate library, but I don't see an easy way to have two destinations.

Is there an option I'm not aware of, or a way to do this with SKILL?

-E

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    I don't think this is possible. I think that both the cellMap option and also if  you use the piCellNameMap SKILL function, it can only map to a different library if it is a reference library (the documentation is really unclear on this, but this seems to be what I've seen from experimentation). In other words, if you already have a few cells in other libraries that you want to re-use and ignore from the OASIS file, you can do that, but not split which destination libraries are used.

    This seems a reasonable request to me. so I think it would be worth contacting customer support (create a case after logging in) and requesting an enhancement. It's possible I've missed some existing capability, but if you try to use a cell map file and the library is not in the ref library list, it ignores it (and tells you that it's ignoring it).

    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