Skip to main content

noRTL - Hardware design beyond register transfer level

noRTL (Not-only RTL) is a Python-based code generation framework for designing and implementing hardware description language (HDL) modules, particularly SystemVerilog state machines. It provides a high-level, Pythonic API for describing sets of finite state machines (FSMs) and hardware components with built-in correctness guarantees.

noRTL aims to make the design of complex digital systems easier by reducing the shortcommings of current hardware description languages that use the register transfer level (RTL) to model digital circuit's behavior. This tool goes beyond this level of abstraction: We digital designers want to describe behavior with cycle-level accuracy but do not want do deal with the complexity of state naming, state coding, starting parallel processes, etc. noRTL realizes this tedious part of digital design inside its core.

The code that is written for noRTL is pure Python code. The noRTL package realizes state handling and data structure assembly for you while the Python code is executed. noRTL can be understood as a fancy generator that assembles state machines and provides the tooling to render it to SystemVerilog and tools for verifying your code.

Want to start right away? Look at our Tutorial section!

Main ideas

noRTL is built with the following concepts and ideas.

  • Each hardware description is an executable Python program. The hardware structure is assembled during execution. There is no need for static code analysis or parsing.
  • There should be no need to declare states explicitely. The number of states is determined during execution of the code.
  • The behavior description should be easily readable and feel procedural. Control structures should work similar to Python equivalents.
  • Checks and Optimizations are to be done during runtime of the Python code. Post-Optimization has not been necessary (yet).

Installation

A prerequisite for noRTL is the availablility of icarus Verilog in your path. This can be installed using your system's package manager or using the oss-cad-suite (https://github.com/YosysHQ/oss-cad-suite-build)

Method 1: Using pip (Public Registry)

# Install nortl
pip install nortl

Method 2: Using uv (Recommended)

# Clone the repository
git clone https://github.com/IMMS-Ilmenau/nortl
cd nortl

# Install dependencies
uv sync

# Activate the virtual environment
source .venv/bin/activate  # On Windows: .venv\Scripts\activate

Method 3: Development Installation

For development work, install in editable mode:

# Clone the repository
git clone https://github.com/IMMS-Ilmenau/nortl
cd nortl

# Install development dependencies
uv sync --all-extras

# Activate the virtual environment
source .venv/bin/activate

Your First State Machine

Let's create a simple state machine that toggles an output based on an input.

from nortl import Engine, Const

# Create an engine with a module name -- Clock and reset signal is automatically included
engine = Engine("my_first_engine")

# Define input and output signals
enable = engine.define_input("enable", width=1)
output = engine.define_output("output", width=1, reset_value=0)

# Don't define states -- define behavior!
with engine.while_loop(Const(True)):
    engine.wait_for(enable == 1)
    engine.set(output, 1)
    engine.sync() # Wait one clock cycle
    engine.set(output, 0)
    engine.wait_for(enable == 0)

# Generate SystemVerilog code
verilog_code = engine.to_verilog()

print(verilog_code)

Citation

If you use NoRTL in your research, please consider citing it:

DOI

Citations of individual versions are also possible using the version-specific DOIs on the Zenodo-Site. Please use the link of the DOI-badge for more information.

Acknowledgement

The DI-Meta-X project where this software has been developed is funded by the German Federal Ministry of Research, Technology and Space under the reference 16ME0976. Responsibility for the content of this publication lies with the author.

Metadata

Release files for nortl 1.6.3

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

Source distribution (sdist)

Source distribution for nortl 1.6.3
File Size Uploaded Provenance Actions
nortl-1.6.3.tar.gz 280.9 kB Without provenance Details for nortl-1.6.3.tar.gz

Built distribution (wheel)

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

Total release size: 447.4 kB

Release files / nortl-1.6.3.tar.gz

Download URL nortl-1.6.3.tar.gz
Size 280.9 kB
Tags Source
SHA-256 checksum
How to use checksums
7f17d1e47ed19d367ba4922ff512d998f873334621280d6b9a519257a9331dd5
BLAKE2b-256 checksum
How to use checksums
7802986ec2d6e8c24760c9c6f88d26f84bba6c657769f341f266f0ef75580abe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.6 {"installer":{"name":"uv","version":"0.12.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / nortl-1.6.3-py3-none-any.whl

Download URL nortl-1.6.3-py3-none-any.whl
Size 166.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
56f82b5e1b4bec3c14d53beef450c84fb146f2050ef223fa703f85f16e2d80b2
BLAKE2b-256 checksum
How to use checksums
f7323bc3744ab6e67feaa9213f3ba6d7014628d36efcf160ca7cc30dc54d3d21
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.6 {"installer":{"name":"uv","version":"0.12.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for nortl 1.6.3

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