嗨队,
你能帮助指出如何修复BR/EDR配对总是失败的问题后,未配对操作之前?
下面详细描述这个问题。
环境:
IDE:Woice Studio1.1.0.85
安卓
手机
HW:CYW20719-B1模块
繁殖步骤:
1。建立和下载APP/SNIP/BT/A2DP1Sink项目到CYW20719-B1模块设备,并等待A2DPJ-Sink应用程序启动。
2。在Android手机设备中,发现并找到A2DPX下沉设备。
三。单击A2DPiSink设备配对并首次建立连接。
4。配对和连接成功后建立。用S2DPi下沉设备断开和配对Android手机。
5。关闭Android手机上的蓝牙,然后再打开它。
6。在Android手机设备中,发现并找到AD2pxink设备。
7。单击A2DPiSink设备配对并建立第二次连接。
8。在这里,我们发现A2DPX接收器设备不能被配对和连接。
我们可以看到30s超时问题或PIN码错过匹配错误时,尝试重新连接到设备。
下面是当A2DP1Sink固件运行时使用以上步骤捕获的固件日志:
A2DP接收器应用程序启动
A2DPX-SIKKM管理回调0x15
A2DPX-SIKKM管理回调0x00
A2DPX-SnkkWr.EIR 269BB0
EIR:09,77,69,63,65,64,20,61,32,64,70,20,20,6e,6b,α,6c,…
A2DPX-SIKKM管理器回调0x14
A2DPX-SIKKM管理器回调0x14
A2DPX-SIKKM管理回调0X09
A2DPX-SIKKM管理回调0x08
配对能力请求,BDA 94 65 2D 90 C1 42
A2DPX-SIKKM管理回调0x04
A2DPX-SIKKM管理回调0x0B
配对完成0
A2DPX-SIKKM管理器回调0x12
NVRAM ID:512写入:136字节结果:0
A2DPX-SIKKM管理回调0x0C
加密状态事件:BD(94 65 2D 90 C1 42)RES 0
A2DPX-SIKKM管理回调0X09
A2DPX-SIKKM管理回调0x08
配对能力请求,BDA 94 65 2D 90 C1 42
A2DPX-SIKKM管理回调0x0B
配对完成5
谢谢,
杜德利
以上来自于百度翻译
以下为原文
Hi Team,
Could you help indicates how to fix the BR/EDR pairing always failed issue after unpair opera
tion 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