Disconnection of the peripheral is done without enabling another connection, the only way is to reset the module.
It happens sometimes after 5 min up to 1-2 hours.
If there is an internal error due to data transfer, how can it recover without reset?
Disconnection of the peripheral is done without enabling another connection, the only way is to reset the module.
It happens sometimes after 5 min up to 1-2 hours.
If there is an internal error due to data transfer, how can it recover without reset?
Hi,
Could you print the disconnect reason?
In ble_evt_handler, you could do something like this:
case BLE_GAP_EVT_DISCONNECTED:
NRF_LOG_INFO("Disconnected reason: %d.",p_ble_evt->evt.gap_evt.params.disconnected.reason);
Also note that a reset indicates that you are running into the error handler, where the default behavior is to do a reset. You should then debug in order to find the reason for the reset. See this post about debugging: https://devzone.nordicsemi.com/f/nordic-q-a/10729/my-device-is-freezing-and-restarting
If you are using SES IDE, then make sure to use the Debug configuration and not the Release configuration.
Regards,
Marjeris
Hi,
Could you print the disconnect reason?
In ble_evt_handler, you could do something like this:
case BLE_GAP_EVT_DISCONNECTED:
NRF_LOG_INFO("Disconnected reason: %d.",p_ble_evt->evt.gap_evt.params.disconnected.reason);
Also note that a reset indicates that you are running into the error handler, where the default behavior is to do a reset. You should then debug in order to find the reason for the reset. See this post about debugging: https://devzone.nordicsemi.com/f/nordic-q-a/10729/my-device-is-freezing-and-restarting
If you are using SES IDE, then make sure to use the Debug configuration and not the Release configuration.
Regards,
Marjeris