• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 90 subscribers
  • Views 717 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 283260
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

rfConnect was bonding with my DK-52 and no longer does.

AllenS

During the development process, I had no trouble bonding with the rfConnect (current version from the website).  After many changes to code, I got it to bond one time and deleted the bond again and now it will no longer bond between the DK-52 and the rfConnect App.  I have not changed any of the code that relates to the BLE portion of the HeartRateMonitor demo App.  I have only been experimenting with the Battery Service portion of the demo.  I have no trouble seeing the device in rfConnect but it will not allow bonding or pairing anymore.  Any ideas?

  • +1

    Hi Allen Shea, 

    Please clarify: 

    - Is it the nRF Connect app on Android/iOS or it's the nRF Connect app on PC ? 

    - If you do a chip erase to clear any previous bond stored on the chip , can you bond to the nRF Connect app ? 

    Please note that by default zephyr won't allow re-pair meaning if the peer device lose the bond information you must explicitly remove bonding on the local device (calling bt_unpair() ) to be able to bond again. 

    Or you can use BT_SMP_ALLOW_UNAUTH_OVERWRITE=y to allow unauthentication (just work) bonding to be able to replace previous bond.  

  • 0 in reply to Hung Bui

    Hello Hung Bui,

    Thank you for your responses.  I will try them and see what happens.  I am using the Segger IDE.  Is there a way to do a chip erase from there or do I need to use the command line utilities to perform that?

    What is zephyr?

    I was using the nRF Connect app on the Android.  I did not think to try using the PC.  I was deleting the bond/pair information from the android because every time I made changes to the firmware on the chip and reprogrammed to test with the HRM app under nRF Toolbox the unit would no longer bond.  I would go into the nRF Connect app and delete the bond/pair information and then exit the app and restart and do the bond with the newer firmware that needed to be tested.  That worked for a little while and now it does not work.

    Thanks,

    Allen Shea

  • 0 in reply to AllenS

    Hi Allen, 
    I was having the impression that you were using nRF Connect SDK (Zephyr) but I guess you are using softdevice and nRF5 SDK instead ? 
    If it's the case you just need to enable allow_repair, please have a look here: https://devzone.nordicsemi.com/f/nordic-q-a/37837/sdk15-paring-problem

    To be able to erase the chip you can either use the Programmer application on nRF Connect for Desktop application. 
    Or you can install the command line tool and use nrfjprog.exe --eraseall 

Related
Terms of service