ccbb5e84f9
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. |
||
---|---|---|
.. | ||
arduino_zero | ||
feather_m0_adalogger | ||
feather_m0_basic | ||
feather_m0_flash | ||
metro_m0_flash | ||
samd21x18-bootloader-external-flash.ld | ||
samd21x18-bootloader.ld | ||
samd21x18-external-flash.ld | ||
samd21x18.ld |