• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 63 subscribers
  • Views 6852 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 103754
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
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

MIO ALPHA pairing with S120 1.0.0 and SDK 6.1.0 on nrf51822

Inge Aune Paulsen

I have successfully been using the MIO ALPHA heart rate monitor with S120 0.8.0-3.aplha and SDK 5.1.0, using the SDK application "ble_app_hrs_c"

Im trying to migrate to S120 1.0.0 and SDK 6.1.0, but i'm having problems with pairing now. The connection is established and lost again instantaneously. This happens over and over in an infinite loop, about every third second. The debug printout is:

[APPL]: 180d
[APPL]: >> DM_EVT_CONNECTION
[APPL]:[8C 79 18 16 E0 F8]: Connection Established
[APPL]: << DM_EVT_CONNECTION
[APPL]: >> DM_EVT_SECURITY_SETUP_COMPLETE
[APPL]: << DM_EVT_SECURITY_SETUP_COMPLETE
[APPL]: >> DM_EVT_DISCONNECTION
[APPL]: << DM_EVT_DISCONNECTION
[APPL]: 180d
[APPL]: >> DM_EVT_CONNECTION
[APPL]:[8C 79 18 16 E0 F8]: Connection Established
[APPL]: << DM_EVT_CONNECTION
[APPL]: >> DM_EVT_SECURITY_SETUP_COMPLETE
[APPL]: << DM_EVT_SECURITY_SETUP_COMPLETE
[APPL]: >> DM_EVT_DISCONNECTION
[APPL]: << DM_EVT_DISCONNECTION

I'm having trouble seeing from the nRF sniffer logs what the problem is. I get a "Pairing not supported" on the new soft-device/SDK (S120 1.0.0 and SDK 6.1.0). Could it be bad FW on the MIO?

BLE Sniffer log: BLE_Sniffer.zip

BLE Sniffer screenshot:

S120 1.0.0 and SDK 6.1.0 - infinite connect/disconnect loop: image description

S120 0.8.0-3.aplha and SDK 5.1.0 - working OK: image description

Parents Reply Children
  • 0 in reply to Inge Aune Paulsen

    I am facing same issue with nRF5_SDK_11.0.0_89a8197 and S130 with nrf51 dongle. I have tried with default as well as commentiong out line dm_security_setup_req() in device_manager_event_handler() function's DM_EVT_CONNECTION case.

    Logs for default code: Same as posted by Inge Aune Paulsen

    Logs for commenting out dm_security_setup_req():

    DM_EVT_CONNECTION << DM_EVT_CONNECTION DM_EVT_DISCONNECTION << DM_EVT_DISCONNECTION 180d DM_EVT_CONNECTION << DM_EVT_CONNECTION DM_EVT_DISCONNECTION << DM_EVT_DISCONNECTION

Related