BT NUS logging blocked

[iivanov]

In our development using NCS-2.6.1 it is desirable to have logs using BT NUS. 

"Serial Bluetooth Terminal" android application is used.

For testing purposes NCS\v3.0.2\nrf\samples\bluetooth\central_and_peripheral_hr been used with modification to support ble logging with next lines added to prj.conf

CONFIG_LOG_BACKEND_BLE=y
CONFIG_LOG=y
CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=2048
# Uncomment to use the maximum buffer size
CONFIG_BT_L2CAP_TX_MTU=600
CONFIG_BT_BUF_ACL_RX_SIZE=600
CONFIG_BT_NUS_LOG_LEVEL_DEFAULT=y

CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_BACKEND_UART=y

PCA10056 boards been used for testing with central_and_peripheral_hr and peripheral_hr.

Logs are blocked in case when phone app connected to firmware app implementing central and peripheral and peripheral device connects. Logs filled with "<wrn> bt_gatt: Device is not subscribed to characteristic." messages. Disconnecting peripheral does not recover logging.

Same happens if nRF Toolbox is used

Note that in case when firmware app implementing central and peripheral and peripheral device connected first and after that phone app connects then logging is OK.

[Ressa]

Hi Ivan,

Regarding the code example you have been using, is the prj.conf only thing you have modified? If you have other modifications can you share your source code? 

 Just to make sure we are on same ground, my understanding is that : you are using two PCA10056  boards programmed for "Central_Peripheral" and "Peripheral", and you want to receive the log information on mobile app and the board programmed with "Central_Peripheral" is going to act like a relay to pass the information to the mobile app. And when you first connect "Peripheral" board to "Central_Peripheral" board and then connect mobile app to "Central_Peripheral" board, you receive log information perfectly fine, but when you first connect mobile app to the board and then connect the other board, you are receiving log error?