BLE_GAP_SEC_STATUS_CONFIRM_VALUE how menage

[annapalu]

Hi all,

sometimes this events occurs on my code. My start point was the glucose app, to implemented a "just work" pairing and bonding. When this event occurs a disconnect event it's called for the design that we have. I would understand why this event happens, to understand if this design it's correct or not.

someone can help me, what is the best way to implement the JUST Work bonding?

Thanks, -Anna

[annapalu]

Hi Petter, sorry the question is different.

Sometimes occurs the event BLE_GAP_SEC_STATUS_CONFIRM_VALUE, and the bonding failed. because when it occurs, the function

static void auth_status_process(ble_gap_evt_t * p_gap_evt)
{
    switch (p_gap_evt->params.auth_status.auth_status)
    {
        case BLE_GAP_SEC_STATUS_SUCCESS:
            auth_status_success_process(p_gap_evt);
            break;

        default:
            auth_status_failure_process(p_gap_evt);
            break;
    }
}

that menages it as a failure and so i can't bonding and device.

How, can i menage this to allow again the bonding

Regards, -Anna