• 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. StrmOut from Virtual Memory

Stats

  • Locked Locked
  • Replies 13
  • Subscribers 143
  • Views 19207
  • 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

StrmOut from Virtual Memory

Yaosan
Yaosan over 15 years ago

I would like to make some modifications to my cellview in scratch view mode and stream that out directly from virtual memory. Is there a way for me to do it using SKILL i.e. without using the GUI (File > Export > Stream...)?

Thanks in advance!

  • Cancel
Parents
  • Yaosan
    Yaosan over 15 years ago

    Hi Andrew,

    I'm not sure when we're moving to IC614 but if it's already released then it probably won't be long before we can start using it.

    I have another question that are slightly unrelated. What is the proper way of working in scratch view mode? Should I create a new view in scratch mode and copy over the object one by one before I start doing the modification I need? This seems to be quite troublesome with all the new blockages, vias and other OA objects listed under different property of cellviews.

    I tried opening an existing, opened cellview in scratch mode, hoping it will be a new copy i.e. with new dbID that exists only in memory, but somehow it shares the same cellview ID as the original opened cellview. I also tried to use dbCopyCellView() but it won't let me copy to the scratch view unless I specify the overwrite flag, which will write the scratch view to disk, defeating the purpose of having one in the first place.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Yaosan
    Yaosan over 15 years ago

    Hi Andrew,

    I'm not sure when we're moving to IC614 but if it's already released then it probably won't be long before we can start using it.

    I have another question that are slightly unrelated. What is the proper way of working in scratch view mode? Should I create a new view in scratch mode and copy over the object one by one before I start doing the modification I need? This seems to be quite troublesome with all the new blockages, vias and other OA objects listed under different property of cellviews.

    I tried opening an existing, opened cellview in scratch mode, hoping it will be a new copy i.e. with new dbID that exists only in memory, but somehow it shares the same cellview ID as the original opened cellview. I also tried to use dbCopyCellView() but it won't let me copy to the scratch view unless I specify the overwrite flag, which will write the scratch view to disk, defeating the purpose of having one in the first place.

    • 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