DA14531 allowing to connect without pairing and allowing to send or receive data from BLE Application.

Question

Hi Team, 
 When i click on Connect for the first time pairing pop-up is coming, even if i not entered passcode also it started communicating with BLE Application. 
 In my code i have set 
 user_app_on_init() 
 { 
 codeless_env.pin= 123456; 
 
 } 
 Iam expecting, after entering pairing code only it should connect and start communicating with Application. 
 Pls help me in fixing this issue. 
 
 Regards, 
 Laxmi Narayana.

OV_Renesas · Answer

Hi Laxmi, Thank you for the reply. 
 laxmi said: we are not using any AT commands like AT+SEC, AT+PIN and we disabled all AT commands. 
 What is the point of using the Codeless SDK if you have disabled all AT commands? Why not create a project with the Generic SDK6? Please check our Central with Security example: BLE_SDK6_examples/connectivity/central_Security_Demo at main &middot; dialog-semiconductor/BLE_SDK6_examples (github.com) 
 laxmi said: Iam using codeless Version:6.380.14.22. laxmi said: My device is central. 
 Please refer on the Codeless SDK Release Notes : The Bonding support for the Central role in Codeless is supported from SDK v6.380.16.55 version and later. You will have to define the CFG_BOND_CMD_SUPPORTED macro in the da1458x_config_advanced.h file. On the SDK v6.380.14.22, if you define the CFG_BOND_CMD_SUPPORTED macro and build the project you should receive the following in the output window: You should either migrate into a later Codeless SDK version or use the Generic SDK6 to create your application since you are not utilizing the AT commands. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Laxmi, Thank you for the reply. laxmi said: using sdk codeLess 6.380.14.22. Apologies, but I worked on the latest Codeless SDK you mentioned on your initial post: laxmi said: is it possible with DA14531MOD and codeLess: v6.380.18.63. We added 3 custom AT commands that will enable/disable the Pairing option upon connection, and 1 AT command to check if the status is enabled or disabled. Changes required on SDK v6.380.18.63 : On user_at_commands.h file: #define USE_AT_PR_MD // This is a new set of AT commands . . . //On the AT_COMMAND_ID_t typedef enum add the following: #ifdef USE_AT_PR_MD AT_EN_PR_MD, AT_DIS_PR_MD, AT_GET_PR_MD, #endif AT_INVALID, /**< Command to execute in case of an invalid command. */ AT_LAST_VALUE /**< Enumeration length. */ } AT_COMMAND_ID_t; //At the end of the file declare the fuctions for the AT commands #ifdef USE_AT_PR_MD void user_at_en_pr_md(struct at_cmd_params_t* arg, char* reply_string); void user_at_dis_pr_md(struct at_cmd_params_t* arg, char* reply_string); void user_at_get_pr_md(struct at_cmd_params_t* arg, char* reply_string); #endif I have also removed the AT+CENTRAL and AT+GAPSCAN commands since you are not going to use the DA14531MOD in central role and we needed more space for the new AT commands. For memory issues, I have also removed the SUOTA feature from user_modules_config.h and user_profiles_config.h files. On user_codeless_env.h file I added the following on the struct codeless_env_t : #ifdef USE_AT_PR_MD bool is_pr_md_en; #endif On user_codeless.c file, on the user_app_on_pairing_request at the start of the function I added: void user_app_on_pairing_request(uint8_t conidx, struct gapc_bond_req_ind const *param) { #ifdef USE_AT_PR_MD // When a connection attempt is made this function will be called only if // a pairing has not taken placed already. Therefore if pairing mode is disable the device // should just disconnect if (!codeless_env.is_pr_md_en) { // Disconnect app_easy_gap_disconnect(0); app_env[0].pairing_in_progress = false; } #endif . . . On the user_at_commands.c file, at the at_command_characteristics_t struct I added: #ifdef USE_AT_PR_MD { AT_EN_PR_MD , 0, 0, "ENPRMD" , user_at_en_pr_md }, { AT_DIS_PR_MD , 0, 0, "DISPRMD" , user_at_dis_pr_md }, { AT_GET_PR_MD , 0, 0, "GETPRMD" , user_at_get_pr_md }, #endif On the same file I added the following functions: #ifdef USE_AT_PR_MD void user_at_en_pr_md(struct at_cmd_params_t* arg, char* reply_string) { codeless_env.is_pr_md_en = true; arg->success_flag = true; } void user_at_dis_pr_md(struct at_cmd_params_t* arg, char* reply_string) { codeless_env.is_pr_md_en = false; arg->success_flag = true; } void user_at_get_pr_md(struct at_cmd_params_t* arg, char* reply_string) { arch_sprintf(reply_string,(codeless_env.is_pr_md_en ? "ENABLED":"DISABLED")); arg->success_flag = true; } #endif // USE_AT_PR_MD Finally, on the da14531_config_advanced.h file I defined the CFG_USE_DYNAMIC_PRF_PERMS macro: /****************************************************************************************************************/ /* If this macro is defined, CodeLess will change the permissions to access the custom profile database */ /* dynamically depending on the AT+SEC selection.This macro and CFG_BOND_CMD_SUPPORTED are mutually exclusive */ /****************************************************************************************************************/ #if defined(__DA14531_01__) #define CFG_USE_DYNAMIC_PRF_PERMS #else // DA14531 #if defined(CFG_BOND_CMD_SUPPORTED) #undef CFG_USE_DYNAMIC_PRF_PERMS #else #define CFG_USE_DYNAMIC_PRF_PERMS // #define this macro here if you need dynamic profile permissions #endif #if defined(CFG_USE_DYNAMIC_PRF_PERMS) #warning This feature will probably not fit in DA14531.Please remove some other feature to include this in #endif #endif After those changes you can compile and run the project. The new AT commands: AT+ENPRMD : Enable pairing mode. This command will enable the pairing mode and any new device that can provide the correct pin will be able to pair and will be added to the bonding database. AT+DISPRMD : Disable pairing mode. This command will disable the pairing mode. Any device that is not previously bonded will be disconnected when trying to pair. Any device that is already in the bonding database will be able to connect seamlessly. The pairing mode is disabled by default when the device starts. AT+GETPRMD : Get the pairing mode status. This command will print the current status of the pairing mode to the console. Either a "ENABLED" or "DISABLED" string will be printed. An example sequence of commands would be the following: AT+SEC = 0 (enable secure connections), AT+PIN=123456 (set a passkey),AT+ENPRMD (enable pairing mode) - perform a connection and pairing with mobile phone A - AT+DISPRMD (disable pairing mode).Mobile phone A will be able to connect without issues. No other phone will be able to pair since a disconnection will occur immediately. On my side I tested it and it works as expected. Regarding the LED question: laxmi said: My second issue is i have one LED which iam used as connection status for the user, so i enabling LED GPIO using set_connection_indicator_output(true); in user_on_connection() function as shown below. but i notice that LED turning on in paring process. ideally LED should turn ON when user connected to the device. The BLE devices, first establish a connection and if any of the Peripheral or Central wants to implement a security scenario they will need to send a security request. When you have used the AT+SEC command, the Peripheral (DA14531MOD) will automatically send the security request when the connection is established. Best Regards, OV_Renesas