suspect-devices/circuitpython/shared-bindings/nativeio/DigitalInOut.c, branch 0.9.0 CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=0.9.0 2017-02-19T15:11:33+00:00 Switch enum-like attributes to all caps and add print support for them. Make room for this functionality by adding a shared __enter__ function object. #76 2017-02-19T15:11:33+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2017-02-19T15:11:33+00:00 urn:sha1:e9659e61f89fb9ef84011c42e89849f7fd9bc9c1 More fixes to pin pull thanks to jerryn: 2017-01-16T23:32:23+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2017-01-16T23:32:23+00:00 urn:sha1:d239dbdc2807322c86d5dc5563dc263fa47087d1 * Correct atmel-samd pin pull state. * Correct conversion from python pull objects to C enum. Fix pull kwarg DigitalInOut.switch_to_input and add example use to docs. 2017-01-16T18:35:46+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2017-01-16T18:35:46+00:00 urn:sha1:df96823deed7af4587cb9ebfa7f5d471417f90f1 Thanks to jerryn from the Adafruit Forum for finding the bug! Add time.struct_time support. 2017-01-05T22:00:48+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2017-01-05T22:00:48+00:00 urn:sha1:e52fbf2e6aa13a34ceae60e8ee6ad2c3a18092ee atmel-samd & esp8266: Make sure pins are not already in use. 2016-12-07T23:21:14+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2016-12-06T18:31:38+00:00 urn:sha1:0ae344841ff048424b886e1f386b16c0c9ba4ee2 This prevents corrupting previous functional objects by stealing their pins out from under them. It prevents this by ensuring that pins are in default state before claiming them. It also verifies pins are released correctly and reset on soft reset. Fixes #4, instantiating a second class will fail. Fixes #29, pins are now reset too. shared-bindings: Ensure pin objects are actually pins. 2016-11-29T23:50:01+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2016-11-29T23:49:50+00:00 urn:sha1:4933fa1c27f987be558a33b1736089b04e880a03 Fixes #12 This introduces an alternative hardware API called nativeio structured around different functions that are typically accelerated by native hardware. Its not meant to reflect the structure of the hardware. 2016-11-21T22:11:52+00:00 Scott Shawcroft scott@chickadee.tech 2016-11-03T22:50:59+00:00 urn:sha1:ccbb5e84f980e252f7380d96fcc5c417a8a64523 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.