michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/boards/arm/96b_carbon_nrf51/Kconfig.defconfig

15 lines
263 B
Plaintext
Raw Permalink Normal View History

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 13:45:29 +01:00
# 96Boards Carbon nRF51 board default configuration
boards: 96b_carbon_nrf51: add support for 96Boards Carbon nRF51 chip This adds support for the nRF51 chip on the board. If you'd like to run Zephyr on the STM32F4 chip on Carbon, you need to use the 96b_carbon board instead. The current SPI Bluetooth protocol only uses 5 wires, so we use the remaining pin as UART TX. Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org> Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2016-09-23 15:13:13 +02:00
# Copyright (c) 2016, 2017 Linaro Limited.
# SPDX-License-Identifier: Apache-2.0
if BOARD_96B_CARBON_NRF51
config BOARD
boards: defconfig: Consistently quote string defaults In preparation for introducing a warning. Unquoted string defaults work through a quirk of Kconfig (undefined symbols get their name as their string value), but look confusing. It's done inconsistently now too. Suggested by Kumar Gala. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-05-25 20:56:38 +02:00
default "96b_carbon_nrf51"
boards: 96b_carbon_nrf51: add support for 96Boards Carbon nRF51 chip This adds support for the nRF51 chip on the board. If you'd like to run Zephyr on the STM32F4 chip on Carbon, you need to use the 96b_carbon board instead. The current SPI Bluetooth protocol only uses 5 wires, so we use the remaining pin as UART TX. Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org> Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2016-09-23 15:13:13 +02: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-07 18:24:30 +01:00
config BT_CTLR
default BT
boards: 96b_carbon_nrf51: add support for 96Boards Carbon nRF51 chip This adds support for the nRF51 chip on the board. If you'd like to run Zephyr on the STM32F4 chip on Carbon, you need to use the 96b_carbon board instead. The current SPI Bluetooth protocol only uses 5 wires, so we use the remaining pin as UART TX. Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org> Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2016-09-23 15:13:13 +02:00
endif # BOARD_96B_CARBON_NRF51
Copy permalink