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\ U sleep\ U模式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.

I 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.

就一个与之类似的基本项目而言，它将是用户/外围设备项目和睡眠模式的代理项目的组合。

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.

当使用flash启动时，设备肯定会进入睡眠状态当我没有按下按钮或在广告之间时，睡眠电流会下降到~10uA。

我使用printf来确定它是否冻结了。当按下该按钮时，睡眠被禁用，计时器0被启动并每100ms生成一个中断。中断处理程序所做的只是打印一个递增索引。递增索引工作2.7秒，直到它停止，这就是为什么我知道它在2.7秒后会一直冻结。

这是或多或少地得到解决。I 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\u ble\u ext\u wakeup\u 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\u DEVELOPMENT\u 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\u ble\u ext\u wakeup\u get（））
{
拱力唤醒（）；
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.