The BLE firmware gets stuck when BLE signal crashes.

[Meetali Patel]

Hello Support Team,

I am using an nrf52832 module in our project. During testing, we have observed that the BLE firmware gets stuck and it stops advertising further when we crash the BLE signals by keeping the device in an RF chamber.

We tried to debug using the JLink and enabling the logs. We observed that it goes to NRF_ERROR_INVALID_DATA or NRF_ERROR_RESOURCES state. Can you please guide us on how to handle this issue.

Thanks & Regards

Meetali Patel

[Jørgen Holmefjord]

Hi,

Which SDK version and example are your application based on? Which function call returned the NRF_ERROR_INVALID_DATA and NRF_ERROR_RESOURCES error codes?

The API documentation in our infocenter will normally tell you the reason for the error codes. Search up the name of the function that returns the error and check if there are any suggestions.

Best regards,
Jørgen

[Meetali Patel]

Hi Jorgen,

The function ble_nus_data_send() returns the error code NRF_ERROR_INVALID_DATA and NRF_ERROR_RESOURCES. It has also been observed that sometimes the application simply gets stuck and no further logs are seen. We are using SDK v15.0.0.

Thanks & Regards

Meetali Patel

[Jørgen Holmefjord]

NRF_ERROR_RESOURCES is returned by the call to sd_ble_gatts_hvx() in the end of ble_nus_data_send(). The reason for this error is described in the API documentation:

"The number of Handle Value Notifications that can be queued is configured by ble_gatts_conn_cfg_t::hvn_tx_queue_size When the queue is full, the function call will return NRF_ERROR_RESOURCES. A BLE_GATTS_EVT_HVN_TX_COMPLETE event will be issued as soon as the transmission of the notification is complete."

I cannot see NRF_ERROR_INVALID_DATA being a valid error code from this function call. Are you sure this is the error you are receiving? 

[Meetali Patel]

Hi Jorgen, 

The error code is NRF_ERROR_INVALID_STATE. Sorry for the mistake. 

[Meetali Patel]

Hi Jorgen,

I enabled the DEBUG flags and observed that the APP_UART_COMMUNICATION_ERROR event is received. Can you please help in letting me know how can I handle this.