Stats

  • Locked Locked
  • Replies 7
  • Subscribers 64
  • Views 12753
  • 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

timeaverage and sample(jitter)

3peaklvlu

Hi there,

I am trying to understand the difference and correlation between timeaveraging and sampled jitter method.

For sampling jitter, it calculates noise at particular threshold point. And for time averaging it calculates noise with AM and PM, whether the noise varies signal's amplitude or phase.

So I simulate jitter of one inverter, get result of PSD_pm0 and PSD_pm1,which are rising edge and falling edge pm jitter results .

Then I add a limiter(comparator in ahdlLib) at inverter output, simulating its harmonic 1st's USB/LSB noise in dBc/Hz using time averaging, at this moment there is no AM noise. 

Further more, I simulate PMOS or NMOS's noise contribution by using analog option, and get result PSD_pmos and PSD_nmos.

I guess PSD_pm0= PSD_pmos and PSD_pm1= PSD_nmos but what I get is  PSD_pm0= PSD_pmos+6dB and PSD_pm1= PSD_nmos+6dB

my working environment is ic618.

 

Best regards,

Lu Lv

Parents
  • csn165309964

    I think a clock with jittery rising edge could be modeled as below. Sampled(jitter) pnoise analysis would yield n(t).
    sin(wt + n(t) (cos(wt)+1)/2)
    When n(t)<<1, it can be approximated as below.
    sin(wt + n(t)/2) + n(t)/4 + cos(2wt) n(t)/4
    Time average pnoise analysis around the fundamental would yield n(t)/2. The remaining is at baseband and around the second harmonic.

Reply
  • csn165309964

    I think a clock with jittery rising edge could be modeled as below. Sampled(jitter) pnoise analysis would yield n(t).
    sin(wt + n(t) (cos(wt)+1)/2)
    When n(t)<<1, it can be approximated as below.
    sin(wt + n(t)/2) + n(t)/4 + cos(2wt) n(t)/4
    Time average pnoise analysis around the fundamental would yield n(t)/2. The remaining is at baseband and around the second harmonic.

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.