• 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. saving designs in virtual memory to disk

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 17217
  • 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

saving designs in virtual memory to disk

harishgurram
harishgurram over 10 years ago

hi,

I am opening a cell view with dbOpenCellViewByType() command in read mode, and copying this view to some other view with the dbCopyCellView(...x...) command. 

 Now I am opening the copied view in append mode and making some edits on this layout view, and saving the same with dbSave(), and closing the view with dbClose() command. and also closing the view that is opened in read mode.

Now I am facing two problems,

The opened views are still existing in the virtual memory, they are not saving into the disk. how to write it into disk, and free virtual memory.

And I am getting a warning *Attempt to save read only design*...  (why this warning, i am not saving the read mode opened design.)

Is There  any commands to save the design in virtual memory to disk...Please help me

Thanks

Harish 

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

    Here's a transcript showing what I just tried (in IC616), which shows everything working fine. Which just shows the importance of what Lawrence mentioned - seeing your code. It may be you've made a mistake in the code which we might be able to spot if we can see it.

    cv=dbOpenCellViewByType("opamp090" "adc_sample_hold" "layoutTry")
    db:0x1ac01192
    cv~>mode
    "r"
    new=dbCopyCellView(cv "opamp090" "adc_sample_hold" "layoutTryCopy")
    db:0x1ac00492
    new~>mode
    "a"
    cv~>mode
    "r"
    new~>someNewProp="hello"
    "hello"
    dbSave(new)
    t
    dbClose(new)
    t
    dbClose(cv)
    t
    dbGetOpenCellViews()
    (db:0x1dd0f512 db:0x1dd0e892 db:0x1dd0e392 db:0x1dd0df12)
    dbGetOpenCellViews()~>cellName
    ("inv_2x_hv" "nmos2v" "pmos2v" "pmoscap2v")

    So as you can see, the original and copy are no longer in memory. It definitely saved it too:

    tryCopy=dbOpenCellViewByType("opamp090" "adc_sample_hold" "layoutTryCopy")
    db:0x1ac01192
    tryCopy~>someNewProp
    "hello"

    Regards,

    Andrew.

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

    Here's a transcript showing what I just tried (in IC616), which shows everything working fine. Which just shows the importance of what Lawrence mentioned - seeing your code. It may be you've made a mistake in the code which we might be able to spot if we can see it.

    cv=dbOpenCellViewByType("opamp090" "adc_sample_hold" "layoutTry")
    db:0x1ac01192
    cv~>mode
    "r"
    new=dbCopyCellView(cv "opamp090" "adc_sample_hold" "layoutTryCopy")
    db:0x1ac00492
    new~>mode
    "a"
    cv~>mode
    "r"
    new~>someNewProp="hello"
    "hello"
    dbSave(new)
    t
    dbClose(new)
    t
    dbClose(cv)
    t
    dbGetOpenCellViews()
    (db:0x1dd0f512 db:0x1dd0e892 db:0x1dd0e392 db:0x1dd0df12)
    dbGetOpenCellViews()~>cellName
    ("inv_2x_hv" "nmos2v" "pmos2v" "pmoscap2v")

    So as you can see, the original and copy are no longer in memory. It definitely saved it too:

    tryCopy=dbOpenCellViewByType("opamp090" "adc_sample_hold" "layoutTryCopy")
    db:0x1ac01192
    tryCopy~>someNewProp
    "hello"

    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