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.
24 lines
736 B
C
24 lines
736 B
C
// LEDs
|
|
#define USB_REPL
|
|
|
|
#define MICROPY_HW_BOARD_NAME "Adafruit Feather M0 Flash"
|
|
#define MICROPY_HW_MCU_NAME "samd21g18"
|
|
|
|
#define MICROPY_HW_NEOPIXEL &pin_PA14
|
|
|
|
#define SPI_FLASH_BAUDRATE (1000000)
|
|
|
|
// On-board flash
|
|
#define SPI_FLASH_MUX_SETTING SPI_SIGNAL_MUX_SETTING_E
|
|
#define SPI_FLASH_PAD0_PINMUX PINMUX_PA12D_SERCOM4_PAD0 // MISO
|
|
// Use default pinmux for the chip select since we manage it ourselves.
|
|
#define SPI_FLASH_PAD1_PINMUX PINMUX_DEFAULT // CS
|
|
#define SPI_FLASH_PAD2_PINMUX PINMUX_PB10D_SERCOM4_PAD2 // MOSI
|
|
#define SPI_FLASH_PAD3_PINMUX PINMUX_PB11D_SERCOM4_PAD3 // SCK
|
|
#define SPI_FLASH_CS PIN_PA13
|
|
#define SPI_FLASH_SERCOM SERCOM4
|
|
|
|
#define AUTORESET_DELAY_MS 500
|
|
|
|
#define FLASH_INCLUDE "spi_flash.h"
|