DA14531 ADVERTISEMENT WITH TIMEOUT

Question

How does the advertise with timeout function work? 
 static const struct default_handlers_configuration user_default_hnd_conf = { // Configure the advertise operation used by the default handlers // Possible values: // - DEF_ADV_FOREVER // - DEF_ADV_WITH_TIMEOUT .adv_scenario = DEF_ADV_WITH_TIMEOUT, 
 // Configure the advertise period in case of DEF_ADV_WITH_TIMEOUT. // It is measured in timer units (3 min). Use MS_TO_TIMERUNITS macro to convert // from milliseconds (ms) to timer units. .advertise_period = MS_TO_TIMERUNITS(5000), 
 
 I have defined the above configuration. Advertisement timeout shall happen after 5 seconds. 
 After the timeout, which callback shall get called? 
 I want to advertise for 5 seconds then have a timeout and go to deep sleep mode. Then upon pressing a GPIO, my dialog will wake up and restart advertising. How shall I do? 
 Which callback/function shall I put the button wakeup press function so that when I press SW2 in dialog board, my system wakes up? 
 When will the below callback function be called?

OV_Renesas · Accepted Answer

Hi Satakshi, Thank you for the reply. The Screenshot you shared shows that it took the DA14531 187ms to download the source code into SRAM. With the project I shared I was able to see a similar time between the Wake up controller interrupt and the DA14531 going back into Extended Sleep. 
 Satakshi_R said: After 10 seconds if I press SW2 again, it is advertising but why am I not able to scan it in my mobile phone? 
 I am only advertising for 5 seconds, and I am able to see my DA14531 advertising with the SmartBond App. Could you please test the project I shared on my previous answer? 
 Satakshi_R said: Also one more thing, if I am advertising continuously without any sleep mode implementation, then why is the average current constantly reducing? 
 If you want to measure the current measurement, you should enable the Power Profiler (Initialize-Start) after the FW has been downloaded into the DA14531. Ideally you should let the DA14531 for 2-10minutes running on the Power Profiler in order to see the Average Current Measurements. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Satakshi, Thank you for posting your question online. You can either use the DEF_ADV_WITH_TIMEOUT option as your adv_scenario or you can implement it with a timer yourself, please refer on this ticket: Advertising with timeout in loop - Bluetooth Low Energy - Wireless Connectivity - Renesas Engineering Community 
 Satakshi_R said: I have defined the above configuration. Advertisement timeout shall happen after 5 seconds. 
 After the timeout, which callback shall get called? 
 When you have set the DEF_ADV_WITH_TIMEOUT as your adv_scenario, the default advertise operation is going to call the app_easy_gap_undirected_advertise_with_timeout_start API: void default_advertise_operation(void)
{
 if (user_default_hnd_conf.adv_scenario == DEF_ADV_FOREVER)
 {
 app_easy_gap_undirected_advertise_start();
 }
 else if (user_default_hnd_conf.adv_scenario == DEF_ADV_WITH_TIMEOUT)
 {
 app_easy_gap_undirected_advertise_with_timeout_start(user_default_hnd_conf.advertise_period, adv_timeout_callback);	//static void (*adv_timeout_callback)(void)
 }
}

/**
 ****************************************************************************************
 * @brief Start advertising for undirected connection with timeout start.
 * @param[in] delay Delay of the timer
 * @param[in] timeout_callback Timeout callback function
 ****************************************************************************************
 */
void app_easy_gap_undirected_advertise_with_timeout_start(uint32_t delay, void (*timeout_callback)(void));

/**
 ****************************************************************************************
 * @brief Stop advertising with timeout stop.
 ****************************************************************************************
 */
void app_easy_gap_advertise_with_timeout_stop(void); After the period of advertising you had set has passed, then the app_easy_gap_advertise_stop_handler will be executed to terminate the advertising. After that one of the callback functions for advertising is going to be executed: .app_on_adv_nonconn_complete = NULL,
 .app_on_adv_undirect_complete = NULL,
 .app_on_adv_direct_complete = NULL, You will have to declare your own custom callback functions and work inside there. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Satakshi, Thank you for the reply. From the code snippet you shared I saw that you have commented out the app_easy_gap_advertise_stop API to stop the advertising. So you are not actually stopping the advertising, you are going straight into the Deep Sleep Mode. I would personally suggest to call the app_easy_gap_advertise_stop API and then do the Deep Sleep implementation inside the user_app_adv_undirect_complete custom callback function which is going to be executed after that. 
 Satakshi_R said: Is this correct, because my system is entering sleep mode after 10 seconds but when I press SW2, it is not waking up as I am not able to scan the device again. What could be the issue for the same? 
 Please refer on the ble_app_sleepmode example inside the SDK, it has the same functionalities as the one you want to do, but it has Extended Sleep Mode instead of Deep Sleep. If you are working with our Dev Kit Pro, you can also check the Power Profiler to make sure that the device is actually in Deep Sleep mode or Advertising. Inside the app_button_enable function, it is not necessary to call the if statement that checks the GPIO_GetPinStatus API. You can just configure the wake up controller for the GPIO you have configured in order to wake up the DA14531. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Satakshi, Thank you for the reply. Please find attached the ble_app_peripheral_adv_timeout_deep_sleep.zip file. I worked on SDK v6.0.18 with Dev Kit Pro and the DA14531MOD DB. I worked on a ble_app_peripheral example and I copied the Deep Sleep configuration from the prox_reporter example. After 5 seconds, the Advertising Stops and the DA14531 goes into Deep Sleep, then I press SW2 (P0_11) and I wake up the device, it automatically starts advertising for another 5 seconds and goes to Deep Sleep again. Please see the screenshots captured from the Power Profiler: It works on my side as expected. Please share any feedback. ble_app_peripheral_adv_timeout_deep_sleep.zip Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Satakshi, Thank you for the reply. 
 Satakshi_R said: When I remove the shorted J9 jumper, the blue LED goes off in the dev kit pro. After that, I start measuring it but it shows 0 in mA mode also and uA mode also. Is there any additional step I should do in smart snippets toolbox ? 
 Yes, the blue LED shows that the current circuit is active for the SmartSnippets Toolbox. No you would not need any other steps on the SmartSnippets Toolbox to measure the current consumption. Regarding the OTP: Are you able to see your device advertising or scanning? Please refer on the AN-B-072 , on section 10. Boot from OTP, on page:22 and on section 4.Booting Sequence and Booting Pins Best Regards, OV_Renesas