Learn MoreFAQsTutorials

4 posts / 0 new
Last post
DanyloVodopianov
Offline
Last seen:3 months 2 weeks ago
加入:2019-09-30 19:35
Pairing failed

Hello

I work with da14585 and da14586 chips.

From phones I use:

iPhone xs iOS14

iPhone 11 iOS 13

Samsung galaxy s8 Android 9

Pixel 4 with Android 10

I use bonding and all worked well on the SDK 6.0.10

Then on the forum, when I asked about PWM, your engineers advised me to update from SDK6.0.10 to SDK6.0.14 according to the tutorial.

And now I have a bug with pairing.

On the device, 585 everything works well on the new SDK6.0.14.

But when I run my code for device 586 I get pairing failed with reason: "The pairing procedure cannot be performed as authentication requirements cannot be met due to IO capabilities of one or both devices."

I have the next security settings:

#定义USER_CFG_FEAT_IO_CAP GAP_IO_CAP_DISPLAY_ONLY
#define USER_CFG_FEAT_OOB GAP_OOB_AUTH_DATA_NOT_PRESENT
#define USER_CFG_FEAT_AUTH_REQ (GAP_AUTH_BOND | GAP_AUTH_MITM | GAP_AUTH_SEC)
#define USER_CFG_FEAT_KEY_SIZE 0x10
#define USER_CFG_FEAT_SEC_REQ GAP_SEC1_SEC_PAIR_ENC
#define USER_CFG_FEAT_INIT_KDIST (GAP_KDIST_ENCKEY | GAP_KDIST_IDKEY | GAP_KDIST_SIGNKEY)
#define USER_CFG_FEAT_RESP_KDIST (GAP_KDIST_ENCKEY | GAP_KDIST_IDKEY | GAP_KDIST_SIGNKEY)

Keywords:
Device:
TR_Dialog
Offline
Last seen:11 hours 58 sec ago
Staff
加入:2014-06-30 23:52
Hi DanyloVodopianov,

Hi DanyloVodopianov,

I am checking with our team to see if there is any known issue. If we do not find anything we will ask for a sniffer trace to debug the issue.

Thanks,

TR_DIALOG

DanyloVodopianov
Offline
Last seen:3 months 2 weeks ago
加入:2019-09-30 19:35
Hello. thank you for your

Hello. thank you for your answer.

I can fix this issue only by changing

from

#define USER_CFG_FEAT_SEC_REQ GAP_SEC1_SEC_PAIR_ENC

to

#define USER_CFG_FEAT_SEC_REQ GAP_SEC1_NOAUTH_PAIR_ENC

PM_Dialog
Offline
Last seen:8 hours 37 min ago
Staff
加入:2018-02-08 11:03
Hi DanyloVodopianov,

Hi DanyloVodopianov,

Thanks for your indication and glad that you fixed your issue.

Thanks, PM_Dialog