DSPS V6.150.2配对问题

嗨Andrey_Kiselnikov，

Could you please clarify which SDK are you using? Be aware that the security tutorial is based on the SDK 6.0.4. It is highly recommended to use the latest version of SDK6.0.8.

Thanks, PM_Dialog

嗨Andrey_Kiselnikov，

You have to change the permission to each characteristic in order to be authorized. If you set the characteristic as AUTH this means that you will add security into the characteristic and an authorization is needed. Could you please clarify which security scenario are you using? Please check the .security_request_scenario of user_default_hnd_conf structure into the user_config.h header file. With DEF_SEC_REQ_NEVER option an authorization is required during read/write of a characteristic and with DEF_SEC_REQ_ON_CONNECT an authorization is required during connection

Thanks, PM_Dialog

嗨Andrey_Kiselnikov，

Could you please download firmware from the default ble_app_security example of the SDK6? Do you face the same problem? I have tested and I am not able to replicate your problem. Also, could you please clarify if you develop your own application or if you tried to modify the default ble_app_security example? The DEF_SEC_REQ_NEVER is referred to the security scenario and it does not mean that the security is enabled when requests on reading and write operations by choosing the parameter. Be aware that each characteristic has its own security. Please check if you are using the app_set_prf_srv_perm(TASK_ID_CUSTS1, APP_CUSTS1_SEC_REQ); command. This command enables the security of all the characteristics and overrides the permissions that you give them into the database.So, if you are using this, you will be able to access all the characteristics of the database without any security request. The past thread that you posted is for DA14680 chip and not for DA14580, so this will not help you.

Thanks, PM_Dialog

嗨Andrey_Kiselnikov，

DSP参考应用程序不支持安全性，因此如果要使用此应用程序，则需要自己实现。正如我已经提到的那样，DSPS演示不使用安全功能，因此设备之间没有配对，这就是为什么您能够在不配对的情况下读取/写入该特征。您可以通过在da1458x_config_basic.h中设置cfg_app_security定义来启用安全性，并且还将成员Security_Request_scenario更改为def_sec_req_on_connect，以便在连接时请求安全性。这将根据位于User_Security_Information中的User_Config.h文件中的参数来绑定您的设备。请检查一下ble_app_security.为了了解如何实现安全功能的SDK示例。此外，我强烈建议您遵循这些步骤Tutorial 5 : Pairing , Bonding & Security" to enable security in the DSPS. You will be able to find the tutorial in the Documents tab at the Tutorials section or by following the below link

https://support.dialog-seminile.com/system/files/restricted/training_05_ble_security_example_v1.1.pdf.

Thanks, PM_Dialog

嗨Andrey_Kiselnikov，

3.我可以跳过这个窗口，阅读和写作服务仍然可以从手机中获得

The gapc_bond_ind_handler() should be called if you refuse the pairing, and this function will disconnect the phone.

static const struct ke_msg_handler app_sec_process_handlers [] =
{
.......
{gapc_bond_ind，（ke_msg_func_t）gapc_bond_ind_handler}，

嗨安德烈，

You can test the different IO capability type in use_config.h. I think you should disable user escape the pairing window on the phone.
你能用Light Bule来测试你的固件吗？

/************************************************************
*设备IO功能（@see gap_io_cap）
*
* - 只显示GAP_IO_CAP_DISPLAY_ONLY
* - GAP_IO_CAP_DISPLAY_YES_NO Display Yes No
* - GAP_IO_CAP_KB_ONLY Keyboard Only
* - GAP_IO_CAP_NO_INPUT_NO_OUTPUT无输入无输出
* - GAP_IO_CAP_KB_DISPLAY Keyboard Display
*
*仅选择一个选项。
************************************************************
*/
#define user_cfg_feat_io_cap gap_io_cap_no_input_no_output // gap_io_cap_display_yes_no

嗨Andrey_Kiselnikov，

很高兴您的问题已得到修复。谢谢你的迹象。

Thanks, PM_Dialog

嗨Andrey_Kiselnikov.　

我想要在DSP上添加对功能，

can u give me your source code for reference