nRF52832 Bluetooth peripheral_uart sample: use RX data and not sent to BLE

[BradEA]

I want to intercept some data in the RX (in section UART_RX_READY in uart_cb() as a command with arguments.  And I do not want this data to be sent on the the BLE.

After I get the data that I want, what should I do with the buf, so the process continues getting new data from the UART RX?

Do I just k_free(buf)?  Or something else?

[Karl Ylvisaker]

Hello,

You can input your specific checks for the commands in the handling of the UART_RX_BUF_RELEASED event.
If you omit the call to k_fifo_put(&fifo_uart_rx_data, buf); it will not be sent over BLE.
If you wish to discard the data afterwards you call k_free(buf) to free the buffer, correct.

Best regards,
Karl

[BradEA]

I moved by command handling code to the UART_RX_BUF_RELEASED section.  At the end I set buf->len = 0, so the buf will be freed, k_free(buf).  But something still seems to be around because I get the following when I switch back to "data mode" and connect to a tablet running nRF Connect:

RING:CONNECTED
[00:10:15.156,921] <inf> peripheral_uart: Connected 43:76:74:54:A2:83 (random)
[00:11:36.653,747] <wrn> bt_att: No ATT channel for MTU 39
[00:11:36.653,778] <wrn> bt_gatt: No buffer available to send notification
[00:11:36.653,869] <wrn> peripheral_uart: Failed to send data over BLE connection

[BradEA]

I went back and found that the above was due to not using the proper steps when I would be using command mode.

I propose to use the following steps:

1. Disconnect the BLE link
2. Change to Command Mode
3. send the commands to the radio uart
4. Change back to Data Mode
5. Connect to the BLE link