Windows bonding/pairing issue

RE: Windows bonding/pairing issue

Sensorion — Fri, 23 Sep 2016 18:40:37 GMT

The issue wound up being a SD to chip revision mismatch. Trying to run SD2 on an engineering rev b chip. Thanks

RE: Windows bonding/pairing issue

Sensorion — Fri, 23 Sep 2016 18:39:36 GMT

The issue wound up being a SD to chip revision mismatch. Trying to run SD2 on an engineering rev b chip. Thanks

RE: Windows bonding/pairing issue

bjorn-spockeli — Thu, 11 Aug 2016 06:44:41 GMT

Have followed the steps shown on this Infocenter page?

RE: Windows bonding/pairing issue

Sensorion — Thu, 11 Aug 2016 06:14:59 GMT

I have basically just tried to add the DFU support from the HRS example to the FreeRTOS HRS example. Is there some special support needed to make this addition?

RE: Windows bonding/pairing issue

Sensorion — Thu, 11 Aug 2016 06:13:30 GMT

My testing has shown that the culprit lies in the DFU app support being added to my application. If I compile with this code removed, undefine BLE_DFU_APP_SUPPORT as in the HRS example, the bonding works fine. I based the code off of the HRS example and have confirmed that that code does work with my bootloader even when it has the DFU support enabled, so I must be missing something but what that is I just don't know.

RE: Windows bonding/pairing issue

Sensorion — Thu, 11 Aug 2016 05:38:12 GMT

Thanks for the tip. That is now turned on but no change.

I based the code off of the HRS example and have confirmed that that code does work with my bootloader even when it has the DFU support enabled, so I must be missing something but what that is I just don't know.

RE: Windows bonding/pairing issue

bjorn-spockeli — Wed, 10 Aug 2016 11:29:36 GMT

EDIT:

Issue caused by chip revision mismatch. The S132 v2.0.0 is not compatible with the Engineering revision B chip, please refer the nRF52 Compatibility Matrix.

@sensorion : It sounds like that the bonding data is deleted during the DFU. You can configure the bootloader to preserve the bonding information during the DFU process, i.e. not erase the flash pages that contain the bonding data. This is done by setting the DFU_APP_DATA_RESERVED define to a value corresponding to the number of flash pages you want to preserve, e.g. one flash page(0x1000). See this Infocenter page for more information. Note: One flash page on the nRF52 is 4kB(0x1000) and not 1kB (0x400) like for the nRF51.