Sleep Mode

Hi GAK,

Could you please clarify what you mean with the “next 2^nd和每一个”?如果我可以理解正确地摇来摇去m what you mention, your device be default start advertising (step 1), and if the button is pressed, stops advertising and it goes into sleep mode (step 2). Both step 1 and step 2 are fully functional, is that correct? But if you are pressing continuously the button in the step 2, the device enters the sleep mode but the WKUP controller is triggered? Could you please provide me the configurations in step 2 and 3? Something is triggering the wake the controller up and the DA1580 wakes up.

Thanks, PM_Dialog

Hi GAK,

Something is getting wrong with the interrupts and when wakes up the GPIO interrupt is triggered as well, so your application code returns to step2. Let me ask you something first. In the user_app_adv_start(), why are you still using the app_easy_timer() timer? Upon the timer expiration the adv_data_update_timer_cb() will be triggered. I am not aware if this is your whole project, but in ble_app_sleemode example of the sdk, when the adv_data_update_timer_cb() the advertising is going to be stopped. I am trying to test you code and create a short demo for you. I will get back to you shortly. Both the WKUP and GPIO interrupts should be active low, correct?

Thanks, PM_Dialog

Hi GAK,

I created a short dame code demonstrating how to use the SW3 in order to stop advertising and then wake up. I use only the wake-up controller and not the IRQ, because if you are using any of the sleep modes the IRQ will not be detected. Please find attached the configurations of the wake-up controller. The wkup_flag should be stored into the retention RAM in order to retain the value when going to sleep. Except from the configurations of the wake-up controller you should do the following modifications in the ble_app_sleepmode example of the SDK:

• Initialize the wkup_flag to false into the user_app_init()
• In user_app_adv_start() remove the app_easy_timer() and call the app_button_enable();

All the other should be as in default ble_app_sleepmode example of the SDK.

Thanks, PM_Dialog

Hi GAK,

If you are using extended sleep mode between the advertising intervals, you can only detect the interrupt through the wake up controller. Is there any specific reason you want to use the IRQ and not the wake up controller?

Thanks, PM_Dialog

Hi GAK,

Apologies for the delay. DO you have any specific reason to use the IRQ for step #2? The device enters the sleep mode between the connection intervals, so you might miss the interrupt. Why don’t you implement it with the wake-up controller as I suggested you?

Thanks, PM_Dialog

Hi GAK,

Could you please try to provide me more clarifications regarding your last question? What do you mean with the sleep mode in the ble-app_peripheral example? If you would like to enter the sleep mode between the advertising or connection intervals, you could use the either arch_set_deep_sleep() in case of deep sleep or arch_set_extended_sleep() in case of extended sleep in user_app_adv_start, as it is implemented in ble_app_sleepmode example of the SDK. Also, you should change the app_default_sleep_mode configuration in user_config.h header file.

Thanks, PM_Dialog

Hi GAK,

When you disconnect the DA14580 from a peer device, the user_app_disconnect() will be triggered. So, you will have to configure the DA14580 into the extended sleep mode inside this function.

Thanks, PM_Dialog