nrf51822 bonding/whitelist creation

RE: nrf51822 bonding/whitelist creation

run_ar — Thu, 09 Feb 2017 12:26:40 GMT

OK, let us know how that goes. It might make sense to use the zip version of the SDK, then you can have multiple SDK versions on the same pc without any problems.

RE: nrf51822 bonding/whitelist creation

the_purple_pig — Thu, 09 Feb 2017 10:03:00 GMT

I will try update the SDK on another PC, so as to not change my config on my main PC in case I need to go back it it, and see if that helps. Not getting stuck in error handler - the program marches past that point and continues to work just fine in all other respects.

RE: nrf51822 bonding/whitelist creation

run_ar — Thu, 09 Feb 2017 09:44:23 GMT

Not sure exactly which SDK version that is, but it looks like it would be a rev3 compatible one. Are you getting any app erros / asserts, or any resets (which would indicate that you are ending up in the app error handler)?

RE: nrf51822 bonding/whitelist creation

the_purple_pig — Thu, 02 Feb 2017 09:13:01 GMT

That's the exact sort of thing I was hoping to find out, I wrote the firmware a long time ago, but it was working great so I don't want to change it - but of course if it doesn't run on certain chip variants, I will have to. I am using the s120 Softdevice version 2.0.0, and the SoftPacks versions in uVision list as follows: ARM:CMSIS - 4.3.0 nRF_BLE - 2.0.0 nRf_DeviceFamilyPack - 7.1.1 (maybe this needs updating) nRF_Drivers - 2.0.0 nRF libraries - 2.0.0 nRf_SoftDeviceCommon - 1.1.2

RE: nrf51822 bonding/whitelist creation

run_ar — Thu, 02 Feb 2017 07:58:14 GMT

The 01 variant (QFAA G0) is the second revision of the chip. While the 02 variant (QFAA H0) is the third revision. Which Softdevice and SDK version are you using? Maybe you could be missing a workaround or something.

RE: nrf51822 bonding/whitelist creation

the_purple_pig — Wed, 01 Feb 2017 16:49:40 GMT

I don't have a Nordik SDK HRM unfortunately, but I have used a few polar belts with a few '01' variants, swapped them between devices, never had any issues until this '02' module arrive. I (try) initiate the bonding: case BLE_HRS_C_EVT_DISCOVERY_COMPLETE: // Initiate bonding. err_code = dm_security_setup_req(&m_dm_device_handle); APP_ERROR_CHECK(err_code);

it's all very strange

RE: nrf51822 bonding/whitelist creation

run_ar — Wed, 01 Feb 2017 16:34:15 GMT

What happens if you try to connect to a nordic SDK HRM? I guess we don't know what is going on on the polar device either. Could there be any old bonds or something that stops the bonding from happening? Do you know which device is initializing the bonding process (sniffer log or are you calling sd_ble_gap_authenticate somewhere)?

RE: nrf51822 bonding/whitelist creation

the_purple_pig — Wed, 01 Feb 2017 16:23:26 GMT

Yes, exactly the same FW. My workflow is like this: Use nrfjprog to do full erase then program in SoftDevice V2.00, then load the application code on directly from uVision via a JLINK, and run it. I've only got one '-02' variant modules on a PCB, I have just taken delivery of a few more so will try swap that one out and see if it seems an isolated issue.

RE: nrf51822 bonding/whitelist creation

run_ar — Wed, 01 Feb 2017 16:02:14 GMT

Are you 100% sure you are using the same firmware on the modules? I assume you are using the Nordic SDK and has done a full erase of both module types, before programming it with both Softdevice and application (which SDK and SD version are you using)? How many BL-620-SA-02 modules have you tested?

RE: nrf51822 bonding/whitelist creation

the_purple_pig — Wed, 01 Feb 2017 13:34:59 GMT

Correct - with the same firmware running on BL620-SA-01 (containing nRF51822-QFAA-G0 ), the HR belt gets bonded when I do an open scan, and a whitelist is created, and I can whitelist scan and connect afterwards. Using exactly the same firmware on the newer module BL-620-SA-02 (with nRF51822-QFAA-H0 inside), when I do an open scan, I can connect to the HR belt but the connection never advances on to do bonding as it does in the other module. Therefore I can never create a whitelist. I just don't understand why the bonding step does not occur in the one module.

RE: nrf51822 bonding/whitelist creation

run_ar — Wed, 01 Feb 2017 13:29:50 GMT

But you are able to do whitelist scanning with the one that is bonded, right? The whitelist is created using dm_whitelist_create, which get's the device address'es and IRK's from the bond table. So it you haven't bonded nothing will be there to create the whitelist.

RE: nrf51822 bonding/whitelist creation

the_purple_pig — Fri, 27 Jan 2017 15:53:05 GMT

Ok, I've found something strange. I use a Laird BL620 module to run my app on. On one of my units, the HR belt gets bonded to when pairing it. On the other, it pairs and connects but never goes on to do the bonding. The only difference seems to be in the part number of the Laird modules - BL620-SA-01 for the one that bonds, BL620-SA-02 for the module that doesn't bond. Very strange..

RE: nrf51822 bonding/whitelist creation

the_purple_pig — Fri, 27 Jan 2017 10:12:16 GMT

this is what I get out of the debug output, no mention of bonding:

[APPL]: af0[APPL]: 180d[APPL]: >> DM_EVT_CONNECTION[APPL]:[88 B7 DB D0 22 00]: onnection Established[APPL]: << DM_EVT_CONNECTION[APPL]: Battery Service discovered.[APPL]: Reading battery level.[APPL]: Enabling Battery Level Notification.[APPL]: >> M_EVT_SECURITY_SETUP_COMPLETE[APPL]: << DM_EVT_SECURITY_SETUP_COMPLETE[APPL]: HR easurement received 0û[APPL]: HR Measurement received 0[APPL]: Battery Level Read as 100 %[APPL]: HR Measurement received 0[APPL]: HR Measurement received 0

RE: nrf51822 bonding/whitelist creation

the_purple_pig — Fri, 27 Jan 2017 10:05:10 GMT

Hi, No it doesn't appear to be bonding, I don't hit a breakpoint in the BLE_GAP_EVT_AUTH_STATUS case in dm_ble_evt_handler.. How do I initiate bonding? from what I can see bonding is supposed to be carried out. I do hit a breakpoint in the bit below:

case BLE_HRS_C_EVT_DISCOVERY_COMPLETE:
        // Initiate bonding.
        err_code = dm_security_setup_req(&m_dm_device_handle);
        APP_ERROR_CHECK(err_code);

My debug printf's look like this when doing the inital pairing: *edit - I can't paste the debug printf's in this stupid comment box, only the first line shows up. I'll try paste it in as an answer to my question, don't know what else to try *

RE: nrf51822 bonding/whitelist creation

run_ar — Fri, 27 Jan 2017 05:58:57 GMT

Are you sure you are actually bonded with the HR belt? Do you get a BLE_GAP_EVT_AUTH_STATUS event, where the bonded field = 1?