Pairing/bonding with ble_app_template example not working for me

RE: Pairing/bonding with ble_app_template example not working for me

EggplantSystems — Fri, 26 Oct 2018 23:23:50 GMT

I had a similar problem with the ble_app_bms example.

My first pairing (with my smartphone) worked. After unpairing and trying to reconnect, I would get PM_EVT_ERROR_UNEXPECTED.

In another answer, Hung Bui advised setting allow_repairing = true in the call to pm_conn_sec_config_reply(). That fixed it for me.

RE: Pairing/bonding with ble_app_template example not working for me

Matej — Fri, 27 Jan 2017 14:44:34 GMT

Hi, unfortunately no. I didn't have that much time although. After not being able to make it work with the template from github I decided to follow the tutorial for Segger Studio from this page. But I get two leds that are always on and not one blinking like it would be if device was advertising. I don't know exactly why that would be as the precompiled hex file that comes with the SDK works. Is there something that you have to set up in the environment for specific board or no? The github project has a file for ble400 pins but I don't know how would the precompiled hex file then work out of the box.

RE: Pairing/bonding with ble_app_template example not working for me

Petter Myhre — Thu, 26 Jan 2017 09:45:13 GMT

Have you solved the issue? If not, what memory setting are you using? Have you been able to do a sniffer trace?

RE: Pairing/bonding with ble_app_template example not working for me

Matej — Thu, 19 Jan 2017 12:36:08 GMT

I managed to enable the logs and I got NRF_ERROR_INTERNAL I also tracked the PM_EVT_ERROR_UNEXPECTED and it gets called by SM_EVT_ERROR_UNEXPECTED on line 300 in peer_manager.c

I will look at the tutorials maybe I will find something useful. To set up the project I just opened the GitHub project that I mentioned before. That worked out of the box. Then I imported the project from examples to SEGGER Studio and changed the .emProject file to resemble the file from GitHub project. I think that I might have missed out some detail in that process that may have caused this behavior.

RE: Pairing/bonding with ble_app_template example not working for me

Hung Bui — Wed, 18 Jan 2017 11:29:20 GMT

The error value is in p_evt->params.error_unexpected.error, you can use SEGGER_RTT_printf to print out.

There are only 3 place where PM_EVT_ERROR_UNEXPECTED is assigned inside peer_manager, you can track them down.

I assume you have followed the tutorial here (a bit out of date) and here ?

Also make sure you erase the chip completely when you test. There could be that earlier data stored can cause an issue when bonding is stored.

You can try to capture a sniffer trace to see what happens over the air.

RE: Pairing/bonding with ble_app_template example not working for me

Matej — Tue, 17 Jan 2017 17:18:51 GMT

Hmm ... the precompiled hex works. Could there be something in the project settings that might interfeere? I used the SEGGER Studio template: github.com/.../nrf51822_s130_ble_app_uart from here but it is somewhat outdated so I changed the .emProject file a bit to make it work. I just added some preprocessor paths.

How can I display the error code of PM_EVT_ERROR_UNEXPECTED. Right now the only way I know to display debug data is through SEGGER_RTT_WriteString function while I debug in SEGGER Studio. I tried to display the code like that but it didnt show.

RE: Pairing/bonding with ble_app_template example not working for me

Hung Bui — Tue, 17 Jan 2017 15:34:29 GMT

Please try to test again with unmodified example, you can test with the precompiled hex file. It works fine for me here. You can also try to test with another example, for example hrs or proximity.

Please find the error code when the PM_EVT_ERROR_UNEXPECTED happen.

RE: Pairing/bonding with ble_app_template example not working for me

Matej — Tue, 17 Jan 2017 13:28:45 GMT

Hi,

I dug a little bit deeper and I get the PM_EVT_ERROR_UNEXPECTED error pm_evt_handler (I also switched to example from 12.2.0 now but the problem is still there)

This is what happens:

I upload the code to device
Device starts advertising (led is blinking)
I scan with nRF Connect
I connect with nRF Connect (led is off)
I start bonding with nRF Connect (led is off)
Bonding fails (led is still off)
Device automatically disconnects (led is off)
Device automatically disconnects (led is off)
If I run scan again device isn't found anymore

I managed to make it work but with this setup: #define SEC_PARAM_BOND 0
#define SEC_PARAM_MITM 0
#define SEC_PARAM_LESC 0
#define SEC_PARAM_KEYPRESS 0
#define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_NONE
#define SEC_PARAM_OOB 0
#define SEC_PARAM_MIN_KEY_SIZE 7
#define SEC_PARAM_MAX_KEY_SIZE 16

and

sec_param.kdist_own.enc = 0; sec_param.kdist_own.id = 0; sec_param.kdist_peer.enc = 0; sec_param.kdist_peer.id = 0;

If I want to do any other combination with #define SEC_PARAM_BOND 1 it fails

RE: Pairing/bonding with ble_app_template example not working for me

Hung Bui — Tue, 17 Jan 2017 12:29:28 GMT

Hi Matej,

When it "hang" what happened after that ? Would the device advertise ?

Please follow this guide and find out where in the code it stuck.

The ble_app_template does support bonding. Did you add any modification to the code ?