• 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. implement noise behavior of transistor in spice code in...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 12893
  • 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

implement noise behavior of transistor in spice code in spectre

Bo Yu
Bo Yu over 4 years ago

Hi,

It's very nice to be here. I got several problems solved by reading the threads here.

But there are some more as is always the case when I try to learn something new.

So I did dc and ac simulation with a very simple common source amplifier (See attached picture.). I used the generic nmos transistor in analoglib and used a model card (level=1, thus mos1 model) for the nmos model. 

Those simulations were successful. 

Further, I want to study the output noise of the circuit. And I would also like to replace the nmos model with RPI polysilicon TFT models.

In the mos1 model, there are no parameters available for noise. The same case goes for poly-Si TFT models. How can I implement the noise model? I want to include flicker noise and channel noise. Some literature suggested writing a spice code to do this. I just don't know how it's worked out in cadence.

Thank you for your time.

Bo

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    Why do you think that mos1 and psitft don't have noise parameters? With spectre (you didn't mention the simulator, but I'm guessing it's spectre):

    from "spectre -h mos1":

    Noise model parameters:
    96      noisemod=1        Noise model selector.
    97      kf=0              Flicker (1/f) noise coefficient.
    98      af=1              Flicker (1/f) noise exponent.
    99      ef=1              Flicker (1/f) noise frequency exponent.
    100     wnoi=1e-5 m       Channel width at which noise parameters were
                              extracted.

    from "spectre -h psitft":

    Noise model parameters:
    100     noisemod=1        Noise model selector.
    101     kf=0              Flicker (1/f) noise coefficient.
    102     af=1              Flicker (1/f) noise exponent.
    103     ef=1              Flicker (1/f) noise frequency exponent.
    104     wnoi=1e-5 m       Channel width at which noise parameters were
                              extracted.

    So both support noise parameters.

    Also, what is the sudden interest in the Poly-Si TFT model? You're the second person to ask about it in the last few days. Has somebody set this as an exercise on a university course?

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Bo Yu
    Bo Yu over 4 years ago in reply to Andrew Beckett

    Thanks Andrew. I was reading Virtuoso Simulator Components and Device Models Reference, 2015 version. There are noise model parameters for MOS1 but not for psitft.

    What are the possible values for noisemod? Is it that only flicker noise are supported in the model?

    haha...I don't know about the other post...I myself am not working for some university course homework. poly-Si TFT devices are getting better performance. It's time to look for more applications using polySi TFT.

    thanks again

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to Bo Yu

    First of all, I was going to suggest that looking at a 5-6 year old manual was not the right thing to do, but I see it's missing even in the SPECTRE20.1 version of the model manual. The noise equations are common to many other models, and so I think will work just as (say) the EKV model which does give the equations. I believe noisemod just controls the flicker noise model.

    However, this needs to be corrected in the documentation. Please contact customer support.

    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