Skip to main content
LibSV
PyPI https://github.com/bensampson5/libsv/actions/workflows/ci.yml/badge.svg Documentation Status

Welcome to LibSV! Click here to go to LibSV’s documentation.

LibSV is an open source, parameterized SystemVerilog digital hardware IP library. While similar libraries may already exist, LibSV is unique in that it takes advantage of open-source, state-of-the-art development best practices and tools from across the software and digital design community, including:

Getting Started

LibSV is very easy to use. First, install the libsv package from PyPI:

pip install libsv

We recommend using a Python virtual environment so that the installation is project-specific and isolated from the rest of your system.

Then add the site-packages/ folder, where LibSV was just installed, to your include path when building your project so that your design tools can find LibSV.

Finally, at the top of your design file where you want to use LibSV modules, for each module you want to use, add:

`include "libsv/<path>/<to>/<module>.sv"

Running Testbenches

Running the LibSV testbenches require Cocotb, Verilator, and a number of other dependencies to be installed. Instead of trying to install everything manually on your machine, the easier and recommended way to run the LibSV testbenches is to use the pre-built LibSV Docker images on Docker Hub that have the complete set of LibSV developer tools already installed.

To use a LibSV Docker image, first you’ll need to install Docker, if you don’t already have it.

Next, pull the latest LibSV Docker image:

docker build --pull -f Dockerfile.dev \
  --build-arg UID=$(id -u) \
  --build-arg GID=$(id -g) \
  -t libsv .

Then, start a new Docker container using the LibSV image and mount the project folder to the container:

docker run --rm -it -v $(pwd):/code libsv

Finally, within the Docker container, run pytest:

pytest

This will run all the LibSV testbenches for the entire library (Warning: This may take a while!).

Instead, to list all the available LibSV testbenches, run:

pytest --co

Then, you can run an individual or subset of testbenches using the -k flag which will only run tests which match the given substring expression:

pytest -k EXPRESSION

Each testbench generates an associated .fst waveform file that is written to the build/ directory and can be viewed using GTKWave.

Bugs/Feature Requests

Please use LibSV’s GitHub issue tracker to submit bugs or request features.

Contributing

Contributions are much welcomed and appreciated! Take a look at the Contributing page to get started.

License

Distributed under the terms of the MIT license, LibSV is free and open source software.

Metadata

Release files for libsv 0.2.1

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

Source distribution (sdist)

Source distribution for libsv 0.2.1
File Size Uploaded Provenance Actions
libsv-0.2.1.tar.gz 34.9 kB Without provenance Details for libsv-0.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for libsv 0.2.1
File Interpreter ABI Platform Actions
libsv-0.2.1-py3-none-any.whl Python 3 none any Details for libsv-0.2.1-py3-none-any.whl

Total release size: 71.3 kB

Release files / libsv-0.2.1.tar.gz

Download URL libsv-0.2.1.tar.gz
Size 34.9 kB
Tags Source
SHA-256 checksum
How to use checksums
548ece92712faac2919a897842a12436d106e9cebac3eb4038dcb127aeeb1445
BLAKE2b-256 checksum
How to use checksums
17cb29805c22ce14f574f8276d81b5c208903d47c2a7fdf41e102f5a8f7f1936
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.10

Release files / libsv-0.2.1-py3-none-any.whl

Download URL libsv-0.2.1-py3-none-any.whl
Size 36.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
719efa616bc28c9304ab150d2fa64eaa2312aa791dd7e0c4879dae3102f13ab8
BLAKE2b-256 checksum
How to use checksums
aeffaf025085ed4aa440a7b71d752ec41c27b1e5f201ef415833be5ead38b5c8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.10

Security for libsv 0.2.1

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.

Release history Release notifications | RSS feed

This release

0.2.1 This release

2 release files No provenance

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