Stats

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

Use standalone scs tech file

gocoba
Hi there, Can anyone tell me how to include this tech file into Cadence simulator? www.mosis.com/.../v15d_8rf_8lm_dm_k3-params.txt This is directly from MOSIS website and I just wanted to do some simply simulation use that process. But I don't know how to convert this file into cadence. Should I save it as a scs file? Also, do I need to add any line in the text like "simulator lang=spectre" ? What should I be aware of it while converting this tech file? Many thanks!

  •  Hi Gocoba,

    Well, strictly speaking this is not spectre format, in fact the file even says it is SPICE.  However, to try to answer your questions, if you save the file with a ".scs" extension, then I believe that the 'simulator lang=spectre' is assumed, so you would not need to supply it. Spectre has a parser for SPICE built-in (no separate pre-parser is needed/used) but to understand SPICE syntax you should include the folowing at the top of the netlist: "simulator lang=spice".  Also note that there are many lines in that file which should be commented out with the appropriate comment character(s) (this may depend on where you put the above switch as whether the SPICE comment or Spectre comment should be used [* vs // I think].

    I have not tested this with the file but hope that the above information helps you.

    Regards,

    Lawrence.

  • If the suffix of the file is anything other than ".scs" it's assumed to be in SPICE syntax anyway, so after commenting the lines which aren't part of the model file (use the SPICE comment character "*" at the beginning of each commented line), you can use it with whatever suffix you like (other than ".scs" - if you use that, you'd have to add the simulator lang=spice directive that Lawrence mentioned).

    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.