suspect-devices/circuitpython/shared-bindings/neopixel_write, branch 2.2.4 CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=2.2.4 2017-07-12T21:59:26+00:00 shared-bindings: Fix neopixel_write example. I forgot to save in the editor. Fixes #163 2017-07-12T21:59:26+00:00 Scott Shawcroft scott@chickadee.tech 2017-07-12T21:59:26+00:00 urn:sha1:b69507fc64a0248db6d3e4afe7fb98d976f47f1d shared-bindings: Add neopixel_write example. Fixes #163 2017-07-12T18:55:17+00:00 Scott Shawcroft scott@chickadee.tech 2017-07-12T18:32:46+00:00 urn:sha1:5e231bd8f9237dbecf3bd6835f0eaf85942a8f3b Split up nativeio. 2017-04-10T20:32:19+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2017-04-10T20:32:19+00:00 urn:sha1:f28f8ba56809fd56e777eabceae21127f95b89ed This was done to allow greatly granularity when deciding what functionality is built into each board's build. For example, this way pulseio can be omitted to allow for something else such as touchio. shared-bindings: Do a pass on the docs and make sure keyword only arguments make sense and are documented correctly. Fixes #109 2017-03-07T11:58:57+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2017-03-07T11:58:57+00:00 urn:sha1:4aaa0ea00864dea835161b96a75c15e8c5242744 Check that neopixel write is actually given a DigitalInOut. 2017-02-22T19:10:10+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2017-02-22T19:10:10+00:00 urn:sha1:4c05086661bd486490442318934a57b93304aa0e Save space by only supporting 800khz neopixels. 2017-02-19T16:22:42+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2017-02-19T16:22:42+00:00 urn:sha1:f0b62a2b0eef5d6a825d6ca19a8c50f019e2628f 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.