Extended sleep mode disable/re-enable

我设置了默认值_operation_adv = NULL, rather than user_app_adv_start as all the other examples did. Once its put back to user_app_adv_start then it works fine in the flash while the advertising is running. If I wait until the advertising is complete to press the button then it again does the freezing. Based on the current consumption when it freezes, it looks like its not actually in extended_sleep mode, and actually still in active mode, just stuck somewhere.

你有什么想法是否为什么？从我的角度来看，所有这些都改变了它在开始时的广告，但它似乎影响不仅仅是那样的。

该模块在ext_sleep_mode中配置withoutOTP copy, user_app_init is used as the .app_on_init, and the wakeup controller is configured to use a GPIO as the wakeup from the button. When the chip wakes up it does not start advertising, because I have purposedly removed that aspect. The user_app_adv_start() callback is only called when someone holds the button for 10 seconds.

我可以使用GPIO触发器从睡眠中唤醒它。一旦它醒来，除非是启用广告，否则将在3-4秒后冻结，除非是广告，在这种情况下，一切都将正常工作。

The problem with running in debug mode is that everything works fine in debug mode, but not when running from the flash.

一世understand the aspect of default_operation_adv = user_app_adv_start automatically starting the advertising at the beginning. Im just not sure why that seems to change the behavior of the code in terms of getting frozen after the defined period, versus working as expected.

就它类似的基本项目而言，它将是睡眠模式的User_Peripheral one和代理一个的组合。

The code also works fine if I use the app_easy_timer() instead of setting up the timer0 as the counter. I know the timer0 is disabled in extended sleep mode but im using arch_disable_sleep() upon wakeup from the button so I dont see why that would be a problem.

在从按钮唤醒时，定时器完全重新初始化/配置，因此它似乎是正确的，但在一段时间后，代码只是停止。

Edit: This time from button wakeup until freeze is 2.7 seconds, very consistently. And its definately not sleeping, the run current goes up from 200uA to 300uA when the freeze occurs.

当使用闪光灯启动时，当我没有按下按钮或在广告中占用时，设备肯定会睡觉，睡眠电流下降到〜10ua。

我正在使用printf，以确定它被冻结。按下按钮后，禁用睡眠状态，并启动Timer0并每100ms生成中断。所有中断处理程序都已打印递增索引。递增索引工作2.7秒，直到它只是停止，这就是我知道它在2.7秒后始终冻结。

这是或多或少地得到解决。一世don't exactly know why it was freezing after the 2.7 seconds, or why it was working when advertising is enabled, but it works properly now when I've removed the

if（arch_ble_ext_wakeup_get（）））in the button press callback. I think it's in the example projects because the button starts the advertising, and it only evaluates true when the advertising is complete. So for my project it makes sense for it to not be there.

WDOG未在配置文件中定义，但那些时间似乎太接近是巧合。定义了CFG_DEVELINMENT_DEBUG。从Flash运行时出现此问题，并发生调试器是否已连接。

So I tried enabling the watchdog and that seems to solve it also, rather than removing the check on the arch_ble_ext_wakeup_get in the wakeup callback. I'll summarize the combinations here for people:

如果你有

if（arch_ble_ext_wakeup_get（）））
{
ARCH_BLE_FORCE_WAKEUP（）;
arch_ble_ext_wakeup_off();
app_easy_wakeup（）;
}

And you want to disable sleep for some period, then re-enable sleep at some later point, then the watchdog must be enabled. Otherwise after waking the code will freeze after the watchdog timeout, still not sure why exactly. There's also the case when advertising is enabled then it will work while the device is advertising, then will freeze again when finished, therefore with infinite advertising you dont see this problem.