How to delete the bond info when connected with 51822

RE: How to delete the bond info when connected with 51822

jimlin — Fri, 28 Mar 2014 07:44:42 GMT

Hi Morten,

What you said is correct.
I can't find what the proper conn_handle is from the SDK document. Could you show me what value is correct?

RE: How to delete the bond info when connected with 51822

Ole Morten — Wed, 19 Mar 2014 11:19:31 GMT

I didn't notice at first, but it's illegal to pass BLE_CONN_HANDLE_INVALID to sd_ble_gap_disconnect(). You'll most likely get a 0x3001 error code back; BLE_ERROR_INVALID_CONN_HANDLE. I therefore suspect that the HardFault you see in fact doesn't come from the disconnect call itself, but from the app_error_handler. Please try passing a proper conn_handle to the disconnect function, and try fixing your error handler.

RE: How to delete the bond info when connected with 51822

jimlin — Wed, 19 Mar 2014 08:35:20 GMT

I set the timer interrupt as P3 which is the lowest priority, and call the BLE_GAP_DISCONNECT() when interrupt occured. But it still got the HardFault???

RE: How to delete the bond info when connected with 51822

jimlin — Mon, 17 Mar 2014 15:25:43 GMT

OK I will check the priority to validate it .

Thanks.

RE: How to delete the bond info when connected with 51822

Ole Morten — Mon, 17 Mar 2014 15:15:23 GMT

If you get a HardFault, I suspect what you see is this: https://devzone.nordicsemi.com/index.php/how-to-redefine-ppi-tasks-inside-a-timer-interrupt

Bottom line is that you can't call softdevice API functions from APP_HIGH interrupts, so you can for example use the scheduler to transfer the event to the main loop.

RE: How to delete the bond info when connected with 51822

jimlin — Mon, 17 Mar 2014 15:00:03 GMT

Hi Morten,

Thanks for your answer.

I prefer to use the second way for the ram would be cleaned while reset.

But, when call the sd_ble_gap_disconnect() as follow, it still got the HardFault by simulating.

[i] if(bind_info_clear == true) { BLE_GAP_DISCONNECT(); }[/i]

and BLE_GAP_DISCONNECT() define as:

[i]#define BLE_GAP_DISCONNECT()
do
{
uint32_t err_code;
uint16_t m_conn_handle = BLE_CONN_HANDLE_INVALID;
err_code = sd_ble_gap_disconnect(m_conn_handle,
BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
APP_ERROR_CHECK(err_code);
}while(0)[/i]

Is there anything wrong?

RE: How to delete the bond info when connected with 51822

Ole Morten — Mon, 17 Mar 2014 10:34:26 GMT

The easiest way to do this is actually to just do a reset after 3 s, check the button on power up and if it's pressed, go into limited advertising mode, potentially first erasing old bond information (the latter may not be needed, as the nRF51822 is capable of having multiple bonds, but if you do, you'll have to make sure to handle the situation with full bond storage properly).

If you don't want to reset for whatever reason, you don't really have to disable the softdevice; you can just call sd_ble_gap_disconnect() and then restart advertising with whatever parameters you want when you get the BLE_GAP_EVT_DISCONNECTED event.