wolfBoot/config/examples/stm32c5-dualbank.config

41 lines
1.2 KiB
Plaintext

ARCH?=ARM
TZEN?=0
TARGET?=stm32c5
SIGN?=ECC256
HASH?=SHA256
DEBUG?=0
VTOR?=1
CORTEX_M0?=0
CORTEX_M33?=1
NO_ASM?=0
NO_MPU=1
EXT_FLASH?=0
SPI_FLASH?=0
ALLOW_DOWNGRADE?=0
NVM_FLASH_WRITEONCE?=1
WOLFBOOT_VERSION?=1
V?=0
SPMATH?=1
RAM_CODE?=1
DUALBANK_SWAP?=1
# Dual-bank swap layout (2x512KB, 8KB pages, 1MB total). BOOT and
# UPDATE sit at the same offset within their respective banks so that
# WOLFBOOT_PARTITION_BOOT_ADDRESS = 0x08010000 stays valid before and
# after FLASH_OPTCR.SWAP_BANK toggles which physical bank is mapped
# to 0x08000000. fork_bootloader() in hal_init keeps a copy of
# wolfBoot at the start of bank 2 so the chip boots from either bank.
# Bank 1 (active by default):
# 0x08000000 wolfBoot (64 KB)
# 0x08010000 BOOT partition (448 KB)
# Bank 2 (active after SWAP_BANK toggle):
# 0x08080000 wolfBoot copy (64 KB)
# 0x08090000 UPDATE partition (448 KB)
WOLFBOOT_SECTOR_SIZE?=0x2000
WOLFBOOT_PARTITION_SIZE?=0x70000
WOLFBOOT_PARTITION_BOOT_ADDRESS?=0x08010000
WOLFBOOT_PARTITION_UPDATE_ADDRESS?=0x08090000
WOLFBOOT_PARTITION_SWAP_ADDRESS?=0xFFFFFFFF
FLAGS_HOME=0
DISABLE_BACKUP=0
DEBUG_UART=1