circuitpython/atmel-samd/boards/feather_m0_basic/mpconfigboard.h

// 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"
Blinking the LED works. Clocks should be set up correctly. Everything works fine without USB being plugged in but faults (I think) when USB is plugged in. This is switched away from the USB code from the bootloader onto the USB code thats generated by Atmel Studio using the high level classes from ASF. 2016-08-23 02:48:09 -04:00			`// LEDs`
atmel-samd: Add D13 led as mass storage write indicator. 2016-10-25 18:06:05 -04:00			`#define MICROPY_HW_LED_MSC PIN_PA17 // red`
Add support for REPL on Arduino Zero through EDBG via UART. 2016-08-23 19:47:53 -04:00			`// #define UART_REPL`
			`#define USB_REPL`
Change the board information used in the header to be board specific. 2016-08-23 20:36:29 -04:00
atmel-samd: Rename Feather M0 Bluefruit files to Feather M0 Basic because there isn't anything Bluefruit specific yet. 2016-10-14 16:01:59 -04:00			`#define MICROPY_HW_BOARD_NAME "Adafruit Feather M0 Basic"`
Change the board information used in the header to be board specific. 2016-08-23 20:36:29 -04:00			`#define MICROPY_HW_MCU_NAME "samd21g18"`
atmel-samd: Support auto-reset based on USB write activity. It will soft-reboot micropython after a burst of writes to the file system. This means that after you save files on your computer they will be automatically rerun. This can be disabled in the build by unsetting AUTORESET_TIMER in mpconfigboard.h. Using the REPL will also prevent the soft resets until you reset with CTRL-D manually. 2016-10-25 17:27:59 -04:00
atmel-samd: Increase autoreset delay to reduce duplicate resets. 2016-10-31 14:31:33 -04:00			`#define AUTORESET_DELAY_MS 500`
This introduces an alternative hardware API called nativeio structured 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. 2016-11-03 18:50:59 -04:00
			`#define FLASH_INCLUDE "internal_flash.h"`