How to verify a CCS library against SPICE
Short answer
Build a test bench for every timing arc of every cell, drive a distributed RC (DSPF) load with instances of the same cell as fanout, and compare the delay your static timing analyzer reports with the delay SPICE measures under the same conditions. Large deviations point to wrong entries, missing arcs or bad driver and receiver models.
Why current source models need their own test
Unlike previous generations of delay models, where the characterization model and the delay calculation model assumed the same lumped capacitance approximation, current source models are used with distributed loads. That makes it important to check model accuracy under distributed load conditions, not only at the characterization points.
This is usually done for isolated instances of clock drivers in a manual fashion, by comparing delay calculation to SPICE simulation. Doing it for every arc of every cell needs automation.
What usually goes wrong
| Problem | Typical cause | How it shows up |
|---|---|---|
| Wrong timing values | Hand-made or template-based libraries | STA delay far from SPICE on some arcs |
| Missing timing arcs | State-dependent arcs not identified | Arc absent from the library |
| Wrong input capacitance | Manual measurement or wrong state | Receiver load error in the fanout |
| Slope or load range too narrow | Tables do not cover real conditions | Delay calculation accuracy compromised |
| Liberty and Verilog mismatch | Models built separately | SDF back-annotation problems |
The flow, step by step
- Recover the function. If the Liberty library came from elsewhere, Syn2acdl generates ACDL functional descriptions of the cells.
- Run functional tests first. If the SPICE netlist and the Liberty entry disagree, a timing comparison is meaningless.
- Build the test bench per arc. The cell drives a distributed RC network described in DSPF; the same set-up is written in Verilog for the timing analyzer and in SPICE.
- Compare and narrow down. Change fanout, RC loading or characterization set-up to find the source of a deviation.
makelib ccstestsThe command carries out all intermediate steps for all corners and library cells.
FAQ
Does this only work for CCS?
No. The suite was designed for current source models like CCS and ECSM, and it also tests NLDM libraries for interpolation errors.
Can it check a library that was not built with SolutionWare?
Yes. Syn2acdl recovers ACDL descriptions from an existing Liberty library, so the functional and timing tests can run on it.
How long does it take?
The run time of CCSTEST is a small fraction of the characterization time.
Sources: CCSTEST product documentation; “Library Technologies, Inc. Announces CCSTEST Library Verification Suite for Current Source Models”, May 19, 2008.