• 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 Design
  3. Why need to launch license every time?

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 125
  • Views 18095
  • 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

Why need to launch license every time?

emax
emax over 12 years ago

I have installed ic610 on CentOS 6.4 but failed to open schematic editor with an error:

(deLicense-5) Could not get the license for Schematics. Open aborted. 

I found a solution on another forum and it works by launching the license first using command: lmli before starting the virtuoso in work directory.

Now I do not want to launch the license by typing "lmli" every time I start a new virtuoso. Is it possible to append a "lmli" command in .cdsinit or is there an alternate solution for this?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    It would have helped if you'd had explained what "lmli" is; it's certainly not a standard command, and I only found it by searching a bit and finding a few mentions on the edaboard forums. It seems to be an alias definition to run "lmgrd -c pathToLicenseFile".

    I see no reason why you should have to start the license server each time you run the software; the license server should be launched once on whatever machine is your license server machine, ideally at boot time. This is covered in the licensing documentation that comes with the software.

    Then all you would need is to have the $CDS_LIC_FILE env var set to point to the port@host where it is running.

    In general running the license server each time you invoke virtuoso would fail because it would probably be running anyway, or you might be invoking virtuoso on a different machine than the license server host.

    Also, if the license server was not running, I would expect it to fail because of not being able to access the 111 (Framework) license - virtuoso shouldn't even start without that (in IC61 releases).

    Probably best to contact customer support if the above does not help resolve your issue.

    Regards,

    Andrew  

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • emax
    emax over 12 years ago
    Yes, its strange... the virtuoso starts without complaining for license but the schematic editor does.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • emax
    emax over 12 years ago

    Hi Andrew

    In my case virtuoso (ic610) starts without stating the license but of course the schematic editor does not start. I have veriffied this with "lmstat" command. Once I start the license with "lmli" command defined as alias in .bashrc as

    alias lmli='/home/eda/ic610/tools/bin/lmgrd -c /home/eda/ic610/share/license/license.dat'

    everything works fine.

    But I want the license to start at boot or at least automatically... how can I configure this? Please provide detailed configuration steps as I am new to linux.

    Also there is an issue mentioned in this post (reply #6):

    http://www.edaboard.com/thread148317.html

    that after editing LD_LIBRARY_PATH environment and invoking "source .bashrc" and using commands "killall lmgrd", "lmli", "virtuoso" there will be a license error... how that relates if the license is started at boot?

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    As I said, starting the license server each time is nonsensical. It's hardly surprising that you get license errors if you kill the license server off during an existing run of icfb - because then it has no license server any more.

    As I said, this is well documented - see  <instDir>/doc/license/license.pdf (which you could have found in any Cadence installation, and also by running cdnshelp, or cdsdoc in old releases). This covers how to start the license server at boot time.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • emax
    emax over 12 years ago

    Thanks, that's what I was looking for.

     One more question, for IC610 and MMSIM61 which oldest version of Assura and Calibre are compatiable? I suppose 610 use OA and Assura and Calibre should also be different from previous versions?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    If you are really using IC610 (check using help->about in the CIW), then those are both very old and unsupported versions. There would have been a corresponding Assura version (marked with 610 in the version info) but it's hard to be precise with releases that are 7 years old; none of these versions will be on our downloads site. 

    As for Calibre, that's not a Cadence product, so I can't help you with that (either).

    Do you really have to use such old versions?

    Kind Regards,

    Andrew 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • emax
    emax over 12 years ago

    Yes, I really have to use the old version (ic610).

    To be precise will ASSURA 4.12.004-615 lnx86 works with IC610 and MMSIM61. I know it is meant for ic615 but it should be backward OA compatible?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago
    See my reply to your other post
    • 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