| 1 |
# By default the filesystem is in external QSPI flash. But by setting the |
| 2 |
# following option this board puts some code into external flash set in XIP mode. |
| 3 |
# USE_MBOOT must be enabled; see f769_qspi.ld for code that goes in QSPI flash |
| 4 |
USE_QSPI_XIP ?= 0 |
| 5 |
CFLAGS += -DUSE_QSPI_XIP=$(USE_QSPI_XIP) |
| 6 |
|
| 7 |
# MCU settings |
| 8 |
MCU_SERIES = f7 |
| 9 |
CMSIS_MCU = STM32F769xx |
| 10 |
MICROPY_FLOAT_IMPL = double |
| 11 |
AF_FILE = boards/stm32f767_af.csv |
| 12 |
|
| 13 |
ifeq ($(USE_MBOOT),1) |
| 14 |
ifeq ($(USE_QSPI_XIP),1) |
| 15 |
|
| 16 |
# When using Mboot and QSPI-XIP the text is split between internal and external |
| 17 |
# QSPI flash, and the filesystem is in internal flash between the bootloader and |
| 18 |
# the main program text. |
| 19 |
LD_FILES = boards/STM32F769DISC/f769_qspi.ld |
| 20 |
TEXT0_ADDR = 0x08020000 |
| 21 |
TEXT1_ADDR = 0x90000000 |
| 22 |
TEXT0_SECTIONS = .isr_vector .text .data .ARM |
| 23 |
TEXT1_SECTIONS = .text_qspi |
| 24 |
|
| 25 |
else |
| 26 |
|
| 27 |
# When using Mboot but not QSPI-XIP all the text goes together after the bootloader |
| 28 |
# (at same location as when QSPI-XIP is enabled so the same Mboot can be used for |
| 29 |
# either configuration) and the filesystem is in external flash. |
| 30 |
LD_FILES = boards/stm32f769.ld boards/common_blifs.ld |
| 31 |
TEXT0_ADDR = 0x08020000 |
| 32 |
|
| 33 |
endif |
| 34 |
else |
| 35 |
|
| 36 |
# When not using Mboot (and so no ability to load text into QSPI) all the text goes |
| 37 |
# together at the start of internal flash, and the filesystem is in external flash. |
| 38 |
LD_FILES = boards/stm32f769.ld boards/common_basic.ld |
| 39 |
TEXT0_ADDR = 0x08000000 |
| 40 |
|
| 41 |
endif |
| 42 |
|
| 43 |
# MicroPython settings |
| 44 |
MICROPY_PY_LWIP = 1 |
| 45 |
MICROPY_PY_SSL = 1 |
| 46 |
MICROPY_SSL_MBEDTLS = 1 |
| 47 |
|
| 48 |
FROZEN_MANIFEST = $(BOARD_DIR)/manifest.py |