• State Verified Answer
  • Replies 12 replies
  • Subscribers 65 subscribers
  • Views 3661 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 109810
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

iOS9 can not pairing (SDK6.1/SD7.0.0)

Matt

Use SDK6.1 / SD7.0, iOS9 can not pairing! dm_ble_evt_handler() return error "BLE_GAP_SEC_STATUS_UNSPECIFIED"! It is the captured packets file: ble_proximity_ios9.1.pcapng. The project hex: ble_app_proximity.hex

Parents
  • 0

    I'm not able to reproduce it here now, don't know why. The issue seems to be that in the Rcvd Identity Address Information sent from the slave to master the address is 0x00, 0x00, 0x00, 0x00, 0x00, 0x00. If you see the 6 bytes after 0x09. The master doesn't accept this address and this triggers pairing failed. Could you check what address you have in FICR? Open a command window and type nrfjprog --memrd 0x100000A4 and nrfjprog --memrd 0x100000A8. Could you also check what address and address type you get if you use sd_ble_gap_address_get()?

Reply
  • 0

    I'm not able to reproduce it here now, don't know why. The issue seems to be that in the Rcvd Identity Address Information sent from the slave to master the address is 0x00, 0x00, 0x00, 0x00, 0x00, 0x00. If you see the 6 bytes after 0x09. The master doesn't accept this address and this triggers pairing failed. Could you check what address you have in FICR? Open a command window and type nrfjprog --memrd 0x100000A4 and nrfjprog --memrd 0x100000A8. Could you also check what address and address type you get if you use sd_ble_gap_address_get()?

Children
No Data
Related