Skip to main content

LibreCell - Lib

Characterization kit for CMOS cells.

Getting started

See install instructions in top-project.

Characterize a cell

An ready-to-run example can be found in the examples folder. The script run_example.sh should characterize the INVX1 inverter.

The following example determines the input capacitances and timing delays of a combinational cell.

It is assumed that FreePDK45 is installed in the users home directory.

Required inputs are:

  • --liberty: A template liberty file which defines how the cells should be characterized.
  • --include: SPICE files or models to be included.
  • --spice: A SPICE file which contains the transistor level circuit of the cell (best including extracted parasitic capacitances).
  • --cell: Name of the cell to be characterized.
  • --output: Output liberty file which will contain the characterization data.

Characterize a single cell:

lctime --liberty ~/FreePDK45/osu_soc/lib/files/gscl45nm.lib \
	--include ~/FreePDK45/osu_soc/lib/files/gpdk45nm.m \
	--spice ~/FreePDK45/osu_soc/lib/source/netlists/AND2X1.pex.netlist \
	--cell AND2X1 \
	--output /tmp/and2x1.lib

Characterize multiple cells in the same run:

lctime --liberty ~/FreePDK45/osu_soc/lib/files/gscl45nm.lib \
	--include ~/FreePDK45/osu_soc/lib/files/gpdk45nm.m \
	--spice ~/FreePDK45/osu_soc/lib/source/netlists/*.pex.netlist \
	--cell INVX1 AND2X1 XOR2X1 \
	--output /tmp/invx1_and2x1_xor2x1.lib

Vizualize the result:

libertyviz -l /tmp/and2x1.lib --cell AND2X1 --pin Y --related-pin A --table cell_rise

Merging liberty files

lctime will output a liberty file containing only one cell. The libertymerge command allows to merge this kind of output file back into the liberty template.

The following example will take base_liberty.lib as a template and update its cell entries with the data found in the liberty files in the characterization directory.

libertymerge -b base_liberty.lib \
    -o output_liberty.lib \
    -u characterization/*.lib

This approach allows to run characterization runs of multiple cells independently and in parallel (e.g using make).

Metadata

Release files for librecell-lib 0.0.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for librecell-lib 0.0.8
File Size Uploaded Provenance Actions
librecell-lib-0.0.8.tar.gz 52.5 kB Without provenance Details for librecell-lib-0.0.8.tar.gz

Release files / librecell-lib-0.0.8.tar.gz

Download URL librecell-lib-0.0.8.tar.gz
Size 52.5 kB
Tags Source
SHA-256 checksum
How to use checksums
2dccb7da4292e00e945f9c98e54454d0415d09ddad366dfd79e4ebbb740d8eec
BLAKE2b-256 checksum
How to use checksums
31c6aff67e54ed077602281c0cb6a434425bbd4b6bad86bbd2636ffa4c7ee297
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.3.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.7.3

Security for librecell-lib 0.0.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page