summaryrefslogtreecommitdiff
path: root/shared-bindings/board
AgeCommit message (Collapse)Author
2019-11-27make UART.write be blocking on SAMD; add timeout propertyDan Halbert
2019-06-11Merge latest 4.0.x fixes into masterDan Halbert
2019-06-06Include display objects in gc.Dan Halbert
2019-05-30Improve rST consistency for rst2pyi useScott Shawcroft
2019-04-09Fix boards with no shared busses.Scott Shawcroft
2019-04-08Reorganize board busses into shared-bindings and shared-module.Scott Shawcroft
2018-06-01atmel-samd: Re-org helper peripheral files into their own subdirectory.Scott Shawcroft
Ideally in the future they won't depend on ASF4 or MicroPython.
2017-08-25Initial merge of micropython v1.9.2 into circuitpython 2.0.0 (in ↵Dan Halbert
development) master. cpx build compiles and loads and works in repl; test suite not run yet esp8266 not tested yet
2016-11-21This 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.