zephyr

History

Victor Chavez bee43bd972 logging: Fixed BLE backend buffer size independent of MTU The BLE backend has a bug that when the MTU size is less than the buffer the notification always fails and does not allow to flush the buffer. This fix checks for the MTU size of the current connection and adjusts it. In addition, the buffer size is no longer settable by the user and depends on the transmission size of MTU set with CONFIG_BT_L2CAP_TX_MTU. Signed-off-by: Victor Chavez <chavez-bermudez@fh-aachen.de>		2023-06-19 08:38:08 +02:00
..
src
CMakeLists.txt
prj.conf	logging: Fixed BLE backend buffer size independent of MTU	2023-06-19 08:38:08 +02:00
README.rst	logging: Fixed BLE backend buffer size independent of MTU	2023-06-19 08:38:08 +02:00
sample.yaml	samples, tests: convert string-based twister lists to YAML lists	2023-05-10 09:52:37 +02:00

README.rst

.. _logger_ble_backend:

Logging: BLE Backend
########################

Overview
********

Sample that demonstrates how to setup and use the BLE Logging backend. The
BLE Logger uses the NRF Connect SDK NUS service as UUID to make it compatible
with already existing apps to debug BLE connections over UART.

The notification size of the ble backend buffer is dependent on the
transmission size of the mtu set with `CONFIG_BT_L2CAP_TX_MTU`. Be sure
to change this configuration to increase the logger throughput over BLE.

Requirements
************

* A board with BLE support

Building and Running
********************

This sample can be found under :zephyr_file:`samples/subsys/logging/ble_backend` in the
Zephyr tree.

The BLE logger can be tested with the NRF Toolbox app or any similar app that can connect over
BLE and detect the NRF NUS UUID service.