Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 7919
  • 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

define variable in scs file

sjwprcker

Hi,

I would like to create a .scs file, which will be included as a normal model file. 

The content is

section AAA

parameters

+ X=0

+ Y=0

+ Z=0

endsection

X,Y,Z are variable to be defined. I wish their function the same as the variable defined in corner setup.

The sim always fail. It seems the syntax is wrong. 

I am wondering what is the standard format to define my own .scs file?

my cadence version is IC618.500.24. Specter version is 21.1.0.460.isr10. 

  • It does tend to help if you actually share the error. Otherwise how are we supposed to know what was wrong?

    Normally (by convention) any file containing sections would also have library/endlibrary around it; however, this is not compulsory.

    I used your file, and included it with:

    include "sectiononly.scs" section=AAA

    and it works with no problem. If you had tried to include it without specifying the section, it will fail with:

    Error found by spectre during circuit read-in.
    ERROR (SFE-874): "sectiononly.scs" 2: Cannot run the simulation because syntax error `Unexpected keyword "section"' was encountered at line 2, column 0. Correct the syntax error and rerun the simulation.
    ERROR (SFE-874): "sectiononly.scs" 12: Cannot run the simulation because syntax error `Unexpected end of section "endsection"' was encountered at line 12, column 0. Correct the syntax error and rerun the simulation.

    If you don't want to have to specify a section at the time you include the file, simply omit the section AAA and endsection lines from your file. The whole point of sections is that you can have multiple alternative sections within a file and choose which to include by using the section parameter of the include statement.

    Andrew

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.