micropython-sram
SRAM/EERAM library for micropython
Primary used to work with 23LCV1024 (SPI SRAM with battery backup) memory which can be used as EEPROM/Flash but with unlimited number of writes. For applications where you need offten writes.
Simple code just use default sequenatial mode and allow to read/write whole SRAM memory, in case of 23LCV1024 it's full 128kB.
Nice2have TODO:
- support also other chips (for example 47xx, 48xx) and protocols (like I2C)
- IO Stream support
- Page/Byte access modes (for example to prevent overwritting other data by buffer overflow)
- Filesystem emulation (? - maybe if there will be IOStream, then someother lib could be used?)
- Direct support to write other data types than buffer ? Like string, int
Metadata
Release files for micropython-sram 0.0.1
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 |
|---|---|---|---|---|
| micropython-sram-0.0.1.tar.gz | 3.3 kB | Without provenance | Details for micropython-sram-0.0.1.tar.gz |
Release files / micropython-sram-0.0.1.tar.gz
| Download URL | micropython-sram-0.0.1.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7eeb018479c9656bbf6a5e706d5a78f440596f26d1d657927924dbeb43b2df1
|
|
BLAKE2b-256 checksum How to use checksums |
9baa9b91f9224dfb5dbf5cfa5906a3067734466b49be7d3d54b77bd51f996ea4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.64.0 CPython/3.10.4
|
Security for micropython-sram 0.0.1
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.