Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 15478
  • 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

Simulation error in ADEXL, runs fine in ADE

suhasg26

Hi Team,

I face this peculiar problem, whenever I switch to ADEXL to run a bunch of simulations (ADE standalone simulations run fine). The ADEXL simulation errors out saying

ERROR (SFE-874): "input.scs" 43: 63: Unexpected integer "0". Expected close parenthesis. Cannot run the simulation because of syntax error. Correct the error and rerun the simulation.
ERROR (SFE-683): "input.scs" 43: Badly formed parameters statement.

A huge string of parameters (DPAR_* as shown in the below snapshot) are defined by ADEXL which are not part of the intended design variables list (not seen in the netlist parameter set generated by ADE).
And ADEXL sets one of these parameters to 0 (highlighted in green) and flags it as an error. 

I did search for this issue on this forum and on google, found no discussion about it. So I'm posting it here.
Any suggestions are welcome. Thanks!

Parents
  • Andrew Beckett

    I found a small number (2 or 3) reports of this issue in the past (the most recent was a couple of years ago, assuming my search was complete enough), when using the ADE XL parameterisation of certain devices. I think it was happening with a particular TSMC PDK, but in both cases we never really received enough information from the customer to identify and resolve the issue.

    So first thing I would suggest is make sure you're using an up to date IC version (e.g. IC617 ISR23 or IC618 ISR2) to see if the issue has been resolved in a later version than the one you're using. If not, please contact customer support because I think we'll need more information to allow us to reproduce and investigate the problem further.

    Thanks,

    Andrew.

Reply
  • Andrew Beckett

    I found a small number (2 or 3) reports of this issue in the past (the most recent was a couple of years ago, assuming my search was complete enough), when using the ADE XL parameterisation of certain devices. I think it was happening with a particular TSMC PDK, but in both cases we never really received enough information from the customer to identify and resolve the issue.

    So first thing I would suggest is make sure you're using an up to date IC version (e.g. IC617 ISR23 or IC618 ISR2) to see if the issue has been resolved in a later version than the one you're using. If not, please contact customer support because I think we'll need more information to allow us to reproduce and investigate the problem further.

    Thanks,

    Andrew.

Children
  • suhasg26
    in reply to Andrew Beckett

    Thanks for the quickest reply, Andrew. appreciate it.
    We are using Virtuoso ICADV12.3 (I don't know where this stands w.r.t the versions you've mentioned)
    But I will contact customer support. 

    Thanks again,

    -Suhas

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.