pm_conn_sec_status_get bug?

[Stayhungry]

phenomenon:

When master successfully encrypts using previous binding information, pm_evt_handler in main.c receives a PM_EVT_CONN_SEC_SUCCEEDED event and gets a bonded state of 0 using pm_conn_sec_status_get.

My point is:

After the master has successfully encrypted using the previous binding information, the slave should also be in the bonded state. By looking at peer_manager.c, since the above process is considered PM_LINK_SECURED_PROCEDURE_ENCRYPTION, the bonded flag is not set in pm_sm_evt_handler

Is it my understanding wrong? If I did not understand it, how to fix it?

[Petter Myhre]

I haven't tested, but you do get PM_EVT_BONDED_PEER_CONNECTED right? It seems the bonded flag is set there? ble_conn_state_user_flag_set(p_im_evt->conn_handle, m_bonded_flag_id, true);

[Øyvind Rønningstad]

Which SDK version are you using?

[Stayhungry]

Hi,petter. Yes,i get PM_EVT_BONDED_PEER_CONNECTED.

Hi,Øyvind Rønningstad SDK14.1

[Øyvind Rønningstad]

@Stayhungry: Yes, it looks like a bug in pm_sm_evt_handler().

Try changing

ble_conn_state_user_flag_set(p_sm_evt->conn_handle, m_bonded_flag_id, bonded);

to

if (bonded)
{
    ble_conn_state_user_flag_set(p_sm_evt->conn_handle, m_bonded_flag_id, bonded);
}

[Stayhungry]

Hi,Øyvind Rønningstad.

Why do you want to change this way?Could you tell me ?I'm a little confused.

using the previous binding information, is still consider as PM_LINK_SECURED_PROCEDURE_ENCRYPTION, the result should be the same, boneded = 0?