<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/atmel-samd/samdneopixel.c, branch main</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=main</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2016-11-21T22:11:52+00:00</updated>
<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>
<entry>
<title>atmel-samd: Rework tick timer to use TC5 and support neopixel status LED.</title>
<updated>2016-10-29T03:16:39+00:00</updated>
<author>
<name>Scott Shawcroft</name>
<email>scott@chickadee.tech</email>
</author>
<published>2016-10-29T03:16:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=5b3a143ffe126b8cd999a6298ab3de9ec5532242'/>
<id>urn:sha1:5b3a143ffe126b8cd999a6298ab3de9ec5532242</id>
<content type='text'>
The tick timer needed to be reworked because the ASF delay functions also
use the SysTick timer. Now, it uses TC5 and calls out to the autoreset
logic every tick. Fixes #43.

Added neopixel status colors and corrected the latch time from ms to us.
Fixes #42.
</content>
</entry>
<entry>
<title>atmel-samd: Implement time.ticks_ms function using SysTick timer, add global interrupt enable/disable functions.</title>
<updated>2016-10-13T04:59:43+00:00</updated>
<author>
<name>Tony DiCola</name>
<email>tony@tonydicola.com</email>
</author>
<published>2016-10-13T04:59:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=903bc8d04edef0e60fd755e8b9e46ef6a8ec2584'/>
<id>urn:sha1:903bc8d04edef0e60fd755e8b9e46ef6a8ec2584</id>
<content type='text'>
</content>
</entry>
<entry>
<title>atmel-samd: Add low level neopixel_write module &amp; function for WS281x/neopixel RGB LEDs.</title>
<updated>2016-10-05T19:35:23+00:00</updated>
<author>
<name>Tony DiCola</name>
<email>tony@tonydicola.com</email>
</author>
<published>2016-10-05T19:35:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=9c676052333f45c74791ab30cc62b827631523f5'/>
<id>urn:sha1:9c676052333f45c74791ab30cc62b827631523f5</id>
<content type='text'>
</content>
</entry>
</feed>
