Wait, Which Version of the Tool Did Your EDA Folks Install?

Do you get a pop up with this message, when you click the Run button in Assembler?

ERROR (ASSEMBLER-1613): Following tests use older version of Spectre

<list of tests>

Make sure to use MMSIM60 or above for these tests.

Look in your CIW for a message about setenv and spectre.dat.

If the path it mentions contains tools.lnx86 and you don't see that folder in your file-system, it may mean the installation (that is, which <tool name> returns *some* thing) was for the wrong processor. That's possible - if it's just about downloading a binary - the vendor isn't going to give you the source to build 😊



Comments

Post a Comment

Popular posts from this blog

Plotting Device Parameters (gm, vdsat, etc) Vs Time or Temp

Image
I feel like this has gotten more complicated. I think it might have been easier 10 years ago. Then again, I could be w. Go to resource: How to save and plot operating point parameters for Spectre simulator from ADE Explorer/Assembler In Explorer, you go to Outputs > To be Saved > Select OP Parameters Now, the schematic window is active and you can click on instances and each gets highlighted as you do. These get populated in the Assembler Outputs Setup You will see that the "Type" is not signal but oppoint. If you click on the Details field, it splits into two - the /whatever/deviceName is on the left, and on the new field on the right, you can enter parameters appropriate for that device, like vdsat, vth, cgs, etc.  The UI is very poor, but, on the right of this field is a button you can actually click to choose from a list. It'll even run a sim if necessary! If you want these plotted, you have to check the box to the right under the Plot column. Other gems Finding...
Read more

When You Want to Get Cycle-to-Cycle Jitter at PLL Output Due to the Reference Oscillator

Image
Caution - the script does not provide the correct result. You expect cycle-to-cycle to be a high-frequency phenomenon - and therefore, to not depend on the oscillator phase-noise or jitter. But the script will show a large value for c2c jitter on the PLL output. If you can figure it out, please post/comment. Designers Guide : Phase Noise and Jitter prediction , by Ken Kundert Converting Phase Noise to Cycle-to-Cycle Jitter in a PLL When designing or analyzing phase-locked loops (PLLs), one key metric of interest is the RMS cycle-to-cycle jitter at the output. Given phase noise data (typically in dBc/Hz) for the reference oscillator, how do we estimate the jitter after the PLL processes it? 🎯 Goal Estimate RMS cycle-to-cycle jitter (in seconds or picoseconds) at the output of a PLL , based on: Measured or simulated phase noise data (dBc/Hz vs. offset frequency) PLL dynamics: natural frequency ( fn ), damping ratio ( ΢ ), divider ratio ( N ) Carrier frequency ( fc ) ...
Read more

Jitter - How to Characterize Your Oscillator or Clock Source

Image
You can plot instantaneous frequency using freq(). You can plot the cycle-to-cycle jitter using period_jitter(). That gives you a nice waveform containing all the sample values. But, now, you need to report the standard-deviation of the samples. What can you do? Fortunately, the ViVA Calculator has you covered. Change default from Population to Sample and Set Continuous to No so that, in the the buffer, you see something like: stddev(period_jitter(clip( VT("/clk") 200n nil) "rising"  ?mode "auto"   ?binSize 0 ?xName "time"   ?outputType "plot"  ) ?type "sample" ?continuous nil ) And you're done.
Read more