WICED CYW20719-B1: BR/EDR pairing always failed after pair and unpair operations

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
LixinD_46
Employee
Employee
10 replies posted 5 replies posted 10 questions asked

Hi Team,

Could you help indicates how to fix the BR/EDR pairing always failed issue after unpair operation was done before?

Detail of this issue is  described below.

Environments:

IDE: WICED Studio 6.1.0.85

HW: Android Phone

HW: CYW20719-B1 module

Steps to reproduce:

1. Build and download the app/snip/bt/a2dp_sink project to the CYW20719-B1 module device, and wait the a2dp_sink app started up.

2. In Android Phone device, discover and find the a2dp_sink device.

3. Click the a2dp_sink device to pair and established the connection for the firstly time.

4. After pair and connection established successfully. disconnect and un-pair the Android phone with the s2dp_sink device.

5. Turn off the Bluetooth on the Android Phone, then turn it on again.

6. In Android Phone device, discover and find the ad2p_sink device.

7. Click the a2dp_sink device to pair and established the connection for the second time.

8. Here, we found that the the a2dp_sink device cannot be paired and connected anymore.

    We could see 30s timeout issue or PIN code miss-matched error when try to re-connect to the device.

Following is the firmware log that captured when the a2dp_sink firmware running with above steps:

A2DP SINK APP START

a2dp_sink_management_callback 0x15

a2dp_sink_management_callback 0x00

a2dp_sink_write_eir 269bb0

EIR :09 77 69 63 65 64 20 61 32 64 70 20 73 69 6e 6b 20 64 75 64 6c 03 03 0b 11 00 e5

a2dp_sink_management_callback 0x14

a2dp_sink_management_callback 0x14

a2dp_sink_management_callback 0x09

a2dp_sink_management_callback 0x08

Pairing Capabilities Request, bda 94 65 2d 90 c1 42

a2dp_sink_management_callback 0x04

a2dp_sink_management_callback 0x0b

Pairing complete 0

a2dp_sink_management_callback 0x12

NVRAM ID:512 written :136 bytes result:0

a2dp_sink_management_callback 0x0c

Encryption Status Event: bd ( 94 65 2d 90 c1 42  ) res 0

a2dp_sink_management_callback 0x09

a2dp_sink_management_callback 0x08

Pairing Capabilities Request, bda 94 65 2d 90 c1 42

a2dp_sink_management_callback 0x0b

Pairing complete 5

Thanks,

Dudley

0 Likes
1 Solution
Anonymous
Not applicable

You might have encountered the "can't communicate with device" error. This is mostly because the paging didn't go through. The phone is sending ID packets on channels that do not overlap with the channels 20719 is scanning on.

You could refresh the scanned device list before connecting. During inquiry, the clock of the slave is received by the phone which can be used to aid the paging process.

However, the "incorrect PIN" could be an issue. I am not able to reproduce the "incorrect PIN" issue with WICED 6.1 and a couple of Android phones.

View solution in original post

3 Replies
MichaelF_56
Moderator
Moderator
Moderator
250 sign-ins 25 comments on blog 10 comments on blog

dudl

This appears to be a duplicate of the discussion created here: https://community.cypress.com/message/161348?et=watches.email.thread#161348

0 Likes

Maybe the root cause of these two threads were same.

But the behavior to cause the pair issue are different, so I would like to trace them in different threads.

Thanks,

Dudley

0 Likes
Anonymous
Not applicable

You might have encountered the "can't communicate with device" error. This is mostly because the paging didn't go through. The phone is sending ID packets on channels that do not overlap with the channels 20719 is scanning on.

You could refresh the scanned device list before connecting. During inquiry, the clock of the slave is received by the phone which can be used to aid the paging process.

However, the "incorrect PIN" could be an issue. I am not able to reproduce the "incorrect PIN" issue with WICED 6.1 and a couple of Android phones.