f4350a9303
This adds initial support for the Laird Connectivity BL5340 development kit hardware Signed-off-by: Jamie McCrae <jamie.mccrae@lairdconnect.com>
114 lines
3 KiB
Text
114 lines
3 KiB
Text
# BL5340-DVK board configuration
|
|
|
|
# Copyright (c) 2019 - 2021 Nordic Semiconductor ASA
|
|
# Copyright (c) 2021 Laird Connectivity
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
config IPM_NRFX
|
|
default IPM
|
|
|
|
config RPMSG_SERVICE_DUAL_IPM_SUPPORT
|
|
default RPMSG_SERVICE
|
|
|
|
if RPMSG_SERVICE_DUAL_IPM_SUPPORT
|
|
|
|
config IPM_MSG_CH_0_ENABLE
|
|
default y
|
|
|
|
config IPM_MSG_CH_1_ENABLE
|
|
default y
|
|
|
|
config RPMSG_SERVICE_IPM_TX_NAME
|
|
default "IPM_0" if RPMSG_SERVICE_MODE_MASTER
|
|
default "IPM_1" if RPMSG_SERVICE_MODE_REMOTE
|
|
|
|
config RPMSG_SERVICE_IPM_RX_NAME
|
|
default "IPM_1" if RPMSG_SERVICE_MODE_MASTER
|
|
default "IPM_0" if RPMSG_SERVICE_MODE_REMOTE
|
|
|
|
config IPM_MSG_CH_0_TX
|
|
default RPMSG_SERVICE_MODE_MASTER
|
|
|
|
config IPM_MSG_CH_0_RX
|
|
default RPMSG_SERVICE_MODE_REMOTE
|
|
|
|
config IPM_MSG_CH_1_TX
|
|
default RPMSG_SERVICE_MODE_REMOTE
|
|
|
|
config IPM_MSG_CH_1_RX
|
|
default RPMSG_SERVICE_MODE_MASTER
|
|
|
|
endif # RPMSG_SERVICE_DUAL_IPM_SUPPORT
|
|
|
|
if BOARD_BL5340_DVK_CPUAPP || BOARD_BL5340_DVK_CPUAPPNS
|
|
|
|
config BOARD_ENABLE_DCDC_APP
|
|
bool "Enable Application MCU DCDC converter"
|
|
select SOC_DCDC_NRF53X_APP
|
|
default y
|
|
|
|
config BOARD_ENABLE_DCDC_NET
|
|
bool "Enable Network MCU DCDC converter"
|
|
select SOC_DCDC_NRF53X_NET
|
|
default y
|
|
|
|
config BOARD_ENABLE_DCDC_HV
|
|
bool "Enable High Voltage DCDC converter"
|
|
select SOC_DCDC_NRF53X_HV
|
|
default y
|
|
|
|
choice BT_HCI_BUS_TYPE
|
|
default BT_RPMSG if BT
|
|
endchoice
|
|
|
|
config HEAP_MEM_POOL_SIZE
|
|
default 4096 if BT_RPMSG
|
|
|
|
config BT_HCI_VS
|
|
default y if BT
|
|
|
|
config BOARD_ENABLE_CPUNET
|
|
bool "Enable nRF53 Network MCU"
|
|
help
|
|
This option enables releasing the Network 'force off' signal, which
|
|
as a consequence will power up the Network MCU during system boot.
|
|
Additionally, the option allocates GPIO pins that will be used by UARTE
|
|
of the Network MCU.
|
|
Note: GPIO pin allocation can only be configured by the secure Application
|
|
MCU firmware, so when this option is used with the non-secure version of
|
|
the board, the application needs to take into consideration, that the
|
|
secure firmware image must already have configured GPIO allocation for the
|
|
Network MCU.
|
|
default y if (BT || NRF_802154_SER_HOST)
|
|
|
|
config DOMAIN_CPUNET_BOARD
|
|
string
|
|
default "bl5340_dvk_cpunet" if BOARD_BL5340_DVK_CPUAPP || BOARD_BL5340_DVK_CPUAPPNS
|
|
depends on BOARD_ENABLE_CPUNET
|
|
help
|
|
The board which will be used for CPUNET domain when creating a multi
|
|
image application where one or more images should be located on
|
|
another board. For example hci_rpmsg on the bl5340_dvk_cpunet for
|
|
Bluetooth applications.
|
|
|
|
endif # BOARD_BL5340_DVK_CPUAPP || BOARD_BL5340_DVK_CPUAPPNS
|
|
|
|
if BOARD_BL5340_DVK_CPUNET
|
|
|
|
# BT_CTLR depends on BT. When BT is enabled we should default to also
|
|
# enabling the controller.
|
|
config BT_CTLR
|
|
default y if BT
|
|
|
|
config BT_ECC
|
|
default y if BT
|
|
|
|
config DOMAIN_CPUAPP_BOARD
|
|
string
|
|
default "bl5340_dvk_cpuapp" if BOARD_BL5340_DVK_CPUNET
|
|
help
|
|
The board which will be used for CPUAPP domain when creating a multi
|
|
image application where one or more images should be located on
|
|
another board.
|
|
|
|
endif # BOARD_BL5340_DVK_CPUNET
|