• 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. Mixed-Signal Design
  3. Unable to edit a cellview in a RAK

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 64
  • Views 17867
  • 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

Unable to edit a cellview in a RAK

mhkvy4
mhkvy4 over 6 years ago

Hello,

I was running the RAK for AMS designer and following the given instructions. When I try to open the example cellview in edit mode I get the following error:

Could not open "EXAMPLE top schematic " for edit. 

dbOpenCellViewByType: Unable to lock database file for Example/top/schematic.

It seems I can only open it for read. This makes it impossible for me to complete the rest of the RAK because I cannot edit the file at all. Anyone know how I can open the example in edit mode and not read? 

  • Cancel
Parents
  • Saloni Chhabra
    Saloni Chhabra over 6 years ago

    Can you also please confirm exactly which RAK are you working with? We'll fix the database so there are no edit locks in the first place.

    Thanks,
    Saloni

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mhkvy4
    mhkvy4 over 6 years ago in reply to Saloni Chhabra

    intro to ams designer simulation version 9

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Saloni Chhabra
    Saloni Chhabra over 6 years ago in reply to mhkvy4

    I've just downloaded the RAK and there are no edit locks in the library, so they have most probably been created by you then. Do you have more than Virtuoso sessions open working on the same RAK?

    When a lock file does exist for a view, the Library Manger shows who has edit permissions for that view. Next to the view name, there is a column called 'Lock' showing this (empty Lock field will mean the file isn't open for editing by anyone). Can you check if your config view is locked?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mhkvy4
    mhkvy4 over 6 years ago in reply to Saloni Chhabra

    it was an issue with some permissions which I managed to fix. However I am running into a new one when following the RAK and running the AMS simulation.

    I am getting the error that no connection module was found but I did include the connectlib libraries. I also tried compiling the amsConnectLibCompile script found in $AMSHOME/tools/affirma_ams/etc/install/amsConnectLibCompile

    The compile log gives me the error that ERROR:ncvlog binary does not exist or has wrong permissions 

    I am also getting the following error when I am trying to create the netlist

    *ERROR*: Error encountered while registering text designs in the configuration.
    Refer to the following messages and correct the errors.
    ncvhdl: *E,BADTMPENV: ycalc: Failed to open Directory file..
    ncvhdl_p: *F,NOYOPN: cannot open file file '/tmpdir/ncvhdXXXXXX'.
    irun: *E,VHLERR: Error during parsing VHDL file (status 2), exiting.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to mhkvy4

    First of all, it sounds as if the "configuration" step was not done when  installing your INCISIVE (or XCELIUM) installation. You should do that to ensure all reference libraries are compiled (InstallScape has a button to do configuration). Running the script would work if you have permissions, but you should ensure that <INCISIVEinstDir>/tools/bin is in your UNIX path before doing so.

    For the second error, do you have the $TMPDIR UNIX environment variable set? I get that error if I have $TMPDIR set to "/tmpdir" - not sure why you would do that if /tmpdir doesn't exist though.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mhkvy4
    mhkvy4 over 6 years ago in reply to Andrew Beckett

    The $TMPDIR env variable is not set to anything. Should it be set to something to avoid the error? 

    Again the error is the same as before

    ncvhdl: *E,BADTMPENV: ycalc: Failed to open Directory file..
    ncvhdl_p: *F,NOYOPN: cannot open file file '/tmpdir/ncvhdXXXXXX'.
    irun: *E,VHLERR: Error during parsing VHDL file (status 2), exiting.
    TOOL: irun(64) 15.20-s060: Exiting on Sep 23, 2018 at 01:31:29 CDT (total: 00:00:03)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to mhkvy4

    I can't see any way for this to happen without $TMPDIR being set somewhere. /tmpdir is not a normal default setting for the temporary dir location so I wouldn't expect it to be set somewhere.

    If you can't get to the bottom of this, please contact customer support.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to mhkvy4

    I can't see any way for this to happen without $TMPDIR being set somewhere. /tmpdir is not a normal default setting for the temporary dir location so I wouldn't expect it to be set somewhere.

    If you can't get to the bottom of this, please contact customer support.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • mhkvy4
    mhkvy4 over 6 years ago in reply to Andrew Beckett

    Ok I just checked the env variable is set to /tmpdir

    What should the $TMPDIR env variable be set to? Or should I not use the variable at all? 

    edit: The $TMPDIR env variable was set to /tmp and that fixed the issue. This thread can be closed now. Thanks for the help. 

    • 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