<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/shared-bindings/nativeio/__init__.c, branch 6.1.x</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.1.x</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.1.x'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2017-04-10T20:32:19+00:00</updated>
<entry>
<title>Split up nativeio.</title>
<updated>2017-04-10T20:32:19+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott.shawcroft@gmail.com</email>
</author>
<published>2017-04-10T20:32:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=f28f8ba56809fd56e777eabceae21127f95b89ed'/>
<id>urn:sha1:f28f8ba56809fd56e777eabceae21127f95b89ed</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Add low-level OneWire support class.</title>
<updated>2017-03-25T12:04:49+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott.shawcroft@gmail.com</email>
</author>
<published>2017-03-25T12:04:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=ff208d767741104f7d2644a58269d7064d4c1b6a'/>
<id>urn:sha1:ff208d767741104f7d2644a58269d7064d4c1b6a</id>
<content type='text'>
This class focuses on the timing sensitive parts of the protocol.
Everything else will be done by Python code.

This also establishes that its OK to back a nativeio class with a
bitbang implementation when no hardware acceleration exists. When
it does, then bitbangio should be used to explicitly bitbang a
protocol.
</content>
</entry>
<entry>
<title>Add PulseIn support which can be used to measure a series of pulse widths.</title>
<updated>2017-03-24T10:30:15+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott.shawcroft@gmail.com</email>
</author>
<published>2017-03-13T20:55:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=7cb54864aa7c651fc65350708afcddfab2a15fcc'/>
<id>urn:sha1:7cb54864aa7c651fc65350708afcddfab2a15fcc</id>
<content type='text'>
This is useful for infrared input and DHT sensors.
</content>
</entry>
<entry>
<title>Add PulseOut which can pulse a PWMOut for IR remote transmission.</title>
<updated>2017-03-10T18:17:54+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott.shawcroft@gmail.com</email>
</author>
<published>2017-03-10T18:17:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=d200a621647aa9fc05aae29ad7bc38363025438b'/>
<id>urn:sha1:d200a621647aa9fc05aae29ad7bc38363025438b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Improve docs and update to CircuitPython.</title>
<updated>2017-01-06T00:20:46+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott.shawcroft@gmail.com</email>
</author>
<published>2017-01-06T00:20:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=7c302c395ec699738bade269673c06a38cbedbff'/>
<id>urn:sha1:7c302c395ec699738bade269673c06a38cbedbff</id>
<content type='text'>
</content>
</entry>
<entry>
<title>atmel-samd: Add preliminary support for UART</title>
<updated>2016-12-19T21:03:50+00:00</updated>
<author>
<name>Sebastian Plamauer</name>
<email>oeplse@gmail.com</email>
</author>
<published>2016-10-31T19:18:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=1598e44231a9ea2dbf20f487fcd05ded90e80d9a'/>
<id>urn:sha1:1598e44231a9ea2dbf20f487fcd05ded90e80d9a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>atmel-samd: Basic capacitive touch button support.</title>
<updated>2016-12-12T23:11:25+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott.shawcroft@gmail.com</email>
</author>
<published>2016-12-07T02:39:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=3972bc19c7c788d5c587156aba39ea659decc420'/>
<id>urn:sha1:3972bc19c7c788d5c587156aba39ea659decc420</id>
<content type='text'>
Currently only works on a single channel and is only enabled for boards with
SPI flash. Only really designed for hardware testing at this point.
</content>
</entry>
<entry>
<title>shared-bindings: Fix blinky example. Fixes #55</title>
<updated>2016-11-29T22:37:25+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott.shawcroft@gmail.com</email>
</author>
<published>2016-11-29T22:37:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=16764dfa31c8ca9331c725dee164738792a8d617'/>
<id>urn:sha1:16764dfa31c8ca9331c725dee164738792a8d617</id>
<content type='text'>
</content>
</entry>
<entry>
<title>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.</title>
<updated>2016-11-21T22:11:52+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott@chickadee.tech</email>
</author>
<published>2016-11-03T22:50:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=ccbb5e84f980e252f7380d96fcc5c417a8a64523'/>
<id>urn:sha1:ccbb5e84f980e252f7380d96fcc5c417a8a64523</id>
<content type='text'>
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.
</content>
</entry>
</feed>
