• 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. how to pass array of parameters through CDF down to a verilogA...

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 127
  • Views 22705
  • 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

how to pass array of parameters through CDF down to a verilogA code?

naderi
naderi over 13 years ago

 Hello all,

 Is there any way to pass an array of parameters down to a verilogA code?

if I put following statement in a verilogA sub-circuit.

parameter real vdc[3:0] ={0,0,1,0};

Then {0, 0, 1, 0} appears in CDF parameters for vdc. However, spectre complains later during circuit read-in.The error message is :

 Error found by spectre during circuit read-in.
    ERROR (SFE-874): "input.scs" 1087: Unexpected block statement "{".

I realized if I enter the parameters within double-qoute as "{0, 0, 1, 0}" at CDF, then spectre will be happy and goes for simulation, but the results are incorrect.

 

I wonder if there is any solution?

Thanks,

Ali

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

    Narasimhan,

    There's not a need for spectre and veriloga to be aligned in terms of syntax, but there is a CCR for this to be handled correctly in the CDF - CCR 1094193. However, there is no plan to fix this - maybe that would change if more people asked for this via customer support.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Narasimhan,

    There's not a need for spectre and veriloga to be aligned in terms of syntax, but there is a CCR for this to be handled correctly in the CDF - CCR 1094193. However, there is no plan to fix this - maybe that would change if more people asked for this via customer support.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • nouning
    nouning over 6 years ago in reply to Andrew Beckett

    hi Andrew, I am facing the same issue: "ERROR (SFE-874): "input.scs" 1087: Unexpected block statement "{"." Has this issue been resolved yet? Can Spectre now handle VerilogA arrays such as {1,2,3,4}. Thank you.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to nouning

    Not sure when this was fixed, but a parameter such as in the example above now (in IC618 ISR3 - may have been this way for some time though) gets changed in the CDF to [0,0,1,0] (square brackets rather than curly brackets). This then works correctly because the netlist would contain the spectre vector syntax.

    In earlier versions before this was done automatically, you can use Tools->CDF->Edit CDF, set the type to "Base" and pick the cell for which you have your VerilogA view. Change the vector parameter to have square brackets.

    Then when instantiating the design in a schematic, on the create instance or edit properties form set the value with square brackets if you want something other than the default.

    Regards,

    Andrew.

    • 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