cocotbext-ral
A Python-native Register Abstraction Layer (RAL) for cocotb.
cocotbext-ral provides UVM-like register modeling, access-type-aware prediction, and automated checking -- all in pure Python, designed for cocotb hardware verification.
Features
- Runtime-backed architecture with clean separation of register spec vs mutable state
- Full access-type coverage: RW, RO, WO, W1C, W1S, RCLR, RSET
- Smart volatile inference: RO, RCLR, RSET fields default to volatile (overridable)
- Safe field writes that reject unsafe read-modify-write sequences, plus byte-strobe partial writes
- Field enumerations & reset domains -- symbolic field values and soft/secondary resets
- Backdoor resolution and multiple address maps that scale to replicated blocks and chiplets
- Wide-register splitting, bus-response checking, and pre/post access callbacks
- Transaction logging with detailed per-transaction file output
- Pure-Python core -- model, predictor, and policies work without cocotb
- cocotb 1.x and 2.x compatible
Architecture
RegisterModel (spec)
|
RuntimeState (per-instance mutable state)
|
RuntimePredictor + AccessPolicy
|
RuntimeRAL -- front-door bus + prediction/checking, RMW safety,
| backdoor resolution, and transaction logging
Backdoor / Transaction Log
Installation
pip install cocotbext-ral
Optional extras:
pip install cocotbext-ral[cocotb] # cocotb + cocotbext-axi
pip install cocotbext-ral[rdl] # SystemRDL compiler
pip install cocotbext-ral[all] # Everything
cocotb 1.x and 2.x
cocotbext-ral works on both cocotb 1.x and cocotb 2.x. Under cocotb 2.x
you need a cocotbext-axi build that is itself cocotb-2.x compatible; the
public PyPI release may lag, in which case install a patched/forked build:
pip install "cocotb>=2.0" cocotbext-axi
(The library itself ships type hints — py.typed — so editors and mypy see them.)
Quick start
With cocotb simulation
import cocotb
from cocotbext.axi import AxiLiteMaster, AxiLiteBus
from cocotbext.ral import RuntimeRAL
from cocotbext.ral.adapters import load_json
@cocotb.test()
async def test_registers(dut):
model = load_json("registers.json")
ral = RuntimeRAL("my_ip", model, dut_handle=dut, txn_log=True)
master = AxiLiteMaster(AxiLiteBus.from_prefix(dut, "s_axil"), dut.clk, dut.rst)
ral.attach_master(master, protocol="axil", interface="dut.s_axil")
# Write and read with automatic prediction checking
await ral.write("CTRL", 0x01)
val = await ral.read("CTRL")
# Field-level access with RMW safety
await ral.write_field("CTRL", "enable", 1)
en = await ral.read_field("CTRL", "enable")
# Check results
ral.raise_on_errors()
ral.close_txn_log()
Standalone (no cocotb)
The core model, predictor, and policy layers have zero dependencies:
from cocotbext.ral import RegisterModel, Register, RegisterField, SwAccess
from cocotbext.ral.runtime_predictor import RuntimePredictor
model = RegisterModel("my_ip")
reg = Register("CTRL", address=0x0, size_bits=32, fields=[
RegisterField("enable", lsb=0, msb=0, reset_value=0, sw_access=SwAccess.RW),
RegisterField("irq", lsb=8, msb=15, reset_value=0xFF, sw_access=SwAccess.W1C),
])
model.add_register(reg, hierarchical_name="block.CTRL")
pred = RuntimePredictor(model)
pred.predict_write(0x0, 0x01)
result = pred.predict_read(0x0, 0x01)
assert result.passed
API classes
| Class | Description |
|---|---|
RuntimeRAL |
The RAL: runtime-state-backed prediction + front-door bus, RMW safety, backdoor resolution, and transaction logging |
RuntimePredictor |
Standalone prediction engine (no cocotb needed) |
RuntimeState |
Per-instance mutable register state |
AccessPolicy |
Per-field read/write behavior |
TransactionLogger |
Detailed file-based transaction logging |
BackdoorResolver |
HDL path resolution (base, Prefix, Mapping variants) |
RegisterModel |
Structural register specification |
Register loading
from cocotbext.ral.adapters import load_json, load_rdl
model = load_json("registers.json") # RDL-generated JSON
model = load_rdl("regs.rdl", top_name="my_ip", incdir=[]) # SystemRDL source
Access types
| SwAccess | Write behavior | Read behavior | Volatile by default |
|---|---|---|---|
RW |
Update value | Check prediction | No |
RO |
Ignored | Not checked | Yes |
WO |
Update value | Not checked | No |
W1C |
Clear written-1 bits | Check prediction | No |
W1S |
Set written-1 bits | Check prediction | No |
RCLR |
Ignored | Clears to 0 after read | Yes |
RSET |
Ignored | Sets to all-1s after read | Yes |
Aliases: WOCLR=W1C, WOSET=W1S, RC=RCLR, RS=RSET
Transaction logging
Enable detailed per-transaction file output:
# Default filename (register_txns.log)
ral = RuntimeRAL("ip", model, txn_log=True)
# Custom path
ral = RuntimeRAL("ip", model, txn_log="my_regs.log")
# Phase annotations
ral.set_txn_phase("Phase 1: Reset value check")
await ral.write(addr, value)
# Summary and close
ral.close_txn_log()
Each transaction entry includes: model path, address, data, protocol, interface HDL path, status (PASS/FAIL/SKIP), mirror state, per-field breakdown, and RMW safety assessment.
Testing
pip install -e .[dev,rdl]
pytest # pure-Python unit tests
ruff check cocotbext/ # lint
mypy # type-check
196 pure-Python tests covering: register model (including search / group helpers, field enums, reset domains), runtime predictor (all access types, external-read side-effects), access policies, RMW safety, backdoor resolvers (including cocotb 1.x/2.x value resolution), runtime state, volatile policy, debug helpers, checker, JSON loader, RDL loader, transaction logger, RuntimeRAL construction / reset / check-toggle helpers, and the completeness features (wide-register splitting, bus-response checking, byte-strobe partial writes, callbacks, memory burst, address-offset maps). (RDL loader tests require the rdl extra; they skip otherwise.)
Documentation
Read in this order:
- Quick Start -- 10-step walkthrough covering all access types and the common flows.
- Architecture -- layer-by-layer design and the rationale behind each decision.
- API reference (pick what you need):
- Core Model --
RegisterModel,Register,RegisterField,SwAccess. - Runtime API --
RuntimeRAL, mirror update modes, RMW logging, search / bulk APIs. - Integration and Loaders -- JSON/RDL loaders, backdoor resolvers, transaction logging.
- Core Model --
License
MIT
Metadata
Release files for cocotbext-ral 0.6.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 |
|---|---|---|---|---|
| cocotbext_ral-0.6.0.tar.gz | 60.5 kB | Without provenance | Details for cocotbext_ral-0.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cocotbext_ral-0.6.0-py3-none-any.whl | Python 3 | none | any | Details for cocotbext_ral-0.6.0-py3-none-any.whl |
Total release size: 107.9 kB
Release files / cocotbext_ral-0.6.0.tar.gz
| Download URL | cocotbext_ral-0.6.0.tar.gz |
|---|---|
| Size | 60.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b10f6b8f2e9652834d3187ee85438d884608a8e7ebb14b033a99b57de4dcb251
|
|
BLAKE2b-256 checksum How to use checksums |
08769911aa54bea0522e5287ea7c56a5fa7d74826e991516228127157918acbf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / cocotbext_ral-0.6.0-py3-none-any.whl
| Download URL | cocotbext_ral-0.6.0-py3-none-any.whl |
|---|---|
| Size | 47.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4176b769adf25d4cdc896b3e1fd33268541d428a9b6035b9223aa035f9f6694b
|
|
BLAKE2b-256 checksum How to use checksums |
6e09b7ee6f5f97916a0f52348ebbf9b21f0bc36532cf34d839cb3a6c5994ad2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for cocotbext-ral 0.6.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.