Skip to main content

regmap

regmap is a lightweight library to manage direct register field manipulation.

Many times been in the situation where for development I have wanted to interact with an embedded system, where for testing I just want read and write raw register values. Most of these devices contain registers with multiple fields of varying bit lengths. This library abstracts away the awkward bit manipulation into a simple register definition.

Installation

You can install regmap from PyPi with the following command:

pip install regmap

Usage

Define an interface

The interface is the code that interacts with the system containing the registers. A read and a write method need to be defined.

from regmap import Interface


class DeviceInterface(Interface):
    def read(self, address: int) -> int:
        # Function to go read a register from the device
        value = read_val_from_register(address)
        return value

    def write(self, address: int, value: int) -> None:
        # Function to go write a value to a register on the device
        write_val_to_register(address, value)

Define our registers

from regmap import BitField, Register


class config_reg_a_def(Register):
    _name = "config_reg_a"
    _address = 0x2000

    output = BitField(7, 1)
    enable = BitField(0)


class config_reg_b_def(Register):
    _name = "config_reg_b"
    _address = 0x2004

    setting2 = BitField(7, 5)
    setting1 = BitField(4, 2)
    setting0 = BitField(1, 0)


class Registers:
    def __init__(self, interface):
        self.config_reg_a = config_reg_a_def(interface)
        self.config_reg_b = config_reg_b_def(interface)

Set some values

The context manager will deal with reading and writing to the register. By default the context manager will do read, modify, write. This can be changed to perform read-only or write-only operations.

from regmap import Mode


interface = DeviceInterface()
registers = Registers(interface)

# Perform read, modify, write
with registers.config_reg_a:
    registers.config_reg_a.output = 20
    registers.config_reg_a.enable = 1

# Perform read only, will warn if modifications were attempted
with registers.config_reg_a(mode=Mode.RO):
    print(registers.config_reg_a.output)

# Perform write only, zeros will be written in any unset fields
with registers.config_reg_b(mode=Mode.WO):
    registers.config_reg_b.setting1 = 2

Metadata

Release files for regmap 0.2.0

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

Source distribution (sdist)

Source distribution for regmap 0.2.0
File Size Uploaded Provenance
regmap-0.2.0.tar.gz 8.5 kB With provenance Details

Built distribution (wheel)

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

Total release size: 16.6 kB

Release files / regmap-0.2.0.tar.gz

Download URL regmap-0.2.0.tar.gz
Size 8.5 kB
Tags Source
SHA-256 checksum
How to use checksums
827cafb312df60b3ebeee612554204d1dfab8bd5cb89e08f2aaa8593995848ee
BLAKE2b-256 checksum
How to use checksums
e61339a32dd3b25ded01ebd628d2ce14ca94ac8311c8886431273a7d45df69e9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.8

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 Feb 12, 2025.

Transparency log

Release files / regmap-0.2.0-py3-none-any.whl

Download URL regmap-0.2.0-py3-none-any.whl
Size 8.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e28e2c5168d22cd906aeba4a79e3dfba952e9d5ddb0d8a849b235d1b6be36e5f
BLAKE2b-256 checksum
How to use checksums
b9448a8979902b5f00813e4c7d6c7fe966e741dd8117a37dd7f190422d407fbe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.8

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 Feb 12, 2025.

Transparency log

Security for regmap 0.2.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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for regmap-0.2.0.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 Feb 12, 2025.

Transparency log

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.0 This release

2 release files Full 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