suspect-devices/circuitpython - CircuitPython - a Python implementation for teaching coding with microcontrollers

Age	Commit message (Collapse)	Author
2017-02-22	Check that neopixel write is actually given a DigitalInOut.	Scott Shawcroft

2017-02-19	Add print support to Pin. #83 #76	Scott Shawcroft

2017-02-19	Fix pin free check to ignore None objects. Fixes #89	Scott Shawcroft

2016-12-07	atmel-samd & esp8266: Make sure pins are not already in use.	Scott Shawcroft
	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.
2016-11-29	shared-bindings: Ensure pin objects are actually pins.	Scott Shawcroft
	Fixes #12
2016-11-21	This introduces an alternative hardware API called nativeio structured ↵	Scott Shawcroft
	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.