This package provides class to control the GPIO on Olinuxino A10S. Current release does no support any peripheral functions.
Example
Typical usage:
#!/usr/bin/env python import A10S_GPIO as GPIO #init module GPIO.init() #configure module GPIO.setcfg(GPIO.PIN#, GPIO.OUTPUT) GPIO.setcfg(GPIO.PIN#, GPIO.INPUT) #read the current GPIO configuration config = GPIO.getcfg(GPIO.PIN#) #set GPIO high GPIO.output(GPIO.PIN#, GPIO.HIGH) #set GPIO low GPIO.output(GPIO.PIN#, GPIO.LOW) #read input state = GPIO.input(GPIO.PIN#) #cleanup GPIO.cleanup()
Warning
Before using this tool it is HIGHLY RECOMENDED to check Olinuxino A10S schematic.
Changelog
- pyA10S 0.1.0 (2013-05-03)
Initial release
Metadata
Release files for pyA10S 0.1.2
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 | |
|---|---|---|---|---|
| pyA10S-0.1.2.tar.gz | 6.3 kB | Without provenance | Details |
Release files / pyA10S-0.1.2.tar.gz
| Download URL | pyA10S-0.1.2.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cfd0ec5bcdcca669172077384d86c39e4f2f33ba3d463d192b2bb22070c9b203
|
|
BLAKE2b-256 checksum How to use checksums |
5707db4db343c1e9c0204ed9f82c2150701180a81f219f37ceb485ae6b5777f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyA10S 0.1.2
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.