• 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. transistor model - netlist - spectre - matlab

Stats

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

transistor model - netlist - spectre - matlab

AmeliAmeli
AmeliAmeli over 8 years ago

Hi everyone,

I have a question regarding netlisting, matlab, spetre and the mosfet model.

From what I understand, when we run a simulation using spectre, a netlist is created which will be fed to the spectre engine. In that netlist we can find the schematic connections, simulator options and etc.

If we analyse the first part of the netlist, when it comes to the transistor definition I can see, apart from the type of transistor being used, length, width, nf, etc,  some other variables where the number of finger is used in the expression. For example, one of the variables is as, than it has an expression where the nf appears dividing a number in there.

That said, if I want to use matlab to launch the simulation, making use of the spectre/matlab toolbox, do I have to define those as well?

For example, I have tried two different situations: The first optionI have put only the basic transistor definition: Mnfet (v1 v2 0 v3) nchannel w=10e-06 l=length nf=10 and the second optionI have put exactly the same definition as before plus the other definitions (the variables) that I mentioned above that we get using spectre (where those extra variables with the number of finger dividing some numbers in the expression).

When I run the matlab script with the first option, everything goes well. But when I use in the matlab script in the second option (same definition that spectre gives me in the netlist of the same circuit), I get the following error:

Error found by spectre during circuit read-in.
    ERROR (SFE-874): "myfile.scs" 17: Unexpected equals "=".

Does anyone has an idea of what might be happening? I have a guess. Before telling what my guess is, does anyone knows what the number 17 means?

Regarding my guess: I guess that the simulator doesn't allow you to specify those extra variables, like the as mentioned above. This is something that is intrinsic to the simulator/model which it is shown in the input file that is fed to the spectre engine. I am not sure. It's just a guess.

Another experiment that I did was the following. I have ran a simple simulation using the script (with the first option configure in my script) and using spectre/ADEL simulator. For that experiment, I got different results for some capacitances, ids, gm, gmb and gds. That's why I have experiment putting in my script the same transistor definition (the extra variables with the nf dividing some number in it).

Any comments please?

Regards.

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

    Without seeing what you've actually got in your files, it's pretty much impossible to guess what you've done wrong, other than that line 17 has an equal sign when it's not expecting one (the 17 is the line number in the file). Your description doesn't make a whole lot of sense, I'm afraid.

    Andrew.

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

    Without seeing what you've actually got in your files, it's pretty much impossible to guess what you've done wrong, other than that line 17 has an equal sign when it's not expecting one (the 17 is the line number in the file). Your description doesn't make a whole lot of sense, I'm afraid.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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