• 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. Eval error on MATLAB expressions from ADE/Maestro outpu...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 127
  • Views 2361
  • 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

Eval error on MATLAB expressions from ADE/Maestro outputs

MichR
MichR over 1 year ago

For our design we need to perform post-processing of a few waveforms using MATLAB, so we set up a matlabexpr in our Maestro testbench.

So far it works for single point simulations, but the expression sometimes fails to evaluate when the simulation is performed over multiple points by sweeping a design variable or parameter. Oddly enough, the first simulation point gets evaluated correctly, but for the last ones it gives an "eval err" as output.

To debug the problem I modified our post-processing MATLAB function to write a log file as a way to determine where the expression fails to evaluate, and it seems that MATLAB is not even started when the outputs of the second simulation point (and all the remaining points) are evaluated as the log file is unmodified after the first successful evaluation.

With sstatus(errsetTrace t) and _stacktrace=50 I could pinpoint that the issue is in an internal ADE function:

However, I'm totally unable to understand what I should try to fix this issue.

It seems to be reproducible all the time. These are the steps to perform to replicate the issue:

  1. Launch Virtuoso and open a Maestro view with a matlabexpr.
  2. Start a sweep simulation. All the matlabexpr should evaluate correctly.
  3. Start a single point simulation. The matlabexpr should still evaluate correctly.
  4. Start a sweep simulation. Now, the first evaluation is successful, while the remaining ones fail.

Our MATLAB version is r2023b and we are running Virtuoso Studio IC23.1-64b.ISR2.29

  • Cancel
Parents
  • Marc Heise
    Marc Heise over 1 year ago

    Hi,

    there were some Matlab related fixes in ISR33. If you have something reproducible, can you try again with ISR33/ISR34 ?

    Kind regards,

    Marc

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Marc Heise
    Marc Heise over 1 year ago in reply to Marc Heise

    Sorry, I saw that "29"  and took it as ISR29.   23.1. ISR2  should have these fixes already.  Strange.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Marc Heise
    Marc Heise over 1 year ago in reply to Marc Heise

    Sorry, I saw that "29"  and took it as ISR29.   23.1. ISR2  should have these fixes already.  Strange.

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