• 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. Matlab Error When Starting from Assembler

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 10917
  • 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

Matlab Error When Starting from Assembler

strat57
strat57 over 3 years ago

I am getting a Matlab error when I try to start Matlab using the Assembler results toolbar button.  The error is an "Invalid use of operator".

I think the problem is, the run command ADE is trying to get Matlab to use, needs single quotes.  For example, it should be

run('/tmp/adeInitMatlabkn8530.m')

Is this a setup problem, or is there an environment variable or configuration somewhere that is not set correctly?

Thanks

Trent

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    Trent,

    It should be run with quotation marks around the temporary file name. Which IC sub-version are you using (Help->About in the CIW)? Also, which MATLAB version are you using?

    Once MATLAB is running, can you check the process command line? For example, this is what I have:

    workshop_14> ps -ef | grep axlMatlab
    workshop 96444 95423 0 06:41 pts/3 00:00:00 /export/home/apps/IC618_isr/tools/bin/64bit/cdsServIpc -c 58726 -n 5 -r 15 -x axlMatlab -desktop -r "run('/tmp/adeInitMatlabM95423.m');import('cadence.*');import('cadence.srrdata.*');import('cadence.calculator.*');import('cadence.help.*');"

    workshop_16> ps -ef | grep matlab | grep -v helper
    workshop 96445 96444 47 06:41 pts/3 00:02:01 /export/home/apps/matlab_R2021b/bin/glnxa64/MATLAB -desktop -r run('/tmp/adeInitMatlabM95423.m');import('cadence.*');import('cadence.srrdata.*');import('cadence.calculator.*');import('cadence.help.*'); -prefersoftwareopengl

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • strat57
    strat57 over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for the reply.  We're using ICADVM20.1-64b.500.20.  Our Matlab version is 2018b.

    However, checking the process command line made me realize, our tools are bsub'd out to different machines (ie distributed).  The GUI seems to run on a limited capability machine with Matlab (and Spectre sims) farmed out to more capable processing machines.  I don't seem to be able to log into (ssh) the processing machines, so I can't query the process details. 

    Is using a distributed computing platform likely the source of the problem?

    Thanks

    Trent

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to strat57

    Hi Trent,

    This seems unlikely, because Matlab is invoked locally - i.e. on the same machine you're running Virtuoso and Assembler interactively. It is not sent to a remote machine, mainly because it's a single interactive session that you're launching when you press the "M" button.

    I just tried with the exact same versions you are, and all worked fine for me. I don't see the quotation marks missing.

    One possibility is that you have a wrapper command around "matlab" in your environment and that is sending the job to a remote machine via bsub - if so, maybe that is messing up the quotation marks?

    It might be best to follow this up with customer support to diagnose the issue that way.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • strat57
    strat57 over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    Ahhh, that makes sense.  Our CAD group does wrap matlab to submit a bsub job.  I'll check the wrapper definition, but that is likely the problem.

    Thanks

    Trent

    • 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