• 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. RF Design
  3. Copying read only problen in cadence virtuoso

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 63
  • Views 18420
  • 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

Copying read only problen in cadence virtuoso

robert 21
robert 21 over 5 years ago

Hello, i have a realy mistick thing going with copying libraries in cadence virtuoso,

When i copy straight forwart the whole library it gives me a warning that accsess was denied,but when i go into the library and copy it as a single file, then it goes fine.

another problem is it doesnt show in the massage console  ALL the files which could not be copied.(which is the much bigger problem,becuase i would have to pass threw all the subdirectories to verify if all files are there)

Is there a way to see which files wasnt able to be copied?

Thanks. 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    It's really unclear what you're saying (even ignoring the obvious typos). The subject says something about read only - what's readonly? You then talk about "go into the library and copy it as a single file" - what does that mean? What exactly were you doing (in both the case it didn't fully work, and the case when it did work)? What was the warning?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • robert 21
    robert 21 over 5 years ago in reply to Andrew Beckett

    Hello Andrew, I have a library lib1   with hirarchy of schematics.

    i have made a copy of the whole library called it lib1_copy as shown bellow, however when i try to go down the hirarchy in lib1_copy on some component then it goes into a schemtics in lib1 instead of its copy in lib1_copy.

    Where did i go wrong copying the library?
    Thanks.

    .

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 5 years ago in reply to robert 21

    Dear robert21,

    I totally understand your issue. You must manually update the subcircuits in your new directory "lib1_copy" to point to their versions in the "lib1_copy" library. A libray copy will not update the subcrciuits within the copied library to point to their versions in the "lib1_copy" library. This is not how a library copy works.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • robert 21
    robert 21 over 5 years ago in reply to ShawnLogan

    Hello Shawn,i tried to left click a symbol but there is no option to choose another schematics directory for this symbol.

    How can i change the schematics it descends to?(without defining new symbols for every copied subcircuit and building the whole  hierarchy from scratch) 
    Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 5 years ago in reply to robert 21

    Dear robert21,

    You must choose the "Properties" menu item (or type Shift-q with the symbol selected). This will bring up a panel showing the cell name, view, and library. You will need to change the library to your new library.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • robert 21
    robert 21 over 5 years ago in reply to ShawnLogan

    Hello Shawn,my hierarchy has many subcomponents,is there a way to do it automatickly?

    Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 5 years ago in reply to robert 21

    Dear robert21,

    robert 21 said:
    is there a way to do it automatickly?

    As I mentioned in my first response, without writing a SKILL script to traverse your schematic hierarchy, no.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to ShawnLogan

    None of this should be necessary. The statement that Shawn made:

    Unknown said:
    A libray copy will not update the subcrciuits within the copied library to point to their versions in the "lib1_copy" library. This is not how a library copy works.

    is not correct. This is the whole point of the "Update instances" checkbox on the form. If you don't have that checked, then the copies will be exactly the same as in the source library and no re-referencing will be done. If you enable the checkbox, then there are two choices, which will actually behave the same if the destination library doesn't exist and doesn't have any clashing cells. It should update any references to the source library (the "from" library) to the destination library in the copy (the copy updater which runs afterwards does this). So any schematics, configs, ADE views should get updated to fix the references. Hitting the Help button on the form will explain what it does.

    If the copy was done without the update, or it failed for some reason (which would be unusual - this is pretty reliable nowadays), then you can also select the new library in the library manager, and use Edit->Rename Reference Library and change the references to the original library to the new library. There's also the more powerful Edit->Change Library References which could be used to achieve a similar goal - so it's fairly easy to do it for the entire library.

    No need for SKILL here.

    Regards,

    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