8b02141ca7
Deprecate BT_CTLR, and add a new HAS_BT_CTLR as a virtual option which specific users (like BT_LL_SW_SPLIT) select. This also means that we can remove all places that were forcefully enabling the BT_CTLR option, and instead we now depend on devicetree to get some local LL HCI driver enabled which in turn also enables the HAS_BT_CTLR option. Signed-off-by: Johan Hedberg <johan.hedberg@silabs.com>
80 lines
2.8 KiB
Text
80 lines
2.8 KiB
Text
# nRF5340 DK nRF5340 board configuration
|
|
|
|
# Copyright (c) 2019-2020 Nordic Semiconductor ASA
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
if BOARD_NRF5340DK_NRF5340_CPUAPP || BOARD_NRF5340DK_NRF5340_CPUAPP_NS
|
|
|
|
# Code Partition:
|
|
#
|
|
# For the secure version of the board the firmware is linked at the beginning
|
|
# of the flash, or into the code-partition defined in DT if it is intended to
|
|
# be loaded by MCUboot. If the secure firmware is to be combined with a non-
|
|
# secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
|
|
# be restricted to the size of its code partition.
|
|
#
|
|
# For the non-secure version of the board, the firmware
|
|
# must be linked into the code-partition (non-secure) defined in DT, regardless.
|
|
# Apply this configuration below by setting the Kconfig symbols used by
|
|
# the linker according to the information extracted from DT partitions.
|
|
|
|
# SRAM Partition:
|
|
#
|
|
# If the secure firmware is to be combined with a non-secure image
|
|
# (TRUSTED_EXECUTION_SECURE=y), the secure FW image SRAM shall always
|
|
# be restricted to the secure image SRAM partition (sram-secure-partition).
|
|
# Otherwise (if TRUSTED_EXECUTION_SECURE is not set) the whole zephyr,sram
|
|
# may be used by the image.
|
|
#
|
|
# For the non-secure version of the board, the firmware image SRAM is
|
|
# always restricted to the allocated non-secure SRAM partition.
|
|
#
|
|
# Workaround for not being able to have commas in macro arguments
|
|
DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition
|
|
DT_CHOSEN_Z_SRAM_PARTITION := zephyr,sram-secure-partition
|
|
|
|
if BOARD_NRF5340DK_NRF5340_CPUAPP && TRUSTED_EXECUTION_SECURE
|
|
|
|
config FLASH_LOAD_SIZE
|
|
default $(dt_chosen_reg_size_hex,$(DT_CHOSEN_Z_CODE_PARTITION))
|
|
|
|
config SRAM_SIZE
|
|
default $(dt_chosen_reg_size_int,$(DT_CHOSEN_Z_SRAM_PARTITION),0,K)
|
|
|
|
endif # BOARD_NRF5340DK_NRF5340_CPUAPP && TRUSTED_EXECUTION_SECURE
|
|
|
|
if BOARD_NRF5340DK_NRF5340_CPUAPP
|
|
|
|
# BT relies on PSA Crypto API to perform crypto operations. On this platform
|
|
# this is implemented by Mbed TLS which requires a (possibly true) random
|
|
# number generator to initialize properly. We enable ENTROPY_GENERATOR here
|
|
# instead of manually adding it to all samples/tests configuration files because
|
|
# it looks more compact and easier to maintain.
|
|
config ENTROPY_GENERATOR
|
|
bool
|
|
default y if BT
|
|
|
|
endif # BOARD_NRF5340DK_NRF5340_CPUAPP
|
|
|
|
if BOARD_NRF5340DK_NRF5340_CPUAPP_NS
|
|
|
|
config FLASH_LOAD_OFFSET
|
|
default $(dt_chosen_reg_addr_hex,$(DT_CHOSEN_Z_CODE_PARTITION))
|
|
|
|
config FLASH_LOAD_SIZE
|
|
default $(dt_chosen_reg_size_hex,$(DT_CHOSEN_Z_CODE_PARTITION))
|
|
|
|
endif # BOARD_NRF5340DK_NRF5340_CPUAPP_NS
|
|
|
|
config BT_HCI_IPC
|
|
default y if BT
|
|
|
|
config HEAP_MEM_POOL_ADD_SIZE_BOARD
|
|
int
|
|
default 4096 if BT_HCI_IPC
|
|
|
|
endif # BOARD_NRF5340DK_NRF5340_CPUAPP || BOARD_NRF5340DK_NRF5340_CPUAPP_NS
|
|
|
|
if BOARD_NRF5340DK_NRF5340_CPUNET
|
|
|
|
endif # BOARD_NRF5340DK_NRF5340_CPUNET
|