• 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. spectremdl issue : syntax error before or at: trans invalid...

Stats

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

spectremdl issue : syntax error before or at: trans invalid argument to run statement

samung
samung over 12 years ago

Hello !

I am a new user of spectremdl and I make a basic trial, just to check that it works. I want to print a value in a result file.

I don't know why, I have the below log file issues, and especially :  syntax error before or at: trans invalid argument to run statement

I launch (through a job queue) : spectremdl -batch input.mdl -design input.scs -measure results_file 

 

 

log file :

Simulating `input.scs' on clust at 30:52:56 AM, Tue Jun 68, 2033 (process

        id: 115827).

 

Error found by spectre.

    ERROR: line 11, column 5: syntax error before or at: trans

            invalid argument to run statement

    ERROR: line 11, column 10: syntax error before or at: <eof>

            unrecognised statement

    ERROR (MDL-6): Failed to parse MDL control file, `input.mdl'. 

 

 

input.mdl :

alias measurement trans {

input real test_var = 13

run tran_simu 

export test_var

}

 

run trans 

 

input.scs extract :

simulator lang=spectre

global 0

include "xxx/corners_FF.scs"

parameters nmos_tran_model=nsvtlp pmos_tran_model=psvtlp wpen=xxx  wneqi=xxx ... Rright=10 ... lneqi=xxx  lndiff=xxx ...

 

 

subckt inv A1 YN vdd vnw vpw vss

parameters wp=xxx lp=xxx pfolds=1 wn=xxx ln=xxx nfolds=1

M5 (YN A1 vdd vnw) psvtlp w=wp*10e5 l=lp*10e5 nfing=pfolds mult=1  srcefirst=1 mismatch=1 lpe=0 numcos=1 numcod=1 ngcon=1

M2 (YN A1 vss vpw) nsvtlp w=wn*10e5 l=ln*10e5 nfing=nfolds mult=1  srcefirst=1 mismatch=1 lpe=0 numcos=1 numcod=1 ngcon=1

ends inv

 

 

// View name: schematic

subckt ncx ncx

ends ncx

// End of subcircuit definition.

 

Rleft (vli saout_b) resistor r=Rleft

...

M2 (saout saeqi saout_b vpw) nsvtlp w=xxx l=xxx nfing=1 mult=1  srcefirst=1 mismatch=1 lpe=0 numcos=1 numcod=1 ngcon=1

M1 (saout_b saout vss vpw) nsvtlp w=xxx l=xxx nfing=1 mult=1  srcefirst=1 mismatch=1 lpe=0 numcos=1 numcod=1 ngcon=1

M0 (saout net07 vss vpw) nsvtlp w=xxx l=xxx nfing=1 mult=1  srcefirst=1 mismatch=1 lpe=0 numcos=1 numcod=1 ngcon=1

M4 (vli signal1 vdd vnw) psvtlp w=xxx l=xxx nfing=1 mult=1 srcefirst=1  mismatch=1 lpe=0 numcos=1 numcod=1 ngcon=1

...

include ".../_graphical_stimuli.scs"

ic saout=xxx saout_b=0 

simulatorOptions options reltol=1e-3 vabstol=1e-6 iabstol=1e-12 temp=70  tnom=27 scalem=1.0 scale=1.0 gmin=1e-12 rforce=1 maxnotes=5 maxwarns=5  digits=5 cols=80 pivrel=1e-3 sensfile="../psf/sens.output"  checklimitdest=psf 

tran_simu tran stop=10u write="spectre.ic" writefinal="spectre.fc"  annotate=status maxiters=5 

finalTimeOP info what=oppoint where=rawfile

modelParameter info what=models where=rawfile

element info what=inst where=rawfile

outputParameter info what=output where=rawfile

designParamVals info what=parameters where=rawfile

primitives info what=primitives where=rawfile

subckts info what=subckts  where=rawfile

save signal1 

saveOptions options save=allpub subcktprobelvl=2

 

 

Thanks a lot for your help !!

 

P. 

  • Cancel
  • samung
    samung over 12 years ago
    Ok, actually, the issue was that the first line of the .mdl file must not be straigth the "alias measurement" line. Indeed, the following .mdl file returns a sucessfull result : .mdl file : /* test */ alias measurement run_tran_simu { run tran export real test_var = 13 } run run_tran_simu P.
    • 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