This release is a pre-release and may not be stable for production use.
bust generates the register file of an FPGA or ASIC module from a JSON register map. From one file it writes the VHDL register file with its bus endpoint, a self-checking UVVM testbench, C, C++ and Python headers, an IPBus address table and LaTeX documentation.
Features
- Six buses: AXI4-Lite, IPBus, SBI (the UVVM simple bus interface), Avalon-MM, Wishbone and APB. Each is a thin endpoint in front of the same register file.
- Your design reaches every field by name through the
to_hwandfrom_hwVHDL records, and enumerated fields become VHDL enumeration types. - Separate software and hardware access per field, with SystemRDL-style side effects: clear or set on read, set, clear or toggle on write, single-cycle pulses, hardware set and clear, write enables and access strobes.
- The base address is a VHDL generic, so one module can sit at any address.
- A self-checking UVVM testbench for every module, on every bus.
- C, C++ and Python headers, an IPBus address table for uHAL and LaTeX/PDF documentation from the same file.
Installation
bust needs Python 3.9 or newer.
pip install bust
Usage
bust FILE [-o DIR] [[[-F | -f] [-d | -p] [-i]] | [-a] | [-c | -e]]
bust --version
bust -h | --help
A minimal register map with one control register:
{
"bus": { "type": "axi", "addr_width": 32, "data_width": 32 },
"module": {
"name": "blinky",
"version": "1.0",
"description": "LED control.",
"register": [
{
"name": "ctrl", "address": "0x0", "sw": "rw", "hw": "r", "type": "fields",
"description": "LED control.",
"fields": [
{ "name": "enable", "type": "bit", "description": "Turn the LED on." },
{ "name": "rate", "type": "vector", "width": 4, "description": "Blink rate." }
]
}
]
}
}
bust blinky.json -o out -p
This writes out/blinky/ with the VHDL in hdl/, the testbench in tb/, the
headers in header/ and the LaTeX documentation in doc/. hdl/blinky.vhd
is a starter top level that is yours to edit: bust writes it once and leaves it
alone after that. Your logic reads to_hw.ctrl.enable and to_hw.ctrl.rate
from blinky_axi_endpoint, which bust regenerates on every run.
How bust is tested
- The generated files for the example register maps are kept in the repository. Every change is compared with them byte for byte, on Python 3.9 to 3.14.
- Every change to the generated VHDL is simulated with nvc and UVVM. This runs the generated testbench on all six buses, a register map with every class of access mode combination, and two modules compiled into one library.
- Hand-written reference VHDL and testbenches for all six buses run against the generated VHDL. They are the one check that does not come from the generator itself.
Documentation
The full documentation is at bust.readthedocs.io:
Release notes are in the changelog. Report bugs and ideas as GitHub issues.
License
Licensed under the Apache License 2.0. See LICENSE and NOTICE.
Author
Ola Groettvik - GitHub
AI assistance
bust started as a hand-written tool. Most of the code for 1.0 was written with AI assistance. The author reviewed every change, and no change is merged before it passes the checks under How bust is tested above.
Metadata
Release files for bust 1.0.0a3
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 | |
|---|---|---|---|---|
| bust-1.0.0a3.tar.gz | 111.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bust-1.0.0a3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 217.2 kB
Release files / bust-1.0.0a3.tar.gz
| Download URL | bust-1.0.0a3.tar.gz |
|---|---|
| Size | 111.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad7a0a7c9dd81e2396a4f65e704ce3ee8527c42de0aef70a05f6d4d8172dbe53
|
|
BLAKE2b-256 checksum How to use checksums |
6c0013581645ace408d3607e25853f6721219cd45755ba6bdc94700bc5524024
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / bust-1.0.0a3-py3-none-any.whl
| Download URL | bust-1.0.0a3-py3-none-any.whl |
|---|---|
| Size | 105.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6864fbc7e85791c29410f7e55ae2c6dfe0771036059ec1106c1cb44bf3987e3
|
|
BLAKE2b-256 checksum How to use checksums |
a118cef373420a3490a8e60399bf64ff0680f4a7cf032a5f6e9a4d971afd348c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for bust 1.0.0a3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for bust-1.0.0a3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA 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.