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.
12 lines
275 B
C
12 lines
275 B
C
// LEDs
|
|
#define MICROPY_HW_LED_MSC PIN_PA17 // red
|
|
// #define UART_REPL
|
|
#define USB_REPL
|
|
|
|
#define MICROPY_HW_BOARD_NAME "Adafruit Feather M0 Basic"
|
|
#define MICROPY_HW_MCU_NAME "samd21g18"
|
|
|
|
#define AUTORESET_DELAY_MS 500
|
|
|
|
#define FLASH_INCLUDE "internal_flash.h"
|