OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/bluetooth/hci_spi/prj.conf

12 lines
241 B
Plaintext
Raw Normal View History

samples: Bluetooth: add HCI SPI raw handler sample Add a sample application that allows a Zephyr-based Bluetooth controller to interface with an HCI driver via SPI. This sample implements the same BT SPI protocol already as Zephyr's HCI SPI driver. Currently, the sample only supports the legacy SPI API. Provide a single configuration file, avoiding board-specific files. Some board-specific configuration information must be provided via other means: - CONFIG_BT_CONTROLLER_TO_HOST_SPI_DEV_NAME - CONFIG_BT_CONTROLLER_TO_HOST_SPI_IRQ_DEV_NAME - CONFIG_BT_CONTROLLER_TO_HOST_SPI_IRQ_PIN Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org> Signed-off-by: Michael Scott <michael.scott@linaro.org>
2016-09-20 18:44:16 +08:00
CONFIG_GPIO=y
CONFIG_SPI=y
samples: bluetooth: Fix hci_spi sample This commit fixes the following issues introduced when switching to the new SPI API in commit e7de85b5343f2ed118a5c4a043ab7bbae9eec608: - the SPI slave operating mode (and support for it) was not properly selected (the setting was missing in the sample probably because the old nRF SPI slave driver used in this sample was not checking the requested mode at all) - the `txmsg` buffer filled with 0xFF values in the `bt_tx_thread` function was improperly used afterwards in `spi_send` to transmit the slave header frame - the common structures defining buffers for SPI transactions (`tx` and `rx`) were modified in `spi_send` before the corresponding semaphore was taken, resulting in data corruption Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2019-01-31 18:09:42 +08:00
CONFIG_SPI_SLAVE=y
samples: Bluetooth: add HCI SPI raw handler sample Add a sample application that allows a Zephyr-based Bluetooth controller to interface with an HCI driver via SPI. This sample implements the same BT SPI protocol already as Zephyr's HCI SPI driver. Currently, the sample only supports the legacy SPI API. Provide a single configuration file, avoiding board-specific files. Some board-specific configuration information must be provided via other means: - CONFIG_BT_CONTROLLER_TO_HOST_SPI_DEV_NAME - CONFIG_BT_CONTROLLER_TO_HOST_SPI_IRQ_DEV_NAME - CONFIG_BT_CONTROLLER_TO_HOST_SPI_IRQ_PIN Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org> Signed-off-by: Michael Scott <michael.scott@linaro.org>
2016-09-20 18:44:16 +08:00
CONFIG_MAIN_STACK_SIZE=512
CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_MAX_CONN=20
CONFIG_BT_TINYCRYPT_ECC=n
Bluetooth: Refactor bluetooth buffer configuration for simplification Refactor and simplify the bluetooth buffer configurations to improve the easy of configurations and eliminate invalid ones. By moving configurations out of host and controller specific configurations and into a common one it becomes easier to configure the host and controller separately as the same configurations can be used as would be for a combined build. All HCI configurations are now given exluding the matching HCI header, which eases the configuration as the application don't have to know the different header sizes. The BT_RX_BUF_LEN is split into ACL and Event, as well as the suprising use of Command size. BT_L2CAP_RX_MTU is removed as the stack does not support reassembling of HCI ACL data to larger L2CAP PDUs. The application will have to set ACL RX size and account for the L2CAP PDU header itself. BT_EATT_RX_MTU was removed as it is only used for setting a different default value for another option which leads to the stuck kconfig symbol problem. The configurations can be updated according to the table below: ** New configuration | ** Old configuration All configurations BT_BUF_ACL_RX_SIZE | BT_L2CAP_RX_MTU + 4 BT_BUF_ACL_RX_SIZE | BT_RX_BUF_LEN - 4 BT_BUF_EVT_RX_SIZE | BT_RX_BUF_LEN - 2 BT_BUF_CMD_TX_SIZE | BT_RX_BUF_LEN - 3 BT_BUF_CMD_TX_COUNT | BT_HCI_CMD_COUNT BT_BUF_EVT_RX_COUNT | BT_RX_BUF_COUNT BT_BUF_ACL_RX_COUNT | BT_RX_BUF_COUNT BT_BUF_ACL_RX_COUNT | BT_ACL_RX_COUNT BT_BUF_EVT_DISCARDABLE_SIZE | BT_DISCARDABLE_BUF_SIZE - 2 BT_BUF_EVT_DISCARDABLE_COUNT | BT_DISCARDABLE_BUF_COUNT Controller-build BT_BUF_ACL_TX_SIZE | BT_CTLR_TX_BUFFERS_SIZE BT_BUF_ACL_TX_COUNT | BT_CTLR_TX_BUFFER HCI-bridge BT_BUF_ACL_TX_SIZE | BT_HCI_ACL_DATA_SIZE BT_BUF_ACL_TX_COUNT | 6 Fixed invalid configurations setting either BT_L2CAP_RX_MTU or BT_CTLR_DATA_LENGTH_MAX larger than BT_RX_BUF_LEN could lead to buffer overruns. Fix advertising report max data length calculation. This always used the BT_DISCARDABLE_BUF_SIZE macro but this feature can be turned off and advertising reports will be allocated from the RX buffer in that case. Also controller-build does not have this buffer (in hci_raw.c). Also the wrong HCI header was used in the calculation, HCI event header should have been used instead of HCI ACL header. Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2021-04-27 16:38:23 +08:00
CONFIG_BT_BUF_ACL_RX_COUNT=10
CONFIG_BT_BUF_ACL_RX_SIZE=251
samples: hci_spi: Add net_buf headroom for hci_spi We need 1 byte of headroom for the SPI HCI protocol. This is not added automatically on the slave side of the SPI connection. Signed-off-by: Jan Müller <jan.mueller@nordicsemi.no>
2021-04-19 15:45:34 +08:00
CONFIG_BT_HCI_RAW_RESERVE=1