DA1469x\u Custom\u BLE\u服务示例中的属性权限混淆

你好Dialog，

我正在测试示例“BLE_Central”和“DA1469x_Custom_BLE_Service”，以实现GATT客户机和服务器之间的一些通信。在custom service示例中，在peripheral_task.c中，有两个分别用一个和e个特征定义的服务。在这里，我为这两个服务的特性设置了一些随机权限。请查看下面所附的日志文件。

ÿÿð@BLE中央应用程序启动BLE中央应用程序启动@BLE中央应用程序启动@ble中央应用程序启动@ble中央应用程序启动@ vt_gap_connected：conn_idx = 0000 supple_evt_gattc_discover_svc：conn_idx = 0000 uuid = 0x1800 start_h = 0001 end_h = 0007 handle_evt_gattc_discover_svc：conn_idx = 0000UUID = 0x1801 start_h = 0008 end_h = 0008 handle_evt_gattc_discover_svc：conn_idx = 0000 UUID = 11111111-0000-0000-0000-111111111111 start_h = 0009 end_h = 000D handle_evt_gattc_discover_svc：conn_idx = 0000 UUID = 22222222-0000-0000-0000-222222222222 start_h = 000Eend_h = 0016 handle_evt_gattc_discover_completed：conn_idx = 0000 type = 0 status = 0 shower_t_gattc_discover_char：conn_idx = 0000 uuid = 0x2a00句柄= 0002 value_handle = 0003属性= 02（-----）supple_evt_gattc_discover_char：conn_idx = 0000 uuid = 0x2a01句柄= 0004 value_handle = 0005属性= 02（-----）supple_evt_gattc_discover_char：conn_idx = 0000 uuid = 0x2a04句柄= 0006 value_handle = 0007属性= 02（-----）hange_evt_gattc_discover_completed：conn_idx = 0000类型= 2 status = 0 shower_evt_gattc_read_completed：conn_idx = 0000把手= 0003 status = 0 43 75 75 73 74 6f 6d 20 42 4c 45 20 53 6f 6d 20 42 4c 45 20 53 65 72 76 69定制ble servi 63 65 ce handle_evt_gattc_discover_completed：conn_idx = 0000type = 2 status = 0 shower_evt_gattc_discover_char：conn_idx = 0000 uuid = 11111111-0000-0000-0000-00000000/0000-0000-000000000001句柄= 000a value_handle = 000b属性= 22（-R --- i--）supple_evt_gattc_discover_completed：conn_idx = 0000类型= 2状态= 0 handle_evt_gattc_discover_desc：conn_idx = 0000 UUID = 0x2901手柄= 000C handle_evt_gattc_discover_desc：conn_idx = 0000 UUID = 0x2902手柄= 000D handle_evt_gattc_discover_completed：conn_idx = 0000类型= 3个状态= 0 handle_evt_gattc_discover_char：conn_idx = 0000 UUID = 22222222-0000-0000-0000-000000000001 handle=000f value_handle=0010 properties=0a (-R-W----) handle_evt_gattc_discover_char: conn_idx=0000 uuid=22222222-0000-0000-0000-000000000002 handle=0012 value_handle=0013 properties=02 (-R------) handle_evt_gattc_discover_char: conn_idx=0000 uuid=22222222-0000-0000-0000-000000000003 handle=0015 value_handle=0016 properties=02 (-R------) handle_evt_gattc_discover_completed: conn_idx=0000 type=2 status=0 handle_evt_gattc_discover_desc: conn_idx=0000 uuid=0x2901 handle=0011 handle_evt_gattc_discover_completed: conn_idx=0000 type=3 status=0 handle_evt_gattc_discover_desc: conn_idx=0000 uuid=0x2901 handle=0014 handle_evt_gattc_discover_completed: conn_idx=0000 type=3 status=0 handle_evt_gap_disconnected: conn_idx=0000 address=06:06:06:01:01:01 reason=8 handle_evt_gap_connected: conn_idx=0000 handle_evt_gattc_discover_svc: conn_idx=0000 uuid=0x1800 start_h=0001 end_h=0007 handle_evt_gattc_discover_svc: conn_idx=0000 uuid=0x1801 start_h=0008 end_h=0008 handle_evt_gattc_discover_svc: conn_idx=0000 uuid=11111111-0000-0000-0000-111111111111 start_h=0009 end_h=000d handle_evt_gattc_discover_svc: conn_idx=0000 uuid=22222222-0000-0000-0000-222222222222 start_h=000e end_h=0016 handle_evt_gattc_discover_completed: conn_idx=0000 type=0 status=0 handle_evt_gattc_discover_char: conn_idx=0000 uuid=0x2a00 handle=0002 value_handle=0003 properties=02 (-R------) handle_evt_gattc_discover_char: conn_idx=0000 uuid=0x2a01 handle=0004 value_handle=0005 properties=02 (-R------) handle_evt_gattc_discover_char: conn_idx=0000 uuid=0x2a04 handle=0006 value_handle=0007 properties=02 (-R------) handle_evt_gattc_discover_completed: conn_idx=0000 type=2 status=0 handle_evt_gattc_read_completed: conn_idx=0000 handle=0003 status=0 43 75 73 74 6f 6d 20 42 4c 45 20 53 65 72 76 69 Custom BLE Servi 63 65 ce handle_evt_gattc_discover_completed: conn_idx=0000 type=2 status=0 handle_evt_gattc_discover_char: conn_idx=0000 uuid=11111111-0000-0000-0000-000000000001 handle=000a value_handle=000b properties=22 (-R---I--) handle_evt_gattc_discover_completed: conn_idx=0000 type=2 status=0 handle_evt_gattc_discover_desc: conn_idx=0000 uuid=0x2901 handle=000c handle_evt_gattc_discover_desc: conn_idx=0000 uuid=0x2902 handle=000d handle_evt_gattc_discover_completed: conn_idx=0000 type=3 status=0 handle_evt_gattc_discover_char: conn_idx=0000 uuid=22222222-0000-0000-0000-000000000001 handle=000f value_handle=0010 properties=0a (-R-W----) handle_evt_gattc_discover_char: conn_idx=0000 uuid=22222222-0000-0000-0000-000000000002 handle=0012 value_handle=0013 properties=02 (-R------) handle_evt_gattc_discover_char: conn_idx=0000 uuid=22222222-0000-0000-0000-000000000003 handle=0015 value_handle=0016 properties=02 (-R------) handle_evt_gattc_discover_completed: conn_idx=0000 type=2 status=0 handle_evt_gattc_discover_desc: conn_idx=0000 uuid=0x2901 handle=0011 handle_evt_gattc_discover_completed: conn_idx=0000 type=3 status=0

这些是我设置的愚蠢的特征权限。

const mcs \u characteristic \u config \u t custom \u service \u 1[]={/*初始化的特征属性*/特征声明（11111111-0000-0000-000000000001，特征属性值\u MAX \u BYTES，字符写入属性DIS，字符读取属性DIS，字符NOTIF指示EN，初始化特征，NULL，NULL，事件发送\u cb），}；const mcs\u characteristic\u config\u t custom\u service\u 2[]={特征声明（2222222-0000-0000-000000000001，特征属性值\u MAX\u BYTES，特征写入属性EN，特征读取属性DIS，特征不存在，Hello World，NULL，设置变量值\u cb，NULL），特征声明（2222222-0000-0000-0000-000000000002，CHARACTERISTIC\u ATTR\u VALUE\u MAX\u BYTES，CHAR\u WRITE\u PROP\u DIS，CHAR\u READ\u PROP\u EN，CHAR\u NOTIF\u NONE，Hello Dialog，get\u var\u VALUE\u cb，NULL，NULL），CHARACTERISTIC\u声明（22222-0000-0000-0000-000000000003，0，CHAR\u WRITE\u PROP\u DIS，CHAR\u READ\u PROP\u DIS，CHAR\u NOTIF\u NONE，NULL，NULL，NULL），}；

请将权限与附加的输出日志进行比较。您可以看到服务1的唯一特征的属性被打印为（-R---I--），即使我禁用了Read属性。

至于第二个服务特征，它们分别被打印为（-R-W----）、（-R------）和（-R------），这三个特征与我实际授予的权限形成对比。

只有第二个服务的第二个特征根据我给出的正确打印。

我请求您调查为什么会发生这种情况，并建议我如何避免这种情况。这对我的应用程序非常重要，因为我必须在GATT客户机和服务器之间交换数据。

提前谢谢。

当做，

普拉桑纳