OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/boards/arm/nrf9160dk_nrf52840/Kconfig.defconfig

18 lines
333 B
Plaintext
Raw Normal View History

boards: arm: nrf52840_pca10090: rename board to nrf9160dk_nrf52840 We rename the nRF91 Dev Kit board target for the NRF52840 controller (nrf52840_pca10090) to nrf9160dk_nrf52840. We update all associated references in the supportive documentation and all nRF9160-related cofigurations and overlay files in the samples and tests in the tree. We also remove an un-referenced board image file that had erroneously been part of the documentation of this platform. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2020-03-27 21:52:36 +08:00
# nRF9160 DK NRF52840 board configuration
kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 20:45:29 +08:00
boards: arm: add nrf52840_pca10090 Add support for nrf52840_pca10090, i.e. the nRF52840 SoC on the pca10090 development kit. The SoC is tasked to route some of the nRF9160 pins to different components on the development kit. Additionally, it can be used as a Bluetooth HCI device. The routing options appear under "Board config" in Kconfig. Signed-off-by: Emanuele Di Santo <emdi@nordicsemi.no>
2019-01-25 01:22:58 +08:00
# Copyright (c) 2018 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0
boards: arm: nrf52840_pca10090: rename board to nrf9160dk_nrf52840 We rename the nRF91 Dev Kit board target for the NRF52840 controller (nrf52840_pca10090) to nrf9160dk_nrf52840. We update all associated references in the supportive documentation and all nRF9160-related cofigurations and overlay files in the samples and tests in the tree. We also remove an un-referenced board image file that had erroneously been part of the documentation of this platform. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2020-03-27 21:52:36 +08:00
if BOARD_NRF9160DK_NRF52840
boards: arm: add nrf52840_pca10090 Add support for nrf52840_pca10090, i.e. the nRF52840 SoC on the pca10090 development kit. The SoC is tasked to route some of the nRF9160 pins to different components on the development kit. Additionally, it can be used as a Bluetooth HCI device. The routing options appear under "Board config" in Kconfig. Signed-off-by: Emanuele Di Santo <emdi@nordicsemi.no>
2019-01-25 01:22:58 +08:00
config BOARD
boards: arm: nrf52840_pca10090: rename board to nrf9160dk_nrf52840 We rename the nRF91 Dev Kit board target for the NRF52840 controller (nrf52840_pca10090) to nrf9160dk_nrf52840. We update all associated references in the supportive documentation and all nRF9160-related cofigurations and overlay files in the samples and tests in the tree. We also remove an un-referenced board image file that had erroneously been part of the documentation of this platform. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2020-03-27 21:52:36 +08:00
default "nrf9160dk_nrf52840"
boards: arm: add nrf52840_pca10090 Add support for nrf52840_pca10090, i.e. the nRF52840 SoC on the pca10090 development kit. The SoC is tasked to route some of the nRF9160 pins to different components on the development kit. Additionally, it can be used as a Bluetooth HCI device. The routing options appear under "Board config" in Kconfig. Signed-off-by: Emanuele Di Santo <emdi@nordicsemi.no>
2019-01-25 01:22:58 +08:00
boards: arm: nrf: Make Bluetooth optional Instead of enabling Bluetooth by default on nRF5x boards, only enable the controller if Bluetooth has been enabled by the applicaiton. Fixes #5454 Fixes #12215 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2019-02-08 01:24:30 +08:00
config BT_CTLR
default BT
boards: nrf9160dk: Move board control configuration to devicetree Use devicetree instead of Kconfig to configure the board control switches in nRF9160 DK: - add binding for the switches that provide optional signal routings on this board - add binding for the GPIO interface that can be used for communication (e.g. UART based) between the nRF9160 and the nRF52840 on the DK, and add GPIO mapping for this interface so that its lines can be used without caring about of actual pin numbers on both sides - add binding for one GPIO line chosen from the above interface that is to allow the nRF9160 to reset the nRF52840 - update accordingly dts files and board specific code for both board definitions associated with the DK - introduce .dtsi files that can be included from dts overlays in order to facilitate the use of the above GPIO interface; modify the overlay in the hci_uart sample to provide an example of use of those files Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2021-01-26 17:36:35 +08:00
config BT_WAIT_NOP
default BT && $(dt_nodelabel_enabled,reset_input)
boards: arm: nrf52840_pca10090: rename board to nrf9160dk_nrf52840 We rename the nRF91 Dev Kit board target for the NRF52840 controller (nrf52840_pca10090) to nrf9160dk_nrf52840. We update all associated references in the supportive documentation and all nRF9160-related cofigurations and overlay files in the samples and tests in the tree. We also remove an un-referenced board image file that had erroneously been part of the documentation of this platform. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2020-03-27 21:52:36 +08:00
endif # BOARD_NRF9160DK_NRF52840