Stats

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

ADE Assembler evaulates expression prior to simulating - long wait

jehh

Hi,

Based on feedback from Andrew Beckett, in another thread, I recently moved a simulation setup to the LSCS job control mode, instead of ICRP.  Now, every time I launch I get a ton of errors printed in the CIW, along the line of ERROR (ASSEMBLER-2709): Evaluation returned 'nil'.

Since I have a significant amount of errors here, it takes quite some time, before all these errors are printed, and the simulation even starts (half the time from I press simulate, to it finishes, is at least this waiting for this). When the simulations are done, none of these errors are actually true errors.

It seems most likely that LSCS calls some expression evaluation, prior to launching a simulation, evaluating none-existing expressions and then waits until this is done.

Can this behaviour be modified or circumvented? I've looked in the user guide, to no vail.

Versions: Virtuso 6.1.8-ISR14, Spectre 20.1.base

Br,

Christian

  • Dear Christian,

    Is there any chance you are creating your netlist based on a config view that is an extracted view? 

    If so, I am wondering if the expression errors generated using the LCSC based job policy are a result of an issue detailed in the Sourcelink note at URL:

    support.cadence.com/.../ArticleAttachmentPortal

    Basically, there is an issue evaluating expressions using the nomenclature of some extracted view nets. A  workaround is provided which proposes to add the following to your .cdsint file:

    envSetVal("maestro.exprEval" "binaryName" 'string "virtuoso")

    Is there any chance this might apply in your case given the nature of your Assembler expressions?

    Shawn 

  • Dear Christian,

    Is there any chance you are creating your netlist based on a config view that is an extracted view? 

    If so, I am wondering if the expression errors generated using the LCSC based job policy are a result of an issue detailed in the Sourcelink note at URL:

    support.cadence.com/.../ArticleAttachmentPortal

    Basically, there is an issue evaluating expressions using the nomenclature of some extracted view nets. A  workaround is provided which proposes to add the following to your .cdsint file:

    envSetVal("maestro.exprEval" "binaryName" 'string "virtuoso")

    Is there any chance this might apply in your case given the nature of your Assembler expressions?

    Shawn 

  • in reply to ShawnLogan

    Hi Shawn,

    Thank you, this seem to have done the trick - all-though I am running ISR14, and the link you provided says it should be fixed. Might be that the maestro view was created in ISR12?
    None the less, it is now running smoothly, thank you.

    BR,

    Christian

  • in reply to ShawnLogan

    Dear Christian,

    Great! I am happy to read that this avoids the expression errors and that me lag!

    Thank you, very much, for letting us know!

    Shawn

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.