Arch_ble_ext_WakeUp_on的目的是什么？

你好，
We are using SDK 5.0.4 and I was looking at the user_sleepmode example.
它看起来像程序侦听到两个案例中的按钮单击中断。

第一种情况是在连接期间。开始听，user_app_set_button_event.is called and executes:

wkupct_register_callback（user_app_button_press_cb）;
wkupct_enable_irq(WKUPCT_PIN_SELECT(GPIO_BUTTON_PORT, GPIO_BUTTON_PIN),
wkupct_pin_polarity（gpio_button_port，gpio_button_pin，next_event），//极性
1, // 1 event
10）;

并且倾听是停止的user_app_disable_buttonwhich callswkupct_disable_irq（）;。
聆听回调（user_app_button_press_cb.) also callsuser_app_set_button_event.要保持按钮单击按钮（实际上它侦听在按钮模式下切换，通过选择右“Next_Event”）。

The second case is when the program stops advertising (after 10 seconds). Whenuser_app_add_undirect_complete.被称为状态GAP_ERR_CANCELED.(i.e. it's a deliberate adv-stop) it calls:

arch_ble_ext_wakeup_on();
//配置唤醒按钮
app_button_enable();


的目的arch_ble_ext_wakeup_onis:"Puts the BLE core to permanent sleep. Only an external event can wake it up."。它只是将内部标志设置为true。
然后，app_button_enable呼叫：

app_easy_wakeup._set(app_wakeup_cb);
wkupct_register_callback(app_button_press_cb);
wkupct_enable_irq（wkupct_pin_select（gpio_button_port，gpio_button_pin），//选择pin（gpio_button_port，gpio_button_pin）
WKUPCT_PIN_POLARITY(GPIO_BUTTON_PORT, GPIO_BUTTON_PIN, WKUPCT_PIN_POLARITY_LOW), // polarity low
1, // 1 event
40);


即它拯救了app_wakeup_cb除了将来召唤app_easy_wakeup.，并对第一种情况运行类似的代码，以便开始侦听按钮中断。
When the interrupt occurs,app_button_press_cb.is called and executes:

if（getBits16（sys_stat_reg，per_is_down））
{
periph_init();
}
。。。

如果我理解正确，在深度睡眠期间必须在外部唤醒中调用此代码（在使用延长睡眠时调用它是有害的吗？）。
然后，App_Button_Press_CB继续调用：

if (arch_ble_ext_wakeup_get())
{
arch_set_sleep_mode(app_default_sleep_mode);
arch_ble_force_wakeup();
ARCH_BLE_EXT_WAKEUP_OFF（）;
app_easy_wakeup（）;
}

i.e. it checks that the external-wakeup-flag is on, initializes the sleep-mode (app_default_sleep_mode is deep-sleep), wakes up the BLE, turn off the external-wakeup flag (i.e. timers and BLE events can now wake up too) and callsapp_easy_wakeup（）（呼叫app_wakeup_cb正如我之前解释的那样）。

第二种情况下机制有哪些优点？我们可以避免呼唤arch_ble_ext_wakeup_on()and then we won't have to re-configure the sleep mode and re-wake the BLE. What's the point of callingarch_ble_ext_wakeup_on()如果程序没有任何定时器并且不通告（即，定时器和BLE事件无法唤醒该程序anyways- so only an external-wakeup can).

如果我们使用，该计划会在深睡眠期间消耗更少的电力arch_ble_ext_wakeup_on?

How comes the second case never callswkupct_disable_irq（）? Does going to sleep afterarch_ble_ext_wakeup_onmeans that you don't have to callwkupct_disable_irq（）after you wake up?

Thanks,
Oren Zomer