NRF52 Restarts from Main() Instantly on Connect when using CCC Characteristic Notification (Intermittent)

RE: NRF52 Restarts from Main() Instantly on Connect when using CCC Characteristic Notification (Intermittent)

veletron — Mon, 24 Sep 2018 14:21:12 GMT

Thanks for that. I think some it it was down to the way I had ordered the calls vs yourself, but my main issue was my removal of the code for case: BLE_CUS_EVT_NOTIFICATION_ENABLED without removing the APP_ERROR_CHECK!!

No default value was set for the variable err_code , it usually ended up with a zero and hence it worked (NRF_SUCCESS = 0), but if it had another value from a previous use of the memory then it failed - hence my random connect fail issue. So like I said - my code did not change, but due to my failing to specify an initial value for err_code, the underlying value for that variable did change.

I shall get into the habit of initialising err_code with NRF_SUCCESS like the code in bsp.c / etc does.

Thanks again

Nigel

RE: NRF52 Restarts from Main() Instantly on Connect when using CCC Characteristic Notification (Intermittent)

AndreasF — Mon, 24 Sep 2018 12:03:57 GMT

Hi.

I'm not sure what could be wrong, as I don't have access to your code. I've therefore attached my project when I did this example.

Perhaps you could compare what I've done to what you have done?

Download here: devzone.nordicsemi.com/.../custom_5F00_ble_5F00_service.zip

- Andreas

RE: NRF52 Restarts from Main() Instantly on Connect when using CCC Characteristic Notification (Intermittent)

veletron — Thu, 20 Sep 2018 15:51:03 GMT

This appears to be related to the commented out code from the example which goes off on the connect event.

static void on_connect(ble_cus_t * p_cus, ble_evt_t const * p_ble_evt)

{

    p_cus->conn_handle = p_ble_evt->evt.gap_evt.conn_handle;

    /*ble_cus_evt_t evt;

    evt.evt_type = BLE_CUS_EVT_CONNECTED;

    p_cus->evt_handler(p_cus, &evt);*/

}

God knows why it sometimes works and sometimes doesn't, but removing it fixes the example.