Introduction
A library for adding bitbang I2C and SPI to CircuitPython without the built-in bitbangio module. The interface is intended to be the same as bitbangio and therefore there is no bit order or chip select functionality. If your board supports bitbangio, it is recommended to use that instead as the timing should be more reliable.
Dependencies
This driver depends on:
Please ensure all dependencies are available on the CircuitPython filesystem. This is easily achieved by downloading the Adafruit library and driver bundle.
Installing from PyPI
On supported GNU/Linux systems like the Raspberry Pi, you can install the driver locally from PyPI. To install for current user:
pip3 install adafruit-circuitpython-bitbangioTo install system-wide (this may be required in some cases):
sudo pip3 install adafruit-circuitpython-bitbangioTo install in a virtual environment in your current project:
mkdir project-name && cd project-name
python3 -m venv .venv
source .venv/bin/activate
pip3 install adafruit-circuitpython-bitbangioUsage Example
"""
This example is for demonstrating how to retrieving the
board ID from a BME280, which is stored in register 0xD0.
It should return a result of [96]
"""
import board
import digitalio
import adafruit_bitbangio as bitbangio
# Change these to the actual connections
SCLK_PIN = board.D6
MOSI_PIN = board.D17
MISO_PIN = board.D18
CS_PIN = board.D5
cs = digitalio.DigitalInOut(CS_PIN)
cs.switch_to_output(value=True)
spi = bitbangio.SPI(SCLK_PIN, MOSI=MOSI_PIN, MISO=MISO_PIN)
cs.value = 0
while not spi.try_lock():
pass
spi.write([0xD0])
data = [0x00]
spi.readinto(data)
spi.unlock()
cs.value = 1
print("Result is {}".format(data))Documentation
API documentation for this library can be found on Read the Docs.
For information on building library documentation, please check out this guide.
Contributing
Contributions are welcome! Please read our Code of Conduct before contributing to help this project stay welcoming.
1 maintainer
Metadata
1 maintainer
Release files for adafruit-circuitpython-bitbangio 1.3.13
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 | |
|---|---|---|---|---|
| adafruit-circuitpython-bitbangio-1.3.13.tar.gz | 29.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| adafruit_circuitpython_bitbangio-1.3.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.8 kB
Release files / adafruit-circuitpython-bitbangio-1.3.13.tar.gz
| Download URL | adafruit-circuitpython-bitbangio-1.3.13.tar.gz |
|---|---|
| Size | 29.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6dd6753d4f8b1ffc6833028ff621b50335d8f32a3826a8d156998d4544e235a8
|
|
BLAKE2b-256 checksum How to use checksums |
e39513bc710a30a2b45d98d0090a199d0345af90ffe0c238959b9ae0c9807d51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Release files / adafruit_circuitpython_bitbangio-1.3.13-py3-none-any.whl
| Download URL | adafruit_circuitpython_bitbangio-1.3.13-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c6304e84d65eaa6d356a2b64c4fe80a95c97ee5fcd863e991630874a09a9ff32
|
|
BLAKE2b-256 checksum How to use checksums |
87ae25eb1adf5d4f9f4752712c9b9bab555e97eca5c7b76c20f2e89823609268
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Security for adafruit-circuitpython-bitbangio 1.3.13
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.
