| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Fixes #2082
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also copy some notes from busio docstrings to bitbangio docstrings
|
|
|
|
|
|
|
|
|
|
|
|
writeto_then_readfrom has been added to do a write -> no stop ->
repeated start -> read sequence. This is done to match the
capabilities of Blinka on Linux.
Code that uses stop=False will not work correctly on Blinka.
To fix, if stop=False then use writeto_then_readfrom otherwise use
writeto then readfrom_into.
First step in #2082
|
|
|
|
|
|
Also, swap make_news to accept a kwarg map and refine param checking.
Fixes #1237
|
|
|
|
|
|
|
|
Fixes #278, #277, #276, #275.
|
|
more detail to the design guide about their use.
|
|
buffer from start, end and length. The old code miscomputed length
leading to writing and reading from memory past the end of the buffer.
Consolidating the code should make it easier to get right everywhere.
|
|
make sense and are documented correctly. Fixes #109
|
|
each time to share the call.
|
|
1) Bus error will be thrown on read/write errors with errno set. (Read didn't used to fail at all.)
2) try_lock correctly returns boolean whether lock was grabbed.
Fixes #87
|
|
room for this functionality by adding a shared __enter__ function object. #76
|
|
are shared well between threads and underlying MicroPython (SPI Flash
for example.)
It is recommended to use the bus device classes to manage the locks
and other transaction state.
https://github.com/adafruit/Adafruit_MicroPython_BusDevice
Fixed #58
Fixed #59
Fixed #60
|
|
Fixes #12
|
|
around different functions that are typically accelerated by native hardware. Its not meant to reflect the structure of the hardware.
Docs are here: http://tannewt-micropython.readthedocs.io/en/microcontroller/
It differs from upstream's machine in the following ways:
* Python API is identical across ports due to code structure. (Lives in shared-bindings)
* Focuses on abstracting common functionality (AnalogIn) and not representing structure (ADC).
* Documentation lives with code making it easy to ensure they match.
* Pin is split into references (board.D13 and microcontroller.pin.PA17) and functionality (DigitalInOut).
* All nativeio classes claim underlying hardware resources when inited on construction, support Context Managers (aka with statements) and have deinit methods which release the claimed hardware.
* All constructors take pin references rather than peripheral ids. Its up to the implementation to find hardware or throw and exception.
|