Recompilation of ble_app_hrs in nRF5_SDK_17.1.0 package does not work

[jinvers]

Hello,

I am using the Segger Embeddd Studio from the nRF Connect Desktop and the nRF52840-DK board.

I am working over the project into the "ses" directory for SoftDevice S140 version (..\nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral\ble_app_hrs\pca10065\s140\ses\ble_app_hrs_pca10056_s140.emProject). Just as it is, I rebuid the project and it is done without any error or warning. But when I download it to the nRF52840-DK I cannot see the LED 1 flashing and I cannot bond the board.

If I reprogram the nRF52840-DK with the original hex file (ble_app_hrs_pca10056_s140.hex), then the board resets with the LED 1 flashing and prepared from bonding.

What should I consider to be able to get a compilation output to work on the nRF52840-DK board?

Thank you in advance.

Regards.

[jinvers]

Hi,

I downloaded into the chip the .hex file generated by the Segger Studio into the Output file of the project. In 2 ways: one just copying the hex file into the J-Link directory; a second one using the Segger IDE.

Please, could you explain me the right sequence to follow or where may I find this information?

Best Regards,

Joel

[jinvers]

Hi,

I have rebuild the ble_app_hrs application and then downloaded using the Target->Download menu. After doing a reset of the nRF52840-DK, the LED1 have began to blink waiting for bonding. So, this is OK.

However, I have not been able to bond the board to the nRFConnect Android application. I have had to erase all the device, and download again by the Target-> Download option. After doing a reset, then it had bonded and connected. Should this always be the common procedure?

[Hung Bui]

Hi Joel, 
Good to know that it works for you. 

Regarding bonding, by default if you already have a bonding on the nRF52 device but you remove the bond on the phone. It won't be possible to re-bond /re-pair due to security reason (avoiding spoofing attack) 

But it's configurable, you can have a look here:

https://devzone.nordicsemi.com/f/nordic-q-a/20909/nrf52-dk-issues-with-bonding-pm_evt_conn_sec_failed-is-called-every-time

(the code may not available in newer SDK but you can add the code into pm_evt_handler() as suggested in the case )

[jinvers]

Thank you. But it could always be a problem and the need to reinitiate and rebond again, so I think this should be managed in some way or another. If not, the nRF52 device may became non-functional. I will check the case.

Regards,

Joel