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

Age	Commit message (Collapse)	Author
2017-01-05	Rename to CircuitPython	Scott Shawcroft

2016-12-19	atmel-samd: Add help() and remove mem_info functions from smallest builds to ↵	Scott Shawcroft
	make room.
2016-12-09	atmel-samd: Add APA102 support and flash more advanced status.	Scott Shawcroft
	The new sequence is as follows: * Solid blue during the boot/settings script. * Solid green during the main/code script. * After main while waiting to enter repl or reset: * Fading green once main is done successfully. * On error produce a series of flashes: * Long flash color of script. * Long flash color of error: * Green = IndentationError * Cyan = SyntaxError * White = NameError * Orange = OSError * Yellow = Other error * Line number of the exception by digit. Number of flashes represents value. * Thousands = White * Hundreds = Blue * Tens = Yellow * Ones = Cyan * Off for a period and then repeats. At any point a write to the flash storage will flicker red. Fixes #63
2016-12-02	Add try_lock and unlock to I2C and SPI classes to make sure things	Scott Shawcroft
	are shared well between threads and underlying MicroPython (SPI Flash for example.) It is recommended to use the bus device classes to manage the locks and other transaction state. https://github.com/adafruit/Adafruit_MicroPython_BusDevice Fixed #58 Fixed #59 Fixed #60
2016-11-29	shared-bindings: Make MOSI and MISO optional for SPI.	Scott Shawcroft

2016-11-23	uheap: Switch to using gc_nbytes to measure allcoation size so we stop ↵	Scott Shawcroft
	undercounting.
2016-11-22	Add uheap for debugging the size of objects. Still not perfect though.	Scott Shawcroft

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.