da1469x_custom_ble_service示例中的属性许可中的混淆

你好对话框，

我正在测试示例“ble_central”和“da1469x_custom_ble_service”以在GATT客户端和服务器之间实现一些通信。在自定义服务示例中，在peripheral_task.c中，分别有两个与A和THE特征定义的服务。在这里，我为这两个服务的特征设置了一些随机权限。请找到下面附带的日志文件。

ÿ ÐÊ@ BLE Central application started BLE Central application started @ BLE Central application started @ BLE Central application started @ BLE Central application started 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-2222222222 start_h=000e end_h=0016 handle_evt_gattc_discover_completed:conn_idx=0 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 = 0 x2a04处理属性= 0006 value_handle = 0007 = 2 (- r) handle_evt_gattc_discover_completed: conn_idx = 0000 = 2型状态= 0 handle_evt_gattc_read_completed: conn_idx = 0000 = 0003 = 0状态处理43 75 73 74 6 f 6 d 20 42 4 c 45 63 53 65 72 76 69定制的祝福就是公元65年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- 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-000000000002 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_completed: Conn_idx =0000 type=3 status=0 handle_evt_gatt_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-1111111111 start_h=0009 end_h=000d handle_evt_gattc_discover_svc: Conn_idx =0000 uuid=22222222-0000-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_characteristic_config_t custom_service_1 [] {/ *初始化特征属性* / characture_declaration（11111111-000000000001，charperting_attr_value_max_bytes，char_write_prop_dis，char_read_prop_dis，char_notif_indic_en，初始化的特征，null，null，event_sent_cb），};常量mcs_characteristic_config_t custom_service_2 [] = {CHARACTERISTIC_DECLARATION（22222222-0000-0000-0000-000000000001，CHARACTERISTIC_ATTR_VALUE_MAX_BYTES，CHAR_WRITE_PROP_EN，CHAR_READ_PROP_DIS，CHAR_NOTIF_NONE，世界你好，NULL，set_var_value_cb，NULL），CHARACTERISTIC_DECLARATION（22222222-0000-0000-0000-000000000002，CHARACTERISTIC_ATTR_VALUE_MAX_BYTES，char_write_prop_dis，char_read_prop_en，char_notif_none，hello对话框，get_var_value_cb，null，null），compyristic_declaration（22222222-0000-0000-0000-000000000003,0，char_write_prop_dis，char_read_prop_dis，char_notif_none，null，null，null，null），};

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

Coming to the second service characteristics, They are printed as (-R-W----), (-R------) and (-R------) for the three characteristics respectively which are in contrast with the permissions which I actually gave.

仅根据我给出的内容正确打印第二服务的第二个特征权限。

我要求您调查为什么会发生这种情况，并建议我可以做些什么来避免这种情况。这对我的应用非常重要，因为我必须在GATT客户端和服务器之间交换数据。

提前致谢。

问候，

普拉斯坦娜