Implement Static Passkey with SDK12.2.0

RE: Implement Static Passkey with SDK12.2.0

Hung Bui — Fri, 26 May 2017 07:43:20 GMT

Hi longycy,

I tried here with nRFMasterControl panel but don't see the same issue. When I turned off MITM ( turn off keyboard&display security option) to bond and then turn it on again after that, I simply have the passkey asking pop up and can continue normally. Here is the screenshot:

Please make sure you deleted bond information on the RN4020 after the first trial.

Do you have any Nordic board that you can use to test with nRFMaster Control Panel ?

If possible, please record a sniffer trace when you test with RN4020. It can reveal why we have different result when testing with nRFMasterControlPanel vs RN4020.

Also, please try to test with SDK v13.

RE: Implement Static Passkey with SDK12.2.0

longycy — Thu, 25 May 2017 08:05:42 GMT

.You can use another BLE module(eg.RN4020) to do a test if possible. The expeiment can be described like this:

Configure RN4020 without MITM. Then try to connect and bond it. You will be rejected as no MITM protection.
Configure RN4020 with MIMT. Then you try to connect it again. And you may find "Connected to a previously bonded device" in UART log.

Best Regards

RE: Implement Static Passkey with SDK12.2.0

Hung Bui — Wed, 24 May 2017 10:29:32 GMT

That means there is no bonded id in the database, I don't know how with that you would get "Connected to a previously bonded device." ?

RE: Implement Static Passkey with SDK12.2.0

longycy — Wed, 24 May 2017 08:33:39 GMT

Hi Hung Bui, I add break point in im_ble_evt_handler() in id_manager.c, the result is that: focus on code below:

       case BLE_GAP_ADDR_TYPE_RANDOM_STATIC:
        {
            while (pds_peer_data_iterate(PM_PEER_DATA_ID_BONDING, &peer_id, &peer_data))
            {
                if (addr_compare(&gap_evt.params.connected.peer_addr,
                                 &peer_data.p_bonding_data->peer_ble_id.id_addr_info))
                {
                    bonded_matching_peer_id = peer_id;
                    break;
                }
            }
        }
        break;

I add break point in "while(..)" and "if(add_compare(..))", "while(..)" can be excuted but "if(add_compare())" has never been excuted. Because logic in "while(..)" is false.

I don not know why it happens. Thanks a lot!

Best Regards

RE: Implement Static Passkey with SDK12.2.0

Hung Bui — Fri, 19 May 2017 09:24:38 GMT

Hi Longycy,

I suspect the bond deleting was not executed properly. Note that deleting doesn't happen at the same time when you see the debug text. It happens after that when the softdevice schedule the flash operation.

I suspect that the program crashed right after that and reset. Please set optimization level to 0 and add DEBUG into C/C++ preprocessor symbols and add a break point inside app_error_handler() in app_error.c to check if there is any assertion.

Also make sure you do a full erase of flash before you try to test.

You can also add a break point inside im_ble_evt_handler() in id_manager.c to check if the address matched is actually correct or not.

Also please send me the full UART log you have when testing.

RE: Implement Static Passkey with SDK12.2.0

longycy — Fri, 19 May 2017 01:45:09 GMT

Hi Hung Bui,

I use Microchip RN4020 (Core 4.1) as central to test nRF52832. Following your advice, I tried again to debug gls example. The conclusion can be described as below:

Firstly, I configure RN4020 without MITM. When connecting, I find UART print "Collector did not use MITM, disconnecting" and "Collector's bond deleted". That is right and it proves bond information has been erased.

Secondly, I re-configure RN4020 with MIMT.At this time, UART print "Connected to a previously bonded device." and then "connected". This is very strange as bond information has been erased before.

So why? I guess maybe bond information has not been erased correctly even though "pm_peer_delete(m_peer_to_be_deleted);" is excuted and return SUCCESS. Whether function "pm_peer_delete(...)" can be excuted correctly or not?

Thank you very much!

Best Regards

RE: Implement Static Passkey with SDK12.2.0

Hung Bui — Thu, 18 May 2017 11:44:52 GMT

Which was the another BLE module you tested ?

If you were testing with gls, you can find that if the connection was not paired with MITM we will disconnect and set m_peer_to_be_deleted to the current peer in PM_EVT_CONN_SEC_SUCCEEDED in pm_evt_handler().

When we actually disconnect in BLE_GAP_EVT_DISCONNECTED event in on_ble_evt() we will erase bond information.

Please try to debug and check the behavior. Check if m_peer_to_be_deleted set to anything and then if pm_peer_delete(m_peer_to_be_deleted) is called or not and returns success or not.

RE: Implement Static Passkey with SDK12.2.0

longycy — Wed, 17 May 2017 09:45:32 GMT

Hi Hung Bui,

Thank you for your example "ble_app_gls". I have tried this example and it works when using nRFConnect. But when I tried another BLE module, I found a question: In the code if peer did not use MITM, the function pm_peer_id_get(...) will be called to get the bonded peer as BLE Stack has its bond information. Then bond information will be erased when disconnected. Actually, in my test pm_peer_id_get(...) get NULL, because "NRF_LOG_DEBUG("Collector's bond deleted\r\n");" is not printed in UART Tool. So "m_peer_to_be_deleted == PM_PEER_ID_INVALID". Why it cannot get peer id by using "pm_peer_id_get(m_conn_handle, &m_peer_to_be_deleted)" ? Could you please help me to confirm this? Thank you very much!

Best Regards

RE: Implement Static Passkey with SDK12.2.0

Hung Bui — Tue, 16 May 2017 11:07:27 GMT

Hi Longycy,

Could you capture a sniffer trace ?

If you simply test with the ble_app_gls example would you manage to bond and access the service ? (it's not static passkey, but we should start there)

Also please try to use nRFConnect app to test instead of Light Blue.