wolfBoot/config/examples/psoc_c3.config

52 lines
1.7 KiB
Plaintext

ARCH?=ARM
TARGET?=psoc_c3
SIGN?=ECC256
HASH?=SHA256
DEBUG?=0
VTOR?=1
CORTEX_M33?=1
TZEN?=0
NO_ASM?=0
NO_MPU=1
EXT_FLASH?=0
SPI_FLASH?=0
ALLOW_DOWNGRADE?=0
# Flags rewrite in place: write_row erases before programming and the HAL does
# a read-modify-write, so the two-sector write-once scheme is not needed.
NVM_FLASH_WRITEONCE?=0
# This family erases flash to 0x00, not 0xFF. Without the inverted polarity
# the state written by wolfBoot_update_trigger() is indistinguishable from
# erased flash and no update is ever taken.
FLAGS_INVERT?=1
WOLFBOOT_VERSION?=1
V?=0
SPMATH?=1
RAM_CODE?=1
DUALBANK_SWAP?=0
DEBUG_UART=1
# PSOC Control C3, 512 KB internal flash, 512-byte rows. Addresses are in the
# Secure CBUS alias, which is where code executes; the HAL translates to the
# Secure SBUS alias for the BootROM flash API.
#
# 0x12000000 - 0x1200FFFF wolfBoot (64 KB)
# 0x12010000 - 0x12026FFF BOOT (0x17000)
# 0x12027000 - 0x1203DFFF UPDATE (0x17000)
# 0x1203E000 - 0x1203E1FF SWAP (512 B)
# 0x12040000 - 0x1207FFFF free for the application
#
# The layout stays inside the low 256 KB because the debugger flash algorithms
# published for this family stop there, so an image staged above it cannot be
# provisioned. A 128 KB part uses 0xB000 partitions at 0x12008000 / 0x12013000
# / 0x1201E000.
#
# Board wiring is set by make options defaulted in arch.mk for the evaluation
# kit: PSOC_C3_UART_*, PSOC_C3_SPI_*, PSOC_C3_I2C_* and PSOC_C3_PCLK_HZ. See
# docs/Targets.md for the full table.
WOLFBOOT_SECTOR_SIZE?=0x200
WOLFBOOT_PARTITION_SIZE?=0x17000
WOLFBOOT_PARTITION_BOOT_ADDRESS?=0x12010000
WOLFBOOT_PARTITION_UPDATE_ADDRESS?=0x12027000
WOLFBOOT_PARTITION_SWAP_ADDRESS?=0x1203E000