• 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. Installation procedure of cadence virtuoso + MMSIM + assura...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 17678
  • 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

Installation procedure of cadence virtuoso + MMSIM + assura on centos

abdoboua
abdoboua over 6 years ago

can you please give me a well described setup guide for cadence IC 06.17.700 virtuoso + MMSIM 15.10.257 + assura 615 on centos

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

    For a start, none of these are officially supported on CentOS, so there won't be a guide associated with that.

    Also, this mix of versions is not a good combination - for a start, you'd need ASSURA41-617 (not 615). It's also a good idea to have a newer SPECTRE version (SPECTRE is the new release stream replacing MMSIM). We've had 3 major releases of SPECTRE since MMSIM151.

    In general you need to install these using InstallScape (which can be downloaded on downloads.cadence.com), with each in a separate directory. You'd then do:

    set path = ($ICHOME/tools/bin $ICHOME/tools/dfII/bin $MMSIMHOME/bin $ASSURAHOME/bin $path)

    (if using csh). There's no need to have an environment variable for ICHOME and MMSIMHOME (the tools just need to be in  your UNIX path), but $ASSURAHOME must be set as a UNIX environment variable. You'd also normally have $CDS_LIC_FILE set (again, a UNIX environment variable) pointing to your license server - e.g. 5280@licservername

    Hard to know how much to include without knowing where you are starting from. I'd suggest you contact customer support, or if you're a University then your university program contact (such as Europractice).

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    For a start, none of these are officially supported on CentOS, so there won't be a guide associated with that.

    Also, this mix of versions is not a good combination - for a start, you'd need ASSURA41-617 (not 615). It's also a good idea to have a newer SPECTRE version (SPECTRE is the new release stream replacing MMSIM). We've had 3 major releases of SPECTRE since MMSIM151.

    In general you need to install these using InstallScape (which can be downloaded on downloads.cadence.com), with each in a separate directory. You'd then do:

    set path = ($ICHOME/tools/bin $ICHOME/tools/dfII/bin $MMSIMHOME/bin $ASSURAHOME/bin $path)

    (if using csh). There's no need to have an environment variable for ICHOME and MMSIMHOME (the tools just need to be in  your UNIX path), but $ASSURAHOME must be set as a UNIX environment variable. You'd also normally have $CDS_LIC_FILE set (again, a UNIX environment variable) pointing to your license server - e.g. 5280@licservername

    Hard to know how much to include without knowing where you are starting from. I'd suggest you contact customer support, or if you're a University then your university program contact (such as Europractice).

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 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