AVL-RAL- Apheleia Verification Library Register Abstraction Layer
AVL-RAL has been developed by experienced, industry professional verification engineers to provide a simple,
extensible verification component integrating a Register Abstraction Layer (RAL) based on systemdrl.
developed in Python and the AVL library.
AVL is built on the CocoTB framework.
CocoTB 2.0
AVL-RAL supports CocoTB2.0 https://docs.cocotb.org/en/development/upgrade-2.0.html. This was introduced in v0.2.0.
Component Features
📦 Installation
Unfortunately avl-ral isn't available on PyPi. As such to pip install you need to use the longer avl-register-abstraction-layer name. Once install avl_ral is the short-cut.
Using pip
# Standard build
pip install avl-register-abstraction-layer
# Development build
pip install avl-register-abstraction-layer[dev]
Install from Source
git clone https://github.com/projectapheleia/avl-ral.git
cd avl-ral
# Standard build
pip install .
# Development build
pip install .[dev]
Alternatively if you want to create a virtual environment rather than install globally a script is provided. This will install, with edit privileges to local virtual environment.
This script assumes you have Graphviz and appropriate simulator installed, so all examples and documentation will build out of the box.
git clone https://github.com/projectapheleia/avl-ral.git
cd avl-ral
source avl-ral.sh
📖 Documentation
In order to build the documentation you must have installed the development build.
Build from Source
cd docs
make html
<browser> build/html/index.html
🏃 Examples
In order to run all the examples you must have installed the development build.
To run all examples:
cd examples
# To run
make -j 8 sim
# To clean
make -j 8 clean
To run an individual example:
cd examples/THE EXAMPLE YOU WANT
# To run
make sim
# To clean
make clean
The examples use the CocoTB Makefile and default to Verilator with all waveforms generated. This can be modified using the standard CocoTB build system.
🧹 Code Style & Linting
This project uses Ruff for linting and formatting.
Check code for issues:
ruff check .
Automatically fix common issues:
ruff check . --fix
📧 Contact
- Email: avl@projectapheleia.net
- GitHub: projectapheleia
Metadata
Release files for avl-register-abstraction-layer 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| avl_register_abstraction_layer-0.1.0.tar.gz | 5.9 kB | Without provenance | Details for avl_register_abstraction_layer-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| avl_register_abstraction_layer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for avl_register_abstraction_layer-0.1.0-py3-none-any.whl |
Total release size: 14.5 kB
Release files / avl_register_abstraction_layer-0.1.0.tar.gz
| Download URL | avl_register_abstraction_layer-0.1.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f34f772ceaf1fd7a6cfd072d09e6ce8610699f2220f2576444b977539d66fb44
|
|
BLAKE2b-256 checksum How to use checksums |
d3b6c217141a0484e0f084df2d02509c7b5af35eb6b013860d222e5c26b286c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / avl_register_abstraction_layer-0.1.0-py3-none-any.whl
| Download URL | avl_register_abstraction_layer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c6a6b3c7c80b98306d2fb5c9bc9028b4e9e8eb4d2e478ccbe0506b6989b9ba89
|
|
BLAKE2b-256 checksum How to use checksums |
49be724a6604f9658cfeb649acb6529099c5b9a965ed823971e81094019b2a89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for avl-register-abstraction-layer 0.1.0
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.