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/nrf52_pca10040/nrf52_pca10040_defconfig

24 lines
370 B
Plaintext
Raw Normal View History

boards: Add support for the nRF52 DK board (PCA10040) Add board support for the Nordic Semiconductor's nRF52832 (nRF52 series) Development Kit. JIRA: ZEP-377 Change-Id: I6d8f1f7ec1b8a068193f6ba67c8a1ab9f399f80b Signed-off-by: Glenn Ruben Bakke <glenn.ruben.bakke@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Håkon Alseth <haakon.alseth@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-05-18 22:53:48 +08:00
CONFIG_ARM=y
CONFIG_SOC_FAMILY_NRF5=y
CONFIG_SOC_SERIES_NRF52X=y
arm: nrf52: Introduce NRF52 SoC Specific config options Introduce SoC specific config options similar to what exists on NRF51, this is mostly to help distinguish between SRAM & Flash sizes on different variants. Also deleted some unnecessary setting of CONFIG_SOC_NRF528{32,40} in the board defconfig files. Change-Id: I3aaedf0c15423ae12636f87b8e6a39070cbb2c6f Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-04-12 00:24:45 +08:00
CONFIG_SOC_NRF52832_QFAA=y
boards: clean default configs for 96b_nitrogen and nrf52_pca10040 Removing options that are already set by the soc Kconfig files. Change-Id: I603c7797a26e3afedfa5ee72fe989c614c080fe5 Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org>
2016-10-25 21:06:28 +08:00
CONFIG_BOARD_NRF52_PCA10040=y
boards: Add support for the nRF52 DK board (PCA10040) Add board support for the Nordic Semiconductor's nRF52832 (nRF52 series) Development Kit. JIRA: ZEP-377 Change-Id: I6d8f1f7ec1b8a068193f6ba67c8a1ab9f399f80b Signed-off-by: Glenn Ruben Bakke <glenn.ruben.bakke@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Håkon Alseth <haakon.alseth@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-05-18 22:53:48 +08:00
arm: soc: nordic nRF52: Add MPU support We now have generic ARM M4 MPU support added to Zephyr. Let's enable it for use with Nordic nRF52 chips. Memory Layout was generated from Section 8.3 "Memory Map" of nRF52 Product Specifications (for both nRF52832 and nRF52840): 0x00000000: Flash 0x10000000: Factory Information Config Registers 0x10001000: User Information Config Registers 0x20000000: SRAM 0x40000000: APB Peripherals 0x50000000: AHB Peripherals 0xE0000000: ARM M4 Private Peripheral Registers NOT Configured: 0x60000000: External RAM 0x80000000: External RAM 0xA0000000: External Device 0xC0000000: External Device NOTE: More work will be needed for future Nordic MWU (Memory Watching Unit) support. Signed-off-by: Michael Scott <michael.scott@linaro.org>
2017-05-05 12:32:48 +08:00
# Enable MPU
CONFIG_ARM_MPU_NRF52X=y
boards: Add support for the nRF52 DK board (PCA10040) Add board support for the Nordic Semiconductor's nRF52832 (nRF52 series) Development Kit. JIRA: ZEP-377 Change-Id: I6d8f1f7ec1b8a068193f6ba67c8a1ab9f399f80b Signed-off-by: Glenn Ruben Bakke <glenn.ruben.bakke@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Håkon Alseth <haakon.alseth@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-05-18 22:53:48 +08:00
# enable uart driver
CONFIG_SERIAL=y
CONFIG_UART_NRF5=y
# enable console
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
# additional board options
CONFIG_GPIO_AS_PINRESET=y
board: nrf52_pca10040: Include BLE controller by default Enable the new BLE controller by default in Nordic's nRF52 DK (Development Kit) board. Jira: ZEP-702 Origin: Original Change-Id: I578d582536186e326c81f9274faa2c0f1ae851ff Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 19:34:35 +08:00
# bluetooth
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_BT=y
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 19:45:13 +08:00
CONFIG_BT_CTLR=y