micropython/ports/samd
Damien George 2ed976f140 samd/mcu/samd21: Enable MICROPY_STACK_CHECK on SAMD21.
Increases firmware size by +140 bytes and uses +4 extra bytes of RAM, but
allows the test suite to run without crashing.

Signed-off-by: Damien George <damien@micropython.org>
2024-01-08 23:24:39 +11:00
..
boards
mcu samd/mcu/samd21: Enable MICROPY_STACK_CHECK on SAMD21. 2024-01-08 23:24:39 +11:00
modules
Makefile samd/mcu/samd21: Reorganize and enable more firmware features. 2024-01-02 18:46:33 +11:00
README.md
clock_config.h
fatfs_port.c samd: Remove the MICROPY_PY_MACHINE_RTC config option. 2024-01-02 18:46:11 +11:00
help.c
machine_adc.c
machine_bitstream.c
machine_dac.c
machine_i2c.c
machine_pin.c
machine_pwm.c
machine_rtc.c samd: Remove the MICROPY_PY_MACHINE_RTC config option. 2024-01-02 18:46:11 +11:00
machine_spi.c
machine_uart.c
machine_wdt.c
main.c
modmachine.c samd: Remove the MICROPY_PY_MACHINE_RTC config option. 2024-01-02 18:46:11 +11:00
modmachine.h extmod/modmachine: Provide common Python bindings for bootloader(). 2023-11-30 16:11:11 +11:00
modos.c extmod/modos: Factor os.dupterm_notify() function to common extmod code. 2023-12-18 12:20:47 +11:00
modsamd.c
modtime.c
mpconfigport.h samd/mpconfigport: Simplify and consolidate config options. 2024-01-08 23:24:39 +11:00
mphalport.c ports: Fix sys.stdout.buffer.write() return value. 2023-12-22 10:32:46 +11:00
mphalport.h ports: Move definitions of ATOMIC_SECTION macros to mphalport.h. 2023-12-01 14:37:48 +11:00
pendsv.c
pendsv.h
pin_af.c
pin_af.h
qstrdefsport.h
samd_flash.c
samd_isr.c
samd_qspiflash.c
samd_soc.c samd: Remove the MICROPY_PY_MACHINE_RTC config option. 2024-01-02 18:46:11 +11:00
samd_soc.h
samd_spiflash.c
sections.ld
usbd.c

README.md

Port of MicroPython to Microchip SAMD MCUs

Supports SAMD21 and SAMD51. For each supported device there is a subdirectory in the boards/ directory.

The entry point for the specific port documentation is at https://docs.micropython.org/en/latest/samd/quickref.html, which also shows the assignment of IO-Functions to pins. The generic MicroPython documentation applies for anything not specific for the SAM port.

Due to the different flash sizes of SAMD21 and SAMD51 devices, the coverage of MicroPython modules differ. Use help("modules") to tell, which MicroPython modules are provided.

Build instructions

Before building the firmware for a given board the MicroPython cross-compiler must be built; it will be used to pre-compile some of the built-in scripts to bytecode. The cross-compiler is built and run on the host machine, using:

$ make -C mpy-cross

This command should be executed from the root directory of this repository. All other commands below should be executed from the ports/stm32/ directory.

An ARM compiler is required for the build, along with the associated binary utilities. The default compiler is arm-none-eabi-gcc, which is available for Arch Linux via the package arm-none-eabi-gcc, for Ubuntu via instructions here, or see here for the main GCC ARM Embedded page. The compiler can be changed using the CROSS_COMPILE variable when invoking make.

Next, the board to build must be selected. There is no default board. Any of the names of the subdirectories in the boards/ directory is a valid board. The board name must be passed as the argument to BOARD= when invoking make.

All boards require certain submodules to be obtained before they can be built. The correct set of submodules can be initialised using (with ADAFRUIT_ITSYBITSY_M4_EXPRESS as an example of the selected board):

$ make BOARD=ADAFRUIT_ITSYBITSY_M4_EXPRESS submodules

Then to build the board's firmware run:

$ make BOARD=ADAFRUIT_ITSYBITSY_M4_EXPRESS clean
$ make BOARD=ADAFRUIT_ITSYBITSY_M4_EXPRESS

The above command produces binary images in the build-ADAFRUIT_ITSYBITSY_M4_EXPRESS/ subdirectory (or the equivalent directory for the board specified).

Flashing the Firmware

Most SAMD21 and SAMD51 boards have a built in firmware loader. To start it, push the reset button of the boards twice. The speed varies a little bit. If the firmware loader starts, a drive will appear in the file manager of your PC. Copy the created firmware.uf2 file to that drive. If the upload is finished, the drive will disappear and the board will reboot.